We write about the whole business of getting software built. Working out what you actually need. Saying it clearly enough that someone builds the right thing. Designing it around the people who have to use it. Knowing when something off the shelf will do, and when it will quietly cost you more. What all of it should cost, and why so few people will tell you straight. And what to do when a project has gone wrong.
Thirty years of doing this for other people, written down by the people who do the work, not by a marketing department.
We price most jobs from a few paragraphs. Five things need to be in there: what the software should do, whether it exists already,...
We read the websites of 225 East Yorkshire business. Nearly half run WordPress; of those 24% are at least a major version behind,...
Most failed software projects are recoverable. Secure the domain, DNS, hosting and code repository in your own name before anythin...
Nobody sets out to specialise in other people’s unfinished software. What thirty years of opening unfamiliar codebases teaches you...
No discovery call, no proposal a week later. What you need before you ask, what happens after you send it, how long it really take...
A lot of people never ask, assuming their job is too small or too odd. Scripts, WordPress changes, integrations, mobile apps, besp...
Most software is sold by the hour, which puts all the risk on you. What actually drives the cost, what to expect to pay, and the s...
Turn it on when you need it, off when you don't, and pay for the work you asked for. What the on tap model actually means, what it...
Tell us what is going wrong and we will price the fix up front. No hourly billing, no commitment.