Start a project · 33 services · from $29/mo
Tell us the task.
Anything technical, in plain words. A developer drafts the scope and answers within 24 hours — a straight reply on whether we can do it, roughly what it costs, and how long it takes.
What helps
- What the thing should do
- Who uses it
- When you need it live
- Anything you've already built or bought
What we won't do
- Add you to a mailing list
- Sell your details to anyone
- Chase you with a five-email sequence
- Send an automated reply pretending to be a person
01 What you need
No mystery
What happens after you hit send
The whole sequence, so you know what you're starting. Nothing is billed until you've approved a number in writing.
01
Tell us what you need
One message describing what you want and roughly when. You get a written reply from a human within 24 hours — including, sometimes, that we're not the right studio for it and who might be.
24 hours
02
A scoping call
Half an hour. You describe the thing; we ask the questions that decide the scope and the price. No slides on either side, and nobody tries to sell you a retainer you didn't ask about.
30 minutes
03
Scope and price in writing
What it does, what it deliberately does not do, what it costs and the date it goes live. One document, agreed before the first commit. If we disagree about what we're building, we find that out here rather than in week six.
2–3 days
04
Build in the open
A staging URL in the first week that updates as we work. A developer writes the first pass — code, copy, design, audits — and a second engineer reviews, corrects and ships it. You watch the thing get built. No status decks, no weekly call to tell you what a commit log already says.
Days to weeks
05
Ship, hand over, look after
Live on your domain with your billing, analytics and accounts. Repository transferred, every key handed over, written handover doc. Then a fixed window of post-launch fixes, and a care plan if you want us to keep watching it.
Launch day
Book a one-to-one call
Pick a time that suits you.
Thirty minutes, one to one, to talk through what you need and what it would cost. No slides and no pitch deck — and you never need a call to get a price.
Questions
Asked before every first call.
Answered here so the call can start somewhere more useful. Anything not covered, put it in the form — you'll get a reply within 24 hours.
Who actually does the work?
Developers on our team. One of them scopes your project, writes it and ships it, and a second engineer reviews everything before it reaches you — that is the whole chain, and there is no account manager in it. We use AI heavily as a tool, the way any serious team now does, and we also build and sell AI agents as a product. Neither of those means a machine delivering your project unsupervised. Our prices sit under agency rates because you are paying for the people building the thing and nothing else.
Can I give you a task that isn't on the services list?
Yes. Describe it in plain words — anything technical that touches your business online — and we'll scope it. If it maps to a service you'll get that price; if it's new we'll quote it; and if the honest answer is that you don't need us, you'll hear that instead.
How much does a project actually cost?
Every service on this site has a public starting price, so you can see the floor before you talk to anyone. After a scoping conversation you get one fixed number for your exact scope, in writing, before any work starts. We don't run an hourly meter that ticks while you wait for a reply.
Do I own the code and the accounts?
Completely. Repository, domain, keys, accounts and data are transferred to you at handover. Nothing is licensed back to you, and nothing runs on our infrastructure unless you specifically ask us to host it. If we never speak again after launch, you lose nothing.
I have an idea but no spec. Is that enough?
Yes — that's what scoping is for. You bring what the product should do and who it's for; turning that into a buildable specification is our job, and you approve it in writing before anything is built.
Can you take over something another developer started?
Usually. Send the repository link and say where it stalled. We'll audit it and give you an honest verdict — finish, refactor or restart — with the reasoning shown. Sometimes a restart genuinely costs less than a rescue, and if so we'll prove it before you decide.
Do you work with businesses outside your country?
Yes — clients are spread across several countries and everything runs remotely. Scoping calls are booked in your timezone, and written updates mean you're never waiting on an overlap window to find out where things are.
What do you need from me to start?
A description of what you want and roughly when you need it. That's genuinely enough for a first reply. Anything you already have — a repository, brand assets, analytics access, a half-written brief — speeds up scoping, but none of it is required to begin the conversation.
What do you do with my answers?
We keep them, and your email if you give it, so we can see which questions people get stuck on and so we can pick up the conversation where you left it. We do not sell them and there is no drip sequence. Ask us and we will delete them.