Guarantees

Clear commitments, in writing.

These are the process commitments we work to on every engagement. Each one states what it covers and where its limits are, so expectations are agreed before work begins.

The signed proposal and statement of work set the binding terms for an engagement. This page explains the commitments we bring to that agreement. If a point matters to your organisation, ask us to confirm it in writing before you sign.

A written fixed quote before work starts

You receive a written fixed quote before any billable work begins.

The quote itemises scope, deliverables, assumptions, and exclusions.
Work starts only after you approve the quote in writing.
If discovery changes the scope, we issue a revised quote before any extra work.
The quote and its approval are kept with the project record.

Applies to: All services

Milestone-based payments

Invoices follow agreed delivery milestones rather than a single upfront payment.

Each milestone has a defined deliverable and a stated amount.
You are billed when the milestone is reviewed and accepted.
The payment schedule is written into the quote before work starts.
Ongoing retainers are billed monthly in advance unless agreed otherwise.

Applies to: All services

You own the code and intellectual property

On final payment, ownership of the custom code and project deliverables transfers to you.

Ownership transfers when the agreed fees have been paid in full.
Third-party libraries and tools remain under their own licences.
We keep no licence to reuse your proprietary code.
A written intellectual property assignment can be included in the contract.

Applies to: All services

Code in your repository from day one

Project code is committed to a repository you own from the first working day.

You keep administrative access to the repository throughout the project.
We work on branches and submit changes for review.
Commit history remains available to your team.
Where you prefer, we use your GitHub, GitLab, or Bitbucket account.

Applies to: All services

A 30-day defect-fix window after launch

For 30 days after launch, we fix defects against the agreed scope at no additional cost.

A defect is delivered work that fails the written acceptance criteria.
The window starts on the agreed launch date.
New requirements and changes to agreed scope are quoted separately.
Reports should include steps to reproduce and the affected environment.

Applies to: All services

Support response targets for maintenance clients

Maintenance clients receive a first response within one business day, and critical issues the same business day.

Support hours are Monday to Friday, 10:00 to 18:00 IST, excluding public holidays.
Critical means a production outage or a security issue with no workaround.
The target is a first response, not a resolution time.
Issues are triaged against the agreed scope and support plan.

Applies to: Maintenance & Support

No lock-in and a full handover

You can end the engagement at the end of any milestone and receive a complete handover.

Handover includes repository access, deployment documentation, credentials, and open tasks.
Outstanding milestone fees remain payable for work completed.
We do not withhold code or access to force a renewal.
Reasonable transition support can be agreed in writing.

Applies to: All services

Written change requests with a price before work

Every change is documented with its price and timeline before work begins.

Changes are described in a short written request.
You receive the impact on price and timeline before approving.
Work on a change starts only after written approval.
Approved changes are added to the agreed scope and milestone plan.

Applies to: All services

An NDA on request

We sign a reasonable non-disclosure agreement before detailed discussions when you ask.

We can review and sign your standard NDA.
Alternatively, we can provide a mutual NDA for review.
We keep project information confidential whether or not an NDA is signed.
The signed agreement governs and prevails over this summary.

Applies to: All services

FAQ

Questions about the commitments

How the commitments interact with the contract, defects, timelines, and support.

Are these commitments part of the contract?

These are the commitments we work to. The signed proposal and statement of work set the binding terms, and we include the relevant commitments in writing at the start of an engagement. Ask us to confirm any point before you sign.

What counts as a defect?

A defect is delivered work that fails the acceptance criteria agreed in writing before build. New ideas, changed requirements, and work outside that scope are change requests, quoted before any work begins.

What happens if a project runs late?

We share a milestone plan and weekly progress updates so delays surface early. If scope or feedback changes the timeline, we agree a revised plan in writing. The typical timeline is a planning range, not a promise.

How do I raise a support issue?

Maintenance clients receive a support contact and written process at handover. Send the issue with steps to reproduce and its impact. We acknowledge within one business day, and the same business day for critical production issues.

Ask before you sign.

If a commitment needs to be adapted to your procurement or compliance process, raise it early. We will confirm what can be agreed in writing.

Talk to us See the process