Project Overview
| Client Industry | Nonprofit / Public Sector (Social Services) |
| Business Type | Regional nonprofit providing housing assistance and case management, ~45 case workers, 6 county offices |
| Project Duration | 19 weeks |
| AI Service Provided | Custom Application Development |
| Technologies Used | React, TypeScript, Node.js, PostgreSQL, AWS (ECS, RDS, S3), Auth0, Twilio |
The Client Challenge
The client, a nonprofit providing housing assistance and case management across six county offices, managed thousands of active client cases using a combination of paper case files, a generic spreadsheet tracker, and an outdated case management tool that no longer matched how the organization actually operated.
The operational and mission-critical challenges:
- Case workers spent an estimated 8–10 hours a week on administrative documentation, time that could otherwise go toward direct client support.
- Client case history was fragmented a client who moved between county offices (common among the transient population the nonprofit served) often had no continuous case record, forcing case workers to start from scratch.
- The existing legacy case management tool didn’t support the specific workflows required by the state’s housing assistance funding requirements, forcing staff to maintain a duplicate manual tracking process just for compliance reporting.
- Reporting to funders and state agencies required manually compiling data from multiple disconnected sources, taking days each reporting cycle and introducing errors.
- There was no systematic way to track client outcomes over time (housing stability, program completion rates) that funders increasingly required as a condition of continued grant funding.
- The nonprofit’s technology budget was limited, and any solution needed to be genuinely usable by case workers with varying levels of technical comfort, many of whom were skeptical of new systems after a prior failed software rollout.
Our Solution
Air Brite Labs designed and built a custom case management application tailored specifically to the nonprofit’s actual workflows, funding compliance requirements, and cross-office continuity needs built with heavy case worker involvement throughout to ensure real adoption, not just technical delivery.
Key capabilities delivered:
- Unified client case records — a client’s case history follows them across all six county offices, eliminating the fragmented records problem for clients who move between service areas.
- Compliance-aligned workflows — case documentation fields and required steps are built directly around the state’s specific housing assistance funding requirements, eliminating the need for a separate manual compliance tracking process.
- Automated funder reporting — reports required by funders and state agencies generate directly from case data already being entered as part of normal case work, replacing days of manual data compilation.
- Client outcome tracking — housing stability milestones and program outcomes are tracked systematically over time, giving the nonprofit the longitudinal outcome data funders increasingly require.
- Mobile-friendly field access — case workers conducting home visits or meeting clients outside the office can access and update case records from a phone or tablet, not just a desktop workstation.
- Simple, guided interface — designed specifically with input from case workers who were skeptical of technology, prioritizing clarity and minimal clicks over feature density.
Technical Approach
Frontend: Built with React and TypeScript, with significant attention to interface simplicity and guided workflows given the range of technical comfort levels among case workers a deliberate design choice following direct feedback from staff about the prior failed software rollout.
Backend: Node.js API layer managing case records, workflow state, and reporting logic, with PostgreSQL as the central data store consolidating what had previously been fragmented across paper files, spreadsheets, and the legacy tool.
Compliance Workflow Design: Case documentation workflows were built directly from the state’s housing assistance program requirements, working closely with the nonprofit’s compliance staff to ensure required data points were captured as a natural part of case worker documentation rather than a separate, redundant compliance step.
Reporting Engine: Built a reporting module that generates funder and state-required reports directly from case data, with configurable report templates so new funder reporting requirements can be added without custom development for each new funder relationship.
Mobile Access: The application was built responsively from the start rather than as a separate mobile app, allowing case workers to access and update records from any device during field visits without requiring a separate mobile deployment.
Security & Access Control: Auth0 handles authentication with role-based access ensuring case workers only see cases within their assigned counties or caseload, while supervisors and compliance staff have appropriately broader visibility an important consideration given the sensitive nature of client information.
Communication: Twilio integrated for optional SMS appointment reminders to clients, reducing missed appointments that had been a recurring challenge for the nonprofit’s limited case worker capacity.
Infrastructure: Deployed on AWS ECS with RDS for the managed database and S3 for secure document storage (client identification documents, lease agreements), sized appropriately for the nonprofit’s budget constraints while maintaining the reliability the mission-critical case work required.
Implementation Process
- Discovery & Requirement Analysis (Weeks 1–4): Spent extended time with case workers across multiple county offices to understand real workflows, compliance requirements, and specifically what had caused the prior software rollout to fail critical context for designing a system staff would actually trust and use.
- Prototype / PoC (Weeks 5–7): Built a clickable prototype of the core case documentation workflow and tested it directly with a group of case workers, incorporating their feedback before writing production code.
- Development (Weeks 8–14): Built the full case management system, compliance-aligned workflows, and automated reporting engine.
- Integration (Weeks 15–16): Integrated Auth0 authentication and Twilio SMS reminders, migrated existing client case data from spreadsheets and the legacy system.
- Testing (Weeks 17–18): Ran a pilot with two of the six county offices, gathering structured feedback on usability and workflow fit before wider rollout.
- Deployment (Week 18): Phased rollout to the remaining four county offices, with hands-on training sessions designed to rebuild staff confidence after the prior failed rollout.
- Optimization (Week 19 and ongoing): Refined workflow steps and report templates based on real usage feedback from case workers across all six offices.
Key Features Delivered
- Unified client case records accessible across all six county offices
- Compliance-aligned case documentation workflows matching state funding requirements
- Automated funder and state reporting generated directly from case data
- Longitudinal client outcome tracking for housing stability and program milestones
- Mobile-responsive access for field-based case work
- Role-based access control protecting sensitive client information
- Optional SMS appointment reminders to reduce client no-shows
Business Results
- Case worker administrative documentation time dropped from 8–10 hours to approximately 4 hours per week, freeing time for direct client support
- Cross-office case continuity was fully restored, eliminating duplicate intake processes for clients who moved between county service areas
- Funder and state reporting time dropped from multiple days per reporting cycle to under a day
- The nonprofit successfully renewed a major grant that specifically required demonstrable outcome tracking, made possible by the new longitudinal client outcome data
- Staff adoption reached all six offices within the planned rollout timeline, a meaningful outcome given the organization’s history with a previously failed software rollout
- Client appointment no-show rates decreased following the introduction of SMS reminders
Technology Stack
| Layer | Technology |
|---|---|
| Frontend | React, TypeScript |
| Backend | Node.js |
| Database | PostgreSQL |
| Authentication | Auth0 |
| Communication | Twilio |
| Cloud Infrastructure | AWS ECS, RDS, S3 |
Why the Solution Worked
The application succeeded because it was built around the real workflows and real skepticism of the people who would actually use it every day, not around an abstract feature specification. Understanding specifically what had gone wrong in the nonprofit’s prior failed software rollout shaped nearly every design decision, from interface simplicity to the training approach used during deployment.
Building compliance requirements directly into the natural case documentation flow rather than as a separate, redundant reporting burden is what actually solved the nonprofit’s dual-tracking problem. Case workers weren’t asked to do more work for compliance; the system captured what was needed as part of the work they were already doing.
Future Scalability
The platform is designed to support the nonprofit’s continued mission and potential growth, including:
- Extending the case management system to additional service programs beyond housing assistance as the nonprofit’s offerings grow
- Adding data-sharing capability with partner social service organizations for clients receiving support from multiple agencies, with appropriate privacy safeguards
- Building more advanced outcome analytics to help the nonprofit identify which interventions most effectively support housing stability
- Expanding to additional county offices if the nonprofit’s service area grows, using the same unified architecture
Because the system was built with configurable workflows and reporting templates rather than hardcoded logic specific only to the current program, extending to new programs or partner integrations builds on the existing platform.
Final Outcome
The nonprofit moved from a fragmented, paper-and-spreadsheet case management process with a history of failed technology adoption to a unified, compliance-aligned system that case workers actually trust and use. The organization now has the outcome data and reporting efficiency to support its continued funding and, most importantly, more time to spend directly supporting the clients it serves.
