This article is for one specific reader. You run a contracting, trading or services company, and your team built a process that works better than anything on the market. Maybe it is how you track subcontractor variations, or how you quote and chase supplier deliveries. Competitors have asked how you do it, and you are wondering whether to sell it as software. By the end you will know what drives the price, how to compare the quotes on your desk, and whether to build now or wait.
Where you probably are right now
The process lives in a heavily customised Excel file, a shared drive and a WhatsApp group. One person on your team understands all of it. You have collected three quotes: one from a freelancer, one from a local agency and one from a firm with a glossy deck. The highest is several times the lowest, and they cannot all be describing the same product.
Mostly they are not. The cheap quote is usually a single-company tool with a login screen. The expensive one often includes features you will not need until you have dozens of customers. The useful question is not which number is right, but what each supplier assumed you were buying.
What actually drives the cost
SaaS differs from an internal tool in a few expensive ways, and each one is a line you should see in any serious quote.
Multi-company data separation. This is the line that makes it SaaS rather than a shared spreadsheet. Many separate companies use the same system, and none of them may ever see another's data. It has to be designed in from the first day, because adding it later usually means rebuilding the core.
Roles and permissions. Inside your company, everyone trusts everyone. Your customers will want site engineers who can log progress but not see rates, and finance staff who approve but cannot edit. Each extra role multiplies the screens and rules that need building and testing.
Billing. Sign-up, subscriptions, upgrades, failed card payments and VAT-compliant invoices carrying your TRN all have to run without anyone chasing them. Local payment gateways each have their own onboarding steps, settlement timelines and fees. Choosing one early avoids rebuilding billing later.
Integrations. Your customers already use accounting software, email and WhatsApp. Every connection you promise is real engineering, plus ongoing upkeep whenever the other system changes. Start with the one integration most customers ask for, not all of them.
Arabic. A proper right-to-left interface is not a translated English one. It means extra front-end work, because layouts, tables and forms have to mirror correctly, and extra testing, because every screen and every generated invoice or report has to be checked in both directions. Planning for it at the start is far cheaper than retrofitting it.
Security. Once real company data goes in, you need backups that are actually tested, monitoring, access logs and a proper security review before launch. Customers in contracting and trading will ask about this before they sign, often in a procurement questionnaire.
Ongoing support. This is where first-time founders underestimate most. Hosting is the smaller part. The larger part is people: someone has to fix bugs, apply security updates and answer the customer whose upload failed during month-end close. It is less exciting than new features, and it is what keeps your first customers renewing.
How to compare quotes that look nothing alike
Write a one-page scope first: who the customer is, what they do on day one, which of the seven drivers above are in the first version and which are deferred. Send the same page to every supplier and ask them to price against it line by line. Quotes that refuse to break down by line are telling you something.
Then put the answers side by side on these points:
- Data separation: how each customer's data is kept apart, and whether it is in the first version.
- Billing: which payment gateway, and whether VAT invoices are generated automatically.
- Arabic: full right-to-left interface, or translated labels only.
- Security: what testing happens before launch, and how backups are restored.
- After launch: who hosts, who monitors, what support covers and how quickly they respond.
- Ownership: whether you own the code and can move it to another team.
- Change requests: how they are priced once building starts, because they will happen.
The cheapest quote is rarely the cheapest outcome. A build that cannot separate customer data has to be rewritten the moment your second client signs, so you pay twice and lose the time in between. A well-scoped middle quote usually costs more upfront and much less across the life of the product.
The tradeoffs nobody puts in the proposal
The biggest risk is not the build cost. It is building the wrong thing well. A process that works inside your company often depends on habits your customers do not share. Before committing serious money, get three companies to agree, in writing, to pay for a pilot.
A letter of intent costs you nothing, and it tells you more than any market report. If you cannot get three, that is the answer, and it was free.
There is also the opportunity cost to your own business. A SaaS product needs an owner who can spend real hours on it every week, especially early on. If your contracting or trading operation needs you full-time, the software will drift.
Sometimes the right answer is to wait. If your process still changes every quarter, keep it in Excel and automate the painful parts until it settles. The software will be cheaper to build once the process stops moving.
Do it yourself, or bring someone in
If you mainly want to test whether people will pay, you can do a lot yourself. Build a no-code prototype, set up a simple landing page, and sell manually to your first two customers with your existing spreadsheet running behind the scenes. That costs very little and settles the demand question before any real money is spent.
If you already have paying interest and the process is stable, this is specialist work for a small team that has built multi-company systems before. Look for a partner that will also host and support the product after launch, because the handover between builders and maintainers is where many SaaS products start to decay. Hadiati works this way: it builds the platform and then runs the hosting, monitoring and support, so one team is accountable from first sketch to first renewal.
Questions owners ask
What drives SaaS development cost in the UAE? Seven things drive most of it: keeping each customer company's data separate, user roles and permissions, automated billing with VAT-compliant invoices, integrations with the tools customers already use, a proper Arabic right-to-left interface, security and backups, and ongoing support after launch. The number of screens matters far less than these.
Why are SaaS quotes so far apart? Each quote assumes a different product. A low quote is often a single-company tool with a login screen, while a high quote often includes features needed only at a much larger scale. Ask every supplier to price the same written scope, line by line, before comparing.
What ongoing costs come after launch? Cloud hosting, monitoring, security updates, bug fixes and customer support. The people cost is usually larger than the hosting bill, and it is what keeps first customers renewing.
Should I build SaaS from my internal process now or wait? Build when the process is stable and at least a few outside companies have committed in writing to pay for a pilot. If it still changes often, keep it in Excel, automate the painful steps, and build once it settles.
If you would like to talk through your own idea, email hello@hadiati.ae and bring your one-page scope if you have it.