From requirement to handover.
The process from an initial requirement discussion through to handover. No commitment is required from the department until the scope note has been reviewed.
-
01
Requirement discussion
A meeting at your office to understand the mandate, the users and the constraints — existing systems, data, and who will operate it day to day.
No cost -
02
Written scope & estimate
A scope note with deliverables, timeline and cost, in a form that can be placed on file and approved internally.
Typically within a week -
03
Work order
The scope note forms the basis of the work order. Handover, training, audit and support terms are recorded in it.
In your format -
04
Build with review checkpoints
Progress is demonstrated at agreed intervals so the department can review the system during development.
Reviewed during development -
05
Security audit
Pre-go-live VAPT by a CERT-In empanelled auditor, with findings closed and re-tested before the system opens to the public.
Prior to launch -
06
Training & handover
Staff training, user and administrator documentation, followed by handover of source code, database and deployment details. The support window then begins.
Handover on completion
Information required for a scope note.
- The mandate — what the system must achieve, and under whose authority
- Who uses it — citizens, department staff, field officers, or all three
- Any existing system or data that must be carried forward
- Hosting expectation — state infrastructure, departmental, or ours to arrange
- Language requirement — English, Telugu, or both
- Any deadline the work is tied to
If any of the above is not yet decided, it can be settled during the initial discussion.
11/2, Arundelpet, Guntur, Andhra Pradesh 522001
Explore the rest.
What we build
Citizen portals, departmental MIS, dashboards and field apps
Read more →Standards & compliance
GIGW 3.0, WCAG 2.1 AA, DPDP Act and the OWASP Top 10
Read more →Public sector delivery
The departments and agencies we work with
Read more →Our commitments
Source handover, training and defined post-launch support
Read more →Accessibility statement
Our WCAG 2.1 AA conformance and the limitations we know about
Read more →