Straight answers, written down once.

Each engagement page lists the deliverables in full before you pay, together with the timeline in working days, the process, who it suits and what we need from you. Anything not on that list is not included, and the page says so rather than leaving you to assume.

Because a price that depends on who is asking is not really a price. The same engagement costs the same for every client, and your finance team can approve it without a sales call to find out the number.

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

It repeats the scope. Two units of an integration covering five endpoints cover ten endpoints; two units of a monthly support engagement cover two months. It does not stretch a single engagement to cover more.

Ask before you buy. If your requirement fits inside the published scope, we will confirm it in writing. If it does not, we will point you to the engagement 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 Tech Advisory engagement, from ₹100. You bring a question, a codebase or a cloud bill, and get a candid written answer, including which engagement, if any, is worth buying next.

Yes. We work inside your repositories, follow your branch protection and review conventions, and release on your schedule rather than asking you to adopt ours.

Enough to complete the brief, grant the access the engagement page lists, answer questions and review the work. Each engagement page has a "What we need from you" section so you can plan for it before you buy.

Only where the engagement includes a session, such as a walkthrough or training. Most of the work runs in writing, through the brief, review comments and handover material, which is easier to share internally than a recollection of a meeting.

If we realise the engagement you bought will not do the job, we tell you and either switch it or refund it. Finding out partway through that the scope was wrong should not become a change request you pay for.

In your client dashboard, if you check out with an account, which shows your orders, their status and payment details. Without an account, the track-an-order page shows an order's stage from its order number.

Delivery is remote, so location is not a barrier. Invoicing and GST treatment differ for organisations registered outside India, so tell us where you are registered and we will confirm how the invoice will be raised before you buy.

Once we hold your payment, your completed technical brief and the access listed on the engagement page. You can add a short brief at checkout; the full brief follows once payment clears. We confirm a delivery date at kickoff.

Whatever the engagement page lists. Typically that means code committed to your repositories and the documentation needed to run it, plus a walkthrough or training session where the page includes one. The aim is that your own team can take the work forward without us.

Some engagements include a revision round or a support window after handover, and their pages say so. For every engagement, anything in the published scope that is missing or materially wrong, and reported within 7 working days of handover, is put right at no charge.

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

The clock pauses and the delivery date moves by the same amount. Nothing is lost and nothing extra is charged.

No. Outcomes depend on your market, your product and decisions outside our control. What we stand behind is the deliverables, the standard of work and the date on the engagement page.

Yes, at no charge, at any point before work begins. After that, the refund depends on the stage reached, and the refund policy publishes the exact percentages.

Yes. Every price on the site is the final amount payable. Nothing is added at checkout, and your invoice shows the GST component separately.

By UPI, through a licensed payment gateway, using the UPI app you already have. We never see or store card numbers, UPI PINs or banking credentials.

Yes, issued to the billing details you enter at checkout. Add your registered business name, address and GSTIN there if you want to claim input tax credit.

Not for catalogue engagements. They are paid upfront, which is what keeps the fee fixed and the scope clear. If you are booking several engagements together, ask before checkout and we will tell you what is possible.

If your organisation needs a purchase order raised against an order, contact us with the order details before paying. Standard catalogue checkout is prepaid.

We acknowledge a refund claim within 48 hours and give you a written decision within one month, as consumer-protection rules require, and sooner wherever we can. Approved refunds go back to the original payment method, GST included; the final credit time depends on your bank.

Send us the order number and the UPI reference. We reconcile with the payment gateway and either confirm the order or refund you in full. Duplicate charges are refunded without any assessment.

You do. Once the fee is paid in full, everything produced specifically for your engagement, including source code, infrastructure definitions, designs and documentation, belongs to your organisation. We keep no right to resell it.

We prefer permissively licensed components, identify the third-party components we introduce at handover, and ask you first before using anything with copyleft obligations.

In your organisation. Repositories, cloud accounts, registries and licences stay in your name, so nothing has to be rebuilt or moved if you stop working with us.

We ask for the narrowest permissions the work needs, use your single sign-on where you have it, and expect access to be revoked at handover. Please do not send credentials over chat or email.

Yes. We are happy to sign a mutual NDA before you share a brief, and we agree a data processing agreement before any work that involves personal data your organisation controls.

Usually not. We ask for anonymised, masked or synthetic data by default. Where production access is genuinely unavoidable, it should be named, agreed in writing and time-limited.

Not without your written permission.