You will know the number before we write any code.
And you will know what it buys, what it does not, and what happens if you want to stop.
Platforms
Platform builds
Marketplaces, delivery, multi-vendor ecommerce, logistics. Two or more user types, payments and an admin console.
How it's priced
Per phase, agreed up front
Your number comes from the planner, not from a price list.
Operations
Fixed-scope work
POS and retail systems, internal tools, a defined feature on something that already runs.
How it's priced
One number, before it starts
Scoped first, quoted second, built third.
How a platform build is paid for.
Every phase ends in working software you can open. The next phase is a decision, not an obligation.
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.
The part most agencies won't put in writing
If phase one doesn't convince you, you stop — and you keep everything we built.
The code, the repository, the accounts and the handover documents are yours on payment for that phase. No exit fee and no hostage.
In every price
No line item, no surcharge.
- Full ownership of the code on payment — exclusive and perpetual
- Your repository, your accounts, your signing keys
- Handover documents another team could pick up
- Defect fixes — a defect costs you nothing
- iOS, Android and web where the build calls for it
- You talk to the engineer building it, not an account manager
Costs extra, and we say so first
Named in the scope, priced before it starts.
- Scope added after the phase is agreed
- A second payment rail or an unplanned integration
- Third-party fees — gateways, app stores, maps, SMS
- Design of a brand you do not have yet
- Ongoing maintenance beyond the included period
- Support for a platform another team built
What moves the number
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.
Plan your app.
A few guided questions — nothing you can't answer. We shape your idea into a brief and come back with a tailored quote, usually within one business day.
Step 1 of 8
Coding with T · Project planner
What do you want to build?
Pick the closest match. We build for any niche, and every next question adapts to your answer.
Closest match
Where will it live?
Your market shapes payments, languages and the rules we build for. Optional, but it helps a lot.
Launching in · pick any
Who's it for, and where does it run?
Two quick choices. We'll advise if you're unsure.
Who will use it
Platforms · pick any
Which apps do you need?
Most platforms are a few connected pieces. Pick what you need — for the unsure ones, we'll advise.
The pieces · pick any
What should it do?
The features founders in your space usually want. Toggle any, and leave the rest to us.
Features · pick any
Where are you starting, and how big?
No wrong answers. We meet you wherever you are.
What you have so far (optional)
Size of the first version
Goal, design and timeline
The last three, then your brief is ready.
Goal for v1
Design level
Timeline
Here's your brief.
This is your idea, mapped out. Send it over and we'll come back with a tailored quote.
Budget — optional, helps us tailor
No obligation, and nothing is shared until you send it. We'll also tell you where you can save — the features you actually need, and the cheaper choices that still perform.
Straight answers.
Why won't you publish a price list?
Because a number on a page is either padded against you or a promise we would have to break. The planner prices your build instead of an average one.
Who owns the code?
You do, on full payment. Exclusive and perpetual.
What if we want to stop?
Stop at the end of any phase. You keep everything built and paid for.
What if you disappear?
Your repository, your accounts, your signing keys — documented so another team can pick it up.
What does a defect cost?
Nothing. If we built it wrong, we fix it.
Do you take equity instead of cash?
No.
What does a change cost?
We price it before we build it, and you decide. Nothing gets added quietly.
Do you leave at launch?
No. A platform that stops working stops paying people. Maintenance is standard on every build.