How we work
No decks. No discovery phase that ends in a PDF.
A written scope, a staging URL you can click in week one, and a fixed price agreed before anyone starts. Developers do the building and a second engineer reviews every step. The same five steps run on every project in the catalog.
Step by step
The build
The same sequence whether the project is a landing page or a platform. Only the durations change.
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
Rules
Three rules every project runs on
01
The demo is the status report
Progress is something you click, not something you're told. If there's nothing new on the staging URL there's nothing to have a meeting about — so we don't have one.
02
Scope lives in writing
What it does, what it doesn't, the price and the date — one document, agreed before the first commit. When something changes mid-build, the document changes first and you approve the difference.
03
You own all of it
Repository, domain, keys, accounts, data. There is no version of this where your product is hostage to our hosting. If we never speak again after launch, you lose nothing.
Handover
What you walk away with
Everything below is transferred to you. There is no version of this where your product is hostage to our hosting.
- 01The repository, transferred to your account
- 02The production deploy, live on your own domain
- 03A staging environment that stays up for future iteration
- 04Every API key, secret and service account, handed over
- 05Billing connected to your account — revenue lands with you from day one
- 06A written handover: how it runs, how to change it, what to watch
- 07A fixed post-launch window where we fix what real users find
Fit
Who this works for, and who it doesn't.
Being explicit about the second one is what makes the first one worth reading.
We're a good fit if
- You want it built, found and maintained — not just one of the three.
- You'd rather have a fixed price in writing than an hourly meter.
- You want the repository, the keys and the accounts at the end.
- You can make a decision without assembling a committee for it.
We're the wrong studio if
- You want the cheapest possible number and nothing else matters.
- You need a design system delivered in Figma and nothing that runs.
- You'd rather have a big-agency logo on the invoice than the people writing the code.
- The scope changes every week and nobody owns the decision.
Questions
How the work runs.
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.
How long does it take?
A landing page is days. A business website is two to four weeks. A full SaaS product or a mobile app is six to sixteen weeks depending on scope. Every quote carries a real ship date, and if we're going to miss it you hear that early rather than on the day.
Who actually does the work?
a full team of specialists — engineers, designers, SEO strategists and AI developers — staffed to what your project needs. One named lead owns your build and is your point of contact, and the founder is on every scoping call and every architecture decision regardless of project size.
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.
What happens after launch?
A fixed post-launch window is part of every build scope: real users find things no plan predicted, and we fix what they find. After that you can move onto a monthly care plan, hand it to your own team, or walk away — it's your codebase either way.
How do you charge — fixed price or hourly?
Fixed price for projects, monthly for retainers. You approve a number and a scope before work starts. If the scope changes mid-build, the document changes first and you approve the difference — nothing gets added to an invoice you haven't seen.
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 if it goes wrong?
You get told early. Every project has a written scope and a staging URL you can check yourself, so problems surface as visible slippage rather than as a surprise at the deadline. Where something is our error, we fix it at our cost — that's not a policy we advertise, it's just what the scope means.
Step one
It starts with one message.
Describe what you want built and roughly when you need it. That's genuinely enough — turning it into a scope is our job, and you approve it before anything gets built.
Written reply within 24 hours · No mailing list · contact@decodewithmohit.com