Delivery & Handover

Nothing sold on this site is a physical good. There is no courier, no tracking number and no PIN code serviceability check. Every engagement is delivered electronically, and most of it is delivered into systems you already own rather than sent as files.

• Code is pushed to your repository, on a branch, through your review process.
• Infrastructure is provisioned in your cloud account, defined in code kept in your repository.
• Pipelines, dashboards, registries and test suites are set up under your organisation, with billing in your name.
• Documents, design files and recordings are sent by email and made available on the order in your dashboard.

As a result, if you stop working with us after handover, nothing needs to be migrated, re-provisioned or rebuilt, and no licence is held in our name.

The amount at checkout is the full amount. Nothing is added at handover, and there are no rush fees, per-user charges or expenses.

Each engagement page states its turnaround in working days. The turnaround starts only when all three of the following are in place:

1. The payment gateway has confirmed your payment.
2. Your technical brief has been fully submitted.
3. The access listed on the engagement page has been granted and works.

Kickoff follows within 3 working days of that point, and we confirm a delivery date at kickoff. A working day means Monday to Saturday, excluding public holidays observed at our registered office.

If the brief is incomplete, we will come back to you with specific questions rather than make assumptions. The turnaround has not started at that stage, and we will make that clear.

These ranges reflect the durations published across the current catalogue and are provided to help you plan. The turnaround that applies to your order is the one stated on the engagement page you bought.

Buying several units of the same engagement extends the turnaround proportionally. We will confirm the combined date before work begins.

Handover is a defined event with three parts. An engagement is not complete until all three are in place.

• The work, in your systems. Commits are pushed to a branch in your repository and opened as a pull request against your default branch, following your conventions and passing your checks. Infrastructure is applied to your cloud account from code in the same repository. You review and merge; we do not merge to your main branch unless you ask us to.
• The written handover document. A single document in the repository covering what was built and why, the architecture and key decisions, how to run and deploy it, configuration and where secrets are held, a runbook for the most likely failures, each third-party dependency and its licence, and known gaps with suggested next steps.
• The walkthrough recording. A screen recording that takes your team through the code and the runbook, for you to keep and share with future team members. Where the engagement page includes a live session instead, that session is recorded and handed over.

The order page in your dashboard holds the handover material and links, so nothing depends on a single email.

The standard we work to: your own team should be able to take over the work without needing to contact us.

The turnaround pauses while we are blocked by something outside our control. The delivery date then moves by the length of the pause, at no extra charge. Examples include:

• access we requested has not been granted, has expired, or does not have the permissions the work needs;
• an environment we were told about does not exist, is not working, or cannot be reached from outside your network;
• test data, credentials, design files or content listed on the engagement page have not arrived;
• a decision or approval is waiting with you, and we cannot reasonably proceed on an assumption;
• a review request has been open for more than 7 working days;
• a third party is causing the delay, such as a cloud quota increase, a vendor approval, a domain transfer or an app-store review;
• you have asked us to put the work on hold, for any reason.

When the turnaround pauses, we tell you the same day what we are waiting for, and confirm the revised date once the issue is cleared. If we are still waiting 30 days after asking, the suspension clause in the Terms of Service applies.

If an engagement is running late on our side, we tell you before the delivery date, not after it, with the reason and a revised date.

• If we told you before the date, the engagement continues to the revised date, or you can cancel and receive a refund for the stage reached.
• If we did not tell you before the date, you are entitled to a full refund under the Refunds & Cancellation policy.
• Delays caused by a force majeure event are handled under the Terms of Service, and we will still let you know.

An engagement is delivered when every deliverable on its page has been handed over as described in section 5. From that point:

• you have 7 working days to tell us in writing that something in the scope is missing or materially wrong, and we will correct it at no charge as part of the same engagement;
• if you raise nothing within that period, or you put the work into production use, the engagement is treated as accepted;
• acceptance does not shorten the revision window in section 9 or the 15-day defect remedy in the Terms of Service.

Acceptance is measured against the published scope. If the work does what the engagement page described, it is delivered. If you need it to do something else, that is a change request, which we will quote separately.

Every engagement includes one revision round, available for the window stated on its page, which is 15 days from handover unless the page says otherwise.

• Send the revision round as one consolidated list.
• A revision adjusts what was delivered to match the agreed scope: corrections and refinements.
• Anything that changes the brief is a change request. We quote it separately and start nothing until you agree in writing.
• Revision work is scheduled within 5 working days of receiving your list, ahead of new orders.

Support continues for a defined period after handover, at no extra charge.

Questions are answered during our support hours: Mon–Sat, 09:30–19:00 IST. If you need ongoing rather than occasional help, a monthly managed support engagement is the appropriate option, and we will tell you if that is the case.

Our access to your systems is removed at handover as standard. If you would like us to keep time-limited, read-only access for the support period, tell us and we will record it in writing.

Delivery is digital, so there are no serviceable areas. Your PIN code is collected only to issue a correct GST invoice, not to decide whether we can deliver to you. All work and documentation is provided in English.

• We ask for access at the narrowest permission level the work needs, through your own single sign-on where available.
• Please do not send credentials by chat or email. Use a secrets manager, or invite the people working on the engagement directly.
• Access is time-limited and removed at handover.
• We prefer anonymised, masked or synthetic data. Where access to production data is unavoidable, it is agreed in writing and time-limited.

Invoicing and GST treatment differ for clients outside India. Tell us where your business is registered before you buy, and we will confirm how the invoice will be issued.

The Terms of Service, governed by the laws of India, apply to every engagement delivered under this policy.