The questions procurement asks, answered in advance.

How a project actually runs

The same delivery model whether the client is a government department or a product team. It is deliberately unglamorous: the point is that nobody is ever surprised.

• A named delivery lead owns the engagement end to end, and is reachable directly.
• Weekly working demo against a shared plan — not a status report, a running system.
• Written architecture decisions before build, so choices are reviewable rather than discovered later.
• Staged environments with client-side sign-off before anything reaches production.
• A defined escalation path with response times, published at kick-off rather than negotiated during an incident.

Controls, evidence and residency

Security has its own page, because a summary is not what a vendor assessment needs. It states our certification position plainly, walks the layers and the development lifecycle, shows who can reach data at each stage of its life, and names the evidence we can produce for every control.

• Named accounts only, least privilege, time-bound elevation approved by a second person.
• Encryption in transit and at rest; secrets in managed key stores, never in source.
• Data residency and retention agreed in writing before build, honoured in the deployment.
• Immutable audit logging on privileged and record-affecting actions.
• Full controls register and incident severity model: see the Security page.

Accessibility & standards

Public-facing government work is built to be usable by everyone who is entitled to use it, on the devices they actually have.

• GIGW-aligned delivery for Indian government public-facing surfaces.
• WCAG 2.1 AA as the working target for everything else.
• Multilingual delivery treated as a content-model decision, not a translation layer.
• Tested on low-bandwidth connections and older Android devices.

Ownership, handover and exit

Every institutional buyer fears vendor lock-in more than they fear a high price. So we remove the fear rather than argue about it.

• The client owns the source code and the infrastructure accounts.
• Documentation and runbooks are deliverables, not favours.
• Handover to an in-house or third-party team is a defined, priced process.
• No proprietary runtime that only we can operate.

Support & service levels

Agreed per engagement. For systems that operate during live legislative sessions, support is scheduled around the sitting calendar.

• Response and resolution targets set by severity and agreed in the contract.
• On-call coverage aligned to when the system is actually used.
• Session-day readiness for platforms that operate during live proceedings.
• Incident review and written post-mortem after any severity-one event.