25/07/2026
Most people don't need software. They need a problem to stop happening.
Sometimes the answer is a build. Often it's a smaller change, a different tool, or waiting three months until the requirement stops moving.
We'd rather tell you which.
That's why our new piece has no prices in it. It has how software actually gets priced, what moves the number, and five checks for reading a quote you've already been handed:
→ Does it separate thinking from building?
→ Is anything priced for after launch, or is maintenance missing?
→ Who owns the code, and the data?
→ What's excluded? That list tells you more than the inclusions.
→ Could you tell from it how you'd know the work was finished?
It also lists four times when you shouldn't build at all. Each one costs us the job.
If something isn't working, tell us what it is. We'll tell you what we think it takes.
Nothing inflated, nothing hidden.
