Each practice has a senior lead, a handover guide, and at least one engagement we can put you in touch with. We move staff across practices once a year. Most of our team has worked on at least two of these by year three.
We design data systems that field teams actually use: collection on phones with patchy networks, dashboards that answer the question a programme officer is holding, and AI that suggests where to look next without deciding for anyone.
412 ASHA workers in Koppal now log births and immunisations on a single app. Sync rate: 96%.
Plain writing, sturdy design, and distribution that respects how rural readers find information: radio, WhatsApp, paper, in that order.
2.4 lakh families in north Karnataka received drought-relief explainers in Kannada and Lambadi last year.
Workshops with the people who will run the system, not the people who signed the cheque. We write the handover guides and train the team on them.
Thirty-eight CSO partners have taken over their own data ops after a 12-month engagement.
Open-source platforms (CommCare, DHIS2, ODK, Hasura) assembled so a women's collective can run their own books on the phone in their pocket.
2,400 Karnataka villages have collectives keeping their own ledgers in their own language.
Most of what we ship runs on a small set of open-source platforms that have been in production longer than most of our engineers. That is a choice. A partner who inherits the system in year five should not need a vendor to keep it running.
Indicator frameworks, custom dashboards, and tracker programmes for state health departments.
Offline-first registers for ASHAs, ANMs, and peer educators. Sync over 2G, store on the device.
Large-N household surveys, monitoring visits, programme audits. XLSForm-driven so partners can edit.
GraphQL on top of a typed schema. Used wherever a partner organisation needs to build their own front end.
When a partner needs a public portal or staff dashboard, this is what we reach for.
Self-serve dashboards once the data is clean. We prefer the tool the partner team will keep using.
The tools change. The principles don't. These four hold up across the engagements we've shipped since 2014.
Every layer we ship can be forked. If a partner ends the engagement, the system keeps working.
We choose the stack that handles intermittent power and 2G. Cloud-first decisions get tested against this.
We pick the tool that has been in production for a decade. New tools get a 12-month soak before a partner sees them.
Every form, label, and error message is built to localise. We deploy in Kannada, Tamil, Telugu and Hindi today.
A discovery call, a written proposal, then the work, and a hand-back at the end so the partner team can run the system on their own.
Thirty minutes with our team. We bring questions, not slides.
Scope, milestones, cost, and what we'll need from you.
A handover guide, a trained team on your side, and a quarterly check-in for the first year.
