How we estimate a project in 30 minutes.
Estimates are not magic — they are two short questions, an internal model, and a number that costs you nothing.
Most agencies treat estimation like an auction. They ask for "your brief", disappear for a week, and return a proposal calibrated to what they think you can afford. We do the opposite.
A 30-minute call gives us enough signal to commit to a range. Here's the model.
Question 1 — What breaks if this ships late?
Cost of delay is the single biggest variable in software estimation. A marketing launch has a hard date. An internal dashboard doesn't. We calibrate everything else off this answer.
If nothing breaks when it slips, we charge less, and build more carefully. If something breaks — a compliance deadline, a PR cycle, a hiring decision — we over-staff the first two weeks and charge accordingly.
Question 2 — Who has decided what already?
A client with a Figma file and an approved architecture is 30-40% cheaper than a client with "we need a website". Not because the work is less, but because the decisions are already made. Ambiguity is where budget dies.
We ask for whatever decisions exist — even bad ones — because we'd rather argue with a bad decision than create one from scratch.
The internal model
We size projects in three axes:
1. **Scope** — number of distinct product flows (login, checkout, dashboard, admin, etc.) 2. **Integrations** — external systems our code has to talk to (payments, SMS, CRM, analytics) 3. **Uniqueness** — how much of this has someone already solved
Scope multiplies effort linearly. Integrations multiply risk — each one adds a week of slack. Uniqueness is where we either take a huge discount (if the pattern is solved) or charge a premium (if it isn't).
The number you get
After 30 minutes we send you three numbers: - **Minimum** — if decisions stay locked and scope doesn't creep. Happens ~15% of the time. - **Expected** — our honest bet. This is what we commit to in writing. - **Cap** — if you hit it, we absorb the rest. We've hit it twice in 14 years.
Plus a timeline range, stated in weeks not dates. And a one-page scope document that becomes the contract.
Why we do it this way
Because most clients have been burned by a proposal that said ₹X and delivered at 3X. We'd rather anchor at the expected and beat it than quote low and renegotiate mid-build.
You can book that 30-minute call from the contact page. No prep needed — just the two questions above in your head.