1. Home
  2. How we work
How we work

Six phases,
no surprises

We work in short, visible increments with a working system at the end of each one. You always know what you have and what is next.

01

Discovery and validation

2–4 weeks

We map the real workflow — who does what, on which device, with what network. We interview the CDDs and the store officers, not just the programme managers. Output: validated requirements, role and permission matrix, data model, and API specification.

02

Design

2–3 weeks

Interface design in Figma, reviewed with the people who will actually use it. We prototype the hardest screens first — the ones with conditional logic, offline states, and error handling. Output: clickable prototype and a design system.

03

Core build

8–16 weeks

Iterative delivery in two-week rounds. Every round ends with something you can log into and click. Geo hierarchy, users and roles, campaign setup, registration and treatment, stock movements, and the offline sync engine.

04

Field pilot

2–4 weeks

One or two LGAs, real devices, real distributors, real network conditions. This is where the assumptions get tested. We expect to change things here, and we budget for it.

05

Scale and harden

4–8 weeks

Load testing, database indexing and partitioning, queue monitoring, dead-letter handling, automated backups, and per-device rate limiting. The unglamorous work that decides whether a national rollout holds up.

06

Handover and capacity building

Ongoing

Train-the-trainer sessions, admin documentation, runbooks, and a support agreement. The goal is that your team can operate the system without us on the phone.

Ready to make your programme transparent, efficient, and accountable?

Tell us about the campaign, the geography, and the timeline. We will tell you honestly whether we are the right fit.