Delivery Policy

We do not sell physical goods. There is no warehouse, courier, tracking number or PIN code serviceability check. Every engagement is delivered electronically, and most of the work is delivered directly into systems you own rather than sent to you as files.

• Code is pushed to a branch in your repository and goes through your review process.
• Infrastructure is provisioned in your cloud account and defined in code stored in your repository.
• Pipelines, dashboards, registries and test suites are set up under your organisation and billed to your accounts.
• Documents, design files and recordings are sent by email and added to the order in your dashboard.

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

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

Each service page states a turnaround in working days. It starts only when all three of the following are in place:

1. The payment gateway has confirmed your payment.
2. You have submitted your complete technical brief.
3. The access listed on the service page has been granted and is working.

Engineers are assigned and work begins within 3 working days of that point, and we confirm a firm delivery date on the first day. A working day is Monday to Saturday, excluding public holidays observed at our registered office.

If the brief is incomplete, we will send you specific questions. The turnaround does not start until the brief is complete, and we will tell you clearly that it has not yet started.

The ranges below are a guide for planning. The turnaround that applies to your engagement is the one stated on the service page you bought.

Buying several units of the same engagement extends the turnaround proportionally. We will confirm the combined delivery date before you pay.

Handover is a defined step with three parts. An engagement is complete only when all three have been provided.

• The work, in your repositories. Commits are pushed to a branch in your repository and opened as a pull request against your default branch, following your commit conventions and passing your checks. Infrastructure is applied to your cloud account from code in the same repository. You review and merge the work; we merge to your main branch only if you ask us to.
• The written handover document. A single document, stored in the repository, covering what was built and why, the architecture and the decisions behind it, how to run and deploy it, environment variables and secrets and where they are stored, a runbook for the issues most likely to arise, every third-party dependency and its licence, and known gaps with recommended next steps.
• The walkthrough recording. A screen recording in which the engineer who built the work takes your team through the code and the runbook. You keep it and can share it with future team members. Where the service page includes a live session instead, that session is recorded and handed over as well.

The handover pack and the same links are also available on the order page in your dashboard, so access does not depend on a single email.

Our standard is that your own engineers should be able to take over the work without needing to contact us. If they cannot, the engagement is not complete.

The turnaround pauses while we are unable to proceed for one of the reasons below. The delivery date moves by the length of the pause, and there is no extra charge.

• 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 we asked for have not been provided.
• A decision or approval is pending 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 a 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 we give you a revised date once the issue is resolved. We will send reminders. If we are still waiting 30 days after our request, the suspension and termination clause in our Terms of Service applies.

If an engagement falls behind because of us, the person doing the work will tell you before the delivery date, with the reason and a revised date.

• If we notify you before the date, the engagement continues to the revised date, or you can cancel and receive a refund based on the stage reached.
• If we do not notify you before the date, you are entitled to a full refund of the fee under our Refunds & Cancellation policy.
• Delays caused by a force majeure event are handled under the force majeure clause in our Terms of Service, and we will still keep you informed.

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

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

Acceptance is assessed against the scope, not personal preference. If the work does what the service page described, it has been delivered. If you want it to do something different, that is a change request, which we will quote separately.

Every engagement includes one revision round, available within the window stated on its service page. Unless the service page says otherwise, the window is 15 days from handover.

• Send all revision points together in one list; separate notes slow the process down for everyone.
• A revision refines the delivered work against the agreed scope through corrections and adjustments.
• Anything that changes the brief is a change request. We quote it separately and do not start it until you agree in writing.
• Revision work is scheduled within 5 working days of receiving your list and is not placed behind new orders.

Support in the period immediately after handover is included at no extra charge.

Questions are answered during our support hours, Mon–Sat, 09:30–19:00 IST. If you need regular ongoing help, a monthly Managed Support engagement is the appropriate option, and we will recommend it where it fits.

Our access to your systems is revoked at handover as standard. If you would like us to keep a time-limited read-only account during the support period, let us know and we will record the arrangement.

Because delivery is remote, there is no restricted service area, and we can deliver to clients in India and elsewhere. Your PIN code is collected only so that we can issue a correct GST invoice, never to decide whether we can deliver to you. All work and documentation is provided in English.

• Access is requested at the lowest permission level the work needs, through your own single sign-on where available.
• We never accept credentials by chat or email. Please use a secrets manager, or invite the people working on your engagement directly.
• Access sessions are logged, limited in time and revoked at handover.
• We prefer anonymised, masked or synthetic data. Where production access cannot be avoided, it is granted to named individuals, agreed in writing and limited in time.

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