Insights
Thinking, from the people who do the work.
Field notes on building and running systems that have to stay up, written by the people who do it.
Outcome over output: what accountable delivery actually means
Plenty of firms will deliver what you asked for. Fewer will stand behind whether it worked. The difference between output and outcome is where most software value is won or lost — and it starts before the contract.
Read the article →
Your ERP isn't the problem. The gaps around it are.
Most 'we need a new system' conversations are really about the gaps a big platform leaves behind. Before you rip and replace, look at the thin custom layer that could make what you already own finally fit.
AI agents in the enterprise: past the hype, into the workflow
"Agentic AI" is the phrase of the year. Underneath the noise there's a genuinely useful idea — and a familiar set of engineering problems that decide whether it works. A grounded guide to where agents earn their place, and where they don't.
When the spreadsheet became a system: the hidden cost of internal tools
Every business runs on tools it never chose — the spreadsheet that quietly became critical, the app that half-fits. They work, until the day they don't. Here's how to tell when a custom tool has stopped being a convenience and started being a risk.
Making AI work in your business: past the demo, into production
Most enterprise AI never leaves the pilot. The gap between an impressive demo and software people actually rely on is where the real work, and the real value, sits.
Buy, build, or integrate: choosing the right path before you spend
The most expensive technology decisions are made in the first week, when nobody's writing code yet. Here's how we help clients get them right.
Technical debt is a business decision, not an engineering problem
Technical debt is usually framed as messy code the engineers should clean up. Framed that way, it never gets fixed. Treat it as a business trade-off and it finally gets managed.
Build it, then run it: why most technology handovers fail
The moment a system is handed from the people who built it to the people who must run it is where most of the risk lives. Here's how we close that gap.
Cloud cost is a design problem, not a billing one
When the cloud bill climbs, most teams reach for discounts and dashboards. The durable savings are almost always in the architecture.
Custom software vs off-the-shelf: how to actually choose
The choice between building custom software and buying an off-the-shelf product is one of the highest-stakes technology decisions a business makes. Here's a framework that holds up.
How to choose a software development company in India
India has world-class software talent and a very wide range of quality. Here's how to tell a partner that will own the outcome from one that will just take the brief.
How to modernise a legacy system without a big-bang rewrite
The full rewrite is the most tempting and most dangerous way to modernise. There's a slower path that actually finishes.