Monday morning in a 2026 trades shop has the same question every week, asked by the same owner, in the same coffee-stained voice. "What happened last week?" The marketing manager who answers that question with a 22-tab spreadsheet, a 14-slide deck, or a three-paragraph "I'll get back to you" email is the marketing manager who is about to lose the role. The marketing manager who answers with a one-page brief — channel ROAS, booking-% drag, cost-per-booked-call by source, lead-source-to-revenue waterfall, three named anomalies, two named actions for this week — built by AI from CallRail plus ServiceTitan plus GLSA plus Hatch plus NiceJob data, in the marketing manager's own voice, read by the owner in 8 minutes before the dispatch huddle — is the marketing manager who runs the role for the next decade. This lesson is the named-report-cut anatomy of the brief, the data pipes that feed it, the prompt that drafts it, the verify pass that keeps it accurate, and the Monday-morning routine that produces it before the owner asks. 8 minutes to read. 0 to build. AI assembles; the marketing manager edits for 6-9 minutes; the brief ships at 7:55 a.m.

Why Monday Morning and Why 8 Minutes

Monday morning is the operational forcing function. The dispatch huddle starts at 8:00 a.m. The owner walks the floor between 7:30 and 7:50. The CSR row goes hot at 8:00. The marketing manager's brief either lands before 7:55 a.m. and feeds Monday's operating decisions, or it lands at 11:00 a.m. as an FYI the owner skims between calls. The first ships next week's spend reallocation. The second is paperwork.

8 minutes is the read time the owner can defend against the dispatch board calling him. Long enough to absorb seven numbers and three anomalies. Short enough that the owner does not skip it. Marketing managers who ship 18-minute briefs lose readership at month two; marketing managers who ship 8-minute briefs read every Monday for years. The brief's brevity is the leverage; the comprehensiveness is in the underlying data pipes, not in the surface artifact the owner consumes.

The brief is also the artifact that survives owner turnover, marketing-manager turnover, and platform-owner audit. When the shop sells to a roll-up — Wrench Group, Authority Brands, Apex Service Partners, Sila Services, Path Light Pro, Redwood Services — the platform's diligence team asks for the marketing operating cadence. The shop with 52 weekly Monday briefs in a documented format defends a higher EBITDA multiple than the shop with a shoebox of marketing reports. The brief is the operating discipline that converts marketing spend from a cost line to a defendable revenue line.

The Five Data Pipes That Feed the Brief

The brief is only as good as the data pipes. Five named pipes feed every section. CallRail Conversation Intelligence provides inbound call volume, channel attribution via dynamic number insertion, call sentiment, missed-opportunity flags, and the AI-tagged kill reasons on lost calls. ServiceTitan, HCP, or Sera provide booking conversion, dispatch yield, closed-revenue by source, recall percent, average ticket, and the per-tech and per-CSR performance roll-up. GLSA provides spend, leads, ROAS, and the negative-lead dispute status. Hatch provides stale-lead reactivation conversion, sequence performance by segment, and the revenue attributable to nurture touches. NiceJob provides review acquisition velocity, response cadence, customer-story candidates, and the AEO-feeding structured-data publishing log.

The pipes connect to the brief through an AI orchestration layer — Zapier, Make, n8n, or a custom integration — that pulls the prior week's data from each platform into a unified weekly-summary document. The orchestration runs Sunday evening at 11:00 p.m. so the unified summary is ready before the marketing manager arrives Monday morning at 7:00 a.m. The AI drafting prompt ingests the unified summary, applies the marketing manager's voice prompt, and produces the first draft of the brief by 7:15 a.m. The marketing manager edits from 7:15 to 7:50 — adds the contextual anomaly explanations, removes the AI's hedging language, names the action items — and ships at 7:55 a.m. The total elapsed marketing-manager time on the brief is 35-40 minutes per week.

The pipes must be clean. Dirty data in any pipe corrupts the brief. CallRail's dynamic number insertion must cover every channel including the truck-wrap number and the billboard number (which most shops skip and which feeds the "direct/unknown" bucket the brief cannot attribute). ServiceTitan's lead-source field must be populated by the CSR on every booking. GLSA's outcome connector must be wired to ServiceTitan closed-revenue. Hatch's conversion-to-revenue must tie back to the originating sequence. NiceJob's review attribution must connect to the originating job. Quarterly pipe audits verify the connections; broken pipes get fixed before the next Monday's brief.

The Five Named Report Cuts in the Brief

The brief has five report cuts, in this order. The order is the leverage — owners read top-down, so the highest-decision-impact cut goes first.

Cut One: Channel ROAS

One row per channel. GLSA, PPC, organic, NiceJob, Hatch, direct mail, referral, truck-wrap-and-billboard. ROAS this week, ROAS 4-week trend, dollar change from prior week. Anomalies flagged inline (asterisk + one-line explanation). The owner reads channel ROAS first because it answers "is my marketing spend working" in 90 seconds. Format: 6-8 row table. AI generates the table from the unified summary; marketing manager edits the anomaly explanations.

Cut Two: Booking-% Drag

One number — the booking percent on all inbound paid channels for the week. Compared to the 4-week trend and the target. If booking percent is dragging, the AI surfaces the suspected cause from CallRail's kill-reason tags (price-shock, no-window-commitment, dispatch-fee-objection, after-hours-confusion) and the per-CSR breakdown. The owner reads this second because booking-% drag invalidates everything else — if booking percent is broken, channel ROAS is misleading and reallocation decisions are premature. The marketing manager owns surfacing the drag; the operations manager owns fixing it.

Cut Three: Cost Per Booked Call by Source

One row per paid source. Cost per booked call this week, 4-week trend. Flagged when above the source's target band. The 2026 target bands per source: GLSA $40-$80 mature, $58-$110 in early AI-bidding phase; PPC $60-$120; direct mail $90-$180; referral $20-$60. Sources above their target band get a one-line action prompt — pause, reduce, optimize, or accept-because-strategic. The owner reads this third because cost per booked call is the operating-level diagnostic that ties channel ROAS to dispatchable supply.

Cut Four: Lead-Source-to-Revenue Waterfall

The waterfall shows the conversion path from lead arrival to closed revenue. By channel. Lead → booked call → ran job → closed revenue. The waterfall surfaces where each channel leaks. GLSA may produce 80 leads, 64 booked calls (80% booking), 58 ran jobs (91% show), $42K closed revenue ($725 average closed). Hatch may produce 35 reactivations, 28 booked, 24 ran, $186K closed revenue ($7.75K average — Hatch reactivates older replacement-pipeline leads). The waterfall format makes channel comparison apples-to-apples, which the raw ROAS number obscures. AI generates the waterfall as a structured table; marketing manager confirms accuracy against ServiceTitan closed-revenue.

Cut Five: This Week — Anomalies and Action

Two to four anomalies the marketing manager surfaces with one-line explanations. One to two actions for this week. Anomalies are quantitative — "GLSA ROAS dropped from 4.6x to 3.4x; suspect cause: the negative-lead dispute discipline lapsed during the Memorial Day weekend." Actions are quantitative and named — "Run the GLSA dispute batch on Tuesday morning; expected ROAS recovery to 4.2-4.6x range by Friday." This cut is the marketing manager's editorial voice; AI provides the draft, the marketing manager owns the named explanation and the named action. The owner reads this last because actions are what convert the brief from report to decision input.

The Drafting Prompt That Builds the Brief

The AI prompt that drafts the brief is itself a five-part prompt (per L2 Ch1 discipline). Role: marketing manager at a residential HVAC shop drafting the Monday brief for the owner. Context: the unified weekly-summary document is pasted in (CallRail, ServiceTitan, GLSA, Hatch, NiceJob data with prior week and 4-week trend), brand voice is direct-respectful with the marketing manager's voice profile attached, prior 12 weekly briefs are available as a voice reference corpus. Task: draft the 5-section brief in 7-10 lines per section. Format: five labeled sections with the named report cuts (channel ROAS table, booking-% drag, cost per booked call table, lead-source waterfall, anomalies-and-action). 8-minute read target; total brief 600-900 words. No preamble. Constraint: do not invent numbers not in the unified summary; do not hedge anomaly explanations ("possibly," "might," "could" forbidden — name the cause or label as "unclear, requires investigation"); do not propose actions outside marketing-manager scope; do not soften negative trends; flag any pipe-data inconsistency for the marketing manager to verify before edit.

The prompt is saved as a template in the marketing manager's prompt library and updated quarterly as the voice profile, the report cuts, and the constraint discipline evolve. Each Monday the marketing manager pastes the unified summary into the template, runs the prompt, receives the draft, edits for 30-35 minutes, and ships. The prompt is the moat. A new marketing manager hired into the shop inherits the prompt and produces a brief at experienced-marketing-manager quality on week one, against a manual ramp-up that historically took 6-12 months.

The voice profile attached to the prompt is built from the marketing manager's prior 12 briefs plus their other writing samples (Slack updates to the owner, quarterly campaign-plan memos, customer-recovery emails). The profile captures opening-line patterns, anomaly-explanation conventions, recommended-action phrasing, and the manager's preferred contractions and brand voice. Voice-fidelity over 12 weeks of briefs is what makes the owner read the brief as the marketing manager's analysis rather than as AI output — preservation of trust is the entire reason the voice profile matters.

The Verify Pass on the Brief

The brief touches financial reporting and strategic decisions. It gets the L2 Ch7 30-second verify pass before shipping. The five checkpoints applied to the brief: Numbers — every dollar figure, every percent, every count matches the underlying ServiceTitan/CallRail/GLSA/Hatch/NiceJob source. Names — every named CSR, tech, source, or zip code matches the actual record. Channels — every channel attribution traces back through dynamic number insertion or first-touch records; the "direct/unknown" bucket is sized and disclosed. Anomaly Explanations — every named cause is verifiable from the underlying data, not an AI confabulation. Action Realism — every action is within the marketing manager's scope, executable this week, and tied to a named owner-visible metric.

The verify pass takes 4-6 minutes for a clean brief and 8-12 minutes when a pipe issue surfaces. Marketing managers who skip the verify ship briefs with hallucinated numbers; the owner catches the first one, loses trust, and stops reading. Marketing managers who verify consistently build a 12-week reputation for accuracy and then earn the room to recommend bolder reallocation moves. The verify is the trust-preservation discipline; without it, the brief degenerates into AI-generated noise the owner skims dismissively.

The verify also catches the AI's specific failure modes. AI is prone to confabulating per-source ROAS by mis-mapping closed revenue across channels with overlap (a job that came in via GLSA but closed during a Hatch nurture sequence — first-touch GLSA, last-touch Hatch). AI is prone to averaging away anomalies it should have flagged. AI is prone to generating hedge language ("possibly," "might") that softens trends the marketing manager wants surfaced. The marketing manager's verify pass catches all three patterns.

The Monday Morning Routine

The Monday routine for the brief is 35-40 minutes total. 7:00 a.m. (5 min) — coffee, open the unified weekly-summary document the orchestration produced overnight, spot-check the pipe-health flags. 7:05 a.m. (3 min) — paste the summary into the brief-drafting prompt template; trigger the AI draft. 7:08 a.m. (2 min) — read the AI's draft top-to-bottom. 7:10 a.m. (12 min) — edit the five report cuts; remove AI hedging; add named-cause anomaly explanations; sharpen the action items. 7:22 a.m. (8 min) — verify pass on numbers, names, channel attribution, anomaly explanations, action realism. 7:30 a.m. (4 min) — final read; final edits; mark for owner. 7:34 a.m. (6 min) — buffer for any pipe-data issue the verify surfaced; rerun if needed. 7:40 a.m. — ship to owner.

The owner reads at 7:45 a.m. The 8-minute read lands before the 8:00 a.m. dispatch huddle. The owner walks into huddle with two action items: the marketing manager's named action for this week, and any operating-cadence implication the brief surfaced (CSR coaching, dispatch yield review, recall-trend investigation). Marketing-manager and owner conversation about the brief happens in the 15-minute window between huddle end (8:15) and the owner's 8:30 calls — concise, decision-oriented, defended by the brief's numbers and action items.

The routine compounds. Marketing managers who run it 50 of 52 weeks per year produce a documented operating cadence the owner cannot replace with a generic SaaS dashboard; the brief becomes the operating ritual that ties marketing spend to Monday-morning decisions, and the marketing-manager seat shifts from "person who buys ads" to "person who owns the marketing-to-revenue conversion narrative." The 35-40 minutes per week is the highest-leverage write in the role — comparable to the Friday recap, but at the front of the week rather than the back.

Scaling the Brief Across Locations and Brands

For multi-location operators and franchise brands, the brief structure scales. A 6-location plumbing operator runs a brand-level brief plus per-location briefs; the brand-level brief aggregates the five report cuts across locations with a per-location-detail section flagging the outlier locations. A 60-truck Authority Brands or Wrench Group franchisee runs a per-brand brief that rolls up to a platform QBR-ready format with EBITDA-by-location and AI-ROI line items by tool (Avoca, Rilla, Dispatch Pro, NiceJob, Birdeye contributions in dollar terms).

The orchestration layer scales horizontally — the same Zapier/Make/n8n pipes pull from each location's CallRail/ServiceTitan/GLSA/Hatch/NiceJob instance, aggregate at the brand level, and feed the brand-level drafting prompt. The marketing-leader voice profile attached to the brand-level prompt belongs to the brand's marketing director rather than the individual location managers. Per-location managers run their own briefs in parallel; the brand-level brief surfaces the outliers worth platform attention.

The scaled-brief workflow at a platform CEO level (450 locations across multiple brands) produces a quarterly QBR-ready aggregated artifact. The same five report cuts at the platform level, with brand-level outliers flagged and AI-ROI line items by tool aggregated across locations. The platform-level brief is the artifact the platform CEO walks into the PE-board quarterly review with; AI assembles, the marketing director edits, the CEO reads in 8-15 minutes, the QBR conversation moves to strategy rather than data assembly. The same discipline at the same surface, scaled by orchestration rather than by adding analyst headcount.

Key Takeaways

• The Monday brief lands at 7:55 a.m. before the 8:00 a.m. dispatch huddle. 8 minutes to read, 0 to build (AI assembles), 35-40 minutes of marketing-manager edit time. The brevity is the leverage; the comprehensiveness lives in the underlying data pipes.
• Five data pipes feed the brief: CallRail Conversation Intelligence (calls, sentiment, attribution), ServiceTitan/HCP/Sera (bookings, closed-revenue, recall %, average ticket), GLSA (spend, leads, ROAS), Hatch (reactivation conversion, sequence performance), NiceJob (review velocity, structured-data publishing). Orchestration runs Sunday 11:00 p.m. via Zapier/Make/n8n; unified summary ready by Monday 7:00 a.m.
• Five named report cuts, in this order: Channel ROAS (one row per channel, 4-week trend, anomalies inline). Booking-% drag (the operating-level diagnostic that invalidates everything else if broken). Cost per booked call by source (with 2026 target bands: GLSA $40-$80 mature, PPC $60-$120, direct mail $90-$180, referral $20-$60). Lead-source-to-revenue waterfall (lead → booked → ran → closed revenue per channel). This-week anomalies and action (2-4 named anomalies, 1-2 named actions for this week).
• The drafting prompt is itself a five-part prompt (Role/Context/Task/Format/Constraint per L2 Ch1). Voice profile attached from the marketing manager's prior 12 briefs plus other writing samples. Saved in the prompt library; new managers inherit it and produce experienced-quality briefs on week one.
• The 30-second verify pass applies to the brief. Five checkpoints: numbers (every figure matches the source), names (every named CSR/tech/source/zip matches the record), channels (every attribution traces through DNI; "direct/unknown" sized and disclosed), anomaly explanations (every named cause verifiable), action realism (every action within scope, executable this week). 4-6 minutes for a clean brief, 8-12 minutes when a pipe issue surfaces.
• The Monday routine is 35-40 minutes: 7:00 a.m. open the unified summary (5 min), trigger AI draft (3 min), read draft (2 min), edit five cuts (12 min), verify pass (8 min), final review (4 min), buffer (6 min), ship at 7:40 a.m. Owner reads at 7:45; lands before 8:00 a.m. huddle; decisions queued for the week.
• The brief is the artifact that survives turnover and audit. 52 weekly briefs in documented format defend higher EBITDA multiple at sale; the operating cadence converts marketing spend from cost line to defendable revenue line; the brief is what a Wrench Group, Authority Brands, Apex Service Partners, Sila Services, Path Light Pro, or Redwood Services diligence team reads to verify operating discipline.
• The brief scales horizontally. Multi-location operator runs a brand-level brief plus per-location briefs; platform CEO runs a QBR-ready aggregated artifact with brand-level outliers and AI-ROI line items by tool. Same discipline at the same surface, scaled by orchestration rather than analyst headcount.
• The brief is the marketing manager's seat defense. The role shifts from "person who buys ads" to "person who owns the marketing-to-revenue conversion narrative." 50 of 52 weeks of consistent briefs produces the documented operating cadence that justifies the seat in front of an owner, a coach, or a PE partner.