A startup called Atonom was paying $40,000 a year for Salesforce. Twenty-five to thirty people. Standard setup. Their CRO looked at the functionality they were actually using and said: “This is crazy for what we need.”
They built a custom CRM using AI-assisted development tools. Annual cost: roughly $1,200. Not a stripped-down version — the version they actually needed.
This isn’t an isolated story. It’s a pattern reshaping how businesses think about their tools.
The economics are new. The frustration isn’t.
Every operations lead I talk to has the same story: they know exactly what their business needs, they’ve known for years, but the software doesn’t do it. The last time they asked about custom development, someone quoted six figures and nine months. So they built workarounds. Spreadsheets became load-bearing infrastructure. People became the bridge between what software does and what the business requires.
That gap — between what you know you need and what you can actually get — has collapsed. GitHub reports that 46% of all code is now AI-generated. Developers complete tasks 55.8% faster with AI assistants. Y Combinator’s CEO said it directly: “Ten engineers are delivering what used to take fifty to a hundred.”
In practical terms: a functional prototype that would have cost six figures now takes days. A custom internal tool that would have required an engineering team now requires a clear specification and the right platform.
The specification is the product.
There’s a concept called spec-driven development that captures this shift. GitHub’s internal research puts it simply: “The specification becomes the primary artifact. Code is the last mile.”
What this means for business: your domain knowledge — the processes you’ve refined over decades, the workarounds that reveal exactly what the software should do, the institutional memory that no consultant can replicate — that knowledge is now directly translatable into working software.
You don’t need to code. You need to specify. And nobody specifies better than the person who’s been doing the work.
The consultant trap is real — and expensive.
Seventy percent of digital transformation projects fail to meet their goals. Bain puts it at 88%. An estimated **5 million to $20 million and 55% exceed their budgets.
The pattern is familiar: consultancy arrives, runs workshops, produces strategy documents, recommends enterprise tools, oversees multi-year implementation, moves on. The organisation is left with something that sort of works, costs more than promised, and is already outdated.
No consultant should walk into your company, turn it upside down, and leave you poorer and more confused than before.
Fewer tools, connected intentionally.
The average organisation uses 112 SaaS applications. Wastes $21 million a year on unused licences. Accumulates seven new tools every month, most outside IT’s oversight.
The alternative: deliberate simplicity. The right tools, connected the right way, serving proven processes. When nothing fits your specific need, you build it — quickly, cheaply, precisely. When an existing tool works, you keep it. The goal isn’t transformation. The goal is getting your time back.
The person who knows the business best should direct what gets built. Not a consultant who arrived on Monday. Not a vendor whose roadmap ignores your reality. You. The people who built these processes over years know exactly what “good” looks like.
The economics have caught up. Software that works the way your business actually works. Days, not quarters. Thousands, not millions. Owned, not rented.
MAKE YOUR CASE.