Nonprofit/Custom applications
NGO presence
They can send one link. Appointment requests are records, not forwarded screenshots.
Confidential commission. We describe the system. We do not name the organization or show their data.
Public web · Email · Appointments · Database
Result
A visitor can learn what the organization does and ask for an appointment. The organization gets an email. The request is stored. Nothing depends on someone noticing a direct message.
Shipped software for a real organization. No model in the loop.
The situation
Welfare and education work only reaches people who can find it. Without a site, the story lives in conversations. Without intake, every request for time is a message that may or may not be logged.
They needed presence and a front door.
Constraints
The tone had to match care work: quiet, not campaign-loud.
Appointment, email, and a database. A form that goes nowhere was not the job.
The organization is not named here. No address, no leadership names, no live URL.
Approach
Lead with the organization’s outcome, then make the next step obvious: request time. Treat that request as data and as a notification, so it is both stored and seen.
What we shipped
A public narrative site, email capture, appointment request, a notification to the organization, and records in a database.
How it was built
A hosted web application with a small intake backend. Enough to run appointments. Not a CRM they did not ask for.
What we’d do next
A language they actually serve in, if they want it. On DevZo, this page is proof we ship ordinary, useful systems as well as models.