Large platforms are excellent at the eighty percent of a process that looks like everyone else's. The trouble is that the remaining twenty percent is usually where your margin lives — and it is the part the platform expresses least well.
So teams work around it. A custom object here, a flow there, an offline spreadsheet, a report rebuilt by hand each month. Each step is defensible. The aggregate rarely gets priced.
Where the money actually goes
The licence is usually the smallest line. The rest is easy to miss because it sits in other budgets.
- Change latency — weeks of queue time for a rule that takes a day to write, multiplied by every quarter you needed it live.
- Specialist rates — platform-certified work costs a premium, and the work you get is configuration you do not own.
- Per-seat drag — processes designed around avoiding licence counts rather than around the work itself.
- Shadow systems — the spreadsheet that holds the real logic, maintained by someone whose job title says something else.
- Upgrade tax — every heavy customisation is a thing to retest whenever the vendor ships.
The signals that you have crossed the line
Extension is still the right lane for most platform work. But a few signs mean the workaround layer has become the system: the platform can no longer express a rule your business depends on; reports are rebuilt manually every cycle; onboarding a new operator requires oral tradition; and the annual platform spend has stopped correlating with the value delivered.
When three of those are true at once, you are already paying for custom software. The only open question is who owns it.
What we recommend instead
Keep the platform as the system of record. It is good at that, your finance and audit processes rely on it, and ripping it out is rarely justified.
Then move the differentiating decision logic into a thin workflow layer you own, reading from and writing back to the platform through documented interfaces. The platform stays the ledger; the judgement moves somewhere it can be versioned, tested and changed in days.
How to price the comparison
Pick one contested workflow. Add twelve months of change requests, specialist fees and internal hours spent compensating for the gap. Compare that with the cost of owning that workflow outright, including maintenance.
In our experience the comparison is uncomfortable in one direction or the other — and either result is useful. Sometimes the honest answer is that the platform is fine and the process should change. Sometimes it is that you have been renting your own competitive advantage.