Four steps. One fixed price.
You know the scope, the price and the launch date before we write a line of code. After that you get working software on a live link every week — not a status report, not a percentage.
From your first message to go-live.
Every project runs the same four steps. The only things that change are the platforms we ship to and how long step three takes.
Send your requirement
A WhatsApp message is enough. We reply with the questions that actually matter.
Same dayScope & fixed quote
A written scope, the platforms we ship to, a fixed price and a launch date.
Within 48 hoursDesign & build
Clickable screens first, then weekly builds on a live link you can test as we go.
Weeks 1–5Launch & handover
Store release, hosting, code, accounts, training — and 30 days of fixes on us.
Launch weekWhat actually happens in each step.
What we do, what we need from you, and what you hold at the end of it.
Send your requirement
A WhatsApp message, an email or the form on the contact page — all three arrive in the same place. You do not need a specification, a wireframe, or a decision about which technology to use. A paragraph about the problem is enough to start.
We read it the same working day and reply with questions. They are short and specific: how many people will use this, what has to happen when someone pays, which of your existing tools it has to talk to. The point is to find the handful of details that decide the price, not to make you fill in a forty-field brief.
If your requirement is something we should not take on — the wrong size for us, or better solved by software you can simply buy — we say so in the first reply. It costs us an hour and saves you a month.
- We read your message and reply the same working day
- You get five to ten questions back, plus a rough price range
- A twenty-minute call, on WhatsApp or Google Meet, if talking is faster
- You provide: what the software has to do, who will use it, and any date you are working to
- You provide: the names of the tools it has to connect to, if you already know them
Send your requirement
- Duration Same day
- You provide A paragraph and a deadline
- You receive Questions and a price range
- Sign-off None — nothing is committed
Scope and fixed quote
Within two working days you get a written scope. It lists every screen, every user role, every integration and every platform we will ship to. Just as usefully, it lists what is not included, so the boundary is on paper rather than in someone's memory.
The price is fixed against that scope. Not an hourly rate, not a range that drifts upward, not an estimate that grows once we open the code. If we misjudge the effort, absorbing it is our problem — which is exactly why we spend two days getting the scope right instead of two hours.
Payment is split across the project: 40% to begin, 30% when you approve the design, 30% on handover. The scope and the quote themselves cost nothing, and you are under no obligation once you have them.
- A written scope — screens, roles, integrations, platforms, and the exclusions
- A fixed price and a launch date, both held for 30 days
- A payment schedule of 40 / 30 / 30, invoiced with GST
- You provide: your content, logo and brand files, or a decision to have us design them
- You provide: one person on your side who can approve the scope
Scope and fixed quote
- Duration Within 48 hours
- You provide Content, brand files, one approver
- You receive Written scope and fixed price
- Sign-off You approve the scope in writing
Design and build
Design comes first, as clickable screens rather than flat pictures. You open a link, tap through the real flow on your own phone, and tell us what is wrong while changing it still costs nothing. No code gets written until those screens are approved.
After that you get a working build every week on a live link. Not a progress bar, not a screenshot in a slide — software you can log into and use, with your own content in it. Your feedback on one build goes into the next one, and anything outside the agreed scope is priced before we touch it.
How long this step takes depends on what you are building. A website is usually two to three weeks here, a mobile app or a CRM four to six. We tell you which of those you are in when we send the quote, not halfway through.
- Clickable design screens before any code is written
- A working build on a live staging link every week
- Change notes, priced and dated, for anything outside the scope
- You provide: feedback within two working days of each build
- You provide: real content, test data and access to any system we integrate with
Design and build
- Duration Weeks 1–5
- You provide Weekly feedback, real content
- You receive Design link, then weekly builds
- Sign-off You approve the design before build
Launch and handover
Launch week is a checklist, not a leap. We test on real devices, set up hosting and domains, submit to the App Store and Play Store where that applies, and walk the whole flow once more with you before anything goes public. Store review adds a few days that nobody controls, so we submit early and say so in the plan.
Then everything is handed over. The source code goes into a repository under your account, hosting and third-party services move into your name, and we record short training videos for the people who will use the system daily. There is no piece we hold back to keep you dependent on us.
For 30 days after launch we fix anything that does not work the way the scope says it should, at no cost. After that, support is optional and quoted separately — a monthly retainer if you want one, or pay-as-you-go if you would rather call only when something needs changing.
- Real-device testing, hosting, domain setup and store submission
- Source code in a repository you own, transferred at handover
- Hosting, analytics, domain and store accounts all in your name
- Short training videos for your team, plus 30 days of fixes
- You provide: domain access, and developer account details if you already hold them
Launch and handover
- Duration Launch week
- You provide Domain and account access
- You receive Code, accounts, training, 30 days of fixes
- Sign-off You confirm launch, then we hand over
Four things that go in writing.
Not promises on a page. Each of these is in the scope document you approve before the work starts.
The things clients ask before they start.
Nothing for the scope and the quote — you can take both and walk away. Once you approve the scope, 40% starts the work, 30% falls due when you sign off the design, and the final 30% on handover. We invoice with GST and accept bank transfer or UPI. On smaller projects we usually split it in two rather than three, because three invoices for a two-week job helps nobody.
Small changes inside the agreed scope — wording, colours, an extra field on a form — are simply part of the work. Anything that adds a screen, a user role or an integration gets a short written change note with its own price and its effect on the launch date, and you approve it before we build it. Nothing gets added silently, and nothing gets dropped silently either.
You do. At handover the source code sits in a repository under your account, along with the design files, the database and the accounts. We keep no licence over it and no switch that turns it off. If you decide to work with another studio a year from now, everything they need is already in your hands — that is the point of handing it over properly.
You get 30 days of fixes at no cost for anything that does not behave the way the scope specified. After that, support is optional. Some clients keep a monthly retainer for updates, monitoring and small changes; others call us only when they want something new and pay for that piece of work. We do not require a retainer to keep your software running, because it runs on your own accounts.
If the delay is ours, the fixed price does not move, and you hear the new date as soon as we know it rather than in the final week. If it comes from your side — content, approvals, or access to an account we are waiting on — we say so at the time and the date moves with it. App store review is the one variable neither of us controls, so we submit early and leave room for it in the plan.
Send us the paragraph.
Tell us what the software has to do and when you need it live. You get questions back the same working day and a written scope with a fixed price within 48 hours.