Buy versus build: the honest version

We turn down roughly a third of the custom software enquiries we receive, and almost always for the same reason: something off the shelf already does it, properly, for a fraction of what we would charge.

The question that settles it

Not "is our process unusual?" — everybody believes their process is unusual. The useful question is: is the unusual part the reason customers choose us?

If your scheduling is idiosyncratic because nobody ever standardised it, that is not a competitive advantage, that is drift. Buy the standard tool and adopt its process; you will be better off.

If your scheduling is idiosyncratic because it is genuinely how you deliver something competitors cannot, then bending it to fit a generic product destroys the thing you are selling. That is when building is right.

The costs people forget

Custom software has a maintenance floor. Dependencies age, browsers change, integrations break when the other party updates. Budget 15–20% of the build cost annually to keep it healthy. A £30,000 platform is a £35,000 first year and roughly £5,000 a year thereafter. If that number is uncomfortable, buy.

The middle path most people miss

The best answer is frequently neither. Buy the standard products for the standard parts — accounting, payroll, email — and build only the thin layer where you are actually different, connected by integrations.

That is a smaller, cheaper, more durable piece of software than a platform that tries to do everything, and it is what we recommend more often than a full custom build.