GTW × Military.com — Master June 2026 Strategy

Go To War Strategy | Mo Alissa Effective: June 1 – June 30, 2026 Status: Living operating document — review every Monday morning

PART 1 — EXECUTIVE SUMMARY

The Bet

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.

Headline Targets

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.

The Three Things That Compound

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.

Baseline Vetting Timeline

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.

The Single Biggest Risk

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.

PART 2 — WEEK-BY-WEEK ROADMAP

Roadmap Overview

PART 3 — OWNER / DEPENDENCY MAP

Mo Solo

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

Mo + Lauren

• Account operations: spend decisions, pacing rules, cap implementation, ad set management
• Creative approval: every batch brief goes through a 30-minute co-sign call before ship day — no per-ad bottleneck after initial sign-off
• Audience strategy: post-Week 1, once Mo has ad-set-level data, identify over-exposed audiences vs. under-served ones
• Weekend/holiday throttle rule: Lauren sets the caps, Mo documents the rule and the thresholds
• CPL suppression rule: Lauren monitors daily CPL, Mo sets the thresholds ($28 trigger, $25 reset)
• Home budget reallocation: Mo recommends in writing, Lauren executes
• Creative rotation: Mo runs the analysis, Lauren executes pauses and activations

Mo + Dev Team

• CAPI rebuild: Mo provides the diagnostic framework (Part 1 of Deliverable 03) and the event taxonomy; dev builds the endpoint, the postback receiver, and the batch processor
• EMQ quick-fix: Dev implements hashed PII passthrough — a one-line GTM or code change — ideally Tuesday June 2
• Cert hygiene audit: Mo provides the audit spec; dev pulls the lead sample and writes the validation script
• Form migration staging (Phase 1): Dev builds the Iron Corp-hosted form in staging with QW API integration replicated exactly; Mo coordinates the CAPI infrastructure reuse
• QW postback architecture: Dev confirms on Tuesday (webhook vs. batch vs. daily email) — this determines the AcceptedLead implementation path

Mo + Hassan

• Baseline conversation: mid-June, private 1:1, after historical data is confirmed
• Strategic direction: any change to spend ceiling above $40K/day requires Hassan alignment
• QW contract review: Mo surfaces the four migration tiers and the QW exclusivity question; Hassan provides or confirms access to the contract

Blocking Dependencies

PART 4 — EXPECTED IMPACT TIED TO GOAL POSTS

The Goal-Post Structure

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.

GP1: +15% over baseline

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.

GP2: +36% over baseline

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.

GP3: +57% over baseline

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

Summary: The Baseline Negotiation's Dollar Leverage

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.

PART 5 — RISK REGISTER

Ranked by P × I (Probability × Impact). Scale: H=High, M=Medium, L=Low.

PART 6 — MO'S DAILY ROUTINE

Morning (15 minutes — before anything else)

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.

Mid-Day (30 minutes)

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.

Afternoon (45 minutes)

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.

End of Day (15 minutes)

1. Fill in the day's final numbers in the morning draft of the Hassan email. Send at 6PM EST — no exceptions. This is the single most visible credibility signal Mo has in the first 30 days.
2. Note one thing that needs Lauren's attention before tomorrow morning (Slack message, 2 sentences max).
3. Note one thing that needs dev's attention before the next milestone (only if blocking).
4. Plan tomorrow's single most important action. Write it down.

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.

PART 7 — HASSAN COMMUNICATION CALENDAR

Daily Cadence

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.

Weekly Friday Readout

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.

Mid-June 1:1 — Baseline Conversation

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.

End-of-June Review (June 27–30)

Format: One-page document (can be a Notion page or a PDF) delivered before the end-of-June call. Content:

1. Month 1 scorecard: June net revenue total, vs. Week 1 target, vs. May exit pace, vs. May full month. Creative engine stats (ads shipped, ads active, CPL/ROAS of top performers). CAPI status (EMQ score, AcceptedLead events flowing, optimization signal improving).
2. July–August forecast: Conservative, base, and optimistic revenue scenarios tied to specific workstream outcomes. Be specific: "If CAPI optimization switch happens Week 2 of July and home holds at 22% of spend, base case is $[X]K/month."
3. Any scope adjustments requested: If QW contract confirmed Tier 2 is viable, surface the September form migration timeline. If CAPI is ahead of schedule, note the optimization event switch timeline. If any workstream is behind, name it and give the adjusted timeline.

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.

Communication Calendar Summary

PART 8 — WHAT COULD FORCE A STRATEGY PIVOT

Signal 1: June Revenue Tracking >20% Below Conservative Target by Week 2

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.

Signal 2: QW Contract Has Hard Exclusivity Blocking Tier 2

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.

Signal 3: Hassan Resists the Baseline Conversation Entirely

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.

ASSUMPTIONS & OPEN QUESTIONS

Material unknowns going into June 1 — ranked by decision impact:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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)

GTW × Military.com — First-Week Operating Plan

Mo Alissa / Go To War Strategy Effective: Monday June 1 – Sunday June 7, 2026 Account access: Monday June 1 | Office visit: Tuesday June 2

Part 1 — Tuesday June 2 Office Visit Agenda

Opening 90 Seconds (Hassan + the Room)

Deliver this standing, before anything is on a screen:

"Hassan, thank you for the intro. I want to be clear about how I'm wired: I'm not here to replace what Lauren and the team have built — I'm here to run the playbook for the gap between where performance is today and where it needs to be for July. I spent the weekend in the May data. I know exactly what broke in Week 3 and I know the three things we can fix before Friday that will show up in next Monday's numbers. I'm not going to pitch. Let's just get into it."

This sets three things in the first 90 seconds: respect for Lauren, credibility from data work, and urgency without alarm. Do not mention GP1/GP2/GP3. Do not mention the QW migration. Do not mention the baseline negotiation.

People Mo Must Meet in Person (Tuesday June 2)

1. Lauren (In-House Media Buyer)

Tone: Peer-to-peer. She runs the account today. Mo is the strategist bringing a playbook; she is the operator who executes it. Never imply she caused the decline.

5 Questions to Ask Lauren:

1. "Walk me through the current campaign structure — how many campaigns, how are they split between auto and home, and are they in separate ad accounts or the same BM?" (Establishes the exact architecture before Mo assumes anything from ad-level data.)

2. "Which ad sets are you watching most closely right now — and which ones have you already tried pulling back or killing in the last two weeks?" (Identifies what she already knows is fatigued. Avoids Mo flagging something she already killed. Shows respect.)

3. "When you scaled spend in Week 3 — the push up to roughly $36K–$40K days around May 18-19 — was that at Lauren's discretion, directed by Hassan, or triggered by some ROAS threshold in the system?" (Critical for understanding the decision chain. Do not make it accusatory — frame it as "I'm building the pacing rules, I need to know who has authority to scale.")

4. "What's the current bid strategy on auto — lowest cost, cost cap, bid cap? And has that changed at any point in May?" (CPL moved from $18.98 on May 4 to $32.30 on May 23 — a 70% move. Bid strategy changes are the most likely non-creative cause.)

5. "Is there a creative that's still live and still healthy — something running that you'd be nervous about touching — or are they all showing fatigue signals?" (Want to know what NOT to touch. The single worst move is pausing a surviving winner. Get Lauren to flag it.)

2. Dev Lead (Name TBD — confirm before Tuesday)

Tone: Technical peer. Dev owns the funnel, the form, and the tracking infrastructure. Mo needs access, not control. Frame every question as "I want to understand what's there so I don't step on anything."

5 Questions to Ask the Dev Lead:

1. "What's the current Pixel implementation — is it firing standard events only (Lead, PageView, ViewContent), or do custom events exist? And are they firing on the QuoteWizard redirect or on a Military.com-hosted confirmation page?" (If Pixel fires on QW redirect, there is no visibility into post-form quality. This is the data plumbing root cause.)

2. "Is CAPI (Conversions API) live? If yes, what's the event match quality score, and is it server-side only or running alongside the browser Pixel in redundant mode?" (CAPI status determines whether targeting can recover without new creative. If it's absent or broken, that's a Day 1 fix request.)

3. "What does the QuoteWizard postback setup look like — are accepted/sold leads being passed back to Meta as a purchase or custom conversion event, or is the optimization signal just 'lead submitted'?" (This is the value-blind optimization problem. If Meta is optimizing on form submission and QW accept-rate is 40%, Meta is learning on noise.)

4. "What's the CMS migration timeline — specifically, is there any work in flight right now that touches the form, the landing pages, or the tracking stack? And is there a code freeze window coming before July?" (Need to know if there are planned changes that could collide with CAPI work. Also protects the QW migration sequencing decision.)

5. "If I needed to spin up a Military.com-hosted lead form — not replacing QW, just a parallel test with a small traffic split — what's the lead time on the dev side to get that live? What does the dependency chain look like?" (Hassan's second priority. Get an honest timeline now so Mo can sequence it correctly and not promise what can't ship in the measurement window.)

3. Rony Arzoumanian (Valnet Head of M&A, President Iron Corp US Inc.) — Meet if Present

If Rony is in the Montréal office Tuesday, meet him for 10 minutes. He is running Military.com day-to-day and is the day-to-day decision-maker for anything that isn't Hassan's direct attention.

3 Questions for Rony:

1. "What does success in June look like to you specifically — is it net revenue recovery, ROAS floor, or something else?" (Align with Rony's frame early. If his frame differs from Hassan's goal-post model, Mo needs to know.)

2. "Who has authority to approve new creative spend if Mo's team identifies something that needs a fast test budget — $5K-$10K — in the next two weeks? Is that Lauren, you, or Hassan directly?" (Removes a future blocker.)

3. "Is there any current or pending QW contract renegotiation in motion, or is the current payout/accept-rate structure fixed for the 90-day pilot window?" (If QW terms are in flux, Mo needs to know before he builds the baseline case around QW economics.)

Data Mo Must Walk Out With by Tuesday EOD

If Mo leaves Tuesday without the QW contract terms and the Meta ad-level export, those are the two emergency requests — get them by Wednesday morning or nothing else can proceed on schedule.

What Mo Commits to in the Room (and What He Explicitly Does NOT)

Mo commits to:

• A written Wednesday readout of the three highest-priority fixes with specific actions and expected impact range
• A daily performance email to Hassan/Rony starting Thursday (4-line format: spend, net, ROAS, what moved)
• A Friday end-of-week summary covering what was changed, what the data shows, and the Week 2 plan
• Treating Lauren as the account operator — Mo does not touch the account directly without her consent

Mo explicitly does NOT commit to (say this in the room, clearly, once):

• A specific net revenue number for June. Specific target gets locked in the Wednesday readout after Mo has ad-level data. "I can tell you my directional target in the data is a recovery toward $250K net for June. I'll put a number I'll sign my name to in writing on Wednesday once I have the ad-level breakdown."
• GP3 achievement in the pilot window. Do not mention GP3 at all.
• The QW form migration in the measurement window (June-August). Frame it as Q4 infrastructure.
• Any creative production timeline — creative production is Day 8+. Week 1 is optimization and pacing only.

Part 2 — Days 1-7 Quick-Win Action Plan (From May Data Analysis)

Finding 1 — Compliance Sunset: Three "Save Up to 60%" Ads Still Live

The finding: Three ads with known Ad IDs from the prior audit are running the "Save up to 60%" claim. The FTC substantiation standard for "up to X%" requires the maximum savings to be achievable by a non-trivial percentage of purchasers. Industry standard (and FTC guidance post-2022) treats auto insurance savings claims above 15% as needing state-level actuarial backing. Military.com cannot produce that backing. If Meta flags these under the insurance advertising policy update (rolling enforcement since Q4 2025), the account could receive a policy strike or temporary spend restriction — which would be catastrophic during the measurement window.

The action: Pause all three ads Day 1, Hour 1. Do not archive — keep them for reference. Replace with existing ads using "Save up to 15%" language, which is already in the library and has performance history. Submit no new creative with percentage savings claims until Mo reviews with a compliance lens.

Owner: Lauren executes the pause. Mo flags the specific Ad IDs in the Tuesday meeting and sends the written instruction to Lauren by Monday EOD (before office visit) to act first thing Tuesday morning.

Expected dollar impact: Neutral on revenue in the short term. The risk avoided is account-level: a single policy strike during the measurement window would cost multiples more than these ads contribute. Treat as $0 gain, priceless risk reduction.

Timing: Day 1 (Monday June 1) — the single action Mo takes before the office visit.

Finding 2 — Weekend / Holiday Throttle Rule

The finding: Across May, weekends averaged $5,479 net/day on $23,909 spend — a 17% margin. Weekdays averaged $11,063 net/day on $28,714 spend — a 28% margin. The gap is not noise: Monday and Tuesday are the two highest net/day of the week ($12,923 and $13,428 respectively). Saturdays and Sundays are the two worst.

Memorial Day weekend (May 23-25) is the extreme case: $78,321 spent, $1,613 net. A single 3-day window burned $76,708 for nearly zero return. The carrier accept-rate dynamics around holidays are well-documented in insurance lead gen — buyers thin out and RPL collapses. The data shows RPL was $29.20 on Saturday May 23 vs. $36.32 average on Mon-Thu in W1.

The action — Weekend Throttle Rule: Starting immediately, set a standing rule:

• Friday: Reduce spend to 70% of the prior Thursday's spend by 5:00 PM.
• Saturday/Sunday: Cap daily spend at $12,000 total unless ROAS exceeds 1.40 by the 10:00 AM optimization window. If ROAS is below 1.40 at 10:00 AM, cut to $8,000 floor.
• Holidays (Memorial Day, Independence Day, Labor Day): Hard cap at $8,000/day for the 3-day window. Flag these dates in Lauren's calendar now — June has no major holidays; July 4 is the next risk date.
• Monday rebound rule: Do not increase spend above Wednesday-Thursday levels until Monday 2:00 PM performance data confirms ROAS ≥ 1.35.

Owner: Lauren sets the caps. Mo documents the rule in writing by Wednesday and Lauren confirms the implementation setup (dayparting or manual scheduling).

Expected dollar impact: Applying the weekend rule retroactively to May: the 8 weekend days spent $191,126 and generated $44,113 net. At the weekday efficiency level (38% margin), that same $191,126 would have generated $72,628 net — a $28,515 delta. In a full June run (8-9 weekend days), capturing even 50% of that efficiency gap is worth approximately $12,000-15,000 additional net. This is the single largest recoverable dollar value from a structural rule change.

Timing: Document by Day 3 (Wednesday). Live by Day 4 (Thursday) at the latest. The first high-risk weekend is June 6-7 — the rule must be in place before Friday June 5 EOD.

Finding 3 — Bottom-Quartile Days Suppression Rule (May 22-24 + May 29 Pattern)

The finding: Four specific days — May 22 (Fri), May 23 (Sat), May 24 (Sun), and May 29 (Fri) — spent a combined $109,288 and generated $-1,555 net combined (spend of $109K, returns near zero). The common thread is not just the day of week: May 22 is a Friday, but it followed three consecutive days of spending above $35K/day (May 19-21). CPL on May 22 hit $30.90 — 39% above the W1 weekday average. The pattern is: audience exhaustion from over-scaling drives CPL above RPL, and the first casualty is Friday (already a structurally weaker day), which then cascades into a terrible Saturday.

The suppression rule: Implement a rolling 3-day CPL watch. If the 3-day rolling average CPL exceeds $28.00 (the level at which margin compresses below 15% at the May RPL average of $33.52), trigger an automatic spend hold:

• Step 1: No spend increase permitted (freeze any pending scale).
• Step 2: Pull total spend down 20% the next morning.
• Step 3: Do not restore scale until 3-day rolling CPL falls below $25.00.

The $28.00 trigger is derived directly from the data: May 20 CPL was $28.32 and May 21 was $28.12 — the two days immediately before the cliff. May 22 opened at $30.90 and never recovered.

Owner: Lauren monitors CPL daily and applies the hold. Mo provides the written rule and the threshold numbers. Joint review each Monday morning.

Expected dollar impact: The $109K spent across those four days yielded roughly break-even net. If the suppression rule had been in place and spend had been cut to $12K/day on May 22-24 and $12K on May 29 (instead of $34K, $31K, $24K, $20K), the conserved spend would be approximately $53K redirected to Mon-Thu days in June. At Mon-Thu efficiency (28-32% margin), that $53K generates approximately $15,000-17,000 additional net. Realistic one-month impact: $10,000-12,000 (accounting for imperfect redeployment).

Timing: Rule documented Day 3 (Wednesday). Applied immediately to any spend decisions Thursday onward.

Finding 4 — Spend Over-Scaling Cap Until New Creative Is in Market

The finding: The single largest cause of May's collapse was scaling from $24K/day (W1) to $36-40K/day (W3 peak, May 18-19) on the same approximately 10 creative concepts without new entrants. Frequency rises with spend; reach exhausts; CPL climbs. The data shows this precisely: CPL was $18.98 on May 4 (low spend, fresh creative pool), rose to $26.44 by May 19 (high spend, same creative), and hit $32.30 by May 23 (creative fully exhausted, spend still elevated). At the W3 peak, the account was spending 50% more per day and generating 20% less net per day than W1 — a -46% efficiency swing in 18 days.

The action — Spend Cap Rule: Until new creative is in market (minimum 3 new concepts tested and showing ROAS ≥ 1.30), implement a hard daily spend ceiling:

• Auto insurance campaigns: $28,000/day hard cap
• Home insurance campaigns: $5,500/day (see Finding 5 for rationale)
• Total combined ceiling: $33,500/day until new creative validates

This is a reduction from the W3 peak ($40,395 on May 19) and roughly matches W2 efficiency levels where net/day was $13,200 average.

Owner: Lauren sets the caps in Ads Manager. Mo reviews with Lauren on the Wednesday call whether any campaign is currently above ceiling and acts immediately.

Expected dollar impact from the cap alone: Neutral on net revenue in the very short term — but the cap prevents further efficiency erosion. At the W3 peak, every additional dollar of spend above $28K was generating approximately $0.25 net margin (ROAS 1.16 on May 21). Holding at $28K instead of $36K/day saves $8K/day in wasted scale-for-waste's-sake spend and redirects it to higher-efficiency days. Across a 20-day June weekday run: approximately $18,000 in spend conserved, convertible at higher efficiency.

Timing: Day 1. Mo reviews the account Monday and flags to Lauren any campaigns currently above ceiling.

Finding 5 — Home Insurance Budget Reallocation

The finding: Home insurance grew from under 3% of revenue in W1 to over 16% by May 28 and 24% by May 30. More importantly, home ROAS has been consistently better than auto ROAS in the final two weeks of May:

• May 26: home ROAS 1.89, auto ROAS approximately 1.06 (backing out home from blended)
• May 27: home ROAS 1.56, auto ROAS approximately 1.07
• May 28: home ROAS 1.60, auto ROAS approximately 1.08
• May 30: home ROAS 1.07 (degrading as spend increased)

The overall May home ROAS was 1.36 vs. auto overall at 1.33 — nearly identical at scale, but home is on an upward trajectory while auto is declining. Home is also underspent: home received 8.2% of total May spend ($68,854 of $836,793) but contributed 8.4% of gross revenue. More critically, home is not yet fatigued — it has room to scale before hitting the CPL wall that crushed auto.

The specific reallocation recommendation: Move home insurance from 8.2% of total daily spend to 20% of total daily spend starting Week 2 (Monday June 8, after Mo has verified creative inventory on Tuesday).

At the $33,500/day ceiling: $6,700/day to home (up from ~$2,300/day in late May) and $26,800/day to auto.

The rationale for 20% (not higher): home creative inventory is unknown until Tuesday. Do not over-allocate before confirming there are at least 5 active home concepts. At $6,700/day on home with a conservative ROAS of 1.40 (below the late-May peak ROAS of 1.56-1.89), home generates $9,380/day revenue vs. $6,700 spend — a $2,680/day net contribution from home alone. That compares to May W4 where home was generating approximately $700-800 net/day at $2,300 spend.

Expected dollar impact: Moving from $2,300/day to $6,700/day on home at ROAS 1.40 generates an incremental ~$1,880 net/day from home. Over 15 weekdays in June (post-Week 1): approximately $28,000 in incremental net revenue from home alone. This is the single highest-confidence revenue action in Week 1.

Owner: Mo recommends the reallocation in writing by Wednesday. Lauren executes the shift on Thursday June 5 (allowing Wednesday to be the briefing day and Thursday the execution day).

Timing: Recommend Day 3 (Wednesday). Execute Day 4 (Thursday June 5).

Finding 6 — Creative Rotation Strategy for the Existing ~240 Ad Library

The finding: Without ad-level data (arriving Monday), the exact count of active vs. paused ads is unknown. Based on audit context from prior GTW deliverables and the May performance pattern, the account has approximately 240 ads in various states of life cycle. The problem is not the total count — it is that the same concepts are running across the same ad sets simultaneously, creating internal frequency competition and exhausting the audience faster than if rotated.

Week 1 creative management protocol (before new ads are available):

1. Day 1-2 (Mon-Tue): After getting ad-level data Monday, identify the longest-running active variants — any ad that has been live 21+ days without a pause. Flag these as "rotation candidates" (do not pause yet).

2. Day 2 (Tuesday, in the meeting): Ask Lauren: "Which ad sets have the highest frequency per unique user — above 3.5x in the last 14 days?" Those ad sets are the priority rotation targets.

3. Day 3 (Wednesday): Pause the bottom 25% of active ads by 14-day ROAS in any ad set showing frequency above 3.5x. Do not pause globally — pause only within over-exposed ad sets. Move the paused creative to a "rest pool" — they come back after 21 days dark.

4. Day 3-4: In each over-exposed ad set, activate 2-3 previously paused ads from earlier in May (ads that ran in W1 and were paused as W3 scaling happened). These have had rest time and will show lower initial frequency against the same audience.

5. Do not produce any new creative in Week 1. New creative production starts Week 2. Week 1 is exclusively about extending the life of what exists through rotation and rest.

Owner: Mo does the analysis on the ad-level export. Lauren executes the pauses and activations. Joint 30-minute session Wednesday afternoon.

Expected dollar impact: Rotation cannot recover fully fatigued creative, but it can slow the CPL decay rate. If rotation stabilizes CPL at $26-27 instead of continuing to climb toward $30+, the net impact over 15 remaining weekdays in June at 1,000 leads/day is approximately $3-5/lead improvement = $4,500-7,500 in net over the rest of June. This is a secondary benefit compared to the home reallocation and the weekend throttle — but it is zero-cost and takes 2-3 hours to execute.

Timing: Analysis Day 1-2. Execution Day 3.

Summary Table: Days 1-7 Actions

Part 3 — First-Week Dollar Impact Goal

Target

Week 1 net revenue goal: $65,000-75,000 (7-day total)

Compared to: - May exit pace (May 24-30): $3,394/day average × 7 days = $23,758 without intervention - May W1 pace (the high-water mark): $99,929/7 = $14,276/day

A $65-75K week implies an average of $9,300-10,700/day. That is below the W1 and W2 high-water marks — which is intentional. The spend ceiling, the weekend throttle, and the absence of new creative mean Mo cannot promise a return to $14-17K/day weekdays in Week 1. The path is:

• Weekday 1 (Tue June 2): ~$8,000 net (still recovering from Memorial Day hangover, ops day)
• Weekday 2 (Wed June 4): ~$9,000 net (first clean execution day with all rules applied)
• Weekday 3 (Thu June 5): ~$10,000 net (home reallocation begins)
• Weekday 4 (Fri June 6): ~$7,000 net (Friday throttle rule in effect)
• Weekend (Sat-Sun June 7-8 counts as end of Week 1 for reporting): ~$6,500 total
• Remaining weekday (Mon June 7): ~$11,000 net

The math: - 5 weekdays × $9,500 avg = $47,500 - 2 weekend days × $3,500 avg = $7,000 - Total 7-day target: ~$54,500 conservative / $65,000 optimistic

The honest range is $50,000-$70,000. The $65K target is achievable if: (a) the home reallocation is live by Thursday, (b) the spend ceiling prevents further CPL erosion, and (c) no account-level disruptions (policy review, billing hold, etc.).

What is not achievable in Week 1

• New creative impact: Zero. New concepts need production time (minimum 7-10 days from brief to live test). Week 1 performance is entirely a function of existing creative managed better.
• CAPI/Pixel rebuild impact: Negligible in Week 1. Even if CAPI is fixed Tuesday, Meta's algorithm needs 5-7 days minimum to re-learn on improved signal. The CAPI fix is a Week 2-3 payoff.
• RPL improvement: The blended RPL is set by QW accept rates, which are outside Mo's control in Week 1. The only lever is CPL reduction.

Reporting Cadence to Hassan

• Daily: 4-line email at 6:00 PM EST format: spend / net / ROAS / one sentence on what moved. Lauren or Mo sends this — establish the format Tuesday.
• Friday June 6: End-of-week summary email covering: net vs. $65K target, what was changed, what data shows, the Week 2 plan (home scale, creative rotation Phase 2).
• Monday June 9: First weekly review call (15 minutes). Share the scorecard and get Hassan's alignment on Week 2 budget changes.

Part 4 — Tuesday EOD Readout to Hassan

Subject: Military.com — Day 1 readout + first moves

Hassan,

Three things from today:

1. What I found. The May collapse had one root cause: the account scaled from ~$25K to ~$40K/day on the same 10 concepts between May 15-21 without new creative entering the rotation. CPL went from $19 to $32 in 18 days. The three "Save up to 60%" ads I flagged in my earlier note were also still live — I've asked Lauren to pause those today (compliance risk, not a performance question). The good news: home insurance is structurally outperforming auto right now (ROAS 1.40-1.89 in late May vs. auto at ~1.06-1.08), and it's currently only getting 8% of spend.

2. What I changed or committed to changing this week. Compliance ads paused (Day 1). Spend ceiling set at $33.5K/day until new creative is validated. Weekend throttle rule going live by Thursday — auto-reduce spend Fri-Sun unless ROAS clears 1.40 by 10AM. Home insurance budget moving from ~$2.3K/day to $6.7K/day starting Thursday. Lauren is aligned on all of this. Nothing was changed that touches live auto campaigns above their current structure — I'm adding rules, not blowing up what's working.

3. What's coming Friday. By Friday I'll have the full ad-set and ad-level performance breakdown from the May data analyzed, and I'll send you: (a) the creative rotation list — which concepts go to rest and which get reactivated, (b) the Week 2 home scale plan with a specific spend target, and (c) the baseline data request — I need the March and April performance files you mentioned to complete my pre-pilot analysis. The daily performance email starts tomorrow at 6PM EST. Talk Friday.

Mo

ASSUMPTIONS & OPEN QUESTIONS

Assumptions made in this document:

1. The compliance ad IDs flagged in prior GTW deliverables (02_compliance_one_pager.md and 02b_compliance_mini_binder.md) are still live as of June 1. Mo must verify this on Monday with Meta Ads Manager access before directing Lauren to pause — if already paused, skip.

2. The home ROAS figures above (1.40-1.89 in late May) are calculated from the product-level revenue and spend columns in the CSV. These may not perfectly match Meta's reported ROAS if attribution windows differ between product lines. Verify against Meta's ad-set-level home campaign ROAS on Monday.

3. The $33,500/day spend ceiling assumes current auto campaign structure is roughly 2:1 auto-to-home. If the actual split is different, the per-product caps need adjustment after Mo sees the account Tuesday.

4. "Approximately 240 ads" is an estimate from prior audit context. The actual active vs. paused count will be confirmed Monday with account access.

5. The weekly net targets above assume no account-level disruptions (billing issues, policy reviews, audience size restrictions). A single Meta policy flag on the insurance vertical during June would invalidate these projections.

6. The home insurance reallocation assumes there are at least 5 distinct home creative concepts in the account. If home creative inventory is thin (1-2 concepts), the $6,700/day home cap should be held at $4,000/day until new home creative can be produced.

Open questions that must be resolved by Wednesday June 4:

• What are the exact QW contract terms — payout per accepted lead, exclusivity clause, termination notice period, and whether ping-post (sending the same lead to a second buyer) is contractually allowed?
• What is the current QW accept rate? The CSV shows leads_sold as all zeros — this data is not flowing into the internal report. Is it available from QW directly, and can Lauren or dev pull a May accept-rate report from the QW portal?
• Is CAPI live, and if yes, what is the event match quality score? If below 6.0, a CAPI remediation brief needs to be issued Week 1 for Week 2 execution.
• What creative is actually live on home insurance? The CSV shows home revenue but Mo has no visibility into the creative or ad-set structure until Tuesday.
• What is the baseline Hassan will propose in the contract? Mo cannot accept a June baseline higher than $225K net given the May exit trajectory. The historical data pull (March + April) is the negotiating lever — do not concede on this before the data arrives.
• Is Rony Arzoumanian in the Montréal office on June 2? If yes, carve out 10 minutes with him.
• What is the current cost-per-click ($1.85 blended in May) trend at the ad-set level — is the CPC increase concentrated in specific ad sets or account-wide? This determines whether it is a creative fatigue problem (ad-set-specific) or an auction-level problem (account-wide), which changes the fix.

Military.com June 2026 — 30-Day Creative Engine Plan

Owner: Mo / Go To War Strategy Counterpart: Lauren (Valnet in-house buyer) Period: June 1–30, 2026 Status: Day 1 execution document — account access begins June 1

Situation Snapshot

May 2026 exited at ~$87K/month run rate against a $275K full-month result. The collapse was structural, not seasonal: CPL rose 30% (from ~$19 to ~$31 at the worst) while RPL fell 10% (from $34–36 to $25–27) — the classic squeeze of a fatigued creative pool scaled into the ground. Approximately 240 active ads riding ~10 distinct concepts means the account is running a rotation-by-exhaustion strategy without knowing it. Every dollar spent re-showing the same ad to the same person makes the next lead cheaper to get elsewhere and more expensive here.

Home insurance is the bright spot: it grew from under $1K/day on May 1–2 to $3–5K/day through mid-May, ending the month at $3–5K/day (May 28–30). Home ROAS (1.36) slightly exceeded auto ROAS (1.33) on the full month. Home was ~8% of total spend ($68,853 of $836,793) but produced a disproportionate share of late-month margin.

The single highest-leverage Day 1 action is shipping net-new creative. Everything else — pacing, audiences, form migration — is multiplied or neutralized by creative quality.

Part 1 — The Concept Matrix

Framework

4 audience segments × 3 formats × 3 hook categories = 36 base combinations

Audience segments: - A1 — Active Duty (currently serving, any branch) - A2 — Veterans (separated, honorably discharged) - A3 — Military Spouses (married to active or veteran) - A4 — Retirees + Guard/Reserve combined

Formats: - F1 — 9:16 vertical video (mobile-first, 15–30 sec) - F2 — 1:1 static image - F3 — 4:5 carousel (3–5 cards)

Hook categories: - H1 — Savings-led (financial outcome front) - H2 — Identity-led (life-stage recognition, no sensitive attribute call-out) - H3 — Interactive/calculator-led (self-qualification, curiosity gap)

Not all 36 combinations are created equal. The matrix below flags the 20 highest-priority cells with full briefs. Lower-priority combinations are noted as "Later — Week 3+" and receive shorter treatment.

Matrix: Full Concept Briefs

Compliance note on all identity hooks: No ad may use "Are you a veteran?", "Are you active duty?", or any direct special-attribute qualifier as the primary hook. Identity hooks work through life-stage recognition ("You moved 4 times in 6 years"), shared cultural reference ("Base housing doesn't count"), or aspiration framing — not demographic interrogation.

A1 (Active Duty) × F1 (9:16 Video) × H1 (Savings-led)

Codename: FAST MOVERS Hook (first 3 seconds): Text on black screen — "Most people overpay because they never switched. Here's what happened when this soldier did." Cut to talking-head footage. One-line message: Switching auto insurance takes 4 minutes — and military members find rates other people can't access. Visual direction: Real person, civilian clothes, kitchen or living room. No uniforms, no flags, no base gates. The cue that they're military is contextual: a challenge coin on the counter, a unit hoodie visible in the background. Authentic, not costumed. Why this works: Active duty is highly mobile (PCS cycles), meaning their auto situation changes constantly — but they rarely re-shop between moves. The "you've been overpaying" frame creates urgency without requiring the viewer to self-identify as military. Meta's lookalike off the existing buyer file will handle targeting; the creative doesn't need to do the demo filtering. Target product: Auto

A1 (Active Duty) × F2 (1:1 Static) × H2 (Identity-led)

Codename: PCS MATH Hook (headline): "You moved. Your insurance rate didn't." One-line message: Every PCS is a reset opportunity — compare rates in the new state before your old rate follows you. Visual direction: Split-panel. Left: a cardboard box with "HOUSEHOLD GOODS" stencil. Right: a phone screen showing a quote comparison with a green "lower rate" indicator. No people, no faces — keeps it broadly applicable and avoids any casting that could feel exclusionary. Why this works: PCS moves are a universal active-duty pain point with no civilian equivalent. The headline lands without any demographic qualifier because only someone who has PCS'd will feel the gut-punch recognition. Static is the right format for this hook because the information density (two panels, a number, a CTA) doesn't need motion. Target product: Auto + Home (rotate to home variant: "You moved. Your home rate didn't.")

A1 (Active Duty) × F3 (4:5 Carousel) × H3 (Interactive/Calculator-led)

Codename: DEPLOYMENT COST AUDIT Hook (card 1): "While you were deployed, your insurance company kept billing you. Did they bill you right?" Card 2: "4 states have deployment discounts — most people never claim them." Card 3: "It takes 90 seconds to find out if you're owed money." Card 4: CTA — "See your rate." One-line message: Carousel functions as a mini-education sequence — each swipe earns a micro-commitment before the CTA. Visual direction: Clean dark-blue cards, sans-serif white type, minimal iconography (map pin, clock, dollar sign). No stock photos of soldiers. Brand consistency with Military.com's editorial feel. Why this works: The carousel format self-selects for high-intent users — people who swipe through 4 cards are actively considering the topic. The "deployment discount" angle is a genuine curiosity gap: most active duty members don't know whether their insurer applies it. Interactive hooks outperform passive savings claims in financial verticals when CPM is high (which it is, given May's data). Target product: Auto

A2 (Veterans) × F1 (9:16 Video) × H1 (Savings-led)

Codename: THE SWITCH (VETERAN) Hook (first 3 seconds): UGC-style selfie video. Person looks at camera: "I switched my car insurance three months ago. I genuinely didn't expect this." [Pause.] "Here's the number." One-line message: Real veterans showing real outcomes — no testimonial script, just the result. Visual direction: Real veteran creator, current civilian context (car interior, home driveway, garage). One subtle visual signal of service is acceptable if organic — a bumper sticker, a gym shirt — but not the hook. The hook is financial curiosity. Why this works: Veterans are the largest segment by reach in this account's Meta audiences. The "I didn't expect this" structure creates a curiosity gap before the savings reveal. UGC format (raw selfie video, no graphic overlay) will feel native to the feed and will differ visually from every polished creative currently running. Target product: Auto

A2 (Veterans) × F2 (1:1 Static) × H2 (Identity-led)

Codename: POST-SERVICE RATE Hook (headline): "You left the military. Your old rate stayed." One-line message: Separation is a qualifying life event for better insurance rates — most veterans don't know to re-shop. Visual direction: Single person, 30s–40s, business-casual, clearly not in uniform. Suburban or light urban background. Confident posture. Subtext headline: "See your post-service rate in 60 seconds." CTA button: "Compare Free." Why this works: Separation triggers eligibility for different rate structures at many carriers. The phrase "post-service rate" is aspirational and novel — it implies there's something specific to find, without claiming a specific percentage. This differentiates from the generic "save on insurance" creative the account is almost certainly running. Target product: Auto

A2 (Veterans) × F3 (4:5 Carousel) × H3 (Interactive/Calculator-led)

Codename: ELIGIBILITY CHECK Hook (card 1): "Not everyone qualifies for the same rates. Here's the checklist." Card 2: "Honorable discharge — check." Card 3: "Homeowner or renter?" Card 4: "Vehicle age and state — check." Card 5: CTA — "Run your full comparison." One-line message: Turn the qualification process into the ad — each card is a micro-step in the funnel. Visual direction: Clean checklist UI aesthetic. Green checkmarks on white/cream cards. Minimal copy per card. Final card has product image (phone with quote screen) + CTA. Why this works: The "checklist" format implies exclusivity and self-selection without explicit demographic targeting. Veterans who read "honorable discharge — check" will mentally check that box themselves. The carousel pre-qualifies intent better than a single static ad and tends to drive lower CPL at higher conversion rates in financial lead-gen contexts. Target product: Either (A/B test auto vs home final card)

A3 (Military Spouses) × F1 (9:16 Video) × H2 (Identity-led)

Codename: THE MANAGER Hook (first 3 seconds): Person to camera: "My husband's deployed. I handle everything — including insurance. Here's the one thing I changed that actually mattered." One-line message: Military spouses are the household financial decision-makers when the service member is away — speak directly to that role. Visual direction: Spouse, 25–45, in a home setting (kitchen, home office, living room). Natural lighting. Baby or child visible in background is fine and authentic. Tone is competent and calm, not stressed or overwhelmed. The framing is capability, not struggle. Why this works: Military spouses are systematically underserved in financial product advertising that skews toward the service member. They are highly active on Meta, highly influential in household financial decisions, and respond strongly to "you're the one who figured this out" framing. This segment is also less likely to see creative fatigue from existing auto ads that are probably member-coded. Target product: Auto + Home (spouse as household decision-maker applies to both)

A3 (Military Spouses) × F2 (1:1 Static) × H1 (Savings-led)

Codename: DUAL HOUSEHOLD Hook (headline): "Two cars. One base sticker. One good rate." One-line message: Households with multiple vehicles and a military member on the policy often qualify for multi-vehicle discounts that are not automatically applied. Visual direction: Two vehicles in a driveway, one with a base sticker visible (small, not emphasized). Clean suburban setting. Subheadline: "See if you're leaving money on the table." CTA: "Compare Free." Why this works: Multi-vehicle households are a natural upsell from single-vehicle leads, and spouses are the most likely profile to be managing the household policy for two cars. The base sticker is a coded cultural signal that reads to the right audience without requiring any stated demographic qualifier. Target product: Auto

A3 (Military Spouses) × F3 (4:5 Carousel) × H3 (Interactive/Calculator-led)

Codename: ANNUAL REVIEW Hook (card 1): "Do you do an annual insurance review? You should. Here's why." Card 2: "Average military household hasn't compared rates in 3+ years." Card 3: "Home + auto bundle could change your total." Card 4: "Takes 4 minutes." Card 5: CTA — "Start your comparison." One-line message: Frame the comparison as responsible household management — normalizing re-shopping as a smart habit, not a complaint. Visual direction: Lifestyle + data hybrid. Cards 1–2 are lifestyle (kitchen table with laptop, coffee, notebook). Cards 3–5 are clean data/product UI. Warm tones, not clinical. Why this works: Spouses respond to "responsible household manager" framing over "you're overpaying" framing. The carousel educates before asking for action. The home + auto bundle mention primes for a cross-sell that improves lead value. Target product: Either (auto + home cross-sell angle)

A4 (Retirees + Guard/Reserve) × F1 (9:16 Video) × H1 (Savings-led)

Codename: AFTER 20 Hook (first 3 seconds): Talking head, 50s, casual outdoor setting: "After 20 years, I thought I'd figured out every benefit. Then I re-shopped my insurance." One-line message: Retirement is the most underutilized re-shopping trigger in the military community — the rate environment has changed; the policy hasn't. Visual direction: Retiree in civilian context — garage workshop, backyard, casual outdoor. No uniform. Props that signal a life built after service (pickup truck, workshop tools) without being staged. Relaxed energy, not urgency. Why this works: Retirees have more financial stability and are typically higher-value auto insurance leads (better credit, more assets, often multiple vehicles). The "after 20 years" hook creates an emotional anchor — recognition of a life chapter — that softens the financial pitch. Guard/Reserve members face similar life-stage triggers around activation cycles and civilian employment changes. Target product: Auto + Home (retirees often own their home)

A4 (Retirees + Guard/Reserve) × F2 (1:1 Static) × H2 (Identity-led)

Codename: EARNED RATE Hook (headline): "Years of service. Earned a better rate." One-line message: Long-term financial stability and a clean driving record — common in retirees — should translate to lower insurance costs. Help them find out. Visual direction: Single image. Person 50s–60s, outdoor natural light. Clean, professional framing. Subheadline: "Compare rates in 60 seconds." No stock art, no flags, no military iconography. The "years of service" line does the work without a visual uniform cue. Why this works: Retirees are a high-LTV segment that tends to have longer policy tenures, meaning they've often been with the same insurer for 10+ years without comparing. The "earned rate" framing implies they deserve something specific — not that they're overpaying through negligence, but that they've earned the right to a better number. This is aspirational, not accusatory. Target product: Auto

A4 (Retirees + Guard/Reserve) × F3 (4:5 Carousel) × H3 (Interactive/Calculator-led)

Codename: RATE TIMELINE Hook (card 1): "Your rate in 2020. Your rate now. What changed?" Card 2: "Insurance rates have moved significantly — but your policy updates didn't." Card 3: "Guard activations, address changes, vehicle age all affect your number." Card 4: "Run a 60-second comparison." Card 5: CTA. One-line message: The carousel sequences a narrative — past vs. present — that makes re-shopping feel logical and overdue. Visual direction: Timeline aesthetic. Cards use a simple before/after visual language. Clean, minimal, data-confident. Subtext: the insurer changed the math; you haven't checked. Why this works: Guard/Reserve members have irregular service cycles that create genuine rate-change triggers most won't think to act on. Retirees have high household asset levels. The timeline format makes inaction feel like the risky choice — a proven structure in comparison shopping categories. Target product: Either

A1 (Active Duty) × F1 (9:16 Video) × H2 (Identity-led) — Secondary priority

Codename: FOUR YEARS, FOUR STATES Hook: Person in car: "I've lived in 4 states in 4 years. Here's the only financial habit that kept up." One-line message: Constant relocation = constant rate-change opportunities — most active duty members never act on them. Visual direction: Talking head in car interior, sunglasses, relaxed. Driving implied. No uniform. Target product: Auto

A2 (Veterans) × F1 (9:16 Video) × H2 (Identity-led) — Secondary priority

Codename: CIVILIAN SIDE Hook: Person: "Nobody told me this when I got out." [Beat.] "My car insurance rate could have changed the day I separated." One-line message: Transition from service is a financial rate-change trigger most veterans miss. Visual direction: Person in civilian work environment or driving. Clean, confident, not struggling. Transition is a success story, not a hardship narrative. Target product: Auto

A3 (Military Spouses) × F1 (9:16 Video) × H1 (Savings-led) — Secondary priority

Codename: FAMILY BUDGET WIN Hook: Spouse, kitchen setting: "I found an extra $180/month in our budget last year. It took me 6 minutes." One-line message: Insurance re-shopping is the highest-ROI 6-minute task in household financial management. Visual direction: Real home environment. Warm, non-staged. Person is competent and calm. The $180 figure is directional — not a specific savings claim; final creative must use "up to X% or more" compliant language (see Part 6). Target product: Auto + Home

A4 (Retirees + Guard/Reserve) × F1 (9:16 Video) × H3 (Interactive/Calculator-led) — Secondary priority

Codename: TWO-MINUTE AUDIT Hook: Person, 50s: "I thought I was getting a good rate. So I spent 2 minutes finding out for sure." One-line message: Confidence testing — the "nothing to lose" frame for re-shopping. Visual direction: Home exterior or vehicle in driveway. Mature, comfortable lifestyle. Not financially anxious. Target product: Either

Lower-priority matrix cells (Week 3+ testing, brief notes only)

• A1 × F2 × H3 — "What's your rate score?" static with quiz-style CTA. Auto.
• A1 × F3 × H2 — PCS prep checklist carousel. Auto + Home.
• A2 × F2 × H3 — "30-second rate check" static. Auto.
• A2 × F3 × H2 — Transition timeline carousel (service end → first civilian insurance). Auto.
• A3 × F2 × H2 — "You handle the house" static. Home.
• A3 × F3 × H1 — Bundle savings carousel. Auto + Home.
• A4 × F2 × H3 — "What's changed since you retired?" static. Auto + Home.
• A4 × F3 × H1 — Savings math carousel (20-year tenure vs. re-shop). Auto.

Part 2 — Home Insurance Push

Why Home Now

Home insurance went from $1,052/day (May 1) to $5,019/day (May 28) — a 377% revenue increase in 28 days on only 8% of total spend. The auto funnel's deterioration actually makes home's outperformance more pronounced: while auto ROAS fell from 1.56 to below 1.0 by late May, home held positive margin throughout. Home is the account's only growing channel right now.

Competitors (EverQuote, Zebra, Insurify, SmartFinancial) are overwhelmingly auto-first in their Meta creative. Home is undercontested in the military-adjacent Meta environment. This is a window.

Home-Only Concept Briefs (5–7)

H-1 — PCS HOMEBUYER

Codename: PCS HOMEBUYER Segment: Active Duty, Military Spouses Format: 9:16 video Hook (first 3 seconds): Spouse in a moving truck or empty living room: "We bought a house at our last duty station. Here's the one thing I wish I'd done before the movers came." One-line message: Every PCS-linked home purchase is a moment to lock in home insurance before moving costs hit. Most families shop last-minute and take the lender's default option. Visual direction: Realistic moving scene — boxes, bare walls, kids underfoot. No staging, no stock. Warm but slightly chaotic energy that military families will recognize immediately. Angle competitors aren't running: The PCS purchase trigger is a purely military-audience hook. No civilian comparison shopping platform has creative built around "you're buying a house because the military told you to move." This is uncontested territory. Budget implication: Target $2K/day test budget Week 1, scale if ROAS > 1.25.

H-2 — RATE SHOCK RELIEF

Codename: RATE SHOCK RELIEF Segment: Veterans, Retirees Format: 1:1 static Hook (headline): "Your home insurance went up again. Here's what to do about it in the next 5 minutes." One-line message: Home insurance rate shock is a universal 2025–2026 consumer moment — veterans and retirees with owned properties are especially affected. Visual direction: Dual panel: left is an insurance renewal letter with a circled dollar amount (stylized, no real carrier logo). Right is a phone screen with "your new quote" comparison UI. Clean, direct. Angle competitors aren't running: Most home insurance creative is aspirational (nice houses, happy families). This ad names the pain directly — renewal rate shock — which is the actual moment of intent. It runs best in mid-month when renewal letters typically arrive.

H-3 — HOMEOWNER BY 30

Codename: HOMEOWNER BY 30 Segment: Active Duty (younger), Veterans (recently separated) Format: 9:16 video Hook (first 3 seconds): Person, late 20s: "I bought my first house at 27. The VA loan covered the down payment. The insurance part? I figured that out too." One-line message: VA loan homeownership is common in the military community — but most first-time homeowners take whatever insurance the lender recommends without comparing. Visual direction: Real home, real person, first-time homeowner energy. Pride of ownership, not luxury. Suburban or light rural. Natural light. Angle competitors aren't running: VA loan homebuyers are a defined subset with known demographics, higher homeownership rates than the civilian population their age, and a clear product trigger. Nobody is running "you used a VA loan, here's what to do about your insurance" creative.

H-4 — BUNDLE THE SAVINGS

Codename: BUNDLE THE SAVINGS Segment: Military Spouses, Retirees Format: 4:5 carousel Hook (card 1): "You're insuring your home and your car separately. Here's what that's costing you." Card 2: "Home + auto bundle discounts average 10–15% on the combined premium." Card 3: "Military households often qualify for additional multi-policy rates." Card 4: CTA — "See your bundle rate." One-line message: Bundle positioning upsells an auto lead to home or vice versa — cross-sell in the creative, not just the post-conversion flow. Visual direction: Clean product UI cards. Home exterior + car in driveway on card 1. Data/savings visual on card 2–3. Phone screen CTA on card 4. Angle competitors aren't running: Most Meta insurance creative is single-product. Bundle creative drives higher average lead value (both a home and an auto lead from one click through) and is underused in the military segment. Target product: Home + Auto (cross-sell)

H-5 — BASE ADJACENT

Codename: BASE ADJACENT Segment: Active Duty (off-base housing), Military Spouses Format: 1:1 static Hook (headline): "Off base. On the hook for homeowner's insurance." One-line message: Many active duty families living off-base for the first time don't realize BAH doesn't cover the insurance gap — framing this as a practical consideration, not a pitch. Visual direction: Exterior of a modest off-base home, clean neighborhood. Practical, not aspirational. This is about getting something done, not lifestyle aspiration. Angle competitors aren't running: "Off-base homeowner" is a transitional life state that no civilian insurance comparison platform would think to target. The creative is invisible to anyone who isn't in that situation.

H-6 — DISASTER SEASON CHECK

Codename: DISASTER SEASON CHECK Segment: Retirees, Veterans (South/Southeast homeowners) Format: 9:16 video Hook (first 3 seconds): Text on screen: "Hurricane season is June 1. When did you last check your coverage limits?" One-line message: Seasonal urgency (hurricane/wildfire season) creates a genuine review trigger that is independent of price — it's about being properly covered. Visual direction: Aerial shot of a coastal suburb or text-only dark-card treatment. No disaster imagery. The urgency is informational, not fear-based. Angle competitors aren't running: Time-triggered creative (hurricane season begins June 1 — same week this plan launches) is a narrow window competitors aren't set up to deploy quickly. The War Room AI production pipeline can have this in market Day 1.

H-7 — REFINANCE WINDOW

Codename: REFINANCE WINDOW Segment: Retirees, Veterans (purchased homes 2019–2022) Format: 1:1 static Hook (headline): "Refinancing? Don't forget to re-shop your homeowner's rate at the same time." One-line message: Refinancing triggers a lender insurance review — it's also the best time to compare and switch carriers, which most people skip. Visual direction: Clean financial aesthetic. Split visual: left side mortgage paperwork icon, right side house + shield icon. Subheadline: "Take 5 minutes while you're in the process." Angle competitors aren't running: Refinance co-trigger is a moment that comparison platforms completely ignore in their Meta creative. They target homeowners generically; this targets homeowners at the specific moment they're already making a financial decision.

Home Budget Reallocation Target

Current home % of spend: 8% ($68,853 / $836,793) Recommended target by end of June: 22–25% of total spend on home

Rationale: - Home ROAS held at 1.36 vs. auto collapsing to sub-1.0 in late May - Home was growing in absolute revenue ($1K/day → $5K/day) while auto was shrinking - Home creative library is underdeveloped — new concepts have no fatigue risk - Competitors are not meaningfully contesting military-adjacent home insurance on Meta

Execution path: Shift home spend from 8% to 15% in Week 1 (as new home creative ships), to 20% by Week 2, to 22–25% by Week 3 — contingent on ROAS holding above 1.25. Do not reallocate aggressively before new home creative is in-flight; current home creative may also be approaching fatigue.

Dollar impact if home reaches 25% of spend at June target spend level ($25K/day): ~$6,250/day on home at 1.30+ ROAS = meaningful margin recovery relative to continuing to push fatigued auto spend.

Part 3 — Production Cadence + War Room AI Workflow

Guiding Principles

• Mo + Lauren co-sign a weekly batch, not individual ads. One approval session per ship day; no per-ad bottleneck.
• Ship days: Mondays (primary) and Thursdays (secondary). Monday ships give 3–4 days of data before the next ship decision. Thursday ships allow course-correction mid-week if Monday underperforms.
• Every new concept is tagged with its codename at upload — enables clean performance attribution without waiting for ad naming conventions to be standardized.
• Kill threshold: Any ad with CPL > $35 at 500+ impressions gets flagged. Any ad at 1,000+ impressions with ROAS < 1.10 gets paused. Decisions are automated where possible, reviewed by Lauren.

Week 1 (June 1–7): Foundation — 8–10 Net New Ads

Goal: Replace the 5 fatigued longest-running auto ads. Prove the creative refresh can move CPL within 7 days.

Priority concepts for Week 1 ship (Monday June 2 + Thursday June 5):

Concept generation (War Room AI workflow): - Brief input: codename + hook + visual direction + target product + compliance guardrails - Output per brief: 3 headline variants, 3 body copy variants, 1 primary visual direction brief - Mo reviews and selects the top 2 variants per concept before briefing to production - All AI-generated copy is compliance-checked before exit: no specific savings percentages, "up to X% or more" language, no special-attribute triggers

Asset production breakdown: - FAST MOVERS, THE SWITCH, THE MANAGER, PCS HOMEBUYER, DISASTER SEASON CHECK: require real UGC or creator footage — source from the Week 1 UGC outreach (Part 4). If footage isn't available Week 1, run text-on-video or motion-graphic versions as placeholders. - PCS MATH, POST-SERVICE RATE, RATE SHOCK RELIEF, EARNED RATE: AI-generated static composites. No human footage required. Lauren can QA and upload directly. - BUNDLE THE SAVINGS: Designed carousel — Lauren handles Meta upload; card design via War Room AI templates.

Approval/QA gate: - Mo produces batch brief deck by Friday May 31 (today) - Lauren reviews for platform mechanics and account fit by end of day Monday June 1 - Final co-sign batch call, 30 minutes, before first Monday ship - No individual ad-by-ad approval after initial co-sign on the batch

Ship Day 1 target: Monday June 2 (6 ads) Ship Day 2 target: Thursday June 5 (4 ads)

Week 2 (June 8–14): Scale Winners + New Tests — 10–12 Net New Ads

Goal: Double down on the 2–3 Week 1 ads with CPL < $25 and ROAS > 1.30. Ship new test concepts for segments not covered in Week 1. Begin home push escalation.

Production plan: - 3–4 winner variants: take the top Week 1 performer, generate 3 variants (different hook line, same visual direction; different visual, same hook; format cross-pollination — if the video works, make the static) - 4–5 new concepts from the matrix: prioritize A3 carousel (ANNUAL REVIEW), A4 video (AFTER 20), HOMEOWNER BY 30, BASE ADJACENT - 2–3 new home ads: REFINANCE WINDOW, additional PCS HOMEBUYER variant

War Room AI workflow: - Week 1 performance data feeds the variant brief: "the hook that performed was [X]; generate 5 headline variants that use the same emotional anchor with different specific triggers" - Variant generation takes 20 minutes per winning concept; production of static variants is same-day

Asset production: - Winner variants of video concepts: use same footage with new text overlay/hook card if UGC footage is delayed. Do not reshoot Week 2. - New static concepts: AI-generated - AFTER 20: requires UGC creator footage — use placeholder text-on-video if creator footage not yet available

Approval gate: Same Monday/Thursday ship rhythm. Single 30-min co-sign call per week.

Ship Day 3: Monday June 8 (6 ads) Ship Day 4: Thursday June 11 (5–6 ads)

Week 3 (June 15–21): Depth on Winners, Kill Losers — 12–15 Net New Ads

Goal: Aggressive scaling on the 4–5 proven concepts. Ship into under-covered matrix cells (A3 full coverage, A4 carousel). Begin UGC pipeline delivery.

Production plan: - 5–6 winner variants (now with real performance data, variant creation is much more directed) - 4–5 new matrix cells from the lower-priority list (A1 × H3, A2 × H2 carousel, A3 static) - 3–4 first UGC ads (if veteran creator footage is in — see Part 4)

War Room AI workflow: - By Week 3, the AI variant pipeline has 2 weeks of performance signal. Input: "winning concepts, losing concepts, pattern hypothesis." Output: concept briefs that extrapolate from winners and avoid the patterns of losers. - Creative fatigue monitoring: any ad showing CTR declining > 15% week-over-week gets flagged for replacement

Ship Day 5: Monday June 15 (7–8 ads) Ship Day 6: Thursday June 18 (5–7 ads)

Week 4 (June 22–28): Concentration — 10–12 Net New Ads

Goal: Concentrate budget on the top 6–8 proven concepts. New ads are refinements and coverage fills, not exploratory tests. Position for July scale.

Production plan: - 5–6 top-of-funnel volume variants of the 2–3 best-performing concepts (max reach) - 3–4 coverage fills (any segment × format × hook combination with zero performance data) - 2–3 UGC ads (second wave of veteran creator content)

Note: By Week 4, the account should have 40–50 live ads with actual performance data. The goal is to run the best 15–20 actively and rotate in fresh variants every Thursday.

Ship Day 7: Monday June 22 (6–7 ads) Ship Day 8: Thursday June 25 (4–5 ads)

June Totals Target

Part 4 — Veteran UGC Track

Why UGC Is the Defensible Moat

Polished creative is copyable in days. Real veteran creators shooting authentic content in their homes, trucks, and driveways cannot be replicated by EverQuote, Zebra, or Insurify. They are civilian companies. They cannot brief a veteran creator to say something genuine because there's nothing genuine for them to say from lived experience. Military.com has 25 years of brand equity in this community. UGC bridges that brand to the feed.

Outreach Plan

Platform priority: 1. Instagram/TikTok — search "veteran finance," "military finance," "military spouse budget" — these micro-creators have 5K–50K engaged military-community followers and are not yet saturated with brand deals 2. Facebook groups — Veterans in Finance, Veteran Entrepreneurs, Military Spouse Network. Authentic community sourcing, not talent agency. 3. Cameo for Vets / Vetinfluence directory — for faster sourcing if organic outreach is too slow for the June timeline

Creator profile (casting brief): - Veteran or military spouse, currently in civilian life (not active duty — don't create policy complications) - Comfortable on camera, natural delivery — NOT polished. The whole point is authentic. - Does not need a large following. 2,000–10,000 followers with real engagement > 500,000 followers with 0.1% engagement. - No current brand exclusivity conflicts with insurance competitors - Located anywhere in the US (all remote, self-shot)

Brief to creator: - Shoot vertically (9:16) in a natural civilian setting (home, car, garage) - No scripted lines — provide 3 talking points, creator says them in their own words - 60–90 seconds raw footage; we edit to 15–30 sec - Brand: Military.com (established platform they may already know) - Topic: their experience re-shopping auto or home insurance; what they found out

Rate range: $300–$600 per delivered piece (raw footage, usage rights granted). Not per post — we own the usage rights for Meta ads, no posting required on their channel. This is well below what civilian lifestyle creators charge for branded content in the insurance space ($1,500–$5,000 per post), and is appropriate for micro-creator compensation.

Volume needed for June: 5–8 creator outreach contacts by June 2; target 3–5 usable pieces by June 20.

Timeline: - June 2–5: Contact 8–10 creators across platforms. Brief: 200 words max, subject line "Military.com — veteran creator brief, 1-day shoot, $400" - June 6–12: Agreements, brief confirmations, payment setup - June 13–17: Creators submit raw footage - June 18–21: Edit, compliance review, Meta upload preparation - June 22–25 (target): First UGC ads live in-market

Backup plan: If UGC pipeline is delayed past June 20, Week 3–4 ships use text-on-video and motion-graphic substitutes. UGC becomes early July's differentiator rather than late June's.

Why competitors can't replicate this: - The content is authentic by definition — it requires a real veteran to have real opinions about insurance products marketed to their community - The Military.com brand grants credibility for this pitch that no aggregator platform can match - The creator relationship is direct; it doesn't run through a talent agency that would sell access to EverQuote the next day

Part 5 — Managing the Existing 240 Ads in Week 1

The Problem

240 active ads on 10 concepts means Meta is allocating budget across 24 near-identical ad variants per concept. The algorithm cannot distinguish signal from noise, so it spreads budget thinly, learns slowly, and over-exposes the top performers until frequency kills them. This is exactly what happened in May Week 3–4.

Immediate Pause/Sunset List (Week 1 Action)

These categories of ads get paused Monday June 1 — before any new creative ships:

Category 1 — The 5 longest-running auto ads Pull the 5 ads with the oldest creation date from the account on Monday. These are near-certain to be: - The core auto savings concepts that drove the May Week 1 performance - Now responsible for the CPL inflation and frequency-driven cost increases - Pausing them immediately concentrates remaining spend on less-fatigued creative while new ads spin up - Tag them "PAUSED-FATIGUE-060126" — do not delete. Reactivation is possible in 4–6 weeks with fresh audiences.

Category 2 — Any ad using "60%" savings language Per the compliance research on file (02_compliance_one_pager.md): the verified real-ad finding is that 60% claims appear in the existing library. These are a Meta policy violation risk and must be paused immediately. Tag: "PAUSED-COMPLIANCE-060126."

Category 3 — Bottom-decile performers (Week 1 identification) Cannot fully identify without ad-level access (which starts June 1). Within 48 hours of account access, Lauren pulls the bottom 10% of ads by ROAS on the last 14 days and flags for Mo review. Anything with ROAS < 1.05 on $500+ spend in the last 14 days is paused.

Expected result of pause action: Reduction from 240 active ads to approximately 150–180. Remaining spend concentrates, each remaining ad gets more impression budget and faster learning.

Rotation Rules for What Stays Live

Rule 1 — Frequency cap at the ad set level: No individual ad should exceed 3.0 frequency in a 7-day window against any single audience segment. If frequency is approaching this, either the ad set is too small, the budget is too high, or the creative needs rotation. Lauren sets this as an alert, not a hard Meta cap (Meta's built-in frequency controls are less granular).

Rule 2 — 14-day rolling CPL review: Every Monday, Lauren pulls CPL for each active ad over the prior 14 days. Any ad with CPL > $32 (flagged threshold — 30% above the $25 May average) and no improvement trend gets queued for replacement by the next ship day.

Rule 3 — No single concept > 25% of total impression volume: Prevents the account from accidentally rebuilding the 10-concept fatigue trap with a new set of 10 concepts. If any single concept codename is accumulating > 25% of weekly impressions, redistribute spend to the next-best performers.

Rule 4 — Reserve 20% of weekly spend for new creative tests: This is a hard budget rule, not a best-effort guideline. If the account runs $25K/day, $5K/day is allocated to ads with fewer than 7 days of live data. This maintains the learning signal.

Frequency Caps Summary

Part 6 — Compliance Gate on Every New Ad

All new creative must clear these checks before Lauren uploads to Meta. Mo reviews and signs off on compliance at the batch level; individual ad compliance is Lauren's QA gate.

1. Savings Claims Language

Required standard: "Up to X% or more" only. No specific savings claim above approximately 15% may be used without documented carrier substantiation.

• Compliant examples: "Save up to 15% or more," "see how much you could save," "find a lower rate"
• Non-compliant examples: "Save 60%," "save 30% guaranteed," specific dollar amounts presented as typical
• The "up to X% or more" construction is the industry-verified safe harbor — it is simultaneously a floor and an open ceiling, which is why it passes FTC and Meta review

Flag: Any AI-generated copy that includes a specific percentage above 15% without a citation goes back to War Room for revision before batch approval.

2. Meta Financial Products & Services — Special Ad Category

Military.com's insurance comparison ads operate under Meta's Special Ad Categories (Financial Products and Services). This means:

• No Lookalike Audiences based on sensitive financial signals — use Advantage+ or broad targeting with interest/behavior overlays, not LAL off converted leads
• No detailed demographic targeting that could constitute discriminatory ad delivery (no age ranges, no zip code targeting, no income targeting)
• Special Ad Category must be selected at campaign creation — Lauren verifies this is set on all new campaigns before spend begins
• Non-compliance here is an account suspension risk, not just a policy warning

3. TCPA and Sensitive Attribute Traps

Do not use these hooks or framings: - "Are you a veteran?" — direct sensitive attribute identifier, Meta policy violation risk - "As a [service branch] member..." — same issue - "Attention: military families" — soft violation; borderline - Any framing that implies the ad was targeted based on military status

Safe framings (use these instead): - Life-stage hooks: "If you've moved for work in the last 5 years..." (catches military without naming them) - Cultural reference hooks: PCS, base sticker, BAH, VA loan — the in-community vocabulary does the targeting implicitly - Universal financial hooks ("overpaying for insurance") with military-contextual visuals

TCPA: The landing page and lead form (currently QuoteWizard-hosted) must have TCPA-compliant consent language. Mo should verify with Lauren and the dev team by June 2 that the current form has: clear disclosure of consent to be contacted, specific mention of text/SMS/phone contact, and the TCPA disclosure above the form submit button. This is a Day 1 audit item, not a June 30 item.

4. Co-Brand Approvals

Thread C (recruitment partner creative — Anduril, GE Vernova, Helmets-to-Hardhats) is a separate pipeline and is not included in this June creative plan. Any ad that features a recruitment partner brand, logo, or co-branded message requires written approval from that partner before shipping. Do not allow recruitment partner creative to flow through this pipeline.

Military.com brand: All creative must be reviewed for alignment with Military.com editorial standards before ship. Lauren owns this check.

Production Summary — June 2026

Dollar Impact Model

The delta between "no intervention" and "full execution" is ~$150–200K net in June alone — and the multiple on that is larger in July/August when the measurement window opens.

ASSUMPTIONS & OPEN QUESTIONS

Assumptions made in this plan:

1. Account access is confirmed June 1 and Lauren has immediate upload capability. If access is delayed, Week 1 ship slides to Thursday June 5 as the earliest.

2. The 5 longest-running auto ads are identifiable by creation date in the ad manager. If the account uses external tools or naming conventions that obscure creation date, Lauren will need to surface this manually.

3. Home insurance leads are being monetized through the same QuoteWizard integration as auto. If home leads go through a different network or form flow, the budget reallocation math may need adjustment.

4. The current QuoteWizard form has TCPA-compliant language. This has not been verified — it must be confirmed June 2 with the dev team.

5. No co-brand or recruitment partner creative is included in this June pipeline. Thread C remains a separate engagement.

6. The War Room AI variant pipeline can turn around compliant ad copy in 24–48 hours for each brief. If production timeline extends, some Week 2–3 ship dates will compress.

7. UGC creator outreach assumes creators can shoot and deliver footage within 10–14 days of brief. Holiday schedules or slow response rates could push first UGC ads to early July.

Open questions requiring answers by June 2:

• What is the exact CPL and ROAS for each of the 10 existing concepts at the ad-set level? (Needed to rank the pause/keep decisions precisely.)
• Are any of the existing 240 ads already in the Meta Special Ad Category compliance framework, or is this a gap that needs to be fixed across the board?
• Does the QuoteWizard form pass TCPA review? Who owns the form — Valnet dev or QuoteWizard?
• What is the current home insurance lead payout rate from QuoteWizard vs. auto? (The RPL difference will affect the budget reallocation math.)
• Is Lauren managing the account alone or does she have a creative resource? This affects which Week 1 assets require outside production support.
• What is Hassan's short-term floor on spend? (Reducing from $36K/day peak to $20K/day while new creative loads may show a revenue dip before the recovery. Need to manage this expectation Day 1.)
• Do any of the existing ad creatives have carrier co-branding or carrier-specific claims that would require removal before this compliance gate is active?
• Is there a naming convention currently in use for campaigns and ads? If not, establish the codename-based naming system at account access, before Week 1 ships.

Tracking + Meta CAPI Rebuild — Technical Scope

Iron Corp / Military.com | Go To War Strategy | June 2, 2026

Context: Why This Document Exists

The May 2026 daily report has leads_sold, click_lead, click_lead_revenue, and lead_revenue all at zero for every single day of the month. This is not a reporting cosmetic — it means QuoteWizard's accept-rate, sold-lead count, and per-lead payout data are not flowing anywhere: not into Iron Corp's internal reporting, not into the CRM, and not into Meta. Meta's algorithm is optimizing on raw lead volume at a $21–28 CPL with zero visibility into which of those leads became revenue. The result is what the GTW audit called "value-blind CAPI" — Meta is flying blind, buying the cheapest leads rather than the most valuable ones, and the performance collapse from Week 1 to Week 4 of May (net-per-lead down 88%, ROAS 1.55 → 1.07) is the measurable cost of that blindness.

The CAPI rebuild is the single highest-leverage technical action available before the July-August measurement window opens. This document is Mo's working brief for the Tuesday June 2 office visit with the dev team. It is not a finished spec — it is the diagnostic and design framework that becomes a finished spec after Tuesday's answers are in.

Part 1 — Tuesday Diagnostic Checklist

Run through this with the dev lead in sequence. Do not skip to solutions. Every architectural decision in Parts 2 and 3 depends on answers here.

A. Current Pixel Implementation

1. What is the active Meta Pixel ID? Is it the same Pixel ID across all surfaces — military.com root, auto.military.com, home.military.com, and whichever domain the form resolves on?
2. Which standard events are currently firing from the Pixel, and on which pages? Specifically: does a Lead event fire on form submit? Does PageView fire on the confirmation/thank-you page? Is there a ViewContent or InitiateCheckout analog anywhere in the funnel?
3. Is the Pixel firing from a GTM container or hardcoded in the page source? If GTM, is it web container only or is there a server-side GTM container already stood up?
4. What is the current Event Match Quality (EMQ) score in Meta Events Manager? Screenshot or number is fine. If EMQ is below 7.0, that is the first thing to fix.
5. Is the Pixel passing any hashed PII — hashed email (em), hashed phone (ph), first name (fn), last name (ln), zip (zp)? If yes, where is that data coming from (form fields captured pre-submit, confirmed-data post-submit)?
6. Is there any iOS ATT signal recovery in place — either Advanced Matching, Meta's Aggregated Event Measurement (AEM) configuration, or modeled conversion data toggled on in the dataset settings? What is the current "Modeled" vs "Measured" split showing in Events Manager?
7. Are there any duplicate Pixel fires being flagged in Events Manager? Dedup key being passed?

B. Current CAPI State (if any)

1. Is there a Conversions API integration running at all? Even a basic partner integration (QW itself, any ad tech vendor) that may be sending server-side events?
2. If yes: What events are flowing server-side? Is the event_id deduplication parameter being sent on both the browser Pixel and the server-side CAPI call for the same event?
3. Is there a GTM server-side container, a custom server endpoint, or a third-party CAPI middleware (Stape, Elevar, etc.) already deployed?
4. What attribution window is set in Meta — 7-day click / 1-day view, or something else? Has this ever been changed?
5. What is the current "Server + Browser" match rate shown in Events Manager for the Lead event?

C. QuoteWizard Postback Flow

1. How does Iron Corp receive QW accept/reject/sold/paid signals today? The specific question: is this (a) a daily email report, (b) a CSV pushed to a shared S3 bucket or SFTP, (c) a real-time webhook posted to an Iron Corp endpoint, or (d) something Mo can pull manually from a QW partner portal?
2. Where do those signals land after Iron Corp receives them — into a CRM, an internal database, a spreadsheet, or are they currently not being stored at all (which the May data suggests)?
3. What is the lag from form submission to QW accept/reject signal? Real-time, hourly, daily batch, or unknown?
4. What is the lag from accept to sold/paid signal? QuoteWizard typically operates on net-30 or net-14 payout cycles — confirmed or different here?
5. What fields does the QW postback carry? Specifically: does it include the original Iron Corp lead ID, the user's hashed or unhashed email/phone, the payout amount per lead, and the carrier ID?

D. CRM / Lead Store

1. Where does lead-level data live after a form submission completes? Is there a CRM (Salesforce, HubSpot, custom), a raw database table, or is the lead data effectively owned entirely by QW after submission?
2. Does Iron Corp retain a lead record that links: source (Meta campaign/ad set/ad), form submission timestamp, user identifiers (email, phone — hashed or otherwise), consent record, Jornaya LeadiD, TrustedForm certificate URL, and QW lead ID?
3. Can Iron Corp's infrastructure make outbound HTTPS calls to Meta's CAPI endpoint (graph.facebook.com)? Any firewall/egress restrictions?
4. Is there an existing internal reporting pipeline that pulls the daily metrics that produced the May CSV? What system generates it? This is the most direct place to attach QW postback data.

E. Form + Consent Surfaces

1. What is the exact form architecture? Three options: - Iframe: QW serves the form inside an <iframe> on a military.com page. Iron Corp's domain is in the URL bar; QW form is sandboxed inside. - Redirect: User lands on military.com, clicks a CTA, gets redirected to a QW-hosted URL (qwlead.com or similar), fills out the form on QW's domain, then gets redirected back. - Iron Corp page posting to QW API: The form lives on military.com, form fields post directly to QW's lead intake API, confirmation is displayed on military.com. No iframe, no redirect.
2. Where do Jornaya LeadiD tokens and TrustedForm certificate URLs get generated and stored? Are they validated server-side before the lead is submitted to QW, or are they generated client-side and passed as fields without server-side validation?
3. Is the consent disclosure language on the form seller-specific (Iron Corp / Military.com named as the seller obtaining consent) or bundled/shared-partner language (consent given to a list of unnamed or broadly defined partners)? This matters for QW's own TCPA exposure and will matter more post-January 2024 FCC one-to-one consent rule enforcement.
4. Is there a confirmation/thank-you page on military.com domain after submission? Even if QW hosts the form, does the user return to a military.com URL?

Part 2 — Event Taxonomy

The goal is to move Meta from optimizing on raw Lead volume to optimizing on AcceptedLead value — and eventually on SoldLead or PaidLead revenue. Each event below is a step up the value chain.

Event Table

Event-by-Event Specification

Lead - Server endpoint: Iron Corp application server (same domain as form or same domain as form-hosting page). Fires immediately on form submit. - Payload: Standard CAPI payload — event_name: "Lead", event_time (Unix timestamp), event_id (UUID generated at submit, shared with Pixel), user_data block with em + ph SHA-256 hashed, fn + ln hashed, zp hashed, fbp and fbc passed from cookies, client_ip_address, client_user_agent. custom_data block: content_name (product line — "auto" or "home"), content_category ("insurance"), value: 0, currency: "USD". - Deduplication: event_id must be identical on both the browser Pixel call and the server CAPI call for the same submission. Meta deduplicates on this field within a 48-hour window. - Backfill: No — fires real-time on submit.

QualityLead - Server endpoint: Iron Corp application server, fires after cert validation and anti-bot logic completes (typically <200ms post-submit if synchronous, or async within seconds). - Payload: Same as Lead plus custom_data.lead_id (internal), custom_data.jornaya_id, custom_data.trustedform_cert_url. value: 0. - Deduplication: Unique event_id. No browser Pixel counterpart — this event is server-side only and will not have a duplicate to resolve. - Backfill: If cert validation is not currently happening server-side, this event can initially be fired as a proxy by Iron Corp's server confirming non-duplicate submission. Full cert validation added in Week 3.

AcceptedLead - Server endpoint: Iron Corp webhook receiver (a new endpoint built in Week 2). QW POSTs accept signals here; the endpoint transforms the payload and forwards to Meta CAPI. - Payload: Same match keys as above (looked up from Iron Corp's lead store by qw_lead_id → iron_corp_lead_id). custom_data.value = QW payout amount (e.g., 18.50). custom_data.currency: "USD". custom_data.qw_lead_id. - Deduplication: event_id constructed as "accepted_" + qw_lead_id. No browser Pixel counterpart. - Backfill: If QW delivers postbacks via CSV or daily email rather than real-time webhook, this event uses Meta's offline Conversions API upload (same endpoint, same payload, event_time set to the actual accept timestamp from QW's data). Historical May data — if QW can provide it — should be backfilled in Week 3 to bootstrap signal.

SoldLead - Server endpoint: Same webhook receiver or a second handler if QW delivers "sold" signals separately from "accepted." - Payload: Same match keys. custom_data.value = carrier payout (if known; use QW sold value if carrier payout is not separately reported). custom_data.carrier_id. - Deduplication: event_id = "sold_" + qw_lead_id. - Backfill: Likely requires offline upload. QW's "sold to carrier" signal may lag 24-72 hours. Batch upload acceptable initially.

PaidLead - Server endpoint: Triggered by Iron Corp's finance/CRM reconciliation process, not a live webhook. - Payload: Same match keys. custom_data.value = actual USD amount received. This is the ground-truth event for long-term algorithm training. - Deduplication: event_id = "paid_" + iron_corp_lead_id. - Backfill: Offline upload on net-14 or net-30 cycle. Lower urgency — implement after AcceptedLead is stable. Most important for annual model quality.

Which event to optimize on (and when)

• Immediately (Week 2-3): Keep optimizing on Lead. Do not change the optimization event until CAPI is verified working and AcceptedLead has at least 50 events/week flowing (Meta's minimum for Value Optimization).
• Week 4: If AcceptedLead volume >= 50/week, test switching to QualityLead optimization first (higher volume, lower noise than AcceptedLead). Run as a holdout — not a full account switch.
• Week 5+ (July): If AcceptedLead signal is clean and volume sufficient, switch Meta campaign objectives to AcceptedLead with value optimization. This is the point where Meta starts buying the right leads instead of just more leads.

Part 3 — Server-Side CAPI Rebuild Architecture

Where the Endpoint Lives

Iron Corp's development team hosts a lightweight HTTPS endpoint on their existing application infrastructure — the same servers that already handle form submission processing. This is not a third-party middleware product (Stape, Elevar, etc.) unless the dev team has a strong preference. Third-party middleware is acceptable if Iron Corp's infra cannot make outbound HTTPS calls to Meta or if the dev team lacks bandwidth, but it adds a vendor dependency and a monthly cost. The spec below assumes Iron Corp infrastructure; if the Tuesday diagnostic reveals a blocker, the Stape/GTM server-side option is the fallback with the same event taxonomy.

Lead Flow: Form to Meta

1. User fills out and submits the insurance lead form on military.com (or on QW-hosted form — architecture varies; see Part 6).
2. The browser Pixel fires Lead with a UUID event_id generated at submit time.
3. Simultaneously (or within <1 second), Iron Corp's server receives the same form submission data, performs validation, hashes all PII fields (SHA-256, no salt, normalized as Meta specifies: lowercase email, E.164 phone, etc.), and POST-s to https://graph.facebook.com/v19.0/{pixel_id}/events with the Lead event payload including the same event_id.
4. Meta receives both the browser event and the server event, matches them via event_id, deduplicates, and counts one Lead with higher match confidence than either signal alone.
5. Iron Corp's server also stores the lead record: iron_corp_lead_id, timestamp, hashed PII, fbp, fbc, product line, form source, Jornaya ID, TrustedForm URL, consent language snapshot.

QW Postback Flow: QW to Meta

Two sub-paths depending on how QW delivers postbacks (the Tuesday diagnostic determines which):

Path A — Real-time webhook (preferred): QW sends an HTTP POST to Iron Corp's webhook receiver endpoint each time a lead is accepted, sold, or paid. The endpoint looks up the original iron_corp_lead_id using the qw_lead_id from the postback, retrieves the stored hashed PII and match keys, constructs the AcceptedLead or SoldLead CAPI payload with the actual payout value, and forwards to Meta within seconds of the QW signal.

Path B — Batch postback (CSV/email/SFTP): Iron Corp receives a daily file from QW. An automated process (cron job or triggered script) parses the file, looks up each qw_lead_id in Iron Corp's lead store, constructs the CAPI payload for each resolved lead, and submits them as a batch to Meta's offline Conversions API endpoint. The event_time in each payload is set to the actual accept/sold timestamp from QW's data — not the upload time. Meta accepts events up to 7 days old for standard CAPI; up to 90 days for offline events API. Historical backfill of May data uses this same mechanism.

Privacy and PII Handling

• No raw PII ever leaves Iron Corp's servers in the direction of Meta. All user identifiers (email, phone, name, zip) are SHA-256 hashed before inclusion in any CAPI payload, following Meta's normalization rules exactly.
• Raw PII is stored in Iron Corp's own systems (lead store / CRM) for consent record compliance and TCPA obligations. It is not transmitted to Meta.
• The consent record — including Jornaya LeadiD, TrustedForm certificate URL, consent language text, and timestamp — is stored in Iron Corp's lead record and is never sent to Meta. It exists for Iron Corp's legal protection.
• The Iron Corp CAPI endpoint requires authenticated access (access token scoped to the Pixel ID). The access token is stored as an environment variable, not in code.
• GDPR/CCPA note: Military.com's audience is US military and veteran demographics. Consent should be validated as US-compliant. If any international traffic is present, geo-filter before sending PII-derived data to Meta.

Logging and Reconciliation

Daily automated reconciliation report (can be a simple email or Slack notification): - Total browser Lead events fired (from Pixel) - Total server-side Lead events fired (from CAPI) - Dedup match rate (should be >90% after Week 2) - Total AcceptedLead events (from QW postback) - Total QualityLead events - Discrepancy flag: if server Lead count differs from browser Lead count by more than 5%, alert

Monthly reconciliation: CAPI AcceptedLead count and total value vs QW's partner statement vs Iron Corp CRM revenue record. Any delta > $500 triggers a manual audit.

Enhanced Match Quality Optimization

EMQ is the single fastest win before the full CAPI rebuild is complete. The steps in order of impact: 1. Pass hashed email + phone on every Lead event. If these are not being passed today, adding them can raise EMQ from 4–5 range to 7+ in 48 hours. 2. Add fbp and fbc cookie values to every server-side event. These cookies are set by the browser Pixel and should be captured on form submit and stored server-side. 3. Add fn, ln, zp hashed on every event where the user provides them. 4. Verify client_ip_address and client_user_agent are being passed on every CAPI event — these are mandatory for match quality and are frequently omitted in basic implementations.

Part 4 — Implementation Timeline (June)

Week 1 — June 1-7: Diagnostic + Spec Lock

Goal: Leave Tuesday June 2 with answers to every question in Part 1. By Friday June 6, have a locked technical spec that the dev team has signed off on.

Actions: - Mo runs Part 1 diagnostic with dev lead on Tuesday June 2. Takes notes; does not push toward solutions until all questions are answered. - Review Events Manager on Tuesday live — EMQ score, current event volume, any CAPI status. - If EMQ is below 7.0 and the fix is purely additive (pass hashed email/phone to existing Pixel), push to do this Tuesday or Wednesday. This is a one-line GTM or code change and should not require a sprint cycle. - Dev lead confirms: (a) which form architecture (iframe / redirect / own-page-to-QW-API), (b) whether QW postback is webhook or batch, (c) whether Iron Corp has a lead store that retains QW lead IDs. - Deliverable: Written technical spec incorporating Tuesday's answers, shared back with dev team by Thursday June 5.

Blocking risks: Dev team is unavailable or has no sprint capacity until the following week. Mitigation: Mo identifies the single EMQ fix that can ship without a sprint (hashed PII passthrough), and the dev lead commits to one engineer for the CAPI work.

Dev capacity ask: One developer, part-time (estimated 3-5 hours for assessment, 2-3 hours for EMQ fix).

Week 2 — June 8-14: Server Endpoint + First Events in Test Mode

Goal: Iron Corp's server-side CAPI endpoint is running in test mode. Lead and QualityLead events are firing server-side and deduplicating correctly with the browser Pixel.

Actions: - Dev stands up the HTTPS endpoint. Integrates with Meta CAPI using the test event tool in Events Manager (test event code lets you verify payloads without counting toward real data). - Verify: event_id deduplication working. EMQ score rising. Server Lead count matching browser Lead count within 5%. - Begin building the QW postback receiver (if webhook) or the batch processor (if CSV/email). Even if this is not live to Meta yet, the Iron Corp side of the pipeline needs to exist. - Confirm: Iron Corp lead store is being populated with qw_lead_id and iron_corp_lead_id linkage. This is the linchpin — without the ID mapping, backfill is impossible.

Blocking risks: QW does not deliver a real-time webhook and the daily CSV process requires a new ingestion pipeline. Mitigation: Start with the CSV/batch path as the fallback; it is slower but achievable in the same week.

Dev capacity ask: One developer, approximately 15-20 hours across the week. If the dev team is resource-constrained, the QW postback processor can slip to Week 3 without blocking the Lead event work.

Week 3 — June 15-21: AcceptedLead Backfill + Live AcceptedLead Events

Goal: AcceptedLead events are flowing to Meta — both historical (May data backfilled) and live (new accepts firing in near-real-time). Meta begins seeing lead value for the first time.

Actions: - Request from QW: export of all accepted leads from May 1-May 30 with accept timestamps and payout amounts. If QW can provide this, backfill via offline CAPI upload. Even 1,000 historical AcceptedLead events with real USD values will immediately change what Meta knows about this account. - Turn on the live AcceptedLead pipeline (webhook or batch) in production. First live AcceptedLead events hit Meta. - Monitor: Does Meta's Events Manager show the AcceptedLead event populating? Does average event value look correct relative to expected QW payout rates? - Add cert validation to QualityLead if not already in place.

Blocking risks: QW refuses to provide the May historical export. Mitigation: Even without historical data, forward-looking AcceptedLead events from June start training the Meta algorithm. The algorithm needs 50 events/week to be useful; if June volume supports it, optimization signal builds within 2-3 weeks from go-live.

Dev capacity ask: One developer, approximately 10 hours (mostly integration testing and the historical upload script). QW partnership contact needed to request the data export — this is Mo's ask, not dev's.

Week 4 — June 22-28: Optimization Switch Test

Goal: Meta campaign is running with real value data flowing. Test switching at least one campaign's optimization objective from Lead to a value-based event.

Actions: - Review AcceptedLead weekly volume. If >= 50 events/week, propose test: create a duplicate campaign optimizing on QualityLead with Highest Value bidding. Run alongside existing Lead-optimized campaign as a holdout (not an A/B split that disrupts existing performance). - If AcceptedLead weekly volume is below 50, do not switch — report the volume gap and set a July target date. - Set up the daily reconciliation report in whatever format works for Lauren and the dev team — spreadsheet email, Slack, or dashboard. - Review SoldLead and PaidLead pipeline feasibility. If QW provides sold signals, stand up that event. If not, document it as a July item.

Blocking risks: Volume is too low to switch optimization event (< 50 AcceptedLead/week). This is the most likely blocker. At $25 CPL and a typical QW accept rate of 40-60%, ~3,500 leads/week should generate 1,400-2,100 accepts. If the accept-rate postback is working, volume should be sufficient. The risk is the postback itself not materializing.

Dev capacity ask: Minimal — monitoring and threshold-check logic. No new development required unless switching optimization events triggers a campaign rebuild.

Part 5 — Expected Impact

The Meta Benchmark

Meta's published performance data for accounts that implement CAPI with quality-signal optimization (optimizing on a downstream conversion event with real value rather than raw lead count): - 15% lower cost-per-quality-lead (CPQL) - 44% higher quality-conversion rate (more accepted / sold leads per dollar spent)

These are averages across verticals. Insurance lead gen is a high-signal vertical — Meta's algorithm is well-trained on insurance purchase intent. The benchmarks are credible here.

Applied to May Numbers

Current state (May Week 1 baseline, the best week): - CPL: $22.23 (May 1) - RPL: $34.74 - Net margin: ~36% - Daily spend: ~$28K - Daily net revenue: ~$15.7K

After CAPI rebuild with AcceptedLead optimization (applying Meta's 15% CPQL reduction): - CPL drops from ~$25 average to ~$21.25 (conservative — using the 15% figure on May's average, not the week 1 low) - At the same ~33K leads/month: spend drops from ~$825K to ~$700K for the same lead volume, or the same spend produces ~18% more leads - At $34 average RPL (holding revenue per lead stable): same spend goes from ~$281K gross to ~$331K gross - Net impact: approximately +$40,000-$55,000/month in net revenue at constant spend, before any creative or audience improvements

More conservatively, if only the CPL improvement materializes (not the quality-conversion rate improvement): approximately +$20,000-$30,000/month.

This Is Foundational, Not a Ceiling

These numbers assume nothing else changes. The CAPI rebuild compounds: - Creative testing becomes more efficient because Meta learns from accepted-lead signal, not raw click-through. - Audience expansion campaigns become less wasteful — Meta stops chasing cheap leads from low-intent audiences. - When form migration to Iron Corp's own form (Phase 2) happens, the CAPI infrastructure is already in place and the historical signal from QW-era leads provides continuity.

The CAPI rebuild is the prerequisite for everything else in July-August to work at its full potential.

Part 6 — Coexistence With QuoteWizard

This is the most architecturally critical section. The CAPI rebuild must not require changes to the QW integration — that migration is Phase 2 and is explicitly out of scope for the June-August measurement window. The implementation approach is different depending on which form architecture Tuesday reveals.

Architecture A — QW Iframe on Military.com Domain

What it looks like: User stays on military.com (e.g., auto.military.com/insurance/). The form appears in an <iframe src="qw-hosted-url.com/...">. The URL bar shows military.com throughout.

The problem: Browser Pixel on the parent military.com page cannot read events that fire inside the QW iframe (cross-origin sandbox). The Pixel fires PageView on the parent page but has no visibility into form field entry or form submit inside the iframe.

CAPI implementation: Iron Corp's server-side endpoint is the primary event source. Iron Corp must receive a postback from QW at the moment of form submission (QW sends a "lead submitted" notification to an Iron Corp URL) — this postback triggers Iron Corp's CAPI Lead event. The browser Pixel fires Lead on the parent page using a custom event triggered by a postMessage from the QW iframe (QW must support this — confirm Tuesday). If QW does not support postMessage, the Pixel Lead event fires from Iron Corp's postback handler via a Meta Pixel server-side pixel event (not a browser event), and deduplication is handled purely server-side.

Risk level: Medium. Depends on QW's willingness to (a) send an Iron Corp postback on submit and (b) support postMessage. Both are standard QW partner features but need confirmation.

CAPI coexistence verdict: Workable without changing the QW form at all. Iron Corp just needs QW to fire a server-to-server "lead received" notification to a new Iron Corp endpoint.

Architecture B — QW Redirect

What it looks like: User lands on military.com, clicks a form CTA, gets redirected to a QW-hosted URL (e.g., leads.quotelab.com/insurance/?...), fills out the form on QW's domain, and gets redirected back to a military.com thank-you page.

The problem: The form submit happens on QW's domain. Iron Corp's Pixel never sees the submit event. The only Iron Corp-domain events are the pre-redirect click and the post-redirect thank-you page load.

CAPI implementation: Iron Corp fires Lead on the thank-you page (when the user returns from QW's domain). This is reliable if QW always redirects back to a military.com URL with a lead status parameter. Iron Corp server fires the CAPI Lead event based on the QW return postback (same as Architecture A). Match quality may be slightly lower because IP/UA forwarding depends on QW including them in the redirect parameters or the return postback.

For fbp and fbc cookies: These persist on the military.com domain through the redirect and are available on the thank-you page. They should be captured on the thank-you page load and included in the server-side Lead event payload.

Risk level: Low to medium. The thank-you page is a clean trigger point. The gap is the ~10-15 second window between QW form submit and Iron Corp thank-you page where the lead technically exists but hasn't fired a CAPI event yet.

CAPI coexistence verdict: Straightforward. No QW form changes required. Iron Corp instructs the thank-you page and the QW return-postback handler.

Architecture C — Iron Corp Page Posting to QW API

What it looks like: The form HTML lives on military.com. On submit, JavaScript on the military.com page POST-s the form data to QW's lead intake API directly. QW returns a response (accepted/rejected/pending) and Iron Corp displays the confirmation on the same military.com page.

The problem: There isn't one. This is the simplest possible architecture for CAPI.

CAPI implementation: Iron Corp's server intercepts the form submit (or the API response), fires the browser Pixel Lead event from the same page, and simultaneously calls its own CAPI endpoint with the full user data payload. The CAPI endpoint hashes the PII and sends to Meta. No iframe sandboxing, no redirect gap, no cross-domain issues.

Risk level: Low. All events fire on Iron Corp's domain with full PII access. EMQ will be highest in this architecture.

CAPI coexistence verdict: Ideal. This is also closest to what the Phase 2 form migration will look like, so the CAPI infrastructure built here carries forward with minimal changes.

Likely Architecture on Tuesday

Based on what the May data shows (military.com URLs appearing in the funnel, QW as the lead buyer, no indication of cross-domain complexity in the reporting structure), Architecture A (iframe) or Architecture C (Iron Corp page posting to QW API) is most likely. Architecture B (full redirect to QW domain) would typically show QW-domain URLs in UTM attribution data. The diagnostic questions in Part 1-E will confirm within the first five minutes of the Tuesday conversation.

ASSUMPTIONS & OPEN QUESTIONS

Assumptions made in this document:

1. QW is the sole or primary lead buyer for the insurance vertical. If there are additional buyers (EverQuote, SmartFinancial, etc.) receiving leads from the same forms, the AcceptedLead event taxonomy needs to accommodate multiple buyer postbacks with different payout structures.

2. Iron Corp has a server-side application layer (not a purely static site) that can be modified to make outbound HTTPS calls to Meta's CAPI endpoint. If military.com is a fully static or CDN-served site with no application server, a lightweight middleware service (Lambda, Cloud Run, or Stape) will need to stand up a new endpoint.

3. QW sends postback signals (at minimum a daily batch) that include QW lead ID and accept/reject status. If QW provides no postback whatsoever and all lead status data lives inside QW's portal without an export mechanism, the AcceptedLead event is blocked until Mo negotiates postback access as a contract term with QW.

4. The Meta Pixel is on a legitimate, active dataset that is linked to Iron Corp's active ad account. If the account is using a different Pixel ID than what is in Events Manager, or if there are multiple active Pixel IDs on different surfaces, deduplication will fail silently and EMQ will be artificially suppressed.

5. The May 2026 daily CSV columns leads_sold, click_lead, click_lead_revenue, and lead_revenue being all zeros indicates the reporting pipeline was never built to consume QW postback data — not that QW isn't sending it. QW almost certainly has this data. The gap is on Iron Corp's side.

6. Dev team has at least one engineer with Python or Node.js experience who can build the CAPI endpoint and QW postback handler. Estimated total dev hours for the full Phase 1 CAPI build: 40-60 hours across June.

Open questions for Tuesday June 2:

1. Does QW currently send ANY postback to Iron Corp? If yes, what endpoint receives it and what fields does it carry?
2. What is the current Meta Pixel EMQ score? (Open Events Manager before the meeting.)
3. Is there an existing server-side GTM container? (This would accelerate Week 2 significantly.)
4. Does Iron Corp store a lead record that maps iron_corp_lead_id ↔ qw_lead_id? Without this mapping, backfill is not possible and real-time AcceptedLead events require the QW postback to carry enough PII to re-identify the user independently.
5. Is the QW relationship governed by a partner agreement that includes postback/API terms? Mo needs to know before requesting the May historical export — if QW can restrict data access contractually, this needs to go through the right channel.
6. What is Lauren's current workflow for reporting — does she pull from the internal tool that generates the daily CSV, or does she use Meta Ads Manager natively? The reconciliation report format should match her workflow.
7. Is there any existing offline conversion upload to Meta — even a manual one-time historical import? If yes, where is that dataset in Events Manager?
8. What is Iron Corp's existing hosting/infra stack? (AWS, GCP, Azure, on-prem, managed WordPress, other?) This determines the fastest path to standing up the CAPI endpoint.

Baseline Vetting Framework + Negotiation Prep

Go To War Strategy — Military.com / Valnet pilot Prepared: May 31, 2026 | Stakes: ~$45–75K USD over 90-day measurement window

One-sentence brief. The baseline Hassan locked into his model ($275K/mo starting June) is May's headline gross net revenue — a number inflated by an early-month spend surge that had already collapsed to a $103K/month exit pace by the final 7 days. Every $10K lower that baseline moves, Mo earns ~$4–6K more over the July–August measurement window (at a 20–30% take rate on lift). The $125K gap between Hassan's number and a defensible trailing-average baseline is worth $50–75K to Mo. This document is the analytical system Mo uses to vet that number when the historical data arrives.

PART 1 — Three Candidate Baseline Methods (+ YoY Seasonality Method)

Stakes table (compute after real data arrives)

Method 1 — Flat May 2026 Headline ($275K)

Formula / computation:

Baseline = May 2026 total net revenue ÷ 1
         = $281,622 ÷ 1
         = ~$275K (Hassan's rounded figure)

Why Hassan argues this: He's using a single-month snapshot at the calendar month level. Simple, defensible at the board level, and conveniently uses the highest month on record (inflated by early-May spend surge).

Why it's wrong: May's $281,622 is not a stable run rate — it's the aggregate of four structurally different operating environments inside one calendar month:

The business that generated $275K in May does not exist anymore. The business that Mo is actually inheriting is producing ~$103K/month at exit. Hassan is asking Mo to prove he beat a number the prior operator never reliably achieved either.

Probable dollar figure: $275K (exactly as Hassan states)

Favors: Hassan, strongly.

Worked example with placeholder data:

When Mar/Apr data arrives:
  Method 1 result = $281,622  [May actual — already confirmed]
  No computation needed. This is Hassan's opening ask.

Method 2 — Trailing 90-Day Rolling Average (ending May 30)

Formula / computation:

Baseline = (March 2026 net revenue + April 2026 net revenue + May 2026 net revenue) ÷ 3

Why this is defensible: It smooths single-month anomalies. It's standard in performance marketing contracts where one month can be distorted by spend ramps, seasonality, or one-time events. Hassan cannot credibly object to averaging — it's more conservative than cherry-picking peak months.

Why it favors Mo: May was artificially high vs. what the business was doing in March and April. Per Hassan's own statement, April was ~$125K. If March was similar, the average is ~$177K — not $275K.

Probable dollar figure:

Favors: Mo (moderate). A $177K–$187K baseline is fair and hard to argue against.

Worked example with placeholder data:

When data arrives, plug in:
  March 2026 net revenue:  $ [PULL FROM HASSAN / INTERNAL TOOL]
  April 2026 net revenue:  $ [PULL FROM HASSAN / INTERNAL TOOL]
  May 2026 net revenue:    $281,622  [confirmed]

  90-day average = (March + April + $281,622) ÷ 3

  Example: ($125,000 + $125,000 + $281,622) ÷ 3 = $177,207

  If Hassan says April was $125K and March was $125K →
  BASELINE = $177,207  →  round to $178K or negotiate to $175K.

Method 3 — Exit Run Rate (last 14 days of May annualized)

Formula / computation:

Exit run rate = (sum of net revenue May 17–30) ÷ 14 days × 30.4 days
             = $70,724 ÷ 14 × 30.4
             = $153,581/month

Excluding Memorial Day (May 23–25, net=$1,613 on $78K spend):
Exit run rate ex-MDW = ($70,724 − $1,613) ÷ 11 days × 30.4
                     = $190,998/month

Why this is defensible: The 14-day exit run rate is the most accurate picture of what the business is actually doing in the absence of unsustainable over-scaling. Weeks 1–2 of May benefited from a fresh creative set that fatigued rapidly and was over-scaled through Week 3, causing the collapse. The exit pace is the true operating floor. The ex-MDW version additionally removes a structurally anomalous holiday weekend where $78K was spent for ~$1.6K net return.

Why it's the strongest argument Mo has: The entire May spike was caused by overspending on fatiguing creative, not by genuine audience demand growth. Mo is being handed a business at $103K/month and asked to prove he beat $275K/month. That's a 2.7x target built on a month that doesn't represent steady-state.

Probable dollar figure: - Raw last 14 days: $153,581/mo - Ex-Memorial Day: $190,998/mo - Raw last 7 days: $103,178/mo

Favors: Mo (aggressive). Hassan will reject the last-7-days version. The last-14-days ex-MDW number at ~$191K is more defensible in a negotiation.

Worked example with placeholder data:

Last 14 days (May 17–30):
  Net revenues by day (from CSV):
    May 17: $4,991 | May 18: $13,826 | May 19: $14,027 | May 20: $9,874
    May 21: $5,793 | May 22: $1,405  | May 23: -$2,953 | May 24: $70
    May 25: $4,496 | May 26: $4,859  | May 27: $5,484  | May 28: $7,144
    May 29: -$77   | May 30: $1,785

  Total 14-day net: $70,724
  Daily avg: $70,724 ÷ 14 = $5,052/day
  Monthly equivalent: $5,052 × 30.4 = $153,581

  Excluding May 23–25 (Memorial Day, $1,613 net on $78,321 spend):
  Adjusted total: $70,724 − $1,613 = $69,111 over 11 days
  Daily avg: $69,111 ÷ 11 = $6,283/day
  Monthly equivalent: $6,283 × 30.4 = $190,998

Method 4 — YoY Seasonally Adjusted Baseline

Formula / computation:

Step 1: Pull net revenue for June 2025, July 2025, August 2025
        (from Meta Ads Manager + QuoteWizard — Mo pulls this starting June 2)

Step 2: Compute YoY growth rate, month-by-month:
        YoY_June  = (June 2026 projected / June 2025 actual) − 1
        YoY_July  = (July 2025 actual / June 2025 actual) − 1  [i.e., natural growth rate]

Step 3: Apply that natural growth rate to the Mar/Apr/May trailing average:
        Seasonally adjusted baseline =
            Trailing_90day_avg × (1 + natural_seasonal_lift_for_June)

Step 4: This is Mo's "honest baseline" — what the business would have done in 
        June 2026 with no Mo, based on what it actually did in June 2025.

Why this is the most rigorous: It's the only method that answers the direct question: "What would June look like if Mo had never been hired?" It removes both the May spike AND any argument about seasonal trends. If Hassan claims the business naturally grows in summer, the YoY data either confirms or denies that.

Why it requires the data pull: Cannot be computed without June–August 2025 actual numbers. Mo pulls this from Meta + QuoteWizard starting Monday June 2.

Probable dollar figure: - If Jun 2025 was ~$130–170K (likely for a newly acquired asset), the seasonally adjusted baseline lands in the same range as Method 2 ($140K–$185K). - If Jun 2025 was already $200K+, Hassan's growth narrative has more support, and Mo needs to rely on exit run rate.

Favors: Neutral. This is the "truth" method. Use it to validate whichever of Methods 2/3 the data supports.

Worked example with placeholder data:

When you pull from Meta + QuoteWizard:

  June 2025 actual net revenue:     $ [PULL]
  July 2025 actual net revenue:     $ [PULL]
  August 2025 actual net revenue:   $ [PULL]

  Natural Jun→Jul seasonal change: (Jul_2025 − Jun_2025) / Jun_2025 = [X%]
  Natural Jul→Aug seasonal change: (Aug_2025 − Jul_2025) / Jul_2025 = [Y%]

  If Jun 2025 = $150,000:
    And business was flat/declining (common post-acquisition):
    Jun 2026 organic expectation = $150,000 × (1 + modest inflation ~ 5%)
                                 = $157,500

  If Jun 2025 = $150,000 and Hassan claims +64% organic growth:
    Jun 2026 organic claim = $150,000 × 1.64 = $246,000
    But that +64% must be visible in 2025 data SOMEWHERE to be credible.
    Ask: "What drove 64% organic growth? Where does it show up in the 2025 data?"

PART 2 — Decision Tree: What Baseline to Argue For

Gate condition: Have the historical data in hand before this conversation. Do not enter the baseline negotiation without March, April, and July–August 2025 numbers confirmed.

START
  │
  ├─ PULL Mar/Apr 2026 from Hassan/internal tool
  │    AND pull Jul–Aug 2025 from Meta + QuoteWizard
  │
  ▼
[A] What did Mar/Apr 2026 show?
  │
  ├─ A1: Mar/Apr each ~$125K (consistent with Hassan's claim)
  │       AND YoY (Jun/Jul/Aug 2025) also ~$120–150K
  │         → DATA CONFIRMS: Business was running ~$125–140K/mo
  │           Trailing 90-day avg = ~$177K (inflated by May spike)
  │           ARGUMENT: "The trailing average including May's anomaly is $177K.
  │                       The cleaner picture is $140–155K. I'll accept $155K."
  │           BASELINE TARGET: $150K–$160K
  │
  ├─ A2: Mar/Apr much higher (~$200K+)
  │         → DATA SHOWS: May was a continuation of a strong spring, not an anomaly
  │           Hassan's $275K headline has more context supporting it
  │           ARGUMENT: Shift to exit run rate + Memorial Day exclusion
  │           "May was strong but the last 14 days ex-MDW ran at $191K.
  │            June is the reset month. $191K is honest."
  │           BASELINE TARGET: $185K–$200K
  │
  └─ A3: Mar/Apr were BELOW $125K (e.g., $80–100K)
            → DATA SHOWS: May was an EVEN BIGGER anomaly
              Hassan was running at $80–100K, spend-scaled unsustainably in May
              ARGUMENT: Trailing average is misleading TOWARD Hassan, not Mo
              "The trailing average ($147K–$160K) actually overstates the run rate.
               The true operating baseline is exit run rate at $153K."
              BASELINE TARGET: $140K–$155K (trailing avg, period.)


[B] What does YoY (Jun–Aug 2025) show?
  │
  ├─ B1: Jun–Aug 2025 was significantly LOWER than Hassan's $275K–$331K projection
  │         (e.g., Jun 2025 was $120–160K)
  │         → Hassan's "+64% organic ramp" is a model assumption, not historical fact
  │           He has no data showing this business has ever grown 64% in 6 months
  │           ARGUMENT: "Your model assumes organic growth no prior period demonstrates.
  │                       The honest starting point is what the business actually did,
  │                       which is ~$140–160K/month."
  │           BASELINE TARGET: $150K–$165K (aggressive)
  │
  ├─ B2: Jun–Aug 2025 shows STEADY GROWTH toward $200K+ by Aug 2025
  │         → Hassan's growth model has SOME historical support
  │           But even so, May 2026 over-scaled and collapsed; use Method 3
  │           ARGUMENT: "The business was growing — I agree. But May's headline
  │                       includes $78K spent over Memorial Day for $1,600 net.
  │                       Clean May ex-MDW = $311K. 14-day exit = $191K.
  │                       The right June baseline is $200K, not $275K."
  │           BASELINE TARGET: $185K–$205K
  │
  └─ B3: Jun–Aug 2025 was ALREADY at or above Hassan's $275K–$331K projection
            → Hassan's model is historically supported
              Mo's best move: don't fight the baseline, negotiate the fee structure instead
              (higher base, lower % threshold, shorter measurement window)
              BASELINE TARGET: Accept $275K, but negotiate contract protections
              (audit rights, adjustment clause for spend policy changes, shorter window)


[C] Wildcard conditions

  WC1: Apr→May jump (+120%+ MoM) was driven by a one-time buyer-side payout increase
         (e.g., QuoteWizard temporarily raised CPLs in April/May, reset in June)
         → May's RPL was artificially elevated. Check the RPL column:
           May W1 avg RPL: $34.49 vs May W4 avg RPL: $31.11 — already declining.
           If June's RPL opens at $27–29, May was a temporary payout spike.
         ARGUMENT: "RPL fell $3.38 in May alone. If buyer payouts normalized,
                     May $275K is mathematically unrepeatable. Baseline = 90-day avg."

  WC2: Pre-July 2025 data shows Monster-era ($200M+ company) performance
         was structurally different from the Iron Corp/Valnet era
         → Revenue levels from 2024 and earlier are not comparable
           The business was rebuilt post-acquisition with different buyers, tracking, ops
         ARGUMENT: "Any data before [acquisition close date] reflects a different
                     business. The relevant baseline window is the post-acquisition
                     operating history. Use [last N months of post-acquisition data]."
         ACTION: Find out when Valnet/Iron Corp acquired Military.com and use only
                 post-acquisition months.

  WC3: May spike was driven by a new ad account or campaign type Mo cannot replicate
         (e.g., a burst of remarketing from email list, a one-time promo, publisher deal)
         → Baseline built on that spike is unreachable even with Mo's best work
         ARGUMENT: "Walk me through what drove weeks 1–2 of May specifically.
                     If that driver is gone, the baseline should reflect what's
                     repeatable, not what was a one-time lift."

PART 3 — Pressure-Test Hassan's Growth Model

Hassan's model: $275K (June) → $451K (December) = +64% organic growth, without GTW.

Implied growth rates

Compound monthly growth rate (CMGR) Jun→Dec:
  ($451K / $275K)^(1/6) − 1 = 8.59%/month

Month-by-month implied targets:
  June 2026:     $275,000   ← proposed baseline
  July 2026:     $298,635   (+8.6%)
  August 2026:   $324,300   (+8.6%)
  September 2026:$352,172   (+8.6%)
  October 2026:  $382,439   (+8.6%)
  November 2026: $415,307   (+8.6%)
  December 2026: $451,000   (+8.6%)

8.59% compounding monthly growth is very aggressive. For context: - A business growing 8.6% per month is growing ~150% per year - The S&P 500 grows ~10% per year - Even top-quartile performance marketing accounts grow 10–30% per year, not 150%

The acid test

Question: Did Iron Corp / Valnet grow Military.com by 64% from June 2025 → December 2025?

Likely answer: No. Here's why the data will almost certainly show this:

1. Acquisition effect. Most acquisitions decline or flatline in months 1–6 as the new operator learns the asset. The outgoing operator (Monster/Randstad) has no incentive to set Mo up for success. Systems change, ad accounts reset, buyer relationships reset.

2. May 2026 tells the story. If the business were organically growing 8.6% monthly, May should have been ~$340–380K given a June 2025 starting point of $275K. It wasn't. It was $281K — roughly flat YoY if Hassan's model is self-consistent.

3. The RPL decline. Revenue per lead fell from $34.49 to $26.56 in a single month. That's a structural compression, not a growth business.

Month-flag analysis (where Hassan's model looks most aggressive)

The stress test in one sentence: If the Jul–Aug 2025 actuals you pull from Meta are below $200K/month, Hassan's December $451K target requires the business to more than double in 18 months with no explanation for what changes — and Mo's "organic" hurdle is a fiction.

What to do with this finding: Do not wave this as a gotcha at Hassan. Use it privately to confirm Mo's baseline argument, and use it in the negotiation as: "Your growth model is ambitious and I believe in it — but it means the June baseline needs to reflect where we're actually starting, not where May happened to peak."

PART 4 — The Case File (1-Page Template)

Mo fills in bracketed values when historical data arrives. Print this and walk in with it.

MILITARY.COM PERFORMANCE BASELINE — Mo's Position

Date of conversation: [mid-June 2026] Prepared by: Go To War Strategy

SECTION A — May 2026: Headline vs. Reality

The single most important sentence: May's $275K is the sum of four different businesses running inside the same calendar month — Week 1 ran at $434K/mo pace, and the last week ran at $89K/mo pace. The baseline for the pilot is not which week came first, it's what the steady-state operating capacity is.

SECTION B — YoY Seasonally Adjusted Baseline

Key finding (fill in): "June 2025 actual was $[X]. Hassan's June 2026 baseline represents a [Y%] YoY lift. The historical data [supports / does not support] that assumption because [evidence]."

If YoY growth was flat-to-negative: "Iron Corp's Military.com has not demonstrated the organic growth trajectory Hassan's model assumes. The honest June 2026 baseline — what the business would do with no GTW involvement — is closer to [Jun 2025 × modest inflation] = $[Z]."

SECTION C — Mo's Proposed Baseline

Proposed baseline: $[TARGET NUMBER]

Methodology: [choose one of below based on what data shows]

Option A (if Mar/Apr ~$125K): 90-day trailing average

March 2026: $[ACTUAL]
April 2026: $[ACTUAL]
May 2026:   $281,622
Average:    $[CALC] → round to $[TARGET]

Option B (if Mar/Apr ~$125K + exit run rate argument):

14-day exit run rate (May 17–30, ex-Memorial Day):
  Net over 11 non-MDW days: $69,111
  Daily: $6,283
  Monthly equivalent: $190,998
  → Baseline: $190,000 or negotiated to $185,000

Option C (hybrid): Average of trailing-90d and exit run rate

Method 2 result: $177,207
Method 3 result (ex-MDW): $190,998
Average: $184,103 → proposed baseline: $185,000

SECTION D — Why This Is Fair to Hassan

"Hassan, the performance fee structure works when the baseline reflects what the business does WITHOUT me. If we set the baseline at a peak that already collapsed before I touched a single campaign, I'm paying back value the account never actually held. You'd be paying me to recover ground that was lost before we signed — not to create new ground.

The right question isn't 'what did May total?' It's 'what would June do if Mo was never hired?' The answer to that question is $[TARGET], not $275K. I'm confident in my ability to beat $[TARGET] significantly. I'm less confident about beating a number the prior operator couldn't sustain for three consecutive weeks.

You don't pay GTW to deliver growth you'd get anyway. You pay for the lift above what the business naturally produces. Let's set the baseline at the natural level so both of us know exactly what we're measuring."

SECTION E — Clause Language (see Part 6 for full contract language)

Key points to put in writing within 48 hours of conversation:

1. Baseline = $[AGREED NUMBER] per calendar month, computed as [METHOD] over [WINDOW]
2. Measurement period = July 1, 2026 – August 31, 2026 (60-day run rate)
3. Goal posts apply to NET revenue above baseline (not gross)
4. Mo has right to audit underlying source data on 5-business-day notice
5. Baseline resets if QuoteWizard payout rates change by >15%, or Meta implements a policy change materially affecting lead qualification

PART 5 — Negotiation Script

Timing

Do NOT bring this up before June 15, 2026.

The sequence must be: 1. June 1–7: Get access, audit account, build trust with Lauren and dev. 2. June 7–14: Ship at least 2 visible quick wins (creative refresh, pacing fix, home scale). These become your credibility tokens. 3. June 14–21: Pull and verify the historical data. Build the case file. 4. June 15–21: Request a 1:1 with Hassan (not the team call, not the group session). "Hassan, I want to walk you through what the data shows on the baseline before we finalize the contract. 30 minutes this week?"

Do NOT negotiate baseline in a group setting. Lauren and the dev team do not need to hear this conversation. It changes the dynamic, puts Hassan on defense in front of his team, and risks making Mo look adversarial before trust is built.

The Opening (2–3 sentences)

"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."

Likely Objections + Responses

Objection 1: "We did $275K in May, that's the baseline."

Response: "We did — and I want to show you exactly how we got there. [open the day-by-day chart]. Week 1 ran at $434K/month pace. Week 4 ran at $89K/month pace. The $275K is the average of those two very different businesses inside the same month. The business I'm taking over is the one that existed on May 30, not May 5. If we baseline at $275K, I spend the first six weeks recovering ground the account lost on its own — and you're paying performance fee for a recovery I shouldn't be charged with causing."

Objection 2: "I built the model already, let's just go with it."

Response: "I've seen the model and I think the growth targets are achievable — that's not my issue. My issue is the starting line, not the finish line. The model works at any baseline; it's just a question of what percentage growth we're measuring from. If we agree on $175K instead of $275K, your upside calculation doesn't change — the account still needs to get to $375K to hit GP2. The only thing that changes is whether I get credit for getting it there, or whether some of that growth was already built into the prior operator's May spike."

Objection 3: "If we cherry-pick the bad weeks, of course you look good."

Response: "I'm not cherry-picking — I'm asking you to use the same standard for bad weeks that you're using for good ones. You're proposing to include Week 1 in the baseline. I'm proposing to include Weeks 1 through 4, which is the trailing average. The trailing average IS the standard methodology for this exact reason — so neither side can cherry-pick. And even the trailing average comes in around $177K using your own April number. I'm actually willing to round up to $185K as a gesture of good faith."

Objection 4: "We're already growing fast, you'd be getting paid for that anyway."

Response: "Then show me the historical data. If June, July, August 2025 showed 8.6% monthly organic growth, I'll accept a higher baseline — your growth assumption would be empirically supported. But if last year's same months came in at $130–160K, then the 64% growth in your model is a projection, not a fact. I'm not arguing about the future — I'm asking that the baseline reflect the past. Pull the 2025 summer data and let's look at it together."

The Close

"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 by [date]. 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. Can we do that?"

Then stop talking. Wait for Hassan to respond.

Follow-up within 48 hours: Send an email with: "Per our conversation — proposed baseline: $[NUMBER], computed as [METHOD] using March/April/May actuals you provided. Please confirm by reply so legal can incorporate." Get it in writing before July 1 or the measurement window is already running with no locked number.

PART 6 — Contract Clause Language

The exact language Mo wants in the Valnet/Iron Corp services agreement.

6.1 — Baseline Definition

"Baseline Net Revenue" means the monthly net revenue figure against which Go To War Strategy's performance fee is calculated, defined as follows:

Computation: The arithmetic mean of net revenue for the three calendar months immediately preceding the Measurement Period (March 2026, April 2026, and May 2026), where net revenue for each month is defined as total gross lead-buyer revenue received from all buyers, less total paid media spend on Meta Ads and any other paid channel, for the Military.com property operated by Iron Corp US Inc. / Valnet Inc.

Dollar amount: Baseline Net Revenue = $[AGREED NUMBER] per calendar month.

Measurement window: The Baseline Net Revenue figure shall be the reference point for all Goal Post calculations during the Pilot Measurement Period (July 1, 2026 – August 31, 2026).

Source data: Baseline shall be computed from data provided by Iron Corp's internal performance reporting tool AND cross-referenced against Meta Ads Manager and QuoteWizard reporting for the same periods. In the event of discrepancy between sources, the parties shall resolve the discrepancy in writing prior to execution of this agreement.

6.2 — Goal Post Calculations

Goal Post 1 (GP1): Monthly net revenue ≥ Baseline Net Revenue × 1.15 (i.e., ≥ $[BASELINE × 1.15]) during the Measurement Period.

Goal Post 2 (GP2): Monthly net revenue ≥ Baseline Net Revenue × 1.36 (i.e., ≥ $[BASELINE × 1.36]) during the Measurement Period.

Goal Post 3 (GP3): Monthly net revenue ≥ Baseline Net Revenue × 1.57 (i.e., ≥ $[BASELINE × 1.57]) during the Measurement Period.

For purposes of Goal Post calculation, monthly net revenue during the Measurement Period shall be computed using the same methodology (same revenue sources, same spend inputs, same attribution window) as used to compute Baseline Net Revenue. Any change in methodology that affects net revenue by more than 5% in either direction shall trigger a re-baselining per Section 6.3.

6.3 — Baseline Adjustment Triggers

The Baseline Net Revenue figure shall be subject to renegotiation in good faith within 15 business days if any of the following occur:

(a) Buyer payout change: QuoteWizard or any lead buyer accounting for >20% of gross revenue changes its per-lead payout rate by more than 15% (up or down) relative to the rate in effect during the Baseline Period. Adjustment shall be proportional to the revenue impact of the payout rate change.

(b) Meta platform policy change: Meta Ads implements a policy change that materially restricts audience targeting, creative formats, or lead generation objectives available to the account, resulting in a documented reduction of qualified leads per dollar spent of more than 15%.

(c) Acquisition or divestiture: Iron Corp / Valnet acquires or disposes of a material asset (generating or consuming >$25,000/month net revenue) integrated with the Military.com paid media account during the Measurement Period.

(d) Budget reduction by client: Client unilaterally reduces monthly paid media budget below $400,000 (the approximate May 2026 monthly budget) without GTW's agreement. GTW cannot be held to Goal Post targets if the budget ceiling prevents reaching them.

(e) Organic revenue reclassification: Any change in how "organic" versus "paid" revenue is attributed that materially affects the net revenue figures used for Goal Post calculation.

6.4 — Audit Rights

Go To War Strategy shall have the right, on no less than 5 business days' written notice, to request source-level data supporting the monthly net revenue figures used for Baseline and Measurement Period calculations. This includes:

• Meta Ads Manager spend and revenue export for the relevant period (account-level and campaign-level)
• QuoteWizard lead acceptance report and payout report for the relevant period
• Iron Corp internal performance report (the same report used to produce the data in this agreement)

Client shall provide the requested data within 5 business days of request. Audit rights may be exercised no more than once per quarter during the term of this agreement and any renewals.

In the event that data provided under audit materially differs from data previously provided for computation of Baseline or Measurement Period net revenue, the parties shall resolve the discrepancy within 15 business days. If unresolved, the discrepancy shall be resolved by reference to the Meta Ads Manager and QuoteWizard reports, which shall govern.

6.5 — Dispute Resolution on Delivered Numbers

If the parties disagree on whether a Goal Post was achieved in a given month:

(a) Either party may invoke this clause by written notice within 10 business days of the end of the relevant calendar month.

(b) Within 5 business days of such notice, each party shall submit its net revenue calculation with supporting data to a mutually agreed accountant or, failing agreement, to a certified public accountant selected by the American Arbitration Association.

(c) The accountant's determination shall be binding and shall be rendered within 15 business days of receiving both submissions.

(d) The cost of the accountant shall be borne by the party whose submitted number was further from the accountant's determination. If the accountant's determination falls equidistant, costs shall be split equally.

(e) Nothing in this clause prevents the parties from reaching a negotiated resolution before invoking the accountant process.

ASSUMPTIONS & OPEN QUESTIONS

Assumptions baked into this framework:

1. Hassan's statement that "April was $125K" is taken at face value as the best available prior-month estimate until the internal tool data arrives. If April was substantially different, the trailing-average calculations change materially — rerun the spreadsheet.

2. May 2026 net revenue of $281,622 is confirmed from the CSV file. This is the ground truth for May. Do not let Hassan propose a different May number without reconciling it against this file.

3. The 90-day pilot measurement window is July 1 – August 31, 2026 (60 days, not 90 calendar days). The 90 days includes June as the ramp month. If Hassan's contract language defines "measurement period" differently, the goal post math changes.

4. Mo's performance fee percentage (the take rate on lift) is assumed to be in the 20–30% range for the dollar-impact calculations. The actual rate is TBD in the contract. The framework holds at any take rate — the baseline negotiation is the highest-leverage single variable regardless.

5. This framework assumes the revenue metric is "net revenue" (gross lead-buyer revenue minus paid media spend) — the same metric in the CSV. If Valnet/Iron Corp wants to use "gross revenue" or "ROAS" as the metric, the entire baseline conversation shifts. Nail down the exact metric in the contract before anything else.

6. The exit run rate calculations treat the last 7 or 14 calendar days of May as the most predictive window for June's starting point. This is a defensible assumption but Hassan will contest it. The 90-day trailing average is the easier baseline to defend in a conversation.

Open questions Mo must answer before the baseline negotiation:

• [ ] What is the exact acquisition date when Valnet/Iron Corp took over Military.com? Pre-acquisition data is structurally incomparable and should not be used.
• [ ] What was March 2026 net revenue? (Hassan said April ~$125K; need March confirmed.)
• [ ] What were June, July, August 2025 net revenues? (Pull from Meta + QuoteWizard, starting June 2.)
• [ ] What is the exact RPL (revenue per lead) that QuoteWizard is paying in June 2026 versus May? An RPL drop of $2–3 on the same volume means the $275K number is not even theoretically repeatable.
• [ ] What is the exact percentage fee Hassan is proposing for lift above baseline? The answer determines exactly how much each $10K of baseline shift is worth in Mo's pocket.
• [ ] Does the contract count organic/direct traffic revenue separately from paid? If organic is bundled into the baseline metric, Mo gets credit (or blame) for things he doesn't control.
• [ ] Is the baseline measurement period exactly June 1 – August 31 (with measurement on July–August), or does the contract define it differently? Lock this before July 1.
• [ ] What triggered the April → May revenue jump? Was it a QuoteWizard payout increase, new buyer onboarding, increased budget, or improved creative? If it was a temporary payout increase that already reversed, May is even less repeatable.

Thread B Compliance Fixes + QuoteWizard Form Migration Scoping Plan

Iron Corp / Military.com — Go To War Strategy Produced: May 31, 2026 | For: Tuesday June 2 office visit with Hassan

PART 1 — Thread B Compliance Punchlist (June Week 1, Day 1–Day 7)

These are not aspirational items. Each one is an identifiable exposure that compounds the longer it stays live. The creative compliance issue was verified May 13 against the live Meta Ad Library. Execute in order.

Action 1: Pause the Three "60%" Creatives — Day 1, Hour 1

What: Three live ads making the claim "save 60% on car insurance" or equivalent superlative-savings language. Verified Ad IDs as of May 13, 2026: - 1004559982134492 (confirmed "60%" variant) - Two additional "60%" creative variants identified in the same May 13 ad library pull (Ad IDs to be confirmed on Monday when account access is granted — pull from the active ad library immediately on login)

Why it's urgent: FTC's "reasonable basis" standard requires substantiated savings claims at the time of publication. A 60% savings claim for auto insurance requires documented actuarial or carrier data showing that specific segment of buyers actually achieves 60% savings. That documentation does not exist. The ads were 7 days old at verification — the Meta algorithm has minimal invested learning in these specific creatives. Pausing them costs almost nothing in performance terms.

Action: In Business Manager, pause all three ad IDs. Do not archive — preserve for audit trail. Screenshot confirmation.

Owner: Lauren (Mo confirms the specific IDs, Lauren executes pause)

Timing: Day 1, Hour 1 — before any other account work begins

Dollar/risk impact: State DOI inquiry or class action exposure. TCPA class actions in the insurance vertical are routinely $500K–$5M+ in settlement value. This is not a hypothetical — SmartFinancial, EverQuote, and Integrity Marketing have all faced consent/claims-based regulatory action in the 2022–2025 period. The cost of pausing three creatives is zero. The cost of not pausing is unbounded.

Deliverable artifact: Screenshot of paused status + internal 1-line log entry: "Paused on [date] per compliance review — unsubstantiated savings claim, pending substantiation or retirement."

Action 2: Full Live Ad Library Audit for High-Claim Variants — Day 1–2

What: Systematically review every currently-active ad in the Meta account for savings claims exceeding 20% (auto) or 30% (home). Flag any claim that asserts a specific percentage without documented carrier substantiation.

The standard: Compliant claim language in the insurance vertical uses ranges with attribution ("drivers who switch save an average of $X, per [carrier] data") or relative comparisons ("compare rates from top carriers"), not unqualified superlatives. Any ad claiming ">X% savings" needs a carrier-signed rate study or it gets sunset.

Action: Lauren pulls the full active creative inventory. Mo reviews copy against the compliance language standard. Any claim above the threshold with no substantiation on file: pause immediately. Any claim above the threshold WITH a carrier data source on file: document the source and preserve.

Owner: Mo (audit logic) + Lauren (pulls inventory, executes pauses)

Timing: Day 1–2

Dollar/risk impact: The audit itself costs 2–4 hours. Missing a second exposure that surfaces in a DOI inquiry after the form migration (when Iron Corp owns full liability) would be significantly more expensive.

Deliverable artifact: One-page "Ad Library Compliance Audit — June 2026" spreadsheet: Ad ID, headline copy, claim made, substantiation status (documented / not documented), action taken (paused / approved / pending review).

Action 3: Jornaya LeadiD + TrustedForm Certificate Hygiene Audit — Day 2–3 (24–48 Hour Dev Sprint)

What: Sample 100 leads from May 2026. For each, verify: (a) is a LeadiD or TrustedForm certificate present in the lead record? (b) is the certificate valid (not expired, not a test cert, not null)? (c) does the cert timestamp precede the lead submission timestamp (mandatory for TCPA safe harbor)?

Why this matters now: Industry benchmark data shows approximately 18% of leads that are reported as "certified" carry invalid, missing, or malformed certificates upon audit. If Iron Corp's current cert yield is at or below that benchmark, two things are true: (1) existing leads have TCPA exposure today, and (2) the QuoteWizard relationship may already have a compliance friction point QW hasn't surfaced yet.

Action: Dev pulls lead sample from the May CSV or internal CRM. Write a quick script to check cert presence and validity against the Jornaya and TrustedForm APIs. Report back cert yield %.

Owner: Dev team lead (Mo provides the audit spec, dev executes)

Timing: Day 2–3. Results needed before the Tuesday Tuesday QW-contract conversation if possible; at minimum before Phase 1 of the form migration begins.

Dollar/risk impact: A 10% invalid-cert rate across ~33K May leads = ~3,300 leads with TCPA exposure. At $500 per lead in a class action (conservative), that's $1.65M in potential exposure. This audit costs one dev-day. It also establishes the baseline that the new form path must beat.

Deliverable artifact: "Cert Hygiene Audit — May 2026" memo: sample size, cert present %, cert valid %, timestamp-order pass rate %, identified failure modes. 1 page.

Action 4: TCPA Consent Language Review — Day 3–4 (Recommend, Do Not Yet Execute)

What: Review the current consent disclosure language on the QuoteWizard-hosted form. Document: (a) is consent bundled (one checkbox covering multiple buyers/partners) or seller-specific (separate disclosure per recipient)? (b) does the disclosure name Iron Corp / Military.com specifically as the data seller? (c) is the disclosure "clear and conspicuous" per FCC's One-to-One Consent rule (effective January 2025)?

The FCC One-to-One rule is live. As of January 27, 2025, the FCC's amended TCPA rules require that consent be obtained on a one-to-one basis — each seller must be individually named, and the consent must be logically and topically related to the website where it's obtained. Bundled multi-partner consent checkboxes are now legally insufficient for calls and texts.

Action at this stage: Document the current state. Do NOT change the QW-hosted form unilaterally — Iron Corp does not control that form today and modifying it requires QW coordination. The recommendation to shift to seller-specific consent is a Phase 2 action tied to the form migration. The purpose of this review is to quantify the current exposure and make the case for migration internally.

Owner: Mo (consent language analysis) + Lauren (screenshot/export current form)

Timing: Day 3–4

Dollar/risk impact: The FCC's January 2025 rule change is the single biggest compliance catalyst in the lead gen industry this cycle. Every lead gen operator still running bundled consent is operating with increasing legal exposure. This is also the reason the form migration has a compliance dimension that goes beyond margin — it is a liability remediation play, not just a revenue play.

Deliverable artifact: 1-page "TCPA Consent Audit — Current State" memo: current language verbatim, FCC One-to-One rule assessment (compliant / non-compliant / ambiguous), recommended language for the new form path. This memo feeds directly into the Phase 1 form build.

Action 5: Compliance Documentation Package for QuoteWizard Affiliate Team — Day 4–5

What: Produce a clean, professional 1-page document addressed to QW's affiliate compliance team summarizing: (a) the high-claim creatives identified and paused, (b) the cert hygiene audit being conducted, (c) Iron Corp's commitment to maintaining compliant lead quality going forward.

Why this is strategic, not just housekeeping: QW's affiliate compliance team audits partners periodically. An unsolicited compliance update that arrives proactively — before any audit trigger — signals that Iron Corp is a sophisticated, self-governing partner. It pre-empts any QW-initiated inquiry. It also opens a line of communication with the QW affiliate contact (whose name Mo needs — see Part 3) that will be essential when the form migration conversation begins.

Owner: Mo drafts, Hassan reviews and signs off before sending

Timing: Day 4–5

Dollar/risk impact: A QW-initiated compliance hold on the affiliate account would pause the lead flow entirely. At the current run rate (~$2,900–$14,300 net revenue per day), a 7-day hold is a $20K–$100K event. Proactive communication costs nothing and insures against that.

Deliverable artifact: "Iron Corp / Military.com — Affiliate Compliance Update, June 2026" (1 page, PDF). Sent to named QW affiliate contact.

Action 6: State DOI Exposure Scan — Day 5–7

What: Review all currently-active and recently-paused ad copy for specific dollar-amount savings claims or percentage savings claims tied to specific states. Flag any state-specific claim. Confirm no ad is making a specific savings representation that would require that state's DOI to have been notified.

What this is NOT: This is not a legal opinion. Do not spend money on outside counsel at this stage. This is a common-sense sweep: if an ad says "Ohio drivers save 60%," that is a different exposure than "compare rates and save." The former requires actuarial documentation specific to Ohio. The latter is comparative advertising.

Reference standard: The compliance mini-binder contains the compliant claim language templates. Any active claim that does not conform to those templates and cannot be immediately substantiated gets paused.

Owner: Mo (sweep) + Lauren (ad copy export)

Timing: Day 5–7. Can run in parallel with Actions 3–5.

Dollar/risk impact: State DOI inquiries move slowly but generate public records. A DOI inquiry on a $275K/month operation is a material business risk. Scan costs 2–4 hours.

Deliverable artifact: "State Exposure Scan — June 2026" checklist (1 page): states mentioned in active ads, claim language used per state, substantiation status, action taken.

Thread B Summary Table

PART 2 — QuoteWizard Form Migration: The Honest Decoder

Hassan said "switch from QuoteWizard hosted form to our own form." That is one sentence covering four distinct projects with dramatically different payoffs, build times, and risk profiles. Mo needs to surface the spectrum on Tuesday so Hassan understands what he's actually asking for — and so the decision to pursue Tier 2 is explicit, not implicit.

Tier 1: Own the Form, Still Post 100% to QuoteWizard's API

What it means: Iron Corp builds and hosts the lead capture form. The form collects the lead data. On submission, Iron Corp's server posts the lead to QW's existing API endpoint — exactly as today, just with Iron Corp controlling the form layer.

What changes: Iron Corp now controls the form UX (faster load, mobile optimization, A/B testing), the consent language (critical for FCC One-to-One compliance), the cert integration (Jornaya / TrustedForm firing reliably), and the CAPI pixel firing (server-side, no ITP issues). Iron Corp also sees every lead field before QW does — that data can feed attribution models even if the monetization path is unchanged.

What doesn't change: Revenue per lead. Iron Corp is still selling 100% of leads to QW at QW's current rate structure. The lead still goes through QW's buyers. The RPL is QW's RPL.

Honest assessment of the margin gain: Modest. The CAPI and UX improvements may lift accept rate 5–15% if the current form has meaningful friction or cert issues. That's real but not transformative. At $33.52 RPL and ~33K leads/month, a 10% accept-rate lift might be worth $30–50K/month in incremental revenue (more leads accepted at the same RPL). The form UX work also enables better Meta CAPI signals, which compounds over weeks. But you're still fully dependent on QW's buyer pool and pricing.

Build time: 2–4 weeks of dev work (form build, API integration, cert wiring, CAPI). Lower compliance complexity because you still have QW's downstream consent architecture partially in play.

Verdict: Worth doing as Phase 1 of the migration — it's the foundation everything else builds on. But doing Tier 1 alone and stopping there is a lot of transition risk for a modest incremental gain. The real money is Tier 2.

Tier 2: Own the Form + Multi-Buyer Ping-Post

What it means: Iron Corp owns the form (same as Tier 1), but instead of posting every lead exclusively to QW, Iron Corp runs a ping-post auction. On lead submission, the lead data (minus PII) is "pinged" to multiple buyers simultaneously. Buyers respond with a price. Iron Corp accepts the highest bid and "posts" the full lead to the winning buyer. QW becomes one buyer in a competitive pool rather than the exclusive buyer.

What changes: Revenue per lead. When QW has to compete to buy a lead, the price goes up. Industry benchmarks for multi-buyer ping-post environments show 20–40% RPL lift vs. exclusive-supply arrangements. At Iron Corp's volume (~33K leads/month), that is the largest single revenue lever available without changing ad spend or traffic volume.

The math (at conservative 20–30% RPL lift): - Current RPL: $33.52 - Ping-post RPL: $40.22 (20% lift) – $43.58 (30% lift) - Incremental per lead: $6.70 – $10.06 - Monthly incremental at current volume: $223K – $335K - Annualized: $2.68M – $4.0M

This is the biggest single lever in the entire engagement. It requires no change to ad spend, no new creative, no new audience targeting. It is a monetization architecture change.

The gate: The QuoteWizard contract. If the existing contract includes an exclusivity clause — Iron Corp can only sell leads to QW — Tier 2 is contractually blocked until that clause is renegotiated or the contract expires. This is the single most important unknown in the entire engagement right now.

Build time: 4–8 weeks after contract gate is cleared. Requires: (a) lead distribution platform (LeadConduit, Phonexa, or Boberdoo, or a custom build), (b) buyer integrations (QW plus at least 2–3 other insurance buyers), (c) accept-rate monitoring to ensure the multi-buyer path doesn't introduce friction that lowers overall accept rate.

Verdict: This is the target. Everything else is preamble.

Tier 3: Run Your Own Lead Exchange

What it means: Iron Corp builds a full publisher-side lead exchange — managing multiple traffic sources feeding into a centralized distribution platform with real-time bidding, lead scoring, compliance verification, and buyer management. Iron Corp becomes a lead marketplace operator, not just a lead generator.

Honest assessment: This is a 6–12 month build for a team with exchange experience. It requires a dedicated ops person, a compliance stack, ongoing buyer relationship management, and real-time fraud/quality scoring. It is the highest-margin path but it is a different business, not just a form change. Not in scope for this engagement.

Tier 4: Direct Carrier Deals

What it means: Rather than selling leads through QW or a multi-buyer ping-post, Iron Corp sells leads directly to insurance carriers (Progressive, GEICO, Liberty Mutual, etc.) under direct data purchase agreements.

Honest assessment: These agreements take 3–6 months of legal and compliance due diligence on the carrier side. Carriers require audited consent documentation, minimum volume guarantees, and carrier-specific data format integrations. Highest per-lead margin but requires the compliance foundation (Thread B) to be airtight before any carrier conversation. Phase 4 at the earliest.

The Honest Tier Summary

PART 3 — Tuesday QW-Contract Discovery Checklist

These are the specific questions Mo needs answered on Tuesday June 2 — from Hassan directly, or from Lauren/dev if Hassan doesn't have the contract in front of him. Do not proceed past Phase 0 of the migration until every question has an answer.

For Hassan:

1. Where is the QW contract physically? Who has executed copies — Valnet legal, Iron Corp US Inc., Rony's team? Can Mo see it before end of day Tuesday?

2. Is there an exclusivity clause? Specifically: does the agreement prohibit Iron Corp / Military.com from selling insurance leads to buyers other than QuoteWizard during the contract term? This is the gate question. If the answer is yes, the entire Tier 2 timeline shifts to "when can we renegotiate or exit."

3. What is the termination notice period? 30 days? 60 days? 90 days? This determines the earliest possible clean migration date. If it's 90-day notice, the migration planning timeline moves accordingly.

4. Does the contract explicitly permit or prohibit ping-post to other buyers? Some affiliate agreements are silent on ping-post (not explicitly prohibited) — that is a negotiating position. Others explicitly prohibit it. Need to know which.

5. What is the current revenue share / accept-rate structure? Specifically: is Iron Corp being paid a flat RPL ($33.52 per accepted lead), a tiered RPL by lead quality / bind rate, or a revenue share of QW's downstream revenue? The structure matters for the migration comp model.

6. Are there volume commitments? If the contract requires Iron Corp to deliver a minimum number of leads per month, a partial migration (Tier 1 A/B test, 10–20% own-form traffic) may trigger a shortfall clause.

For Lauren or dev:

7. Who is the named affiliate relationship manager at QuoteWizard? Need a name and email. This person is the contact for: (a) the proactive compliance package (Action 5 above), (b) any migration conversation, (c) any accept-rate dispute resolution.

PART 4 — Phased Migration Plan (Do NOT Execute in Measurement Window)

The hard sequencing rule governs everything below: the form migration cutover — meaning live traffic moving from the QW-hosted form to the Iron Corp-hosted form — does not land in July or August 2026.

The reason is not caution for its own sake. It is mathematical. July and August are the 60-day measurement window against which Mo's goal-post bonus is calculated. A migration-induced accept-rate dip of even 10–15% — which is a normal transition artifact — could cost Mo $30–60K in net revenue per month and potentially push the run rate below GP1. The upside of an early migration does not compensate for that risk. Phase it after the measurement window closes.

Phase 0: Discovery + Contract Review + Dev Capacity Scoping

Timing: June Week 1–2 (parallel to Thread A creative work and CAPI rebuild) What happens: QW contract reviewed, all 7 discovery questions answered, dev team capacity assessed (can they build the form in parallel with CAPI work without slowing CAPI?), compliance foundation work (Thread B Actions 1–6) executed. What does NOT happen: No code is written that touches the live lead flow. No changes to the QW API endpoint. No changes to the production form path. Decision gate to Phase 1: (a) QW contract reviewed and exclusivity/ping-post language documented, (b) Thread B Actions 1–3 complete, (c) dev capacity confirmed. Dev estimate: 0 dev hours on form build. All hours in Thread B compliance audit (est. 8–16 hours dev time for cert audit). Deliverable: Contract summary memo (1 page) + dev capacity assessment + Thread B completion report.

Phase 1: Build the Own-Form in Staging — No Live Traffic

Timing: June Week 3–4 through July (approximately 3–5 weeks of dev work) What happens: Dev builds the Iron Corp-hosted form in a staging environment. Consent language is drafted per the FCC One-to-One standard (from Thread B Action 4). LeadiD and TrustedForm are wired at the field level — every submission generates a valid cert. Server-side CAPI is built on the new form path (this is the same CAPI work happening in Thread A — they share infrastructure). QW API integration is replicated exactly so the new form posts to QW's endpoint identically to the current form. The form is brought to "demo-ready" status — full functionality, correct cert yield, correct CAPI events — but zero live traffic. What does NOT happen: No production traffic is routed to the new form. QW sees no change in lead flow. Decision gate to Phase 2: (a) QW API integration tested and confirmed, (b) cert yield on test submissions = 100%, (c) CAPI events firing correctly on test submissions, (d) consent language reviewed by counsel (see Part 5), (e) Hassan has seen and approved the demo. Dev estimate: 3–5 weeks, 1–2 dev resources. Overlaps with CAPI build — coordinate to avoid bottleneck. Deliverable: Staging environment URL + test submission log + cert yield report + CAPI event validation report.

Phase 2: Controlled A/B Test — 10–20% of Live Traffic

Timing: July (early-to-mid, after Phase 1 gate is passed) What happens: 10–20% of incoming traffic is routed to the new Iron Corp-hosted form. 80–90% continues on the QW-hosted form. Watch three metrics obsessively for 2 weeks: (a) accept rate on the new form path vs. the QW form path, (b) cert yield on the new form path (should be 100%), (c) CPL and RPL on the new form path vs. the QW path. The test question: Does the Iron Corp form hold or improve accept rate vs. the QW form? If yes, the migration is safe to expand. If no — accept rate dips more than 5% — stop, diagnose, fix before expanding. Why 10–20%: Small enough that a bad outcome doesn't materially move the July run rate (10–20% of ~33K leads/month = 3,300–6,600 leads). Big enough to get statistically meaningful accept-rate data within 2 weeks. Decision gate to Phase 3: (a) New form accept rate within 5% of QW form accept rate for 14 consecutive days, (b) cert yield 100% confirmed, (c) measurement window closed (post-August 31). Dev estimate: 1–2 days to set up traffic split. Ongoing monitoring. Deliverable: A/B test results memo (accept rate, RPL, cert yield, sample size, confidence level).

Phase 3: Full Cutover to Own Form — After August Measurement Window

Timing: September 2026 (after August 31 measurement window closes, assuming Phase 2 gate passed) What happens: 100% of traffic routes to Iron Corp-hosted form. QW-hosted form is deprecated. At this point, if Tier 2 (ping-post) is contractually permitted and technically ready, ping-post to multi-buyer pool can begin — QW becomes one buyer competing for each lead rather than the exclusive buyer. The Tier 2 unlock: If the QW contract permits ping-post and the additional buyer integrations have been built during Phase 1/2 staging, September is when the RPL lift materializes. The $200–330K/month incremental revenue turns on here. Dev estimate: 1 day for cutover. 2–4 weeks prior to cutover for additional buyer API integrations (if Tier 2 is live). Deliverable: Migration completion report + first-week RPL comparison (new form vs. QW-hosted historical baseline).

Phase 4: Multi-Buyer Optimization + Direct-Carrier Exploration

Timing: Q4 2026 What happens: Optimize buyer pool (add/remove buyers based on accept rate and RPL performance), implement lead scoring (route higher-intent leads to higher-paying buyers), begin exploratory conversations with 1–2 direct carrier contacts. Evaluate exchange platform options (LeadConduit, Phonexa) if volume growth justifies the operational overhead. Dev estimate: Ongoing. This is an operational capability, not a one-time build. Deliverable: Quarterly lead distribution performance report + carrier exploration summary.

Phase Summary Table

PART 5 — The Compliance Liability Shift

This is the part Hassan probably hasn't fully internalized. It needs to be said on Tuesday — clearly, without alarm, framed as the reason for phasing correctly rather than the reason not to migrate.

The current state: QuoteWizard hosts the form. QuoteWizard's consent language appears on the form. QuoteWizard's LeadiD and TrustedForm integrations (if any) govern the cert. When a lead is submitted and then called by a downstream carrier or insurance agent, the consent documentation names QW's form as the collection point. In a TCPA action, the plaintiff's first call is to QW's legal team, not Iron Corp's. Iron Corp is upstream — it drove the traffic, but QW collected the consent.

The moment Iron Corp hosts the form: Iron Corp is now the entity that collected consent. Iron Corp's disclosure language is the operative consent document. Iron Corp's server is where the cert was generated. If a plaintiff or regulator wants to know "who got consent to call me about auto insurance," the answer is Iron Corp / Military.com. QW is now downstream — they bought the lead, but Iron Corp took the consent.

This is not a reason not to migrate. It is a reason to migrate with the compliance foundation in place first. Specifically:

Before Phase 3 (full cutover), Iron Corp needs:

1. In-house or partnered compliance counsel who has reviewed the consent language and the cert integration. This is a one-time legal engagement, not an ongoing retainer. Budget: $5,000–$15,000 for a qualified TCPA specialist to review the form and sign off. This is a rounding error relative to the $200–330K/month Tier 2 upside. It is not optional.

2. FCC One-to-One compliant consent language. The consent disclosure on the own-form must name each recipient entity individually (or use a clearly-labeled, narrowly-scoped multi-seller disclosure). Bundled "and our marketing partners" language is insufficient under the January 2025 rule.

3. 100% cert yield on the new form path. Not 95%. Not 98%. Every single lead submitted through the Iron Corp form must carry a valid, timestamped LeadiD and/or TrustedForm certificate before any live traffic migrates. The cert is the safe harbor. A missing cert on a called lead is a $500–$1,500 TCPA exposure per lead.

4. A documented lead data retention and access policy. Iron Corp will be holding consent records. Those records need to be retrievable for 5 years minimum (FCC guidance) in case of litigation.

Thread B is the load-bearing wall for the migration. If Thread B is skipped or half-executed, Phase 3 of the migration creates a compliance exposure that is larger than the current one — because Iron Corp now owns it directly. The reason Thread B is Week 1 is not just about the current 60% creatives. It is about building the compliance posture that makes the form migration safe to execute.

PART 6 — Expected Dollar Impact When Tier 2 Is Live

The following is the math Hassan needs to understand. It is also the math that defines the value of getting the sequencing right.

Baseline: - May 2026 total net revenue: $281,622 - Approximate lead volume: ~8,400 leads (at average CPL ~$25, spend ~$210K implied from daily data; or use RPL cross-check: $281,622 / $33.52 = ~8,400 accepted leads) - Average RPL: $33.52

Note on lead volume: The May CSV shows 33,368 total rows (leads generated), but leads_sold column is all zeros — meaning the internal report does not reflect actual accepted/sold lead count. The $281,622 net revenue at $33.52 RPL implies ~8,400 accepted leads out of ~33,368 total leads generated, which equals approximately a 25% accept rate. This is a critical baseline metric that needs confirmation from QW's affiliate dashboard on Monday.

The Tier 2 math:

Important conditionality: - The RPL lift assumes the multi-buyer environment has at least 3–4 competitive buyers bidding on Iron Corp leads. A thin buyer pool produces a thin lift. - The lift assumes accept rate on the new form path holds at or above current QW accept rate. If the migration introduces any friction that lowers accept rate, the incremental RPL gain is partially or fully offset. - The QW contract must permit ping-post. If it does not, Tier 2 is blocked until the contract is renegotiated or terminates. - Volume must hold. If the form migration introduces tracking/pixel issues that degrade Meta's optimization signal, CPL rises and volume falls — offsetting the RPL gain.

The compounding picture: If Thread A (creative + CAPI) lifts monthly revenue from the current exit rate of ~$87K/month to $220–300K/month by July, and then Tier 2 adds 25% RPL lift on top of that base, the September run rate could be $275K–$375K/month purely from margin improvement on existing volume. That is GP2-to-GP3 territory, which is the zone where Mo's comp structure becomes very interesting.

This is why the form migration is the GM's second priority and Mo's highest-margin lever. But the margin only materializes if the sequencing is correct. A migration that breaks in July costs Mo more than the upside is worth.

PART 7 — Tuesday Talking Points with Hassan

The framing for Tuesday: affirm the instinct, surface the spectrum, name the gate, commit to the phase.

Talking point 1 — Affirm the instinct

"Hassan, you're right that the form migration is the highest-margin move in this engagement. You saw it before I got here. I ran the math: if we get to a multi-buyer environment, we're looking at $50–85K incremental net revenue per month at current volume, potentially more as we scale. That's the target."

Talking point 2 — Surface the four tiers

"When you say 'own the form,' there are actually four different versions of that project. The one that gets us to the real number is Tier 2 — own the form and run a ping-post auction to multiple buyers. Tier 1 alone — own the form and still post 100% to QW — is a meaningful improvement in data and compliance, but it doesn't move the revenue number much. I want to make sure we're aiming at Tier 2."

Talking point 3 — Surface the QW contract as the gate

"Before we plan any of this, I need to see the QW contract. Specifically: is there an exclusivity clause? If QW has Iron Corp locked to selling leads only to them, Tier 2 is blocked until we renegotiate. That's the single question that determines whether the migration is a June-to-September project or a 2027 project."

Talking point 4 — Surface the compliance liability shift honestly

"One thing I want to make sure you and Lauren are clear on: the moment we host our own form, TCPA liability transfers to us. Right now QW is on the hook for a lot of the consent documentation. When it's our form, it's our liability. That's not a reason not to do it — it's the reason we do Thread B first and get a TCPA lawyer to sign off on the consent language before we flip any live traffic. The compliance work is the foundation the migration sits on."

Talking point 5 — Commit to the phased approach and protect the measurement window

"Here's how I want to phase this so we don't blow up July and August. We build the form in staging in June, run a 10–20% A/B test in July, and do the full cutover in September after the measurement window closes. The upside is real, but not if a migration hiccup drops our accept rate in the middle of the window your comp structure is measuring against. Let's capture the win cleanly."

Talking point 6 — Make sure the migration upside is in Mo's comp model

"One thing I want to flag for when the contract comes back from legal: the RPL lift from the form migration is a significant revenue gain that doesn't show up in the spend-based metrics. I want to make sure the comp structure captures net revenue improvement broadly, not just spend efficiency. We should align on that before the contract is signed."

ASSUMPTIONS & OPEN QUESTIONS

Assumptions:

1. The three "60%" Ad IDs cited (including 1004559982134492) are confirmed live as of May 13, 2026. The two additional "60%" variant IDs will be confirmed on Monday June 1 when account access is granted. If the ads have already been paused by Lauren independently, Actions 1–2 are compressed but the audit still runs.

2. The ~$33.52 RPL figure is net of all deductions (accept rate already applied). The May CSV leads_sold column showing all zeros means actual QW-reported accepted lead count and payout has not been reconciled against internal reporting. The $281,622 net revenue figure is treated as reliable (Hassan confirmed it matches his "$275K" claim). The implied ~25% accept rate is an estimate requiring confirmation from QW's affiliate dashboard.

3. A 20–30% RPL lift from multi-buyer ping-post is an industry benchmark, not a confirmed Iron Corp outcome. The actual lift will depend on buyer pool depth and lead quality scoring. The math in Part 6 should be treated as directional until a 2-week A/B test provides Iron Corp-specific data.

4. The QW contract contains standard affiliate agreement terms (non-exclusivity or limited exclusivity, 30–60 day termination notice). If the contract contains a longer exclusivity term or longer termination notice, the Phase 3 cutover date shifts accordingly.

5. The dev team has capacity to build the staging form in June/July without materially slowing the CAPI rebuild (Thread A). If dev capacity is constrained, the CAPI rebuild takes priority — it has faster compounding effect on the measurement window performance.

6. The FCC One-to-One Consent rule (effective January 27, 2025) applies to calls and texts initiated based on leads generated through the Military.com form. If Iron Corp's downstream buyers are limited to internet-delivery only (no calls/texts), the consent standard is different. Confirm with QW what downstream buyer contact methods are used.

Open questions:

1. QW contract: Does it exist in signed form? Who has it? What are the exclusivity and termination provisions? What does it say about ping-post? This is the highest-priority unknown.

2. Accept rate: What is the actual QW-reported accept rate on Iron Corp's May leads? The internal CSV shows zero in the leads_sold column — the real accept rate must come from the QW affiliate dashboard. This number is the denominator for all RPL calculations and the baseline against which the A/B test is measured.

3. QW affiliate contact: Who is the named relationship manager at QuoteWizard for the Iron Corp / Military.com account? Name and email needed for Action 5 and the eventual migration conversation.

4. Dev capacity: Can the dev team build the staging form in parallel with the CAPI rebuild, or does one block the other? What is the team size and current sprint commitment?

5. Current cert yield: Does the QW-hosted form currently fire Jornaya LeadiD and/or TrustedForm on submission? If yes, what is the cert yield rate? If no, this is an active compliance gap that predates the migration.

6. Current consent language: Exact verbatim text of the consent disclosure on the current QW-hosted form. Is it One-to-One compliant? Does it name Iron Corp / Military.com explicitly?

7. Buyer pool: If Tier 2 is contractually viable, which other insurance lead buyers would Iron Corp approach? SmartFinancial, EverQuote, Integrity, MediaAlpha, and Goosehead are the obvious candidates. Has Hassan or Rony's team had any prior relationships with these buyers through other Valnet properties?

8. Baseline lock: Mo has not yet seen March and April 2026 data. The comp model baseline should not be finalized until that historical data is reviewed. If April's run rate was significantly lower than May W1, Hassan's $275K baseline may be generous. If April was stronger than May's exit rate, Mo's comp position improves materially. Do not let Hassan lock the baseline before the historical pull is complete.

9. Counsel: Has Iron Corp / Valnet US used a TCPA-specialized compliance counsel previously? If there is an existing relationship, routing the consent language review through that counsel is faster than starting a new engagement. If not, Mo should have 1–2 referrals ready to provide at the Tuesday meeting.

June 2026 Strategy — Shared Context Brief

This is the current state as of May 30, 2026, the day Mo got account access agreement from Hassan Youssef (Valnet CEO). All agents producing June 2026 strategy work must align with this brief.

The deal (renegotiated, agreed in principle)

• Mo met Hassan Youssef (Valnet CEO) directly, not a GM. Hassan personally wrote the comp terms.
• Comp structure: base fee + % of growth above a baseline. Replaced Hassan's original "5K CAD base + capped goal-post bonus" after Mo pushed back.
• Baseline number is NOT locked. Mo negotiated the right to vet the baseline against past data. This is the highest-leverage open item.
• Term: 90-day pilot (June-Aug 2026), with goal-post check on the July/Aug 60-day run rate average.
• Currency: Mo's fee is USD; revenue model is USD.
• Hassan's growth model (his proposed targets): Baseline grows June→Dec from $275K → $451K (+64% organic). Goal posts: GP1 +15% over baseline, GP2 +36%, GP3 +57%. These are Hassan's projections, not vetted.

Hassan's email next steps (in writing)

1. Account access shared Monday June 1
2. Office visit Tuesday June 2 (intro to Lauren — in-house media buyer — and dev team)
3. Valnet finance/legal drafting contract
4. Initial focus areas: - Account audit + quick wins with Lauren and dev - Build creative pipeline / engine for rapid testing - Second priority: Switch from QuoteWizard hosted form to own form - Optimize/customize lead form for Meta

Key people

• Hassan Youssef — Valnet CEO. Programmatic arbitrage native, "only metric is making more money," litigious (Valnet sued TheWrap $64.5M April 2025), pattern of in-housing what works. Likes Mo personally. Treat as operator-to-operator.
• Rony Arzoumanian — Valnet Head of M&A, President of Iron Corp US Inc. Running Military.com day-to-day per CJR.
• Lauren — In-house media buyer Mo will coordinate with. Critical relationship — augment, don't replace.
• Dev team — Owns the funnel, the form, the tracking. Coordination dependency.

May 2026 performance — the data that exists

CSV path: /Users/mo/Downloads/leadsReport_data2026-05-01_2026-05-30.csv

Headline: May totaled $281,622 net revenue (matches Hassan's "$275K" claim).

The story behind the headline (this is the whole game):

• Net per lead collapsed ~88% from W1 to last 2 days.
• May exit run rate: ~$87K/month (extrapolating last week).
• CPL +30%, RPL −10% inside the same 30 days.
• Memorial Day weekend (May 23–25) was devastating: $80K spent, ~$0 net.
• Auto fatigued; HOME GREW. Home rev went from <$1K/day (May 1–7) → $3–5K/day by mid-month. Home ROAS (1.36) slightly better than auto (1.33).
• Spend over-scaled through Week 3 — $24K/day → $36K/day on the same ~10 concepts.
• leads_sold, lead_revenue columns are all zeros in the file — meaning the QuoteWizard accept-rate/sold-lead data is NOT flowing into the internal report. Value-blind optimization.

Data Mo has + has not yet

• ✅ May 2026 daily (the file above)
• ⏳ March + April 2026 — Hassan said internal tool has it, will send. Easy pull.
• ⏳ Pre-March 2026 (July 2025–Feb 2026) — not in internal tool, Mo will pull from Meta + QuoteWizard himself starting Monday
• ❌ QuoteWizard accept-rate / sold-lead / payout-per-lead data — needed urgently to fix value-blind optimization
• ❌ Campaign / ad-set / ad-level breakdown — Monday access
• ❌ Audience-level data — Monday access

Existing GTW deliverables (built May 13)

Located in /Users/mo/Desktop/military.com/deliverables/:

• 01_proposal_final.md — original three-thread pilot proposal
• 02_compliance_one_pager.md — verified 60% vs 15% (real Ad IDs)
• 02b_compliance_mini_binder.md — deep compliance analysis
• 03_recruitment_buyer_table.md — Thread C buyer table
• 04_creative_concept_mockups.md — Anduril / GE Vernova / Helmets-to-Hardhats concepts
• 05_audit_visual_spec.md — ad library audit findings
• 06_sow.md — signature-ready SOW
• 07_competitive_teardown.md — EverQuote/Zebra/Insurify/SmartFinancial teardown
• 08_stress_test_memo.md — red-team risk register
• 09_meeting_day_package.md — meeting playbook
• 10_verified_research_2026-05-13.md — Perplexity-verified facts (ad library, GE Vernova 96%)
• _context_external_research_pack.md — ground truth on Valnet, compliance, etc.

Original GTW research files in /Users/mo/Desktop/military.com/: - military research.md — strategic memo (parent co., funnel teardown, benchmarks, compliance) - military2.md, military3.md — pitch evolutions - military_proposal.md — original proposal

The bet for June

June is the RAMP month. July-Aug is the MEASUREMENT window (60-day run rate vs goal posts).

• Without intervention, June probably lands $100–150K net (May exit pace + some Memorial Day recovery). That's a disaster for Hassan and a humiliation for Mo.
• With quick wins (creative refresh, pacing, scale home), June can recover to $220–300K.
• With full execution (quick wins + CAPI rebuild + audience work + new creative engine), June can push $300–380K — setting up July-Aug to hit GP1/GP2.
• GP3 territory requires the QW form migration's margin lift, which is risky to land inside the measurement window.

Hard rules for every June deliverable

1. Don't break what's working. Take over carefully. The single worst outcome is Mo being the reason performance gets WORSE in June.
2. Show momentum fast. Hassan needs visible wins in the first 2 weeks or trust erodes. Daily dollar-impact reporting is non-negotiable.
3. Sequence the form migration AFTER the measurement window. Do not let cutover risk land in July/Aug.
4. Protect Mo's negotiating position on baseline. Don't telegraph baseline arguments before the historical data confirms them.
5. Augment Lauren and the dev team — never threaten them. Credit through them. Mo is the operator with the playbook; they are the people who actually push the buttons.
6. Keep War Room infrastructure proprietary. Deliverables = outputs, not playbooks. Hassan's pattern is to in-house what works.

Output rules

• Markdown only
• End every deliverable with ASSUMPTIONS & OPEN QUESTIONS
• Be concrete: specific actions, specific owners, specific weeks
• Tie back to dollar impact wherever possible
• Don't restate this brief; use it