Most growing companies do not have a software shortage.
They have a handoff problem.
An order arrives by email. Someone copies it into a spreadsheet. Someone else checks stock in another system. Purchasing gets a WhatsApp. The customer gets a manual update. Accounting gets the same numbers typed again. That is not five jobs. That is one workflow with bad seams.
If that sounds familiar in Manchester, Melbourne or Auckland, you are not behind. You are normal. The usual next move — buy another SaaS login — often makes the seam worse, because the new tool still has to talk to the old ones, and the person who still talks to both is still you.
Symentic Technologies builds custom operations software for SMEs in the UK, Australia and New Zealand. We also run two live SaaS platforms of our own, so we know what production systems feel like when they break on a Friday. This post is not a pitch for replacing everything you already pay for. It is a way to count the handoffs, decide which ones are worth deleting, and know when a thin custom spine beats another subscription.
What a handoff actually is
A handoff is any moment where work leaves one place and has to be re-created in another before the next step can start.
Typical ones in an operational SME:
- Email or WhatsApp → spreadsheet
- Spreadsheet → stock / warehouse tool
- Stock shortfall → purchase order (often another sheet or supplier portal)
- Status change → customer update (manual)
- Confirmed order → accounting package (re-typed)
- Dashboard request → someone who "knows how it all fits"
Each handoff has a cost that never appears on a pricing page:
- Time — re-keying, chasing, reconciling
- Error — the number that was right in one system and wrong in the next
- Latency — the customer finds out about a back-order when they chase
- Key-person risk — holidays become an operational incident
Bought software is often excellent at its own job. The handoff is what happens between jobs. That gap is where growing businesses quietly hire people to be the integration layer.
Why another SaaS login usually fails first
SaaS products are designed around a standard process for a market. Your business is designed around how you win work.
When the fit is close, buy the product and stop thinking about it. Payroll, email and core accounting are good examples. When the fit is not close, you get one of three outcomes:
- You bend the process to the product — and lose the way you compete (special pricing, odd fulfilment, customer-specific terms).
- You bend the product with configuration — until upgrades become scary and nobody will touch the settings.
- You keep the product and keep the spreadsheet — which means you paid for a login and kept the handoff.
The third outcome is the most common. It looks like progress on the credit card statement. It does not look like progress on Friday afternoon.
We wrote the longer version of buy / configure / integrate / build here: You already built custom software. It's a spreadsheet.. This post starts one step earlier: count the handoffs before you shop.
Count the handoffs on one real order
Pick one order, job or request from last week. Not a happy-path example. A normal messy one.
Write every place it touched:
| Step | Where it lived | Who moved it | What could go wrong |
|---|---|---|---|
| 1 | Email inbox | Ops coordinator | Missed attachment / wrong customer |
| 2 | Shared spreadsheet | Same person | Version conflict / stale stock |
| 3 | Warehouse system | Warehouse lead | Allocation vs actual stock |
| 4 | Supplier email / portal | Purchasing | PO never raised |
| 5 | Customer WhatsApp | Account manager | Late bad news |
| 6 | Xero / MYOB / QuickBooks | Finance | Invoice mismatch |
If you need more than four rows for a single order, you do not primarily have a "we need better software" problem. You have a seam problem.
Do the same exercise for Australia and New Zealand stacks you actually use: MYOB or Xero instead of Sage, local carriers, local payment rails. The tools change. The handoff pattern does not.
When Zapier or Make is enough
Not every seam needs a build. No-code and low-code connectors are the right answer when:
- Both systems have decent, documented connectors
- The flow is short and mostly trigger → action
- Volume is modest and per-task pricing is not the story of your month
- Failure is annoying, not expensive (a missed marketing sync is not a double shipment)
- A non-engineer on your team can understand and fix the scenario
Use them. We will tell prospects to keep Zapier or Make when that is the honest answer. Buying custom work to replace a healthy two-step sync is how budgets get wasted.
Reach past no-code when several of these are true at once:
- The flow touches money, stock, allocations or customer promises
- You need idempotency (re-running must not double-charge or double-order)
- A system in the middle has no usable connector (legacy SQL, file drop, awkward portal)
- Approvals and exceptions are the product, not the edge case
- You want to own the join the way you own the rest of the operation — not rent it on a task meter
That is where a custom operations layer earns its place: not as "another app", but as the spine that holds the apps you keep.
What a custom operations system actually is
Strip the buzzwords. For most operational SMEs it is a system that:
- Captures the work once (order, job, request)
- Applies your rules (pricing, terms, permissions, approvals)
- Checks the live facts (stock, capacity, credit)
- Hands only human decisions to humans
- Pushes clean results into the tools you keep (especially accounting)
- Shows status without asking the person who "knows"
For wholesale and distribution, that often means order → stock → purchase order → customer update in one path, with accounting left alone and integrated. We spelled that pattern out on the wholesale operations page.
For operational service businesses, the nouns change (job, tech, site visit) and the shape stays the same: one record of truth, fewer re-keys, approvals where a person should decide.
It is usually not a rewrite of your entire stack. It is the missing middle that stops your team being the middleware.
Phases beat a leap
A useful first version is smaller than most people expect.
Typical phased path for an ops build:
- Orders / jobs + customers + dashboard — delete the most painful re-keying
- Purchasing or scheduling — only after phase one is used for real
- Inventory or capacity — once the order book is trustworthy
- Email / AI capture — only where a person still checks before commit
Initial focused builds for this kind of work are often measured in weeks, not quarters, when the brief is sharp. We work fixed scope per phase, with something usable at the end of each one, and you own the code. Optional care plans cover hosting and ongoing change; they are not a hostage clause.
If the brief is still "something like a portal, mobile would be good", pause. Fix that first: Offshore isn't the risk. An unclear brief is.
A short scorecard before you buy another login
| Signal | Prefer | Walk carefully |
|---|---|---|
| Problem statement | "These five handoffs on one order" | "We need a modern platform" |
| First fix | Delete a re-key between tools you keep | Replace three tools at once |
| Automation | No-code for low-risk syncs | No-code for money/stock without error design |
| Build | Spine you own, phased, demoable | Big-bang suite with a spreadsheet still beside it |
| Exit | Export + repo + credentials in your name | "You'll never need to leave" |
Also ask the leave question early. If you cannot take your data and rebuild elsewhere, you did not buy software — you rented a hostage situation. Same test we use when every supplier looks the same until you try to leave.
FAQ
Do we need custom operations software if our SaaS tools mostly work?
Only if the joins between them are where the pain lives. If each tool is fine and nobody is re-typing, keep buying. Custom work should remove handoffs, not invent a fourth place to click.
Will a custom operations system replace our accounting software?
Usually no. Accounting is a standard tool. The operations system should pass invoices and order facts across so finance is not re-keying. Replacing Xero, MYOB or QuickBooks is rarely the first honest move.
Is this only for wholesale?
No. Wholesale is a clear example because orders, stock and purchasing are loud. The same pattern shows up in operational service businesses and other SMEs where work moves between people and tools every day.
How is this different from "digital transformation"?
It is narrower. Follow one real order. Delete the stupidest handoffs first. Ship something usable. Then decide the next phase. No programme office required.
What should we send you if we want a straight answer?
A one-page trail of one messy order: where it started, every system it touched, who moved it, and what broke or nearly broke. Roles, source of truth, in/out for version one, and a done-sentence. That is enough for us to say build, integrate, or keep what you have.
The short version
You do not need another SaaS login when the real problem is the gap between the logins you already have.
Count the handoffs on one real order. Use Zapier or Make for low-risk joins. Build a thin operations spine when the flow touches money, stock or customer promises, when connectors do not exist, or when you want to own the join. Keep the standard tools that already fit. Phase the work. Own the code.
That is the whole idea behind custom operations software for SMEs in the UK, Australia and New Zealand: software that fits the business, not a business bent to fit another subscription.
Show us one order. Walk us through how it moves today — email to spreadsheet to stock to customer to accounts. We will tell you which handoffs are worth deleting, which syncs belong in no-code, and what a fixed-price first phase looks like if a spine is justified. If the honest answer is "keep what you've got", we will say that too. See what we've built, or tell us what you're trying to do.
Related reading: You already built custom software. It's a spreadsheet. · Offshore isn't the risk. An unclear brief is. · You paid for it. In most countries, that doesn't mean you own it. · Every supplier looks the same until you try to leave · Wholesale order management & operations software