Every few months a client comes to me having already paid for a SaaS subscription — QuickBooks, Square, Zoho, take your pick — and needing help because it "doesn't quite work" for their operation. The problem is almost always the same. The platform was designed for a different market, a different regulatory environment, and a different set of assumptions about how a business operates.

The currency problem

Zimbabwe's economy runs on multiple currencies simultaneously. You might invoice in USD, receive payment in ZiG, and report to ZIMRA in whatever the current directive specifies. Generic accounting software assumes one functional currency. It assumes exchange rates are stable. It doesn't know what an SI rate is, and it certainly doesn't know about the parallel market.

Every month my clients spend hours manually adjusting figures that should be calculated automatically. That's not a user error — it's a product mismatch.

Compliance is local by definition

ZIMRA fiscal requirements, POTRAZ reporting, medical aid society claim formats, local authority levy structures — none of these exist in the knowledge base of a San Francisco software team. By the time a large SaaS vendor adds support for Zimbabwean compliance (if ever), the regulations will have changed twice.

Custom software can be updated in a day when ZIMRA changes the VAT rate or a medical aid releases a new tariff schedule. A SaaS platform requires a support ticket, a product backlog entry, and quarters of waiting.

Connectivity assumptions

Most SaaS platforms assume always-on, high-speed internet. The restaurant in Harare CBD might have fibre. The same chain's branch in Mutare or Masvingo might be on LTE with unpredictable uptime. A cloud-only POS that goes offline at peak dinner service is a liability, not an asset.

Every system I build has an offline-first consideration baked in from the start — local session storage, queued transactions, grace windows for sync.

The actual cost comparison

A $150/month SaaS subscription sounds affordable. Over three years that's $5,400 — and you own nothing. You cannot modify the workflow. You cannot add a feature. You cannot export your data in a useful format when you decide to leave.

A custom system built for $4,000–$8,000 one-time is cheaper over three years, fits your exact workflow, and you own every line of code. When your business grows or changes, you pay for an update — not for the privilege of staying on a plan tier.

Software that costs money every month but doesn't fit your workflow isn't an asset. It's a recurring liability you're renting.

Where SaaS does make sense

I'm not anti-SaaS as a category. For email hosting, cloud storage, payment gateways, and communication tools — use them. The infrastructure layer doesn't need to be custom. But the operational software that runs your business, touches your data, and defines your workflow? That should fit you precisely.

If your team spends more than an hour a week working around a tool's limitations, it's time to talk about building something that works for you instead. Let's have that conversation.