Every bed request became a case families can follow
Let's Build, a nonprofit that provides beds to children who need them, replaced forms, spreadsheets, email, and paper delivery sheets with one SuiteDash system: web intake, case tracking, delivery scheduling, mobile field forms, and a branded portal where families see where their request stands.
Each request creates a case tied to a lasting family record, so status, contact details, scheduling, and delivery notes stay in one place even when months pass between request and delivery.
A nonprofit that delivers beds to children in families facing housing instability, run by a small staff working with volunteer delivery teams.
- Intake, tracking, scheduling, and communication ran across separate tools, so information had to be copied between them by hand.
- Deliveries were scheduled in spreadsheets, and delivery teams recorded their work on paper that was entered into the system later.
- Families often waited months with no way to see their status or update a changed phone number, so many submitted again or became unreachable and had their cases closed.
What we did
- 1Design the case model
Using our Business Accelerator framework, we finalized the workflows and field mappings, and set up a case-based model: each request becomes a trackable case inside a lasting family record, so a family returning later picks up where they left off instead of starting over.
- 2Build intake, tracking, and scheduling
A bed request form embedded on the Let's Build website that creates a case for every submission. A case tracking dashboard showing status, priority, assigned team, and next action. A scheduling workflow that lines up family readiness, team availability, and logistics, plus mobile-friendly field forms where delivery teams record completion details, photos, and notes on site.
- 3Open the family portal and hand off
A branded family portal on a custom domain where families check their status, update contact information, and find support resources. Automated welcome, status, and reminder emails, post-delivery follow-ups, and outbound email authentication so messages are delivered reliably. Then a team walkthrough with real scenarios, hands-on training, a video guide, and 14 days of priority support.
More from this engagement
The portal and automated status updates show each family that their request was received and what comes next, which cuts down on repeat submissions and status calls.
Families update their own phone numbers and addresses in the portal, so fewer cases are closed because the team can no longer reach them.
Scheduling confirms that a family is ready before a team is assigned, and reminders go out as the delivery date approaches, so volunteers spend less time waiting and rescheduling.
Field teams record each delivery on their phones, and the details attach straight to the right case instead of waiting on paper.
Under the hood
Before the build, the process worked, but it worked harder than it should. Requests came in through forms, schedules lived in spreadsheets, coordination happened over email, and delivery notes came back on paper. With demand growing, every handoff between tools added time and room for error.
On the family side, a request submitted on the website creates a case and a family record, followed by an automated welcome email and access to the branded portal. While they wait, families can see their status and next steps, update their contact details, and find support resources. After delivery, follow-up messages remind them that repair, disassembly, and move support are available.
On the team side, every active case appears on one dashboard by status, priority, and assigned team. Cases follow a reusable delivery template, and status changes trigger the next step automatically. Messages with families and volunteers are kept on the case, so the full history stays intact when a coordinator changes or a family comes back with a new need.
Before handoff, the team tested the system against real scenarios and we adjusted it based on their feedback. Training, a recorded video guide of every key workflow, and a 14-day priority support window followed. With intake, scheduling, and delivery data in one place, the organization also has numbers it can use when it talks to donors about its impact.
What changed
The mission stayed the same. The system behind it caught up: families can follow their request instead of wondering about it, volunteers arrive at homes that are ready for them, and the relationship with each family continues after the bed is delivered.
Let's talk about what you're trying to change.
Tell us where your client work gets stuck. In a short call we'll map it to a SuiteDash build and tell you honestly whether it's a fit.
- Where clients and documents get stuck today
- What a first version of your portal would include
- A realistic timeline and price