Software that fits the business,not the other way round.
Every business runs on workarounds it stopped noticing years ago. Most of them exist because building the right thing used to be unaffordable. That constraint has moved.
Ask anyone who works in an operations team to walk you through their day and you will find the workarounds inside ten minutes. The spreadsheet that sits between two systems that do not talk. The report someone rebuilds by hand every Monday. The field in the CRM being used for something other than its name, because there was nowhere else to put it.
Nobody designed any of that. It accumulated. And it accumulated for a sound reason: building software that fit the business exactly was expensive enough that almost everybody bought something close and adapted around the gaps.
The adaptation has a running cost
It rarely appears on a budget line, which is why it survives so long. It shows up as the hours people spend moving data between places, the errors that creep in when they do, the reporting that is always slightly out of date, and the institutional knowledge sitting in one person’s head about why the process is like this.
Add it up over five years and it usually dwarfs whatever was saved by not building the right thing at the start. But it is diffuse, and diffuse costs do not get signed off against.
Nobody budgets for the workaround. Everybody pays for it.
What actually changed
The economics of building something bespoke have shifted considerably. Not because the thinking got easier, but because the distance between a decision and a working version of it has collapsed. Where a substantial internal system was a multi-year programme, a large amount of it is now a matter of months.
That does not make every custom build sensible. Plenty of businesses should carry on using the off-the-shelf tool, because it fits well enough and the switching cost is real. But the question is worth asking again, because the answer has changed for a lot of organisations who last looked at it five years ago and reasonably concluded it was out of reach.
Where it matters most
The businesses with the most to gain are the ones whose actual operation is unusual. If what you do maps neatly onto a standard product, buy the standard product. If your process is genuinely particular, and most established businesses have at least one part that is, you have probably been bending yourself around software that was built for somebody else.
That is where the compromise compounds. It is also where a system built for how you actually work stops being a luxury and starts being an obvious call.
If you take one thing
Write down every place a person in your business moves information from one system into another by hand. That list is your compromise, itemised. If it runs to more than a few lines, it is worth a conversation about what the alternative now costs.
Three more
worth the time.
If something other than a human reads your page first, then how you structured it matters nearly as much as what you said.
Compressed timelines usually mean corners cut. Occasionally they mean the opposite, and it is worth understanding when.
The bottleneck in a project was never how fast anyone could type. It was knowing which of several plausible answers was the right one.