Delivery & Handover Policy

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

• 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, billed to you.
• Documents and design files are sent by email and made available on the order in your dashboard.

This means nothing has to be migrated or rebuilt if you stop working with us after handover, and no licence is held in our name.

The amount at checkout is the full amount. Nothing is added at handover: no rush fee, per-seat charge or expenses.

Each engagement page states its timeline in working days. That timeline starts only when all three of the following are true:

1. the payment gateway has confirmed your payment;
2. your project brief has been submitted in full;
3. the access listed on the engagement page has been granted and works.

We confirm a delivery date once work begins. A working day means Monday to Saturday, excluding public holidays observed at our registered office.

If the brief is incomplete, we will come back with specific questions rather than make assumptions, and we will tell you clearly that the timeline has not yet started.

The ranges below are taken from the timelines published on our current engagement pages, to help you plan. The timeline that applies to your order is the one printed on the engagement page you bought.

Buying several units of the same engagement extends the timeline proportionally. Ask us for the combined date before you pay.

Handover is a defined event. An engagement is complete when both of the following have been provided.

• The work itself. For code, commits are pushed to a branch in your repository and opened as a pull request against your default branch, following your conventions and 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. Other deliverables, such as designs, reports or documents, are provided in the format the engagement page describes.
• Written handover notes. A document covering what was built and why, the architecture and key decisions, how to run and deploy it, where configuration and secrets are kept, what to do when the most likely things break, third-party dependencies and their licences, and known limitations with suggested next steps.

Where an engagement page includes a walkthrough session, it is scheduled as part of handover and, where recorded, the recording is shared with you.

The handover material is also linked from the order in your dashboard, so it does not depend on a single email. Our aim is that your own team can pick up the work without needing to call us.

The timeline pauses while we are blocked, and the delivery date moves by the length of the pause at no extra charge. Common reasons include:

• access we requested has not been granted, has expired, or lacks the permissions the work needs;
• an environment we were told about does not exist, is broken, or cannot be reached;
• test data, credentials, design files or content we listed 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 holding things up — for example a cloud quota increase, vendor approval, domain transfer or app-store review;
• you have asked us to pause, for any reason.

When the timeline pauses, we tell you the same working day, say what we are waiting for, and give a revised date once it is resolved. If we are still waiting 30 days after asking, the suspension clause in our Terms of Service applies.

If an engagement slips because of us, you will hear about it before the date, not after, 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, our Refund & Cancellation Policy gives you a full refund.
• Delays caused by a genuine force majeure event are handled under our Terms of Service, and we will still tell you.

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 within the scope is missing or materially wrong. We will fix it at no charge as part of the same engagement.
• If you raise nothing in that period, or you put the work into production use, the engagement is treated as accepted.
• Acceptance does not shorten any revision window, nor the 15-day defect remedy in our Terms of Service.

Acceptance is measured against the scope. If the work does what the engagement page describes, it has been delivered; if you would like it to do something different, that is a change request, which we will quote separately.

Where an engagement page includes a revision round, it is available within the window stated on that page — or within 15 days of handover if the page does not state one.

• Please send revision requests as one consolidated list.
• A revision refines what was delivered against the agreed scope: corrections and adjustments.
• Anything that changes the brief is a change request. We quote it separately and start nothing until you approve it in writing.
• Revision work is scheduled within 5 working days of receiving your list.

Questions are answered during our business hours. If you need ongoing rather than occasional help, a monthly managed-support engagement may suit you better, and we will say so.

Our access to your systems should be revoked at handover. If you would like us to keep time-limited, read-only access during the support period, tell us and we will record it in writing.

Delivery is remote, so there is no serviceable area. We work with clients across India and, by arrangement, abroad. Your PIN code is collected to issue a correct GST invoice, not to decide whether we can deliver to you. All work and documentation is in English.

• Access should be granted at the minimum permission level the work needs, through your own single sign-on where available.
• Please do not send credentials over chat or email. Use a secrets manager, or invite the assigned people directly.
• Access should be time-limited and revoked at handover.
• We prefer anonymised, masked or synthetic data. Where access to production data is unavoidable, it should be named, agreed in writing and time-limited.

Invoicing and GST treatment differ for clients outside India. Tell us where you are registered before you buy and we will confirm how the invoice will be raised.