Operational systems
Registration, membership, reporting, care queues, bookings, and role-based dashboards.
04 · Services
Business software
Build the system around how the organisation actually works.
Custom software for work that has outgrown spreadsheets, paper forms, and WhatsApp threads — registration, reporting, dashboards, and administration.
What this is
When the same information is copied between a paper form, a chat, and a spreadsheet, the business does not need another brochure. It needs a system that matches the real workflow.
We design around roles: who submits, who reviews, who exports, and what must stay confidential. The public website and the internal tool are often one platform, not two unrelated projects.
Principles
01
Model the workflow, not a generic app
If leaders already have a form the conference or the school expects, the software should respect that form — not invent a new one they will reject.
02
Institutional memory
Records should stay with the organisation when an officer changes, not leave on someone's phone.
03
A website and a system can be the same product
Visitors use the public side. Staff use the dashboard. Both should share one source of truth.
How engagements look
Portals
A place for customers or members to return to — not only a page they see once.
In the work
These case studies show this service in a real organisation — not a feature list.
From the notebook
Short essays on how we think about this work.