Two things worth
having for free.
Both of these are genuinely useful whether or not you ever speak to us — that is the point of them. One tells you how much trouble your codebase is in; the other gets a build scoped properly before anyone quotes on it. No calls, no gated PDFs, nothing that needs an account.
The tools
Technical debt assessment
Ten questions · two minutesAn honest read on whether your codebase is stable, drifting, or heading for a rescue. Ten questions on ownership, tests, releases, monitoring and key-person risk — the same signals we look for in the first week of any takeover. Your score and the risks you flagged appear on screen the moment you finish; the three fixes we would prioritise come by email if you want them.
Software project brief template
Seven sections · yours to keepThe template we scope from: the problem, the users, what it must do, and just as importantly what it will not do this time. It builds a formatted document as you type, which you can copy or download with no email required — and take to any team. A consistent brief is the only way to compare proposals fairly.
Why we give them away
Because the alternative — a gated PDF and a sales call — wastes everyone’s time.
A better-informed buyer is a better client
Most builds go wrong before a line of code, in a brief that skipped the hard parts, or in a codebase whose risks nobody named out loud. Someone who has worked through either of these arrives knowing what they want and what they are trading away. That makes the engagement better, whoever ends up running it.
We would rather be judged than pitch
Take the brief template to three teams and compare what comes back. If our answer is not the most useful, you should hire whoever gave you the better one. That is a fair trade for the hour it takes.
Rather just
talk?
Tell us what you’re building. It goes straight to Harley and Jonathan, not an SDR, and you’ll get a real reply within 24 hours — including an honest no if we’re not the right fit.