Our work
Six problems, six systems that are still running.
We measure our work by whether it keeps working after we leave the room — still in daily use, still owned by the client, still solving the problem it was built for. These are representative examples, described generically to protect client confidentiality where a full public case study hasn't been agreed.
NGO · Field data & reporting
Turning weeks of field reports into a live dashboard
A health and livelihoods NGO working across three districts was losing days each month stitching together paper forms and WhatsApp updates from field officers into donor reports. We built an offline-capable data collection app that syncs automatically once a connection appears, validates entries as they're captured, and feeds a live dashboard for programme managers.
- Field submissions work with no signal and sync automatically later
- Reporting time cut from around ten days a month to under one
- Donor-ready exports generated in minutes, not rebuilt by hand each cycle
Government · Citizen services
Connecting a district office's existing systems to a national portal
A local government office needed citizens to submit and track service requests online, but the mandate was to integrate with an existing national identity and payment platform rather than build a parallel system. We scoped the integration against the published government APIs, built a citizen-facing request portal on top, and trained office staff to manage the queue that used to live entirely on paper.
- Citizen requests submitted and tracked online, reducing in-person queuing
- Payments and identity verification handled through the official national platform, not a workaround
- Staff dashboard replacing a paper register that made status impossible to track
Education · School management
Giving school administrators their evenings back
A private secondary school's admissions, fee tracking and exam results all lived in separate spreadsheets maintained by different staff, with reconciliation happening manually at term end — usually late at night. We built a single school management system covering admissions, fee schedules and reminders, and results processing, with role-based access so teachers, bursars and administrators each see only what's relevant to them.
- Fee reminders sent automatically instead of chased by phone
- Results processing that used to take a week now takes an afternoon
- Parents can check a child's fee balance and results without a call to the office
Retail SME · E-commerce
Moving a Kampala retailer's order book off WhatsApp
A growing retail business was taking the majority of its orders through WhatsApp messages, which meant lost orders, no stock visibility, and hours spent copying details into a spreadsheet each evening. We built a mobile-friendly storefront with mobile money checkout and live stock levels, wired directly into the same spreadsheet-replacement inventory system so nothing needed double entry.
- Orders and payment captured automatically instead of transcribed from chat
- Stock levels visible to customers in real time, cutting "sorry, that's sold out" messages
- Checkout that works reliably on the mid-range Android phones most customers actually use
Logistics SME · Cloud migration
Replacing a single office server with infrastructure that doesn't go down with the power
A logistics company ran its dispatch and billing system from a single physical server in the office, so a power cut or hardware fault meant the whole business stopped taking bookings. We migrated the system to a right-sized cloud setup in the client's own account, with automated backups and a monitoring alert that reaches someone before customers notice a problem.
- Dispatch system now unaffected by office power or hardware failures
- Backups tested for real restorability, not just scheduled and forgotten
- Monthly cloud spend lower than the office server's electricity and generator fuel had been
Agribusiness · Traceability
Tracking coffee from farmgate to export buyer
An agribusiness cooperative needed to prove the origin of its coffee to meet export buyers' traceability requirements, but collection records were kept by dozens of local agents on paper receipt books. We built a simple mobile data capture tool for agents to log farmer, quantity and location at the point of purchase, generating the batch-level traceability records buyers now ask for as standard.
- Every batch traceable to farmgate collection point and date
- Agents recording purchases on a basic Android phone, no extra hardware needed
- Export documentation that used to take days assembled in under an hour
Want to talk through a similar problem?
If any of this sounds close to what you're dealing with, the fastest way forward is a short conversation about your specific setup.