The process
From a conversation to a running system
You see a working version in 3 days, get the finished system in a month, and pay one fixed price: a small set-up payment at sign-off, the rest only after it passes your acceptance test. Then we host it and look after it.
1 · 30 minutes
Scoping call
We Say whether it is a fit, and tell you if software is the wrong answer.
You Describe what you need and who will use it.
You pay: 0 nothing due
2 · 3 days
Working prototype
We Design every screen your users will touch, as a working version on a link.
You Click through it and tell us what to change. Two revisions are free.
You pay: 0 nothing due
3 · Sign-off
Sign-off and a fixed price
We Write the scope list and set one fixed price for the whole build.
You Agree the prototype and the scope list.
You pay: ₹20K-50K set-up, deducted from the price
4 · 1 month
Production build
We Build it and test every change. Then a security review before it goes live.
You Watch it grow. Comment on the link.
You pay: 0 nothing due
5 · You pay the rest
Acceptance test, then payment
We Fix anything that fails your test. On payment, the code is yours.
You Test the system against the scope list.
You pay: the rest of the fixed price once
6 · Ongoing
Hosting and support
We Host it, back it up every night, apply security updates and fix anything that stops working as agreed.
You Use it. Tell us when something needs attention.
You pay: 0 for the first 6 months
What you pay at each step
Step by step
Every step in detail
What happens, what you get and what you pay, from the first call to the system you use.
-
30 minstep 1
Scoping call
You describe what you need and who will use it. We say whether it is a fit and what the prototype will show. If software is the wrong answer, we say so on this call.
You get: a clear yes or noYou pay: 0
-
day 3step 2
Working prototype
A real, clickable version of the system on sample data, on a link you can open. Every screen your users will touch, with the rules written beside each screen: the first draft of the scope list.
You get: a link you can click throughYou pay: 0
-
revisestep 2.1
Revision and an agreed scope
You tell us what to change and what is missing, and we revise the prototype to match your preferences and requirements. Two revisions are free. Then we agree the scope with you: what is in, what is out, and what the finished product will look like. Only after that do we estimate the work and name the price, so neither side commits to a figure before the scope is settled.
You get: a revised prototype and an agreed scopeYou pay: 0
-
sign-offstep 3
Sign-off and a fixed price
The prototype and its scope list are the contract. One fixed price for the whole build. At sign-off you make a set-up payment of ₹20K-50K: it covers the AI usage and the servers your build runs on, and it is deducted from the price. There are no other payments along the way. Anything not on the list is a change request, priced as a fixed item before work starts and added only when you say yes.
You get: a scope list and one priceYou pay: ₹20K-50K set-up, deducted from the price
-
the monthstep 4
Production build
A team of AI agents builds in parallel; one expert directs them and reads every change. You get a working link that updates every few days, so nothing is a surprise at the end. Automated tests run on every change. Before it goes live, the system gets a security review, which includes a controlled attempt to break in.
You get: a link that updates every few daysYou pay: 0
-
you teststep 5
Acceptance test, then payment
You and your team test the system against the scope list. If it passes, you pay the rest of the fixed price, once. If it does not, we fix it and you test again. The rest is not due until it passes, and a bug found in your test is never a change request. On payment, the code is yours, with its tests, documentation and runbooks (step-by-step guides for running it).
You get: a system that passed your testYou pay: the rest of the fixed price, once
-
ongoingstep 6
Hosting and support
The system runs on hosting we set up and look after: nightly encrypted backups with a rehearsed restore, security updates, and fixes for anything that stops working as agreed. No servers to buy, no IT team needed. The first 6 months are free; after that, the price for maintenance and the production server starts from ₹3K a month. If you plan to move the system to a cloud service of your own, with us or with your own team, the free 6 months keep you covered while it is moved, in the way your team prefers.
You get: a running system, looked afterYou pay: 0 for the first 6 months
Your part
What we need from you
Most of the work is ours. These are the parts only you can do.
-
First 3 days
A few hours of your time
On the scoping call and while you click through the prototype: tell us what you need, who will use it, and what to change.
-
Your files
The documents and files you already have
Price lists, spreadsheets, the forms your team fills in: whatever shows how the work is done today.
-
End of the month
A few days for your acceptance test
You and your team check the finished system against your acceptance test list. We help you write the list, and you decide what done looks like. The test only catches what it checks, so the list is worth writing with care.
The promises
The four promises
What we promise on every build.
- 01
Working prototype in 3 days.
Every screen your users will touch, on sample data, on a link you can open, with the rules written beside each screen.
- 02
Full production system in 1 month.
Built to the scope list the prototype fixed, on a working link that updates every few days. The price does not change, however long the build takes us.
- 03
Pay the rest only after your acceptance test passes.
You check the finished system against the scope list. A set-up payment of ₹20K-50K at sign-off, deducted from the price, is the only payment before it. If it does not pass, we fix it and you test again.
- 04
Simple change requests.
The prototype fixes the scope and the price. Anything beyond it is priced as a fixed item before work starts and built only on your yes.
Changes
Changes along the way
Thought of something new along the way? A change request joins the build or follows it, your choice. Small ones are often free; we say which. A bug found in your acceptance test is never a change request. See example change requests on the pricing page.
Next step
It starts with a 30-minute call
Tell us what you need and who will use it. We say whether it is a fit and what the 3-day prototype will show. If software is the wrong answer, we say so on the call.