What we are on the hook for.

What this page is

A summary, written so you can read it in three minutes and know whether we are worth a call. It is not the contract. The executable terms are sent with any proposal, and they are the ones that govern. If the two ever disagree, the signed document wins.

We do not publish the contract itself because it is negotiated per engagement rather than offered as a standard form. Clients with procurement teams usually want their own paper anyway, and we are happy to work from it.

Who owns the work

You do. All deliverables, source code, designs and documentation are assigned to you on payment, without reservation. We keep no licence back and we do not retain a copy that would let us resell the work to someone else.

Two exceptions, both ordinary. We keep our own pre-existing tools and libraries, which you get a perpetual licence to use inside the delivered work. And anything we build on top of open source stays under that project's licence, which we tell you about up front rather than in the handover.

What we actually commit to

Every stage ends in a named artefact, listed in the process, and that artefact is yours whether or not the engagement continues. If we stop after discovery you leave with a system diagram and a costed plan another firm can execute.

We do not promise an outcome that depends on your market, your users or your funding. We promise the work, the people named in the proposal doing it, and honest reporting when it is going badly.

Payment

Fixed-scope work is invoiced in stages against the deliverables. Retained and embedded work is invoiced monthly in arrears. Net thirty from invoice date unless your procurement requires otherwise, in which case say so before we start rather than after the first invoice.

Prices are quoted in your currency and are what is written on the pricing page unless the proposal says otherwise. They move when the requirements move, which is covered on that page.

Changes to scope

Scope changes are normal and we do not treat them as a failure of planning. They are priced and agreed in writing before the work starts, not billed quietly at the end. If a change makes the original plan wrong, we say so.

Ending it

Thirty days notice, both directions, for any reason. The exit is written into the start so neither side is negotiating under pressure later. On termination you are invoiced for work completed to that date, you keep every artefact already delivered, and we hand over credentials, documentation and access within those thirty days.

Confidentiality

Both directions, surviving the engagement. We will sign your NDA. We do not name clients publicly without written permission, which is why the work page describes engagements without naming most of the companies.

Liability

Capped at the fees paid under the engagement, which is the standard position for professional services and the one your insurer will expect to see. Neither side is liable for indirect or consequential loss. Nothing in the contract limits liability for fraud, wilful misconduct, or anything that cannot lawfully be limited.

We carry professional indemnity cover. The certificate goes out on request for vendor review.

Data

Where an engagement means we process personal data on your behalf, the data processing agreement applies and forms part of the contract. It is not optional and we do not ask you to chase us for it.

Law

Governed by Indian law, with the courts of Bengaluru having jurisdiction, unless the engagement says otherwise. For clients in the EU, the United Kingdom or the United States we routinely agree to a different governing law where your procurement requires it. Ask early rather than at signature.

Questions

Write to [email protected]. A person reads it.

Last updated 24 September 2026. All legal documents.