Manifesto
What we believe about software you didn't want to buy.
Nobody sets out to hire a software company. You hire one because something in the business stopped working. Everything below follows from taking that seriously.
- 01
The specification is the product. The code is the delivery.
If we cannot write down what your system does in language you can check, we do not understand it well enough to build it. So the writing comes first, you approve it, and only then does anyone open an editor. It is why the scope can be agreed before the work starts.
- 02
You should be able to leave at any point without a negotiation.
Repository, database, hosting — created in your name in week one, not handed over at the end when handing over has quietly become leverage. Ownership you have to ask for was never ownership.
- 03
A week is the longest anything should stay a mystery.
Every Friday there is something running that you can look at. Not a status report, not a percentage — the thing itself, against your data. A bad week should be visible in seven days, not in month three when the money is gone.
- 04
Your process is not a problem to be replaced.
Operators arrive apologising for their spreadsheets. Those spreadsheets are usually years of hard-won process, written down. The job is to read them as a specification, not to overwrite them with how generic software assumes a business should run.
- 05
One person should be answerable, and you should know their name.
Account managers exist to absorb bad news on the way to the people doing the work. The engineer who architects your system is the engineer who builds it and the one who answers when it breaks. No telephone game, no handoff, nobody learning on your budget.
- 06
AI is a tool we use, not a thing we hide.
It is how one senior engineer ships at the pace of a team. What it never does is decide what to build, approve a specification, or merge code nobody read. Open the commit history and you will see exactly how the work was done.
And what we won't do.
- We do not bill by the hour. It pays us to be slow.
- We do not start building before you have read and approved what we are building.
- We do not hold code, data, or infrastructure hostage to keep a client.
- We do not put a number on a page we cannot stand behind in a contract.
- We do not describe work in language designed to stop you asking questions.
That's the argument. Here's the test.
One week, one written verdict, and a plan you could hand to any engineer — including one who isn't me.