Go To War Strategy | Mo Alissa Effective: June 1 – June 30, 2026 Status: Living operating document — review every Monday morning
June is the ramp month: Mo has 30 days to rebuild the account's operating foundation before the July–August 60-day measurement window opens and the goal-post comp structure turns live.
| Scenario | June Net Revenue | July–Aug Implication |
|---|---|---|
| No intervention (May exit pace) | ~$87–100K | Disaster. No path to any GP. |
| Quick wins only (pacing + home + compliance) | ~$180–220K | Reaches GP1 if baseline is negotiated correctly. |
| Full execution (quick wins + CAPI + creative engine) | ~$270–340K | GP1 locked, GP2 in range. |
| Full execution + home at 22–25% of spend | ~$300–380K | GP2 achievable; GP3 requires form migration (post-window). |
The ramp logic: Week 1 recovers from Memorial Day ($50–70K target), Week 2 compounds via home reallocation and first creative refresh (+$60–80K week), Week 3 adds early CAPI signal improvement (+$70–90K), Week 4 concentrates budget on proven winners ($80–100K+). Each week builds on the previous one because the account is a learning system — better signals in Week 2 make Week 3 cheaper per lead.
1. Creative engine. 40–49 net-new ads shipped in June across four audience segments and three formats. Every new concept that beats $25 CPL adds margin directly. New creative also restores Meta's ability to find audiences — fatigue is not just a frequency problem, it is an algorithm-degradation problem. The creative refresh is what unlocks spend efficiency everywhere else.
2. CAPI rebuild. Moving Meta from "optimize on raw lead volume" to "optimize on accepted-lead value" is a 15–44% improvement in cost-per-quality-lead by Meta's own published benchmarks. Applied to May's baseline this is worth $20–55K/month at constant spend. The CAPI rebuild compounds: better signal makes new creative test faster, makes audience expansion cleaner, and makes the eventual form migration non-destructive.
3. Home insurance scale. Home ROAS held at 1.36–1.89 while auto collapsed below 1.0 in late May. Home received 8% of total spend ($68,854 of $836,793) but grew from $1,052/day (May 1) to $5,019/day (May 28) — a 377% revenue increase in 28 days on a minor spend share. Moving home from 8% to 22–25% of spend by end of June generates an estimated +$25–30K/month in incremental net at conservative ROAS assumptions, with no creative fatigue risk because the home library is underdeveloped.
The One Thing Not to Do: Do not execute the QuoteWizard form migration cutover inside the measurement window (July–August). A migration-induced accept-rate dip of 10–15% — which is a normal transition artifact — could cost $30–60K net/month and push the run rate below GP1. The Tier 2 RPL lift ($50–85K/month at conservative benchmarks) is real and worth capturing — in September, after the measurement window closes. Build the staging form in June, run the A/B test in July at 10–20% of traffic, cut over in September. Phase it.
Do not surface this conversation before June 15. The sequence is: (a) get access and show visible wins in Weeks 1–2, (b) pull March/April 2026 data and July–August 2025 historical data from Meta + QW starting June 2, (c) build the case file silently using the four baseline methods, (d) request a private 1:1 with Hassan in the June 15–21 window. The dollar stakes: Hassan's proposed $275K baseline vs. a defensible trailing-90-day average of approximately $155–185K (pending historical data) represents a $90–120K difference. At even a 20% take rate on lift, every $10K the baseline moves costs or earns Mo roughly $4–6K over the two-month measurement window. The total swing is $45–75K in Mo's favor if the baseline is argued correctly and the data supports it.
Creative fatigue compounds faster than the creative engine can build. If new ads are not in market by Week 2 and home reallocation is not live by Day 4 (Thursday June 5), the account could continue declining from its May exit pace — showing Hassan a Week 1 that looks like the tail of May rather than the beginning of the recovery. This breaks trust before it is built. Mitigation: the creative brief deck is ready before Monday June 1. Lauren co-signs the first batch by Monday EOD. First six ads ship Day 2 (Tuesday June 2 or Wednesday June 3 at the latest). The compliance pauses and pacing rules go live Day 1 — before any creative ships — so the structural fixes are working before anyone can blame new creative for a performance change.
| Lane | Owner | Week 1 (June 1–7) | Week 2 (June 8–14) | Week 3 (June 15–21) | Week 4 (June 22–28) |
|---|---|---|---|---|---|
| Account ops | Mo + Lauren | Pause 3 "60%" ad IDs (Day 1, Hr 1). Set $33,500/day spend ceiling. Weekend throttle rule live by Day 4 (Thu). CPL suppression rule documented. Home reallocation to $6,700/day starts Thu June 5. | Confirm home at 15% of spend. Rotate bottom-quartile auto ad sets. Monitor 3-day rolling CPL; apply hold if CPL > $28. July 4 holiday cap pre-set. | Home spend to 20% of daily budget. Kill any ad set with ROAS < 1.10 at 1,000+ impressions. Scale only ad sets with CPL < $25. | Concentrate 80% of spend on top 6–8 proven concepts. Hold $33,500 ceiling or adjust upward if new creative holds CPL < $24. Set July scaling plan. |
| Creative production | Mo + War Room | Ship 6 ads Monday June 2 (FAST MOVERS, THE SWITCH, PCS MATH, DISASTER SEASON CHECK, PCS HOMEBUYER, RATE SHOCK RELIEF). Ship 4 more Thursday June 5 (POST-SERVICE RATE, EARNED RATE, THE MANAGER, BUNDLE THE SAVINGS). Pause 5 longest-running fatigued auto ads. | Ship 6 ads Monday June 8: 3–4 winner variants of top Week 1 performers + AFTER 20, ANNUAL REVIEW, HOMEOWNER BY 30. Ship 5–6 Thursday June 11: BASE ADJACENT, REFINANCE WINDOW, HOMEOWNER BY 30 variant, 2 new auto fills. Contact 8–10 veteran UGC creators. | Ship 7–8 ads Monday June 15: deep matrix fills (A3 carousel, A4 full coverage), first UGC ads if footage arrived. Ship 5–7 Thursday June 18. Kill bottom-decile non-performers (CPL > $35 at 500+ impressions). | Ship 6–7 Monday June 22: top-of-funnel volume variants of 2–3 proven winners. Ship 4–5 Thursday June 25: coverage fills + UGC second wave. Target 40–49 ads live with data by June 28. |
| Tracking / CAPI | Mo + Dev | Run Part 1 diagnostic with dev lead Tuesday June 2 (Pixel EMQ score, CAPI state, QW postback architecture, form type). Push EMQ quick-fix (hashed PII passthrough) same day if EMQ < 7. Deliver written technical spec to dev team by Thursday June 5. | Dev stands up CAPI server endpoint in test mode. Lead + QualityLead events firing and deduplicating against browser Pixel. EMQ score tracked. Begin QW postback receiver build (webhook or batch path, based on Tue findings). |
AcceptedLead pipeline goes to production. First live AcceptedLead events hit Meta. Request May historical export from QW for CAPI backfill. Monitor: weekly AcceptedLead volume vs. 50-event threshold needed for value optimization. |
Review AcceptedLead weekly volume. If ≥ 50/week, test holdout campaign optimizing on QualityLead with Highest Value bidding. Set up daily CAPI reconciliation report (browser Lead count vs. server Lead count vs. AcceptedLead count). |
| Compliance (Thread B) | Mo | Day 1 Hr 1: Pause ad IDs 1004559982134492 + 2 additional "60%" variants (confirm IDs at account access, prior to any other action). Day 1–2: Full live ad library audit for claims > 20% auto / 30% home. Day 2–3: Jornaya/TrustedForm cert hygiene audit brief to dev (sample 100 May leads). Day 4–5: Produce QW affiliate compliance package for Hassan sign-off. |
Day 3–4: TCPA consent language review of current QW-hosted form — document state vs. FCC One-to-One rule. Complete cert hygiene audit memo. | Day 5–7 carryover items cleared. Compliance documentation package sent to named QW affiliate contact. State DOI exposure scan complete. | No new compliance actions Week 4. Monitor: any Meta policy flag or QW compliance inquiry triggered by new creative. Confirm all active ads have cleared Mo's compliance gate. |
| Baseline vetting | Mo | Pull March + April 2026 data from Hassan/internal tool and QuoteWizard. Begin pulling July–August 2025 historical data from Meta Ads Manager. Do not raise baseline topic with Hassan this week. | Continue historical data pull. Run the four baseline methods (trailing 90-day, exit run rate, exit run rate ex-MDW, YoY seasonally adjusted) with actual numbers. Build Case File (Part 4 of Deliverable 04). Do not surface with Hassan. | June 15–21: With data in hand, request private 30-minute 1:1 with Hassan. "I want to walk you through what the data shows on the baseline before we finalize the contract." Deliver the opening script. Target: agree on methodology and get proposed baseline number to legal by June 28. | Follow up in writing if baseline conversation happened in Week 3. Send email with proposed baseline number and methodology. Goal: baseline locked in contract language before July 1 measurement window opens. |
| Form migration scoping | Mo + Lauren + Dev | Phase 0: Identify and read the QW contract — confirm exclusivity clause, termination notice period, ping-post language, volume commitments. Get contract copy by Tuesday EOD or it is a Wednesday emergency request. Confirm QW affiliate relationship manager name and email. | Phase 0 complete: Contract summary memo delivered. Determine if Tier 2 (ping-post) is contractually viable or blocked. Share with Hassan the four-tier spectrum and get alignment on Phase 1 staging build starting Week 3. | Phase 1: Dev begins staging form build (no live traffic). Consent language drafted per FCC One-to-One standard. Coordinate with CAPI build — shared infrastructure, do not let this block CAPI Week 3 delivery. | Phase 1 staging progresses. Dev continues staging build in parallel. QW API integration replicated in staging environment. No production traffic routed to new form. |
| Hassan-facing comms | Mo | Day 1 EOD: Send pre-office-visit note with specific ad IDs flagged for compliance. Day 2 EOD (Tuesday): Send Tuesday readout (3-item format per Deliverable 01 template). Daily 4-line performance email starts Thursday June 5 at 6PM EST. Friday June 6: Week 1 end-of-week summary. | Daily email continues. Monday June 9: First weekly review call (15 min). Share Week 1 scorecard and Week 2 budget plan. Friday June 13: Second weekly readout with first creative performance data. | Mid-week 1:1 (if scheduled): Baseline conversation. Otherwise: daily email + Friday readout continues. Content shifts to "creative engine is working, here is the data." | Friday June 27: End-of-June review. Month-1 summary, July–August forecast, scope adjustments. Prepare the July operating plan doc. |
Decisions: - Which ads to pause and which to protect (compliance + fatigue analysis) - Which creative concepts get into the weekly brief deck (War Room AI pipeline) - Which baseline methodology to argue and when to surface it with Hassan - Whether to recommend Tier 1 only or push toward Tier 2 on the form migration, based on QW contract review - What the daily 4-line Hassan email says and what is withheld
Deliverables Mo owns: - Technical CAPI spec (written brief back to dev team by June 5) - Compliance audit memo (ad library, cert hygiene, TCPA consent state) - Baseline case file (when historical data arrives) - Weekly creative brief deck (Monday + Thursday ship batches) - All Hassan-facing written communication — daily emails, Friday readouts, 1:1 prep
Hassan-facing artifacts: - Daily 4-line performance email (6PM EST, Thursday–Friday start, every day thereafter) - Friday weekly readout email (subject + 3-bullet format, see Part 7) - Tuesday June 2 office visit readout (sent same evening per template in Deliverable 01) - Mid-June 1:1 (baseline conversation) - June 30 month-1 summary and July–August forecast
| Dependency | What It Blocks | Mitigation |
|---|---|---|
| QW contract review (Week 1) | Form migration Tier 2 planning; possibly all Phase 1 work if exclusivity blocks even staging | Emergency request if not received by Tuesday — Mo flags this directly to Hassan as the highest-priority document request |
| CAPI endpoint live in test mode (Week 2) | AcceptedLead events flowing to Meta (Week 3), value optimization test (Week 4) | If dev is unavailable Week 2, EMQ quick-fix alone still lifts match quality; AcceptedLead slips to Week 4 |
| AcceptedLead ≥ 50 events/week (Week 4) | Campaign optimization switch from Lead to value-based event |
If volume is too low in June, the optimization switch becomes a July target — does not break the baseline CAPI rebuild |
| March/April 2026 historical data in hand | Baseline conversation with Hassan | Do not enter baseline 1:1 without this data confirmed. If data is delayed past June 14, push the 1:1 to June 21–24 |
| QW contract exclusivity clause not blocking Tier 2 | Form migration Phase 1 staging build (informing what the form needs to be capable of) | If exclusivity blocks Tier 2, Phase 1 is still worth building for CAPI and compliance reasons — scope adjusts |
| UGC footage delivered by creators by June 17 | First UGC ads live in Week 3 | Text-on-video placeholders substitute in Week 3; UGC becomes early July differentiator — does not materially change the June net revenue projection |
| QW accept-rate and per-lead payout data confirmed | Accurate baseline calc, CAPI event value calibration | Pull from QW affiliate dashboard on Monday June 1; this cannot be assumed from the CSV (all zeros in leads_sold) |
Hassan's model uses $275K as the June baseline. Mo's negotiation target is a trailing-90-day average, likely $155–185K pending historical data. The table below models both scenarios at 10% and 15% take rates on lift above baseline. All revenue figures are June net revenue.
| Scenario | Baseline | GP1 Target | June Rev Needed | Probability | Key drivers |
|---|---|---|---|---|---|
| Hassan's baseline | $275K | $316,250 | $316,250 | Low–Medium | Full execution required: creative engine + CAPI + home scale all delivering. No major account disruption. |
| Mo's argued baseline ($175K) | $175K | $201,250 | $201,250 | High | Achievable with quick wins alone (pacing + home + compliance). |
Mo's dollar earn at GP1: - At Hassan's baseline ($275K) and GP1 ($316.25K): Mo earns take rate on $41.25K/month lift × 2 months. - At 10% take: $8,250/month → $16,500 over measurement window - At 15% take: $12,375/month → $24,750 over measurement window - At Mo's argued baseline ($175K) and GP1 ($201.25K): Same math on $26.25K/month lift. - At 10%: $5,250/month → $10,500 — but GP1 is already cleared at much lower June rev, so July/Aug scaling produces much larger numbers - The negotiated baseline unlocks compounding upside in the measurement window, not just in June
What has to happen for GP1: Weekend throttle rule live by Day 4, home reallocation to 20% by Week 2, CPL suppression rule holding. No major Meta policy disruption. Memorial Day-equivalent weekend not repeated (July 4 holiday cap pre-set).
Probability at full execution: High (75–85%) with Mo's argued baseline. Medium (40–55%) with Hassan's $275K baseline.
| Scenario | Baseline | GP2 Target | June Rev That Sets Up GP2 | Probability | Key drivers |
|---|---|---|---|---|---|
| Hassan's baseline | $275K | $374,000 | $300K+ (sets trajectory) | Low | Requires CAPI rebuild delivering optimization improvement AND creative engine scaling into proven winners by end of June |
| Mo's argued baseline ($175K) | $175K | $238,000 | $230K+ | Medium–High | Full execution scenario: creative refresh + home at 22% + CAPI signal improving by Week 4 |
Mo's dollar earn at GP2: - At Hassan's baseline: $99K/month lift × 2 months - At 10% take: $19,800/month → $39,600 over measurement window - At 15% take: $29,700/month → $59,400 over measurement window - At Mo's argued baseline ($175K): $63K/month lift - At 10%: $12,600/month → $25,200 - At 15%: $18,900/month → $37,800
What has to happen for GP2: Everything in GP1 plus — CAPI AcceptedLead events flowing and improving algorithm signal by Week 3–4, home at 22–25% of spend by end of June with ROAS holding above 1.30, creative engine producing at least 3–4 concepts with CPL < $23 by end of Week 3. July–August run rate requires these improvements to compound.
Probability at full execution: Medium (35–50%) with Mo's argued baseline. Low (15–25%) with Hassan's $275K baseline.
| Scenario | Baseline | GP3 Target | What's Required | Probability |
|---|---|---|---|---|
| Hassan's baseline | $275K | $431,750 | Form migration Tier 2 delivering 25%+ RPL lift, creative engine at peak efficiency, CAPI on value optimization — all three compounding simultaneously in the measurement window | Very Low (<10%) |
| Mo's argued baseline ($175K) | $175K | $274,750 | Full execution + form migration A/B test showing early RPL lift in July | Low (15–20%) |
GP3 is a Q4 target, not a measurement window target. The form migration cutover does not happen in the measurement window — this is a hard rule. GP3 territory requires the Tier 2 RPL lift, which requires September cutover at the earliest. Do not promise GP3 at any point during June.
Mo's dollar earn at GP3: - At Hassan's baseline: $156.75K/month lift - At 10% take: $31,350/month → $62,700 over measurement window - At 15% take: $47,025/month → $94,050 over measurement window
The difference between a $175K and a $275K baseline, at GP2 July–August, at 15% take rate: - $175K baseline GP2 ($238K target): Mo earns $18,900/month → $37,800 for the window - $275K baseline GP2 ($374K target): Mo earns $29,700/month only if GP2 is actually hit — but at $275K baseline, GP2 is far harder to achieve
The baseline negotiation is not just about the number. It is about setting a target Mo can reliably beat, which earns more than a target Mo probably can't hit. Arguing to $175K and clearing GP2 at $238K is better economics than accepting $275K and barely clearing GP1 at $316K.
Ranked by P × I (Probability × Impact). Scale: H=High, M=Medium, L=Low.
| # | Risk | P | I | P×I | Mitigation | Early Warning Signal |
|---|---|---|---|---|---|---|
| 1 | Creative fatigue outpaces the creative engine — new ads don't land in market fast enough; account continues May's decline into Week 2 | H | H | HH | Brief deck ready before June 1. First 6 ads ship Day 2 (Tue/Wed). Home reallocation provides a non-creative lever that can hold margin while new auto creative spins up. Weekend throttle and spend ceiling reduce burn rate. | CPL still above $28 by June 10 with no improvement trend. Home ROAS degrading. Week 2 net revenue tracking below $60K. |
| 2 | Baseline gets locked at $275K before historical data is in hand — Hassan pushes to finalize contract before Mo has March/April data to argue against it | M | H | MH | Do not accept the baseline verbally or in writing before June 15. If Hassan pushes, say: "I want to get you a number I can sign my name to — I need the March/April data you mentioned and 48 hours to run the analysis. Let's get it right the first time." Never concede the baseline in a group setting. | Hassan sends a contract draft with $275K baked in before June 14. Legal pushes for signatures before data is confirmed. |
| 3 | Memorial Day-type weekend repeats (July 4) — holiday weekend burns budget for near-zero net | M | H | MH | July 4 holiday cap is pre-set before the weekend: $8,000/day hard cap for July 3–5, 2026. Lauren confirms the cap in her calendar Week 1. Monday June 9 review call explicitly covers July 4 pre-planning. | No pre-set cap in place by June 28. Lauren does not have written rule documentation by end of Week 1. |
| 4 | QW contract has hard exclusivity blocking Tier 2 — the highest-margin lever (multi-buyer ping-post, $50–85K/month) is contractually unavailable until renegotiation or contract expiry | M | H | MH | Identify this Week 1 — not Week 4. If exclusivity is confirmed, shift to: (a) push for contract amendment immediately, (b) negotiate an expiry date that aligns with September cutover plan, (c) ensure Tier 1 (own form, still post to QW) is sequenced correctly for compliance upside. | QW contract cannot be produced by Tuesday June 2. Rony or Lauren says "I don't know where it is" — this is a red flag requiring immediate escalation to Hassan. |
| 5 | Hassan resists baseline conversation or moves to in-house the playbook — pattern of in-housing what works; or baseline negotiation poisons the relationship before measurement window | M | M | MM | (a) Show wins first: visible revenue improvement in Weeks 1–2 makes Mo's credibility unassailable before the baseline conversation. (b) Frame baseline as protecting Hassan's model accuracy, not gaming Mo's comp. (c) War Room infrastructure remains proprietary — deliverables are outputs, not playbooks. IP belongs to GTW. | Hassan or Rony begins asking to see the War Room AI workflow or brief-generation process in detail. Hassan gives vague responses to the baseline 1:1 request. |
| 6 | Dev team capacity is thinner than estimated — CAPI rebuild and form migration staging compete for the same 1–2 engineers | M | M | MM | CAPI rebuild is explicitly prioritized over form migration staging. The EMQ quick-fix (hashed PII passthrough) is a one-day dev task that does not require a sprint. If dev bandwidth is constrained, CAPI Week 2–3 delivery holds and Phase 1 form build slips to August. Middleware fallback (Stape) is available if Iron Corp infra cannot support the CAPI endpoint. | Dev lead says "we don't have sprint capacity until mid-June" at the Tuesday meeting. Estimated dev hours for CAPI (40–60 total) not confirmed by Thursday June 5. |
| 7 | Form migration cutover lands in measurement window — Phase 2 A/B test starts in July and accept-rate dip drops July net revenue | L | H | MH | Hard rule: Phase 2 A/B test at 10–20% traffic in July is explicitly designed to be non-destructive. Full cutover (Phase 3) does not happen before September 1. This rule is documented in writing and agreed with Hassan at the Tuesday meeting. If Hassan pushes for earlier cutover, Mo's response is: "The compounding effect of the migration is worth $50–85K/month — we don't want to risk that in the 60-day window that determines my comp." | Hassan requests full form cutover in July. Lauren schedules a cutover that bypasses the A/B phase. |
| 8 | QW accept-rate data never flows into reporting — leads_sold stays at zero; CAPI AcceptedLead events are blocked without the QW postback |
M | M | MM | If QW does not send a real-time webhook, implement the batch CSV path (Deliverable 03, Path B). Historical May data backfill is possible via Meta's offline Conversions API up to 90 days back. CAPI Lead and QualityLead events still improve EMQ even without AcceptedLead. Mo asks for May historical accept data from QW on Monday June 1 (via QW affiliate portal — does not require contract negotiation). |
Dev confirms on Tuesday that QW sends no postback whatsoever, and QW portal has no data export. This triggers an immediate escalation to Mo's QW contact and potentially to the contract negotiation. |
Open the Iron Corp internal performance tool or the Meta Ads Manager summary. Check: 1. Yesterday's spend, net revenue, ROAS, CPL. Is CPL above $28? Is ROAS below 1.25? Flag immediately. 2. 3-day rolling CPL. If it crossed $28 yesterday, the suppression rule triggers — cap today's spend 20% below yesterday's. 3. Home ROAS vs. auto ROAS. If home is outperforming by more than 0.15 ROAS points, note it as a potential case for increasing home share in today's Lauren sync. 4. Any compliance flags. Meta policy emails, account warnings, QW postback anomalies. These are emergencies — handle before anything else. 5. Draft the 4-line daily email to Hassan (sent at 6PM — write the draft in the morning so it only needs the day's final numbers filled in).
The morning check is not analysis — it is signal monitoring. If everything is within bounds, it takes 10 minutes. If something is off, the morning check is what surfaces it before Mo is in reactive mode at 3PM.
Creative review and ad rotation decisions (Monday and Thursday only, 30 min): - Pull CPL and impressions for all active ads by codename. - Identify any ad at 1,000+ impressions with ROAS < 1.10 (pause threshold). - Identify any ad with CPL > $35 at 500+ impressions (kill threshold). - Confirm the ship-day batch is co-signed with Lauren for that day's upload.
Lauren sync (every day, 10–15 min max, async preferred): - Share any new spend decisions (scale home, pull back over-CPL auto ad set). - Confirm any pacing rule changes needed based on morning data. - Get Lauren's read on anything platform-side that doesn't show up in the CSV (audience size changes, ad set learning restarts, billing alerts).
Non-Monday/Thursday days: Mid-day is 10–15 minutes for Lauren async check-in only. Reserve 30-minute mid-day blocks on Tuesdays and Wednesdays for deeper work.
Rotating focus by day of week: - Monday: Weekly creative brief deck for Thursday ship. Pull the week's performance data, identify top performers, brief 5–6 new variants via War Room AI pipeline. - Tuesday: Deep dive on CAPI/tracking (especially in Weeks 1–2). Review dev progress. Escalate any blocked items. - Wednesday: Baseline vetting work (in Weeks 2–3 after data arrives). Build or update the case file. Hassan report preparation for Friday. - Thursday: Creative QA for same-day ship. Compliance gate review of batch before Lauren uploads. Monday brief preparation begins. - Friday: Weekly readout drafting. Review full week's data, spot any trend changes, update the Week N+1 plan.
The daily routine is designed around a single principle: Hassan sees consistent professionalism in the daily email before he sees anything else. If Mo is in a war room crisis at 5:45PM and sends a late email, that is a trust signal — in the wrong direction. The email routine is non-negotiable.
The 4-line email — sent at 6:00 PM EST, every day from Thursday June 5 onward
This is the non-negotiable. Hassan watches daily numbers. He will form his mental model of Mo's competence from the cadence and precision of these emails more than from any other single artifact.
Format:
Subject: Military.com — [Day, Date] performance
Spend: $XX,XXX | Net: $XX,XXX | ROAS: X.XX vs. prior week same day: Net [+/-]XX% ($X,XXX)
What moved: [one sentence — specific, causal, not vague. "Home ad set (PCS HOMEBUYER codename) generated $X,XXX net at ROAS X.XX — outperforming auto average by 0.18 ROAS points. Held auto spend flat per CPL suppression rule."]
Tomorrow: [one sentence on the plan or the watch item. "Thursday new creative batch ships — AFTER 20 and ANNUAL REVIEW enter rotation."]
Mo
The email is four lines. It is not a report. It does not require Hassan to ask follow-up questions. It is a signal that Mo is watching the right things and nothing is on fire.
Subject: Military.com — Week [N] summary + Week [N+1] plan ($XXK net)
Body (3 bullets, then a one-line forward look):
- This week: $XXX,XXX net revenue ([+/-]X% vs. prior week / vs. $65K Week 1 target). Spend: $XXX,XXX. ROAS: X.XX. [Most important performance story in one sentence — what drove the number up or down.]
- What changed: [Two or three specific changes made this week — ad IDs paused, budget reallocated to home, pacing rule executed, new creative shipped. Be specific. "Paused 3 compliance ad IDs Day 1 per FTC guidance. Moved home from 8% to 15% of daily spend Thursday. 10 new ads shipped this week — first data in Monday's email."]
- Week [N+1] plan: [Two or three specific actions for the next week — e.g., "Home spend increases to 20% Monday. 10–12 new creative ads ship Monday and Thursday. CAPI endpoint going live in test mode — first AcceptedLead events in Meta by Friday June 12."]
On track for $[weekly/monthly target]. Talk Monday.
The Friday readout is the document Hassan shares internally or reads over the weekend. Keep it under 150 words. The shorter it is, the more it reads like control — not like Mo is explaining himself.
Timing: June 15–21 window. Private call, 30 minutes. Not on the group call. Not with Lauren in the room.
Request phrasing: "Hassan, I want to walk you through what the data shows on the baseline before we finalize the contract. 30 minutes this week? I want to make sure we're measuring the right thing from day one."
Opening (deliver these three sentences exactly):
"Hassan, I've been doing the data work before we finalize the contract — that's the due diligence I owe you and me both. I want to walk you through what May actually showed when you look at the daily curve, and share the baseline methodology I think is fairest for the pilot. I'm not trying to game the number — I'm trying to make sure we're measuring what I actually contribute, not what the account happened to do in week one."
Then open the day-by-day chart. Let the data speak. Have the Case File from Deliverable 04 printed or on screen — Week 1 ran at $434K/month pace; Week 4 ran at $89K/month pace; May exit run rate was $103–154K/month. The $275K is a blend of four different businesses. Do not attack Hassan's number — deconstruct it with data.
The close (from Deliverable 04):
"Here's what I'd like to do: let's agree on the methodology today — trailing 90-day average, excluding one-time events — and you send me the March and April numbers. I'll do the math and send you a one-line proposed baseline by [date + 2 days]. If we're aligned, it goes into the contract that week. I want this resolved before July 1 so neither of us is guessing when measurement starts."
Then stop talking. Wait.
Follow-up within 48 hours: Email with proposed baseline, methodology, and source data. "Please confirm by reply so legal can incorporate." Get it in writing before July 1.
Format: One-page document (can be a Notion page or a PDF) delivered before the end-of-June call. Content:
This document should take Hassan less than 5 minutes to read. It is not a performance review — it is the operating plan for Month 2, delivered with Month 1's data as the foundation.
| Cadence | Format | Content | Trigger |
|---|---|---|---|
| Daily (6PM EST) | 4-line email | Spend / Net / ROAS + what moved + tomorrow | Every day, starts Thu June 5 |
| Weekly (Friday) | 3-bullet email | Week recap + what changed + Week N+1 plan | Every Friday |
| Mid-June (June 15–21) | Private call | Baseline conversation | Mo schedules proactively after data arrives |
| End of June | 1-page doc + call | Month-1 scorecard + July–Aug forecast + scope review | June 27–30 |
The trigger: Week 2 cumulative net revenue (through June 14) is below $100K and CPL is still above $27 despite the pacing rules being live. This means the account is not recovering from May's exit pace — it is tracking toward the $87–100K no-intervention scenario.
What Mo does: 1. Pull the ad-set-level CPL breakdown immediately. Is the CPL problem isolated to specific ad sets (creative fatigue in specific segments) or account-wide (bid strategy issue, audience exhaustion, Meta policy change)? 2. If it is isolated: accelerate the creative pipeline — push Week 3 ship day forward to Monday June 15 instead of waiting for the organic schedule. Pull the worst-performing auto ad sets entirely rather than throttling them. 3. If it is account-wide: check for a Meta policy flag or account-level bid strategy change. If the bid strategy (cost cap, lowest cost, bid cap) was changed at any point in May or June, revert to the last known-good configuration. 4. Call Hassan before he notices: "Hassan, Week 2 is tracking below my target. Here's what I see, here's what I'm changing, and here's what I'll report back Friday." Do not wait for Friday to surface a bad trend. Hassan finding out from the Friday email that Week 2 was bad is worse than Hassan hearing it Wednesday with a plan attached. 5. Revise the June target in writing — do not hold the $250K+ target after Week 2 data clearly shows it is out of reach. The credibility of conservative accuracy is worth more than the optics of optimism that doesn't land.
The trigger: The contract, reviewed in Week 1, contains explicit language prohibiting Iron Corp from selling leads to any buyer other than QuoteWizard during the contract term. The termination notice is 60–90 days or longer. Tier 2 (ping-post multi-buyer) is blocked until a contract amendment or expiry.
What Mo does to the form migration scope: 1. Immediately pivot to Tier 1 framing only for the measurement window. The form migration becomes a compliance and CAPI infrastructure project, not a margin lift project. This is still worth doing — cert hygiene, FCC One-to-One consent language, CAPI server-side infrastructure — but the RPL math changes. 2. Initiate a QW contract renegotiation conversation through Hassan or Rony. The ask: an amendment permitting ping-post to 1–2 additional buyers on a trial basis (e.g., SmartFinancial or EverQuote) with a 60-day test window. This is not confrontational — it is a commercial opportunity for QW to demonstrate their competitiveness. 3. Revise the expected impact model. Without Tier 2, the form migration's month-over-month impact drops from $50–85K to $15–30K (CAPI + UX improvement only). Adjust the July–August forecast and Hassan's expectations accordingly. 4. Set a hard date for when the exclusivity clause expires or can be amended. If it's December 2026, the Tier 2 discussion becomes a Q1 2027 planning item. If it's September 2026, the timeline works.
The trigger: Mo requests the private 1:1 and Hassan deflects — "let's just go with the model I built," "we can sort that out after a few months of data," or he involves Lauren or Rony in the conversation. The baseline is being handled as a group matter or deferred past July 1.
Mo's backup: 1. Do not escalate or push further in that conversation. Step back: "Of course — let's talk after you've seen the first few weeks of data. I just want to make sure we have it documented before measurement starts." This buys time without conceding. 2. Send an email within 24 hours: "Hassan, following up on our conversation — I want to make sure the baseline is documented before July 1. I've put together a one-page summary of what the May data shows and a proposed methodology. Can you review and let me know if you'd like to discuss?" Attach the Case File (Deliverable 04, Section D with Mo's proposed talking points removed — just the data section). 3. If Hassan does not respond within 5 business days: Mo accepts the baseline is likely going to be his number ($275K) unless the contract language allows for a post-hoc adjustment. Shift strategy: negotiate hard on the adjustment clause triggers (Deliverable 04, Section 6.3) — specifically, the provision that the baseline resets if QW payout rates change by >15% or if Meta implements a policy change materially restricting targeting. These are the fallback protections. 4. The absolute floor: Do not sign a contract with $275K as a hard, unadjustable baseline and no audit rights. That is the scenario where Mo performs well and the comp structure doesn't reflect it. The audit rights clause (Deliverable 04, Section 6.4) and the adjustment triggers (Section 6.3) are non-negotiable minimums even if the baseline number stays at $275K.
Material unknowns going into June 1 — ranked by decision impact:
QW contract terms (exclusivity clause, termination notice, ping-post language, volume commitments). This is the highest-impact unknown in the entire engagement. It determines whether Tier 2 is a June-to-September project or a 2027 project, and it shapes the entire form migration scope. Must be resolved by Wednesday June 4.
March and April 2026 net revenue actuals. Hassan stated April was approximately $125K — this has not been confirmed with data. The trailing-90-day baseline calculation is entirely dependent on these numbers. Without them, the baseline conversation cannot happen. Mo requests these from Hassan by Tuesday June 2.
QW accept rate and per-lead payout in June vs. May. The leads_sold column in the May CSV is all zeros — the internal reporting system does not consume QW postback data. Mo does not know the actual accept rate (estimated at ~25% based on implied math: $281,622 / $33.52 RPL = ~8,400 accepted leads out of ~33,368 total) or whether the RPL in June will hold at $33.52 or compress further. This is a Day 1 pull from the QW affiliate dashboard.
Current CAPI/Pixel state — EMQ score, whether CAPI exists at all, and which form architecture is live. The CAPI rebuild timeline (Weeks 2–4) and its expected impact ($20–55K/month) depend entirely on what the Tuesday June 2 diagnostic reveals. If CAPI is already partially in place, the timeline accelerates. If the form is a full redirect to QW's domain (Architecture B), the implementation path differs. Unknown until Tuesday.
Dev team capacity for June. The CAPI rebuild requires approximately 40–60 dev hours across June. The Phase 1 staging form build requires an additional 3–5 weeks of dev time. If both are competing for the same 1–2 engineers, one of them slips. The CAPI rebuild is prioritized — but Mo cannot make that prioritization explicit until the Tuesday conversation reveals what the team is currently committed to.
Mo's exact take rate on lift above baseline. The context brief states "base fee + % of growth above a baseline" but the specific percentage is TBD in the contract. The dollar-impact calculations in Part 4 model 10% and 15% scenarios, but the actual take rate changes the dollar stakes of every baseline and goal-post number. This must be locked in writing before July 1.
July–August 2025 historical performance actuals. Hassan's growth model assumes +64% organic growth from June to December 2026 (8.6% CMGR). The YoY seasonally adjusted baseline method (Method 4 in Deliverable 04) requires the 2025 summer actuals to pressure-test whether that growth assumption is historically grounded or an optimistic projection. Mo pulls this from Meta Ads Manager starting June 2. If June–August 2025 came in at $120–160K/month, Hassan's 64% organic ramp has no historical precedent and Mo's baseline argument becomes even stronger.
All five workstream deliverables (01 through 05) are in /Users/mo/Desktop/military.com/deliverables/june_2026/. This master document synthesizes and cross-references them but does not replace them — the action-level detail lives in each workstream file.
Last updated: May 31, 2026 | Next review: Monday June 7, 2026 (end of Week 1)