NGO management systems
Programme management, beneficiary records, field data collection and donor reporting — designed to work where connectivity does not.
The challenge
Field teams collect on paper or on a phone with no signal, and the data reaches the office weeks later.
Donor reporting has a fixed deadline and a fixed format, so the last week of every cycle is spent transcribing rather than checking.
How we approach it
Start from the reporting format
Work backwards from what the donor requires.
Design offline first
Sync is the second concern, not the assumption.
Validate at collection
Catch the error in the field, not in the office.
Train on real devices
The handset field staff actually carry, not a demo tablet.
The same four phases, whatever we are building.
- 012–3 weeks
Discovery
We map your current process, users and constraints, then define scope in writing.
- 022–4 weeks
Design
Interface and data design, reviewed with the people who will use the system daily.
- 036 weeks+
Build
Delivery in two-week increments, each one testable, with progress visible throughout.
- 04Ongoing
Launch & support
Deployment, training and documentation, then optional support at a level you choose.
What you get
- Offline-capable forms with validation on the device.
- Conflict-safe synchronisation over intermittent connections.
- Records with access control appropriate to the data.
- Programme indicator tracking against your logframe.
- Donor-format reports generated, not assembled.
- Field materials in the languages your team works in.
What changes
Faster data
Days rather than weeks between collection and office.
Fewer errors
Validation happens where the data is entered.
Reporting cycle
Stops consuming the last week of every period.
Real conditions
Works on the connectivity you actually have.
Often looked at together.
Government digital systems
Registries, e-services, MIS platforms and reporting for ministries, agencies and regional bureaus.
Data platforms & dashboards
Consolidated pipelines, agreed metric definitions, and views built around decisions.
Mobile development
Native and cross-platform apps built for shared, low-end devices and patchy signal.
About this work specifically.
General questions about scope, ownership and timelines are answered on the resources page.
Days. We design for a phone that is shared, low-end and offline for several days at a time. When a connection returns, the app syncs without overwriting anyone's work.
Access is scoped by role, sensitive fields are restricted, and the device holds only what that user needs. We agree the retention and access rules with you in writing before we build.
Yes. Indicators are stored once and mapped to each donor's export format, so reporting to a second funder does not mean collecting the data twice.
Tell us what you need built.
We reply within two working days with honest scope and next steps — including when we are not the right fit.