Most businesses do not have a completely unique workflow. They have a mostly ordinary workflow with one unusually important part that generic software handles badly.
Short answer: keep the off-the-shelf system for the common work. Find the exceptions that create repeated copying, checking, chasing or rework. Fix that narrow part first—often with an integration, a focused internal tool or a small process change rather than a full replacement.
Why eighty percent can still feel like failure
A product can cover most of a process and still leave the business with the costly part. A generic CRM may store customers but not the approval stages that matter. A booking platform may take appointments but fail on specialist availability rules. An accounting package may be excellent while the evidence feeding it remains scattered across email and spreadsheets.
The missing twenty percent tends to contain exceptions: unusual pricing, approvals, handoffs, specialist terminology and the decisions that require context. Those exceptions are exactly where people create workarounds.
Five signs you have found the awkward part
- The same information is copied between two or more systems.
- One experienced employee remembers rules that are written nowhere.
- A spreadsheet exists mainly to repair what another system cannot represent.
- Customers repeatedly ask for an update your team has to assemble manually.
- Small mistakes survive until invoicing, fulfilment or month-end.
None of these automatically justifies custom software. They identify where investigation should begin.
Measure the workaround before replacing it
Count frequency, minutes and consequences. Ten minutes once a month is an irritation. Ten minutes across forty jobs every day is a system. Include correction time, delayed invoices, missed follow-ups and the cost of only one person knowing how the workaround works.
Our free spreadsheet cost calculator gives you a useful first estimate. The purpose is not to manufacture a return-on-investment number. It is to learn whether the problem is large enough to deserve attention.
Four possible answers
Buy
If another product already handles the exception well, use it. Paying a subscription is usually cheaper than recreating a mature commodity feature.
Automate
If both existing systems are useful and the pain sits in the handoff, connect them. A reliable transfer with exception reporting may be all that is required.
Build
If the awkward part is stable, valuable and genuinely specific to the business, build the smallest tool that owns that part—not an unnecessary replacement for everything around it.
Wait
If the process is still changing or the cost is low, document it and measure again later. Premature software preserves confusion in code.
Start with the exception, not the feature list
A useful brief does not begin with “we need a portal”. It begins with “customers phone twice per job because they cannot see progress”. That description leaves room for the least complicated sensible solution.
If you have found your awkward twenty percent, send it through the Build, Buy, Automate or Wait Review. A short explanation is enough.