We talk
A call of twenty to forty minutes. You describe the problem, we ask the awkward questions. No slide deck, no charge, and no follow-up sequence if it is not a fit.
HOW WE WORK
No surprises,
by design.
Most software projects fail in the same two places: an unclear scope at the start and a long silence in the middle. Here is how we remove both.
THE PROCESS
Six steps, and you can stop after any of them.
We scope it in writing
You get a document: what gets built, in what order, what each stage costs, what it will not do, and what we need from you. It is written so that another developer could work from it.
You decide
Take the scope to someone else if you want a second quote. It is yours. Most of the value of that document is that it exists, not that we wrote it.
We build in stages
The first stage is something you can click on, usually within two to three weeks. Then a new version every week, with a short note on what changed and what is next.
We launch
Your accounts, your domain, your app store entries. We set them up with you rather than in your name, so you can always get back in without us.
We keep it running, or we hand it over
Either a monthly arrangement covering hosting, monitoring, updates and a person who answers, or a clean handover: code, credentials, documentation, one paid session to walk your team through it.
WHAT WE COMMIT TO
Four things you can hold us to.
Every week, you get
A working version and a short written update. If a week produced nothing worth showing, the update says that and why — which is rare, and never a surprise at the end.
One person answers
You are not routed through an account manager. The person writing to you is the person who knows what the code does.
You own everything
Source code, accounts, domains, app store entries, design files. From the first day, not on completion of payment.
We say no
If a request will make the product worse, cost more than it returns, or break something else, we say so before we build it — in writing, with the reason.
HOW WE CHARGE
Three models. We tell you which one fits.
Which model applies depends on how precisely the work can be described, not on which one earns us more. We will say which one we think fits, and why, before you commit to anything.
Fixed scope, fixed price
For work that can be described precisely: a website, an app with a defined feature list, a migration. You know the number before we start. Changes mid-project get their own small quote, so the price never moves quietly.
Time-based, by the week
For work that cannot honestly be pinned down in advance: research, a rewrite of something undocumented, an AI agent whose value depends on what the data turns out to look like. You buy weeks, you can stop after any of them.
Monthly, for keeping it alive
Hosting, monitoring, security updates, small changes and a guaranteed response time. Priced on the size of the system, cancellable with notice. Optional — plenty of clients take the handover instead.
WHAT WE NEED FROM YOU
A project moves at the speed of its slowest answer.
We can do almost everything ourselves. These five are the exceptions — and when one of them is missing, no amount of effort on our side makes up for it.
- One person on your side who can make decisions without a committee
- Access to the systems the new thing has to talk to, early rather than late
- Honest numbers — how many users, how much data, what the real budget is
- Feedback within a few days on each stage, so we are not building on guesses
- Your content: text, images, logins, legal pages. This is the single most common reason a project runs late.
Ready for the first call?
Twenty minutes, no charge, no deck. Worst case you leave with a clearer idea of the problem than you came in with.