The Owner's Morning Brief
One short list, before the crews roll, of what is overdue, what failed and why, and the few things that genuinely need the owner.
- Tier
- Flagship
- Build order
- 7th of 7 for roofing and exteriors
- 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 owner is the escalation path by default and is also in a truck. Problems reach them late and already expensive. Platform dashboards show jobs and revenue, not exceptions. A revenue number does not tell an owner that four estimates over thirty thousand dollars have had no contact in three weeks, that a permit inspection failed on Thursday, or that a supplement package has been sitting unsubmitted since the tear-off.
And people raise problems when they are certain they cannot fix them, by which time a homeowner is already angry.
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, before crews roll, one brief is assembled and sent.
Step 2
Ordered by what needs a decision, not by category.
Step 3Escalation
Needs the owner now: an unacknowledged leak, a failed inspection, a homeowner escalation, a crew blocked on materials.
Step 4
Overdue: enquiries with no outcome, estimates past their next-contact date, change orders awaiting approval, supplements not submitted, warranty registrations outstanding.
Step 5
Failed, and why: messages undelivered, payments declined, material confirmations missing, completion photographs not captured, automations that errored.
Step 6
Open estimate value by age band.
Step 7
Nothing self-reported. Every line traces to an event and links to the record.
Step 8Branch
If there is nothing to raise, it says so in one line.
How it gets built
Built inside what you already run
- JobNimbus
- AccuLynx
- Roofr
- Leap
- 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 owner, 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: estimate value, enquiry age, days a supplement can sit.
- 3
Build
Build exception queries against system event data, not dashboards.
Built inside the software you already run, against your stages and your language.
- 4
Agree
Set the send time against when the owner actually reads, which in this trade is usually before six.
- 5
Prove
Review weekly for a month and cut every line they did not act 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 owner is the escalation path by default and is also in a truck. Problems reach them late and already expensive. Platform dashboards show jobs and revenue, not exceptions. A revenue number does not tell an owner that four estimates over thirty thousand dollars have had no contact in three weeks, that a permit inspection failed on Thursday, or that a supplement package has been sitting unsubmitted since the tear-off.
After this one is live
Problems surface at a day old. The owner stops finding out last, and stops having to ask. And because it is built from events rather than people, it does not depend on anyone raising something uncomfortable.
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. It is what makes the other six trustworthy. Ask the owner what one week of an unattended problem has cost them; they will have an example and it usually involves a homeowner.
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.
Insurance is the line that matters most in this trade.
- No system makes any claim, prediction or representation about an insurance outcome. Not approval likelihood, not supplement acceptance, not what an adjuster will decide, not what a policy covers. Systems document conditions and route information. They do not influence claims.
- Several states regulate what a contractor may say and do regarding a homeowner's insurance claim, including rules on acting as a public adjuster and on advertising around deductibles. Every template touching insurance requires review by the contractor's own counsel in every state they work.
- Never suggest, imply or automate anything relating to deductible waiving or absorption. It is illegal in many states.
United States messaging rules apply in full. Automated SMS sits inside the TCPA and carrier A2P 10DLC registration.
- Classify every system as service or marketing before it sends. A schedule confirmation and a storm-season promotion are different things under different consent standards.
- Storm-event reactivation is the highest-risk system in this playbook, because address-based outreach after a disaster is exactly what regulators and homeowners associate with storm-chasers. It must go only to past customers with an existing relationship, it must be framed as an inspection offer to people whose roof the company installed, and it must never go to a purchased storm list.
- Consent recorded per number with date, source, wording and scope.
- Quiet hours 8am to 9pm in the recipient's local time.
- Honour STOP and free-text opt-outs immediately, cancel queued messages, and propagate suppression across every sending system.
- Route replies to a monitored human queue. A reply saying water is coming in is not a marketing response.
Nothing here is legal advice. State contractor law, insurance regulation, telemarketing statutes and municipal permit rules can each add requirements.
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 forroofing and exteriors.
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.
- 1Storm-Ready Capture, Triage & Instant ResponseFastest visible result, and it survives the first storm Monday, which is when the owner decides whether any of this was real.
- 2Inspection Preparation, Arrival & Complete CaptureProtects the most expensive hour in the sales process and makes the estimate possible.
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 Job SystemThe flagship, once the pieces are proven.
- 6Warranty, Maintenance & Referral EngineCompounds everything, and depends on the job data System 5 starts producing properly.
- 7The Owner's Morning Briefyou are hereOnly meaningful once there are systems to report on.
The tiers are the dependency order for roofing and exteriors, 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
Season note. Build Tier 1 in the shoulder season and let it run through one storm event before starting Tier 2. A contractor who sees System 1 hold on the Monday after hail will build the rest without being sold again.
Back to the roofing and exteriors 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.