Case study · Real estate, San Luis Obispo County
Her business ran on a CRM she didn't own, a spreadsheet, and memory. Now it runs on one system.
A top-producing agent with about two hundred relationships to keep warm, a rotation of notes and pop-bys and emails, and a handful of escrows at a time, each with a legally binding string of contingency dates. Her assistant was out for three months. The follow-up system was about to live entirely in her head.
Before and after
Before
Contacts in a subscription CRM she paid for and didn't live in. Every escrow's deadlines in a spreadsheet rebuilt by hand, per transaction. A home-grown tracker that opened on “203 items pending today.” The rest in her head.
After
One system, hers. Contacts in four tiers with a follow-up rhythm per tier. Escrow deadlines computed from the contract and pushed to her calendar. A portal for each client. A monitor that checks it all every fifteen minutes.
How an escrow runs
An escrow, end to end
Running- 1
Offer accepted
Purchase agreement uploaded
- 2
Terms read
Anything uncertain waits for her OK
- 3
Deadlines computed
In code, never by a model
- 4
Calendar and reminders set
Day before, day of
The real sequence · running in her business today

By the numbers
- 5
- weeks
- scoping to hand-off
- 1
- subscription
- replaced, not added
- 0
- deadlines
- left to a model's math
- 15
- minutes
- between health checks
Three rules she set on day one, all kept: no recording of client conversations · no financial documents stored · tier assignment stays human
I need this system to work for me. I shouldn't be doing more work on something else.
Written by Hayden Perhach, GroundWork ·