How we work
Before you sign, you should know how this goes
The most common fear people bring us isn't that the work will be bad: it's being held hostage by whoever did it. Everything you'd normally find out afterwards is written down here instead.
We handle the hard part. You just get the thing that works.
Integrations, going live, the Saturday-night surprise: those are our problems, not yours. And from start to finish you always talk to the person building your product — not to a middleman who then passes the question on to someone else.
In writing
The awkward questions, answered
These are the same terms that end up in the contract. They're here so you can read them before talking to us, not after.
- Who actually owns the code?
- You do, from day one. The repository is in your name and we work inside it, not the other way round. Domain, servers, service accounts: all yours, with the credentials in your hands straight away — not from the day you ask for them. There's no point in the project where something is ours and then gets handed over.
- What does the contract say?
- A fixed price, not a range: after the scoping call we give you a figure and it holds, unless you ask for more — and if you do, we tell you before we build it, not on the invoice. It has the dates, what's included and, more importantly, what isn't. No minimum term: support can be cancelled with a month's notice and carries no penalty.
- Who actually does the work?
- One person, and always the same one. There's no salesperson who sells you something then disappears, no account manager passing your question along. When you write, the person who answers is the person writing the code. That's also our stated limit: if you ask for something we can't do, or can't do well in the time available, we say so instead of trying.
- What if you disappeared tomorrow?
- You'd already have everything: the code is in your repository, the servers are in your name, and how to deploy it is documented inside the project rather than in our heads. We deliberately use standard, widely known tools — Next.js, PostgreSQL, common cloud services — rather than anything homegrown: any competent developer can pick the work up without starting over. It isn't generosity, it's why we don't need to keep you.
- How fast do you reply?
- Within 24 working hours to anyone who writes, client or not. If the project is yours and something is broken in production, you have a direct line and we move the same day. When we can't fix it immediately, we tell you what happened and how long we expect it to take — we don't leave you refreshing the site on your own.
- What if I change my mind halfway?
- That happens almost every time, and it's planned for. It's why we work in one- or two-week chunks and show you each one: changing course in week two costs little, in week twenty it costs the project. If the change fits the scope we just do it; if it moves the scope, we tell you what it costs and you decide. Neither case turns into an argument.
How we work
Three steps, no surprises
You always know where we are and what's left. From the first conversation through to support after launch.
We talk
You tell us how you work today and what isn't working. We tell you straight away whether we can help, what it costs and how long it takes — before writing a line of code.
No written quote before we've understood the problem. We spend half a day on site or on a call watching how you work today: which spreadsheets you open, where you retype the same thing twice, what wastes your Monday morning. Out of that comes a proposal with a fixed price — one figure, not a range — and dates. If we think it isn't worth doing, or that something smaller would serve you better, we say so here: it's free, and finding out costs you nothing.
- How long it takes
- 1 to 2 weeks, from the first call to the proposal
- What you end up with
- A written proposal with a fixed price, dates and what's included
We build it
We work in small steps and show you often. If something feels wrong you say so right away, not at delivery.
We work in one- or two-week chunks and send you a link at the end of each one. Not a status report: the real thing, to use with your phone in your hand. It matters because you only discover how people will actually use the product by putting it in front of them — and correcting course in week two costs nothing, while in week twenty it costs the project. If something feels wrong, you say so then, not at handover.
- How long it takes
- 3 to 10 weeks, depending on size
- What you end up with
- A link updated every week or two, always live
It goes live, and stays looked after
We put it online and keep looking after it: monitoring, maintenance, and the changes you'll need along the way.
Going live is on us: domain, servers, certificates, and the move from the old site with the redirects in the right places so you don't lose the ranking you already have on Google. Then we stay. Monitoring, updates, the changes you need along the way, and the alert that reaches us before it reaches you when something breaks. Credentials and passwords are yours from day one, not from the day you ask for them.
- How long it takes
- Live in a day or two, then ongoing support
- What you end up with
- The project online, credentials in your name, and someone who answers
What we build it with
Standard, widely used technology — not a closed system. If you ever switch supplier, anyone can pick up where we left off.
