Blog
Straight answers about building software
Written for founders, operators and the people signing off on engineering spend. What things cost, how long they take, what to build first, and how to avoid the expensive mistakes, no jargon required.
Data reconciliation: how to sign off a report when two systems disagree
A practical guide to choosing the control total, tracing a difference and deciding when a replacement report is ready to use.
First pass yield: why one batch can produce three different percentages
Use five inspections to separate first-time quality from successful rework and decide where to investigate.
How to measure on-time pickups when trips have missing timestamps
A dispatcher has five trips and three measured pickups. Work out what the punctuality figure can tell you before changing the rota.
How to calculate rental occupancy rate when a flat is under refurbishment
Follow three flats through September and measure the effect of vacancies and repairs on a portfolio report.
Sales reconciliation: why £445 in retail exports becomes £275 in the sales report
Rebuild a monthly sales total from six invoice arrivals. Identify a repeated line, a price correction and a genuine credit.
Is AI-generated code safe to ship?
Most of your product's code was probably written by a machine. What that changes about your risk, the questions to ask your engineering team, and the controls that actually matter.
Why AI features take five times longer than the demo suggested
The prototype took two days and was genuinely impressive. Then it took four months to ship. Here is where that time goes, why it is not anyone's fault, and how to plan for it.
Should your startup build AI features?
A decision guide for founders under pressure to add AI, how to tell a genuine use case from a defensive one, what it costs to run, and the failure modes that cost customers rather than money.
Build vs buy: a decision framework that survives contact with reality
When to build software yourself and when to buy it, including the ongoing costs of building that rarely appear in the comparison, and the specific cases where buying goes wrong.
When to rewrite vs refactor
Full rewrites fail far more often than teams expect, and for reasons that are predictable. How to tell the rare case where a rewrite is genuinely right from the common case where it is a story people tell themselves.
Technical debt, explained for founders
What engineers mean when they say technical debt, how to tell deliberate debt from neglect, and how to decide when paying it down is worth the delay to your roadmap.
Technical due diligence: what to actually check
A practical checklist for assessing a codebase and engineering team before an acquisition, an investment, or taking over a product, including what has changed now that much of the code was AI-generated.
When to hire your first CTO, and when not to
Founders often hire a CTO too early, or hire the wrong shape of one. What the role actually needs to do at each stage, and the cheaper alternatives that work until you genuinely need one.
Hiring engineers vs outsourcing: how to decide
In-house team, agency, contractors or a mix, a decision framework based on what you are actually optimising for, and the hidden costs on both sides that founders discover late.
How long does software take to build?
Why software estimates are wrong in a consistent direction, what actually determines a timeline, and how to plan around uncertainty instead of pretending it away.
Fixed price vs time and materials: which contract to use
Both pricing models fail in predictable ways. How to tell which one fits the work you actually have, and how to structure either so incentives point in the same direction.
How I scope a build so it does not run over
The specification format I use before writing any code, what goes in it, what deliberately stays out, and why scoping is now the constraint rather than implementation.
What to build first: cutting scope without gutting the product
The hardest decision in a first release is what to leave out. A practical method for finding the one workflow that has to work, and for deciding what can be done by hand instead of built.
How much does it cost to build an MVP?
An honest breakdown of what a first product version costs in 2026, what actually drives the number up or down, and how to tell a realistic quote from an optimistic one.
How to choose a software development partner
A practical framework for evaluating development agencies and contractors, the questions that actually predict a good outcome, the warning signs worth walking away from, and how to structure the first engagement.
Turn the trend into shipped software
I contract as a senior fullstack and data engineer, building the production systems your customers and your reporting depend on.