How we work, in writing.
Writing down how we work forces us to work that way. This isn't a list of values: every point is a concrete promise, and you can use it on the first call to hold us to account.
- 01
The problem first, the tool second
We look at the business problem before the technical solution, and the stack is chosen last. We work with whatever fits your product, your team and your deadline — never the other way round.
- 02
You talk to whoever writes the code
No account managers, no rotating juniors. The person who listens to you on the first call is the one who will build your project, and stays your point of contact until the end.
- 03
If we're not a fit, we tell you before starting
Every service lists when we are NOT for you. We'd rather send you elsewhere in an email than have us both find out halfway through, with your money spent.
- 04
Buy before build, when it's the better deal
If an off-the-shelf product covers what you need, we'll say so: it'll cost you a fraction. Custom software is justified when the part that makes you different is the part that makes you money.
- 05
Scope and estimate before writing code
We come out of discovery with what gets built, what the risks are and what it costs. If we can't estimate with confidence, we say so instead of padding the number.
- 06
Working software every two weeks
Not progress reports: the deployed application, so you can use it and tell us where we got it wrong while fixing it is still cheap.
- 07
The code and the infrastructure are yours
In your repository and your cloud from day one, with documentation your team can maintain. Staying with us should be a decision, not a consequence of not being able to leave.
- 08
Boring is good in production
Automated deployment with a way back, infrastructure as code and observability from day one. Shipping a change shouldn't be an event.
- 09
AI gets measured or it doesn't ship
First we agree the metric, then we choose the model. And we keep a person in the loop wherever being wrong costs money. AI that isn't evaluated isn't a product, it's a bet.
- 10
Accessibility, performance and security as standard
Requirements from the first commit, not a phase that gets cut when deadlines bite. This very site is audited against WCAG AA and its contrasts are verified in the browser.
What we don't promise
The cheapest quote. We won't be it.
Twenty people to hit an immovable date. We're a small team and we're not going to pretend otherwise.
AI that's right 100% of the time with nobody reviewing anything. That doesn't exist today, whoever tells you otherwise.
A firm figure without having understood the problem. Be wary of anyone who gives you one.
Hold us to it.
Tell us about your project and check on the first call whether this holds up. You can also see what we do, and what we don't.
How we work with people, with resources and with the impact of what we build is set out in our commitments.