Build or buy? A Gulf SME owner’s guide to choosing between a ready SaaS and a custom system

We get this question weekly from restaurant, salon, store and shipping owners: “I have a ready system on a monthly subscription — should I build my own?”. The honest answer from a company that sells both — SaaS products like Cash Salon, TtaKkaa POS and WhatsApp Suite, and custom systems for dozens of clients — is: it depends on three questions, not on the budget.

Question 1: is your process ordinary, or is it your competitive edge?

Salon bookings, the restaurant cashier, sending WhatsApp — ordinary processes thousands like you run. Buy. But if what sets you apart is how you price, a matching algorithm, or an operational flow unlike anyone else’s — that is what you build, because you will not find it ready, and if you do, your competitor will too.

Question 2: how much does it cost you to change your mind?

• Subscription: cheap to enter, expensive to leave if it locks your data. Ask before signing: can I export everything tomorrow?
• Custom: expensive to enter, and you own everything after. But ownership means maintenance — who updates e-invoicing when the authority changes its standard?

Question 3: what is your size in three years?

One branch: buy. Ten branches with unified data, custom reports and integrations with your finance system: start with the subscription, and plan to build when the monthly fees exceed the instalment of a system you own.

The practical rule: buy what is common, build what is distinctive, and make sure what you bought is replaceable.

The third option nobody mentions: build on a product

What works best with our clients: a ready SaaS as the base (cashier, bookings, WhatsApp) + a custom layer on top (your reports, your integrations, your flow). TtaKkaa, for example, serves hundreds of stores as a subscription, and some large chains get custom modules on the same core. You pay only for what makes you different.

The numbers we ask the client to compute

1. Monthly subscription × 36 months + the cost of time lost “working around” what the system does not do.
2. Build cost + 15–20% per year maintenance and development + hosting.
3. The value of what you will do with the data once you own it (reports, AI, pricing).

When (1) exceeds (2) minus (3) within three years, build. Otherwise buy, and sleep well.

The mistakes we see

• Building a cashier system from scratch “because it is cheaper long term”, then discovering that e-invoicing alone is a project.
• Subscribing to a foreign system that understands neither Arabic, ZATCA nor WhatsApp, then paying double its price for integrations.
• Confusing “custom” with “from scratch”: good custom software is built on mature frameworks and components; it does not reinvent login.

Bottom line

It is not a battle between subscription and custom; it is a sequence. Start with what is ready, learn exactly where you choke, and build only there. And whoever sells you both honestly will sometimes tell you: “don’t build yet”.