We scope before we quote, and build in phases you can stop.
Every build starts with five questions and a fixed-fee scope of about a week. Then we build in phases. Each phase ends in working software you can open, and each next phase is a decision, not an obligation.
Five questions before we quote.
Most projects fail before any code is written — because a price was given before anyone knew what it would cost to build.
If we can't answer these, we quote a phase, not a platform.
- 01 Marketplace or single vendor? Two sides means two apps and the console between them.
- 02 Your own riders and staff, or third party? Dispatch, shifts and payouts are a build of their own.
- 03 Which payment rails, and who holds the money? Wallets, escrow and payouts cost more than a checkout.
- 04 What is the budget range? It decides what goes in phase two and what waits.
- 05 What already exists, and in what state? Inherited code is sometimes cheaper to replace than to keep.
Built in phases. You pay per phase.
Money is attached to finished work, never to a promise. If phase one doesn't convince you, you stop — and you keep everything we built.
Phase 01
Scope and price
The five questions answered, the build written down, and a named list of what we are not building.
Phase 02
The first working version
The core of the platform, running, with real data. This is where you decide whether to continue.
Phase 03
Everything after
The remaining scope in phases of the same shape, then maintenance. Each one priced before it begins.
We write down what we're not building.
A named list in every scope, not a footnote. It is what lets us say later: good idea, here's what it costs — instead of arguing about what was implied.
What happens when things go wrong.
A date slips
You hear it before it slips, in writing, with the reason and the new date. Not on the day.
You want a change
We price it before we build it, and you decide. Nothing gets added quietly.
Something is built wrong
A defect costs you nothing. If we built it wrong, we fix it.
You want to stop
Stop at the end of any phase. You keep the code, the repository, the accounts and the handover documents.
We don't leave at launch.
A platform that stops working stops paying people. Maintenance is standard on every build; the included period is agreed in the scope.
What happens in phase one?
The five questions answered, the build written down, and a named list of what we are not building. Fixed fee, about a week. The five questions are: marketplace or single vendor, your own riders and staff or third party, which payment rails and who holds the money, the budget range, and what already exists. You keep the written scope whether you continue with us or not.
What does the first working version include?
The core of the platform running with real data: a customer can do the thing, a provider can fulfil it, and you can see it in the console. Everything else is a later phase. It is deliberately small, because it is the point where you decide whether to continue, and that decision is better made with real use in front of you than with a longer feature list.
How do you tell us a date has slipped?
Before it slips, in writing, with the reason and the new date. Not on the day. Uzair runs phases and dates, so the message comes from the person who owns the plan rather than someone passing it on. You also see progress in the weekly written update, so a slip should never be the first sign that something is wrong.
Can we pause between phases?
Yes. Each phase is a decision, not an obligation. When a phase ends you have working software, the code and the documents for it, so there is nothing to lose by pausing. When you come back, the next phase is scoped and priced before it starts. A pause is a good time to put the first working version in front of real users.
How do we communicate?
A shared channel, a weekly written update, and a call when a decision is needed. The channel is for questions and quick answers. The weekly update says what was built, what comes next, and anything at risk. Calls are kept for decisions, so you are not sitting in meetings that could have been a message.
What happens if we disagree about scope?
We go back to what was written down. Every scope names what is in the build and what we are not building, so most disagreements are settled by reading it together. If something was missed, it is priced as a change and you decide whether to add it. If we built something wrong, it is a defect and costs nothing.
Plan your build in two minutes.
No call. A few guided questions, then a tailored quote — usually within one business day.
Or send us the idea in three sentences on WhatsApp, or email support@codingwitht.com.
Read this first
- How pricing works
Per phase, agreed up front, and what costs extra.
- Who you will work with
Three people. No account manager.