How we work

We write the document
before the code.

Architecture, effort and regulatory mapping are settled and signed before development begins. That is why our estimates hold and scope disputes are rare.

DeliveryCommercialsAssurance

Delivery

Four phases, and working software every fortnight from the second one onward.

  1. 01

    First brief

    Day 1–3

    A deep-dive on constraints, not a sales call. We ask hard questions about your security requirements, existing stack, integration boundaries and what “done” actually means. By day three there is a shared, written understanding of the problem space — before a line of code is written.

    You getConstraint and risk map · scope agreement · signed NDA
  2. 02

    Technical alignment

    Week 1–2

    Kickoff involves your dedicated team — engineers, a project manager and senior technical oversight. We produce an architecture decision record covering every integration point, data flow and security boundary before production code begins.

    You getArchitecture record · effort estimate in person-days
  3. 03

    Sprint delivery

    2-week cycles

    Strict two-week sprints. You see working software every fortnight — not presentations, not mockups. Daily stand-ups catch blockers within 24 hours, and priorities can shift between cycles without renegotiating the contract.

    You getWorking software · release notes · 80% unit coverage floor
  4. 04

    Ongoing partnership

    Post-launch

    Most engagements run 12–24 months past launch. We embed as an extension of your team with SLA-backed uptime, monthly health reporting and engineers who already know the codebase. The EMSPL fleet partnership has been running 24 months.

    You getRunbook · training records · SLA, or a clean handover

Senior-led, not handed down

The people who scope the work stay accountable for it. You are not passed to a junior team after signature.

Dedicated, not benched

Engineers assigned to your project work only on your project for its duration. No marketplace, no rotating contractors.

Scale inside a sprint

A bench protocol keeps additional engineers current on your codebase, so a team can go from two to six without losing a cycle.

Estimates you can interrogate

Effort is stated in person-days against a named work breakdown. The custody platform resolved to 1,256 days across 26 weeks — auditable line by line.

Commercials

Four ways to work with us.

Model 01

Fixed-scope build

A defined system, a defined price, a defined date. The right shape for tenders and board-approved capital projects.

  • Person-day estimate published
  • Milestone-linked payment
  • Change control in writing
Model 02most common

Dedicated team retainer

A standing engineering team on a monthly fee, for platforms that keep evolving after launch. Joint IP available.

  • Monthly retainer, transparent rate
  • Rolling roadmap, no re-scoping tax
  • Typical term 12–24 months
Model 03

Sovereign deployment

On-premise or air-gapped AI delivered end to end, including hardware specification, installation and operator training.

  • Delivered inside your perimeter
  • Hardware sizing proven first
  • Offline update procedure documented
Model 04

Support & SLA

Take over an existing system. Stabilise it, document it, then run it against agreed response times.

  • Defined response windows
  • Infrastructure ownership included
  • Quarterly service review

What you own

All of it

Source code, schema, infrastructure definitions and documentation. An open-source base with no per-seat licence at the platform layer.

Where it is built

India, on your clock

Senior engineering at Indian day rates, working Indian Standard Time — which overlaps your working day rather than your night.

What happens after

Either outcome is normal

Support and enhancement under SLA, or a clean handover to your own team with the code and the runbook. We plan for both from day one.

Assurance

Regulatory posture is designed in, not retrofitted.

Our proposals carry a regulatory architecture section before they carry a price. These are frameworks we have already built against in live engagements — not a compliance page written for a website.

DPDP Act 2023 & DPDP Rules 2025

Consent capture, purpose limitation, data-principal rights and breach procedure designed into every India-facing platform. Full compliance due May 2027.

SEBI CSCRF 2024

Cyber security and resilience framework controls mapped for regulated financial-market intermediaries.

BSA 2023 — evidentiary standard

Event ledgers built to be admissible: immutable, hash-chained and independently verifiable.

DSGVO / GDPR and AVV

German and EU data-protection obligations delivered on live client work, including processor agreements.

Air-gapped operating procedure

Documented update, backup and incident procedure for installations with no network path in or out.

Personnel and IP control

Employee NDA and IP assignment with lifelong confidentiality on defence and government information.

Residency by schema

A tenant knows which jurisdiction it belongs to and where it may be processed. Building that on day one is an afternoon; retrofitting it is a rewrite.

The AI layer follows the same rule

If the record cannot leave the country, neither can the prompt containing it. We build the intelligence layer to run on a model you control as readily as a hosted one.

Exportability as a test

If you could not reconstruct your records and history from an export within one working day, it is a silo with an API page — not a platform you own.

These are frameworks we have designed and built against on live engagements. They are statements of engineering posture, not claims of third-party certification.

Send us the constraint. We will send back a scope.

A technical brief, not a sales call — and a concrete next step within four hours.

Start a conversation