◆
Small things stay cheap
A tool used by nine people costs accordingly. That is what makes building it defensible.
Every company has a list of internal tools that would obviously pay for themselves and never get built, because the cost of building and running something small has always been disproportionate to its size.
Used for operations dashboards, admin surfaces, workflow tooling and team utilities.
What this looks like in practice
A tool used by nine people costs accordingly. That is what makes building it defensible.
Internal means internal, by default, rather than by a configuration somebody must remember.
Twenty focused tools rather than one internal platform nobody enjoys. Each can be replaced alone.
A small fix is worth making, which is the difference between a tool people use and one they endure.
Most internal tooling backlogs are not prioritisation failures. They are a rational response to a fixed cost that made small, obviously-valuable things uneconomic.
Every organisation has one: a spreadsheet doing load-bearing work, maintained by one person, with formulas nobody else understands. It persisted because replacing it with software was never worth the fixed cost. That calculation is what changes here, and it changes for the whole backlog at once.
Reporting built for nine people rather than compromised to serve nine hundred.
Workflow tooling that matches how the work is actually done.
Utilities that let the right people fix data without filing a ticket.
Internal surfaces that are internal because that is the default, not a setting.
We built eleven internal tools in a quarter. Every one had been on a list for years with an obvious business case and no viable way to justify the effort.
Yes, and that is the point. The fixed cost that made small tools uneconomic is what goes away.
Private by default. The failure mode where an internal surface turns out to have been public is a configuration failure, so the configuration is the other way round.
Many, in our experience. A focused tool can be replaced by one person in an afternoon; an internal platform becomes something nobody is allowed to touch.
Whoever asked for them, usually, which works precisely because each one is small enough to understand in full.
Start on something that will still be right at a hundred times your size, and pay now what a startup should pay.
Move in stages with the old arrangement still running, and cut over only once the replacement has carried real traffic.
Get capacity when the experiment is ready, keep what produced a result, and put models in front of users without a separate platform.
Keep everything at full fidelity, query it without a project, and stop deciding today what you will want to ask next year.
Ship the application your users touch, on an address that stays put, with every version one click behind you.
Give your engineers a platform that removes decisions rather than adding them, without a platform team to run it.
Begin with one workload. Keep what you have running. Decide whether to continue once you have seen it carry something real.
No migration required to begin. Nothing to tear down if you stop.