Custom software development / Saudi Arabia & the GCC
Custom software, built around the way your company works.
Quotations, approvals, orders, records and reports in one system for your team and your customers, on web and mobile. The scope, price and timeline are agreed in writing first, and the code and data are yours.
When you need custom software
Your work has outgrown spreadsheets, chats and software made for someone else.
- 01
Quotations are typed into a spreadsheet and sent as screenshots.
Every order is written again for the supplier, and mistakes copy along with it.
- 02
Approvals wait in someone's chat history.
Nobody can see where a request is, or who moved it last.
- 03
You pay for an off-the-shelf system and work around it.
Half its screens are unused, and the step you need most is missing.
- 04
The Arabic is a translation.
Your team and customers notice it on the first screen.
- 05
Reports are rebuilt by hand every month.
The numbers exist, but in five places that do not agree.
- 06
Customers or partners need their own access.
Each should see their own requests, and nothing else.
Systems we have built
Software for the people doing the work, and the people managing it.
01Several roles, one system.
Oxygen Academy serves students, instructors and ambassadors, each with their own portal, tools and earnings, on the same platform.
- Separate portals for each role
- Payouts and commissions tracked
- Arabic first
02A dashboard for the business side.
The merchant side of T-CODE: branches, offers, views, followers, used codes and conversion in one view.
- Branches managed separately
- Live figures, no manual reports
- Works on the phone
03Requests that move in clear steps.
The law office side of AlMizan: new requests, active consultations, response rate and average response time.
- Every request has a status
- In-app chat with the customer
- Performance in one view
Some screens show demo data.
One quotation, before and after
What changes when the work moves into its own system.
Based on a system we built for a steel supplier in Oman.
Before
- The quotation is typed by hand into a spreadsheet.
- A screenshot of it is sent to the customer on WhatsApp.
- The order to the supplier is written again from the start.
- Acceptance, delivery and payment are followed from memory and chat history.
With the system
- The quotation is prepared on the phone in four steps: customer, items, delivery site and review.
- Enter tons, pieces or an amount, and the system calculates the other two and the total with tax.
- Two documents are issued at once: a quotation for the customer with prices, and a supply order for the mill without them.
- Both are sent from the company's WhatsApp number, and the system shows when they are delivered and read.
- Every job moves from draft to paid in clear steps, and the outstanding balance updates itself.
What we build
The parts a business system needs, chosen for your workflow.
- 01
Workflows and approvals
Each request moves through your steps, with who approved it and when.
- 02
Quotations and invoices
Documents with your branding and the tax calculated, ready to send.
- 03
Orders and operations
Orders, deliveries, bookings or service jobs, followed from start to finish.
- 04
Customers and records
One record for each customer, supplier or employee, with the full history.
- 05
Roles and permissions
Each person sees the screens and data their role needs.
- 06
Dashboards and reports
Live figures and exports to PDF or Excel, without rebuilding them by hand.
- 07
Customer and partner portals
Outside users follow their own requests, quotes and documents.
- 08
Integrations
Connections to WhatsApp, payments and the tools you already use, where they allow it.
- 09
Web and mobile
A web system for the office, an app for the field, or both on one backend.
- 10
AI where it removes work
Drafts, search and summaries, each with a source and a limit.
Your data, your system
A system your company depends on has to be safe and stay yours.
- Each user reaches only what their role allows, enforced in the database.
- Every step is recorded with who moved it and when.
- Files are stored privately and open through links that expire.
- Keys to payment and AI services stay on the server, never in the browser or the app.
- Personal data is handled with Saudi Arabia's Personal Data Protection Law in mind from the first design.
- The source code, the accounts and the data are registered in your name.
What you receive in writing before we start
- 01
The scope
The workflow, screens, roles and integrations, and what is left out.
- 02
The price
A written price for the agreed scope, before development starts.
- 03
The timeline
The delivery plan, confirmed in the same document.
From our work
Systems we have built for government, healthcare procurement and education.
Each one replaced a process that lived in paper, spreadsheets or chats.
CareerFolio
Performance portfolios for Ministry of Education employees: goals, evaluations, print-ready reports with official branding, and finished years locked as read-only archives.
View the project
WOSTA
Healthcare procurement: clinics and pharmacies post the supplies they need, verified suppliers compete with quotes, and branches, warehouses, quotes and invoices are tracked in one place.
View the projectA legal case workspace
For legal teams in Saudi Arabia: matters, private files, grounded research, drafting, signatures and PDF export, with each team's work kept apart.
Some screens show demo data.
Where it fits
Any company whose workflow does not fit ready-made software.
Trading and supply
Quotations, supply orders, deliveries and balances.
Healthcare and procurement
Requests, quotes, suppliers and invoices.
Government and HR
Employee records, evaluations and official reports.
Education and training
Students, instructors, courses and payouts.
Legal and professional services
Matters, requests, documents and response times.
Retail and services
Branches, offers, bookings and customer records.
An honest comparison
Spreadsheets and chats, ready-made software, or a system built for your company.
| Spreadsheets and WhatsApp | Ready-made software or ERP | Custom software with FLUIDS | |
|---|---|---|---|
| Fits your workflow | You adapt to the file | You adapt to its modules | Built around your steps |
| Arabic, right to left | As you type it | Varies by product | Designed Arabic first |
| Who sees what | Anyone with the file | The product's role settings | Roles you define |
| How you pay | Little money, a lot of time | Usually licences per user, every year | A build you own; hosting and support as agreed |
| Who owns it | You, but it is scattered | You rent it | You, code and data |
| Time to start | Today | Soon, if it fits | After a written scope |
When we will tell you not to build one
- If a ready-made product already covers your workflow, use it. Custom software is for the steps it cannot do.
- If the process is not settled yet, map it first. A workflow session does that before any code.
- If a spreadsheet template solves it, start with the template.
When the work depends on steps no product has, the software should be built around those steps.
How we build it
From the way you work today to a system your team uses.
- 01
Map the workflow
We go through each step, who does it, and where it breaks today.
- 02
Agree the scope
You receive the scope, price and timeline in writing before any work starts.
- 03
Design and build
Review the screens, then try the system as it is built.
- 04
Launch and hand over
We test and launch it, hand over the source code, and agree the support you need.
Questions
What companies ask before they commission a system.
What is custom software?
Software designed and built for one company's workflow, instead of a ready-made product the company adapts to. It can be a web system, a mobile app, or both on one backend.
Should we use an ERP like Odoo or SAP instead?
If a ready-made system covers your workflow, yes. Custom software makes sense for the steps it cannot handle, or when the licences and workarounds cost more than the work they save.
Can it connect to the systems we already use?
Yes, where the other system allows it, for example through an API or an export. Each integration is listed in the written scope.
Web, mobile, or both?
It depends on where the work happens. Office work usually suits a web system, field work an app, and many systems use both on the same backend.
Can it be in Arabic and English?
Yes. It is designed Arabic first and right to left, with English in the same system when you need it.
Who owns the system?
You do. The source code, the accounts and the data are registered in your name, and you receive the full source code at handover.
Do you work with companies outside Al-Khobar?
Yes. We are based in Al-Khobar and build for companies across Saudi Arabia and the Gulf, and several of the apps we have built run in Oman.
How much does it cost, and how long does it take?
It depends on the workflow, the number of roles and screens, and the integrations. After mapping the workflow, you receive a written scope with the price and timeline before any work starts.
What happens after launch?
We agree the maintenance and support your system needs as part of the engagement. New steps and features can follow as separate phases.
Start with the step that costs your team the most time.
Tell us how the work runs today, who is involved and where it breaks. We review it and send a written scope with the price and timeline.
Discuss your system