The Team Leader's Morning Brief
One short list, before the day starts, of what is overdue, what is at risk, and the few things that genuinely need the team leader.
- Tier
- Flagship
- Build order
- 7th of 7 for real estate
- Shape of it
- 8 steps, 1 decision point, 1 escalation rule
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
The team leader is the escalation path and is also supposed to be the top producer. Problems reach them late, usually as a client complaint or an agent resignation.
The CRM shows activity. The transaction platform shows files. Neither shows that six leads have had no human contact in forty-eight hours, that an agent's appointment-set rate has halved this month, that a financing contingency expires Thursday on a deal nobody has mentioned, or that four no-shows last week were never rescued.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
- It decides something
- It escalates to a person
Step 1Trigger
Every morning, one brief is assembled and sent.
Step 2
Ordered by what needs a decision.
Step 3Escalation
Needs the leader now: a transaction milestone at risk, a client escalation, an agent significantly below their own baseline, a lead source producing nothing this week.
Step 4
Overdue: leads without human contact, conversations with no next action, no-shows unrescued, nurture contacts past their stated timing, documents outstanding.
Step 5
Failed, and why: messages undelivered, integrations errored, required outcomes missing.
Step 6
Pipeline: appointments set this week versus baseline, transactions by stage, and lead source performance.
Step 7
Nothing self-reported. Every line traces to an event.
Step 8Branch
If there is nothing to raise, one line says so.
How it gets built
Built inside what you already run
- Follow Up Boss
- kvCORE
- Sierra
- Lofty
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Agree
Agree what genuinely requires the leader, and be strict.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 2
Agree
Set thresholds: hours without contact, deviation from an agent's own baseline, days to a contingency.
- 3
Build
Build exception queries against system event data, not CRM dashboards.
Built inside the software you already run, against your stages and your language.
- 4
Agree
Set send time against when the leader actually reads.
- 5
Prove
Review weekly for a month and cut every line not acted on.
It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.
What changes after it goes live
How it runs today
The team leader is the escalation path and is also supposed to be the top producer. Problems reach them late, usually as a client complaint or an agent resignation.
After this one is live
Problems surface at a day old. Agent performance changes are visible while coaching can still help rather than after a bad month. And the leader stops being the person who finds out last.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
No revenue calculation, and it should not be given a fake one. Ask the leader what one late-discovered problem cost; they will have an example and it usually involves a client or an agent who left.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Agents are independent contractors, and this shapes everything. A system that requires behaviour change will fail. Every system here is built to work whether or not an individual agent cooperates, and anything that cannot be must be flagged to the team leader as a people problem rather than sold as a systems solution.
Fair housing is not negotiable.
- No automation may segment, target, exclude or personalise on race, colour, religion, sex, familial status, national origin, disability, or any protected class under federal, state or local law.
- Life-event triggers are the specific risk. Familial status is a protected class, so an automation that targets people who have recently had a child is a fair housing violation. Life-event prompts in System 6 are human tasks only, never automated messages, and the boundaries must be agreed in writing with the brokerage's compliance officer.
- Geographic targeting can constitute steering. Any farm-area or neighbourhood campaign needs compliance review.
- Advertising rules apply to automated messages exactly as to any other advertising.
Licensing and disclosure.
- Automated messages must comply with state licence disclosure requirements, which vary and often require the brokerage name and licence number.
- Team names and advertising are regulated in many states.
Messaging.
- TCPA and CAN-SPAM apply in full. Consent per number, quiet hours in the recipient's local time, immediate opt-out honoured across every system.
- Portal leads carry their own consent terms which are not the same as a consumer opting in on the team's own site. Treat them as a separate consent category.
- Replies route to a monitored human queue.
Data.
- Transaction files contain financial and personal information. Access controls and retention rules apply, and several states now grant deletion rights that reach a CRM.
Nothing here is legal advice. Fair housing law, state real estate licence law, brokerage policy and MLS rules can each add requirements, and fair housing in particular carries personal liability. Every template requires review by the brokerage's own compliance function before it goes live.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forreal estate.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5The Complete Client JourneyThe flagship, once the pieces are proven.
- 6Sphere, Past Clients & Referral EngineSphere and referral, which depends on the clean client records System 5 produces.
- 7The Team Leader's Morning Briefyou are hereOnly meaningful once there are systems to report on.
The tiers are the dependency order for real estate, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Sequencing note. Systems 1 and 2 together usually pay for the entire engagement within a quarter, because the appointment-set rate is the highest leverage number in a real estate team and almost nobody measures it per agent.
Back to the real estate overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.