Most organisations run on software that nearly fits. It does eighty per cent of the job well, and the other twenty per cent gets absorbed by people doing manual work around the edges. That twenty per cent is where the time goes.
The workaround tax
It shows up as exports into spreadsheets, copy-and-paste between systems, a monthly report someone assembles by hand, a rule that only works because a particular person remembers it. Nobody logs these hours anywhere, which is exactly why they never get fixed. They are invisible on the balance sheet and obvious to whoever does them.
Why small custom tools got viable
Custom software used to mean a long project and a big budget, so the sensible move was to buy something off the shelf and live with the gaps. That maths has changed. A focused tool that does one job properly is now a modest piece of work, and it can sit alongside whatever you already use rather than replacing it.
What a good small tool looks like
It does one thing. It fits how you actually work rather than how a product manager somewhere imagined you might. It is quick to learn, because there is not much to learn. And it removes a task rather than adding a system to maintain. If a tool needs training and a champion to survive, it is probably too big.
Start where the pain is loudest
The best first tool is the thing your team already complains about. Not the strategic transformation, the actual weekly irritation. Fix that, prove it works, and you have both a saved afternoon every week and a much better sense of what to build next. We build tools like this, and often the honest answer to the brief is that you need something smaller than you asked for.