Everything procurement asks, written down once.

The engagement page lists the deliverables in full before you pay, along with the stack, the working days, who it suits and what we need from you. Anything not on that list is not in the sprint, and we say so on the page rather than let you assume it.

Because a quote that depends on who is asking is not a price. The same sprint costs the same for a two-person startup and a listed company, and procurement can approve it without booking a call to discover the number.

Yes. Add as many as you need to your scope and pay once. Each sprint is planned and delivered separately, so a delay on one does not hold up the others.

It repeats the scope. Two units of a five-endpoint integration sprint covers ten endpoints; two units of a monthly managed support sprint covers two months. It does not stretch one sprint to cover more.

Ask before you buy. If your requirement sits inside the published scope we will confirm it in writing. If it does not, we will point you at the sprint that fits or scope the extra work separately. We will not quietly widen a fixed scope and then run out of room halfway through.

A ₹100 advisory session. An engineer reads what you have, answers in writing, and tells you which engagement — if any — is worth buying. Plenty of those end with us recommending nothing.

Yes, and most engagements run that way. We work inside your repository, follow your branch protection and review conventions, and release on your cadence rather than asking you to adopt ours.

Less than a discovery-led project. Expect an hour to complete the technical brief, whatever time granting access takes, and a short review at the end of each week. Anything more than that and we have scoped the sprint badly.

Only if you want them. Written updates go out on a fixed day each week whether or not there is a call, because a written trail is easier to forward than a recollection of a meeting.

We tell you before starting and either swap the engagement or refund it. Finding out mid-sprint that you bought the wrong thing is our mistake to absorb, not a change request to bill you for.

Yes. Delivery is remote and we overlap with European mornings and US mornings by arrangement. Invoicing and GST treatment differ for overseas clients — tell us where you are registered and we will confirm before you buy.

Code merged into your repositories, a written handover document covering architecture, decisions, runbooks and known gaps, and a recorded walkthrough you keep. If your own engineers cannot pick the work up without calling us, the sprint is not finished.

One round on every engagement, inside the window stated on the page. A revision refines what was delivered against the agreed scope. It is not a route to change the brief after the fact — if the brief genuinely changed, we will scope the extra work rather than absorb it silently.

You hear it before the date, with a revised date and the reason. If we miss a stated timeline without telling you first, the refund policy gives you a full refund.

The clock pauses and the delivery date moves by the length of the delay. Nothing is lost and nothing is charged extra. We will chase a couple of times, politely.

No, and treat anyone who does with suspicion. Outcomes depend on your market, your product and decisions we do not control. What we guarantee is the deliverables, the standard of work and the date printed on the engagement page.

Yes, free of charge at any point before kickoff. After work has begun, the refund depends on the stage reached and the refund policy publishes the exact percentages and timelines.

By UPI through a licensed payment gateway — GPay, PhonePe, Paytm, BHIM or any bank app. We never see or store card numbers, UPI PINs or banking credentials.

Yes, issued to the billing details entered at checkout and carrying our GSTIN. Add your registered business name, address and GSTIN there if you need input credit against the purchase.

Not for catalogue engagements — they are paid upfront, which is what keeps the fee fixed and the scope honest. For several sprints booked together, ask before checkout and we will tell you what is possible.

For companies that need a PO raised against an order, yes — write to us with the order details before paying. Standard catalogue checkout stays prepaid.

We acknowledge within 24 working hours, decide within 3 working days, initiate within 2 working days of that decision, and the money typically lands 5 to 7 working days later. Refunds always return to the original payment method.

Send the order number and the UPI reference. We reconcile against the gateway and either confirm the order or refund in full. Genuine duplicate charges are refunded without an assessment.

We use permissively licensed libraries by default and list every dependency and its licence in the handover document. If something copyleft is genuinely the right tool, we ask you first rather than discover it at audit time.

In your organisation, always. Repositories, cloud accounts, container registries, CI runners and licences are provisioned in your name from day one, so nothing has to be rebuilt if you stop working with us.

Least privilege, time-boxed, and revoked at handover. We ask for the narrowest permissions the work needs, use your SSO where you have it, and never accept credentials over chat or email.

Routinely. Send yours before or after checkout, or use our standard mutual NDA and a processing agreement covering DPDP Act obligations and equivalent GDPR terms.

Only where the engagement page says so and only with anonymised or masked data unless you insist otherwise in writing. Where production access is unavoidable, it is named, logged and time-limited.

Not without written permission. We may describe the shape of the work with no identifying detail. Tell us you would rather we did not and we will not.