Build vs. Buy: How Saudi SMEs Should Decide on Software

Sooner or later every growing business asks it: do we buy software off the shelf, or build our own? I’ve done plenty of both — straightforward Odoo deployments on one end, fully custom platforms in Laravel, Python, and TypeScript on the other — and I’ve never found the answer to be “always build” or “always buy.” It’s about knowing which one fits which problem.

Here’s how I think it through.

Default to buying

For anything that isn’t your competitive edge, buy. Accounting, payroll, email, generic CRM, project management — these are solved problems with mature, affordable products. Building your own version is a slow, expensive way to reinvent something you can subscribe to today.

The test is simple: does this process make you different from your competitors? If the honest answer is no, buy it and move on. Your engineering time is too valuable to spend rebuilding a commodity.

Build where you’re genuinely different

Now the other side. There are four situations where building earns its cost.

1. The workflow is your edge. If a process is core to how you compete and no product fits it, forcing your business into off-the-shelf software means giving up the very thing that makes you good. This is where custom pays off. The Mawan ERP was custom for exactly this reason — a multi-branch operation that no standard package modeled well.

2. Nothing actually fits. Sometimes you evaluate every option and they’re all 70% right and 30% painful. The 30% is where you’ll live every day. A custom build around your real workflow can be cheaper over time than fighting a tool that almost works.

3. Integration is the hard part. When the value is in connecting systems — POS to inventory to finance to compliance — the glue is often custom even when the endpoints are bought. This is most of the real work in digital transformation.

4. The SaaS math flips. Per-seat pricing is cheap for a small team and brutal at scale. If you’re paying for hundreds of seats on a tool that does one thing, owning that software can become the cheaper option. Run the numbers across a three-year horizon, not a monthly one.

The ZATCA factor

In Saudi Arabia there’s an extra constraint: ZATCA Phase 2 e-invoicing requires real-time integration with the FATOORA platform. Whatever you choose has to either support this natively or let you add it.

This quietly rules out closed tools that can’t be extended, and it’s one reason Odoo is popular here — it’s off-the-shelf but open enough to integrate compliance into. The practical lesson: factor compliance into the decision early, not after you’ve committed.

Most businesses land on hybrid

In practice, the answer is rarely all-or-nothing. The pattern I see work best for Saudi SMEs:

• Buy the commodity layer — finance, HR, communications.
• Build the thin layer that makes you different — your unusual workflow, your integrations.
• Integrate so the two behave like one system to the people using them.

This gives you the speed and reliability of proven tools where it doesn’t matter, and full control where it does.

A simple way to decide

For any piece of software you’re weighing, ask in order:

1. Is this our competitive edge? → If no, buy.
2. Does a real product fit our actual workflow? → If yes, buy.
3. Will per-seat cost outgrow ownership at our scale? → If yes, consider building.
4. Does it need deep integration or ZATCA compliance? → Plan for custom glue either way.

If you’re facing this decision and want help running the numbers honestly — without a vendor’s incentive to push you one way — get in touch. I’ll tell you what I’d actually do.