Assisted Living Locators

Care coordinators were drowning in leads. Every inquiry got the same priority, a daughter researching for next year sat in the same queue as a son who needed a bed by Friday. No scoring. No triage. Just a spreadsheet and good intentions.

The problem

Assisted Living Locators connects families with senior care options. Their coordinators talk to hundreds of families a month. The issue wasn’t volume, it was signal. They couldn’t tell which leads needed a call today and which could wait a week. That meant slow responses to urgent families and wasted time on cold ones.

What I built

Two surfaces. A scoring flow that ranks and matches families to care options based on urgency, geography, care level, and budget. And a console the coordinators actually use when they pick up the phone, context loaded, match ranked, notes from the previous call already there.

I owned the data layer behind both. The scoring model pulls from intake forms, follow-up signals, and care-facility availability. The console reads from the same source so coordinators never have to cross-reference tabs.

How I worked

Remote, three-month engagement. I was the builder, not the advisor. Shipped production code, not a strategy deck. Stood up the data layer, wired the scoring logic, and built the console interface. When I left, both surfaces were live and in daily use.

What I’d do differently

The scoring weights were set by gut and coordinator feedback. With more time, I’d have built a feedback loop, track which scored-high leads actually converted and retrain the weights against real outcomes.