How we work
A month here ships what used to take a quarter.
We build AI-first: agents do the typing, we do the thinking, and you see working software every few days instead of a status report. The rate is per unit of time because the unit is predictable. What fits inside it is what has changed.
The way a project runs
Day 1 and Day 21 are fixed. In between, working screens land every few days.
Day 1
Discovery
We come to you, photograph the registers, sit with the person who does the job, and fix the scope in writing: what is in, what is out, what "done" means.
Days 2–15
Build, in the open
Working screens land every few days on your real data, not mock-ups. You use them while we build the next ones. Agents write most of the code; every line is reviewed before it reaches you.
Days 10–18
Iterate
Your feedback is folded in while it is cheap. A screen that needs explaining gets redesigned, not documented.
Day 21
Handover
Tests, deployment where you chose, training (with short videos per screen), and the source code on a perpetual licence: yours to run, for good.
Why a month goes so far
Nothing here is a trick. It is the same work, with the slow parts removed.
Agents write, we direct
Most code is written by AI coding agents working in parallel, each on its own branch, under rules we have refined on every project. One person directs; the output is a team's.
We do not start from a blank page
We reuse the parts we have already built for other systems: login, roles, audit trail, email, files, Tally posting, dashboards. The month is spent on what is yours.
No hand-offs
The person who walked your floor is the person who designs the screen and reviews the code. Nothing is lost between a salesperson, a manager and a developer.
Real data from week one
Your history is imported early, so every screen is judged on your numbers. Surprises appear in week two, not at launch.
Agents write, we direct
Most code is written by AI coding agents working in parallel, each on its own branch, under rules we have refined on every project. One person directs; the output is a team's.
We do not start from a blank page
We reuse the parts we have already built for other systems: login, roles, audit trail, email, files, Tally posting, dashboards. The month is spent on what is yours.
No hand-offs
The person who walked your floor is the person who designs the screen and reviews the code. Nothing is lost between a salesperson, a manager and a developer.
Real data from week one
Your history is imported early, so every screen is judged on your numbers. Surprises appear in week two, not at launch.
Pricing
What a month buys
1 day
₹35,000
A day-sized problem: a launch page, an automation, a fix nobody could find.
A real exampleA launch site with a 3D logo and a playable game, built and launched in one day for a preschool expo.
1 week
₹1,50,000
A very small project: a client portal, a practice site with booking, a rebuilt app.
A real exampleA consultancy's financial platform rebuilt end to end and switched over with years of records.
2 weeks
₹2,75,000
A small project: one automation pipeline, measured on your real files, in production.
A real exampleBank statements read and classified into ledgers, with a partner's review screen.
3 weeks
₹3,90,000
A mid-sized project: a storefront with inventory and order flows, or a department's system.
1 month
₹5,00,000
The MVP: a business system with a dozen or more modules on your data, in production.
A real exampleA factory ERP: production logs, stores, QC, dispatch, Tally posting and the owner's dashboard.
Month 2
₹4,50,000
Same project, continued: the next modules, integrations, machines, mobile.
Month 3+
₹4,00,000
Per month, onward. Most systems are complete in two to three.
₹23,800 per working day
That is the month divided by its 21 days. Compare it with the cost of the hours your own people spend on the work the system replaces.
Terms, in plain words
- The unit
- One month is 21 working days, Monday to Friday. Prices are in INR and exclude taxes.
- Payment
- The first three weeks are paid before work starts; the rest is invoiced at go-live for time actually used. No overrun is billed without your written yes.
- Licence
- Everything ships on a perpetual licence. You can run it, host it, and hand it to another developer. Reusable modules stay ours to reuse elsewhere; your data and your unique workflows are yours.
- After go-live
- Optional AMC at 20%: updates, monitoring, tickets tracked until closed. Without it, the system keeps running; you pay per day when you need us.
- Scope
- Scope and the delivery plan are written down together before work starts. Changing it mid-way is fine; it is a conversation, not a penalty.
- What is not included
- Third-party fees (hosting you choose, SMS, payment gateways, AI model usage, marketplace charges) are passed through at cost. Hardware is quoted separately.
Hourly, for advice and short work
Booked in blocks of five hours: an AI setup for your team, a review of a system someone else built, a decision you want a second opinion on.
₹5,000 per hour
Questions
Why not a fixed price for the whole project?
Because the honest unit is time, and the thing that changed is how much fits in it. A fixed price hides a guess about scope; a month shows you working software every few days and lets you stop or continue at each one.
What if it takes longer than a month?
Most business systems take two to three months to be complete; the first month is the working version you can already use. Continuation months are cheaper, and nothing beyond the agreed plan is billed without your yes.
Who actually does the work?
Prerak, with AI coding agents under his direction. There is no account manager and no hand-off. That is why discovery and the code review are done by the same person.
Do we own the code?
You hold a perpetual licence to everything delivered, with the source. You can host it anywhere and hand it to anyone. The reusable building blocks remain ours to reuse; your data and your specific workflows are yours alone.
What happens if you are unavailable?
The source, the documentation and the deployment scripts are yours from day one, so another developer can continue. For hosted systems, backups are tested weekly and an export is available on request.
Tell us what needs solving.
Three minutes, four questions. You will hear from Prerak himself, usually within a working day.