How we work
Six steps from your first message to a site that is live. This page says what happens at each one, what we need from you, and what you have at the end of it.
It also covers the parts most process pages leave out: scope that changes after the price is agreed, and a date that slips. Those happen on real projects, and how they get handled tells you more than the happy path does. We work 9am to 6pm IST, Monday to Friday.
Discovery
You send a message through the contact form or on WhatsApp, and you get a reply within 24 hours. The first conversation is free and it is a fit conversation, not a pitch: what you are building, what you have already tried, and when you need it.
If we think the project is wrong for us, this is where we say so. Turning work down early is cheaper for you than discovering it late.
Fixed-price proposal
You get the scope written down and one flat number against it. The number does not move unless both of us agree in writing what changed. That is the whole point of quoting this way, and it is why the scope is written before the price rather than after.
Indian clients are quoted in rupees, paid by UPI, IMPS, NEFT or a Razorpay link. International clients are quoted the equivalent in USD and usually pay by Wise, which settles in rupees at a fee under one per cent. Stripe, SWIFT and PayPal also work.
Standard terms are 50 per cent before kickoff and the balance against milestones. We do not ask for 100 per cent upfront, and we do not start without the first payment. Work begins within three working days of it clearing.
If you need an NDA before we talk specifics, send your standard one and we will sign it within 24 hours.
Design
You approve screens before anyone writes production code. Moving a section in a design file takes minutes. Moving it in a built page takes days, and someone pays for those days.
This step needs things only you have: photographs, the service list, real prices, the logo. Most of it already exists somewhere in your business and has never been in one place.
Build
Git from the first commit and a staging URL you can open whenever you like. You do not have to ask what state the work is in, because you can look.
During a build you get a written update at the end of our day and one scheduled call a week. The written update matters more than the call, particularly if you are in North America, where our day ends before yours starts.
Launch
Deployment, DNS, SSL and analytics, then a handover. You get the repository, the credentials and a walkthrough with whoever will look after it.
The repository, the domain and the hosting account are in your name from day one, so handover is a conversation rather than a negotiation. Nothing is held as leverage for a retainer.
Growth
Optional, monthly, and cancellable. Updates, off-site backups with a restore that has actually been tested, uptime monitoring, security patching, and monthly reporting on what was fixed.
Changes go to staging first and keep a restore point, so a routine update cannot take your site down on a Friday afternoon.
When something goes wrong
It gets written down and re-priced before the work happens, not after. A fixed price only means anything if changes to it are visible, so a change you asked for on a call becomes a line you approve in writing.
You hear it in the written update that week, not at the deadline. Most slips come from feedback or content arriving late rather than from engineering, and the update says which it was.
You hear it before a contract rather than after. If a date can only be hit by running three workstreams in parallel, that is a different shape of team than a senior one working end to end, and pretending otherwise costs you a quarter.
One thing this page deliberately does not state: what counts as a round of changes. That varies by project and is written into your proposal, so quoting a single version here would be wrong for most readers. Ask on the first call and you will get a straight answer. See also how we keep client work secure and what the maintenance plan covers.