Practical guides
Short reads, real operations
The ideas behind the templates — what actually makes practices run smoothly, and how to get there.
CRM & workflow
How to Keep Your CRM Clean
Most firms don't have a CRM problem. They have a CRM maintenance problem. Data rots quietly: duplicates pile up, fields go stale, stages stop meaning anything — and within a year, nobody trusts the system, so nobody uses it. The fix isn't a new CRM. It's a rhythm.
Daily (5 minutes): log every interaction the day it happens. Every new record gets a status, an owner, and a next action with a date — no exceptions.
Weekly (15 minutes): merge duplicates, close out dead prospects, and fill in records missing key fields.
Monthly (30 minutes): review your pipeline stages. If a stage hasn't moved a prospect in 90 days, it doesn't mean anything — retire it. Spot-check ten random records for accuracy.
Quarterly (1 hour): archive what's past retention, rename fields that confuse the team, and confirm your integrations still sync.
A CRM nobody trusts is just an expensive address book. Fifteen minutes a week keeps it the source of truth.
Operations
How to People-Proof Your Workflows
When a procedure isn't followed, the instinct is to blame training. But most of the time, the procedure is the problem: it's unclear, it's hard to find, or following it takes more effort than winging it. People-proofing means designing the workflow so the right action is the easiest action.
Start with the trigger. Every workflow should begin with a specific, observable event — "new prospect inquiry," not "whenever someone reaches out." Vague triggers produce vague compliance.
Then name one owner. Shared ownership is no ownership. If two people are responsible, neither is.
Write steps for a new hire, not for yourself. If someone who's never done the task can complete it without asking questions, the procedure works. If they can't, rewrite the procedure — don't retrain the person.
Finally, build the guardrails into the system: required fields, checklists, templates. Don't rely on memory for anything that matters.
Daily habits
The 5-Minute End-of-Day Shutdown
The most expensive operations failures don't happen in big moments. They happen in the gaps between days — the follow-up nobody scheduled, the task nobody assigned, the ball nobody knew was in their court. A five-minute shutdown closes those gaps before they open.
Before you log off, answer three questions:
1. What's due tomorrow, and who owns it? If the answer is unclear for any item, assign it now — while it's fresh, not at 9am tomorrow.
2. Did every interaction today get logged? Calls, emails, meetings — if it's not in the CRM, it didn't happen. Log it now; tomorrow you'll forget the details.
3. Is anything stuck? Anything waiting on someone else for more than a couple of days needs a nudge or an escalation — not another day of silence.
Five minutes. Three questions. It's the cheapest operations system ever built, and most practices don't have it.