The lifecycle engine that converts paid-acquired traffic and organic discovery into booked consults, signed contracts, retained customers, and reviews. Built on the Klaviyo Marketing Mix Report 2025 finding that owned channels (email + SMS) drive 28% of total revenue for mature DTC brands at a marginal cost of $0.0014 per send — a 60× efficiency edge over paid acquisition once the list and flow library are operational. Twelve checklist items deliver a deployment-ready system: nine named Klaviyo flows specified down to subject lines, a segmentation matrix, a lead-scoring algorithm, an inter-functional data contract, lifecycle metrics, email templates, SMS strategy, suppression rules, deliverability protection, personalisation rules, a prioritised A/B test backlog, and failure modes.
Five rules govern every flow, segment, and test in the CRM stack. These rules are non-negotiable: if a piece of automation violates one of them, it must be re-engineered before launch. They emerge from Klaviyo's 2025 benchmark of 15,000+ accounts, Drift's conversational-marketing data, and Balfour-style growth loops applied to a high-AOV ($18K-95K) home-services portfolio.
Klaviyo benchmarks show flows generate 3.4× the revenue per sendof broadcast campaigns. YDT must complete all nine flows before sending a single newsletter. A broadcast list with no flow library is a leaky bucket.
Every flow trigger must reference a behaviour event (form submit, page view, quote sent, build milestone) — never a calendar date. Drift's data shows behaviour-triggered email opens at 42% versus 19% for calendar-based "drip" sequences. Calendar drips create unsubscribes.
No flow ships until its success metric is connected to a downstream business outcome: booked consult, contract signed, expansion job, or 5-star review. Open rate alone is a vanity metric. Revenue per recipient (RPR)and flow-to-booking conversion are the only measures that count.
The same household that bought termite damage repair this year is the prospect for a pool renovation in three years and a kitchen renovation in five. The CRM is the asset that monetises this. Every flow must consider cross-LOB next-best-offer (NBO) at the appropriate lifecycle moment — never spammy, always contextual (Balfour growth-loop principle).
A list that emails everyone equally is a list on a path to spam-folder jail. Suppression rules (CR-08) protect deliverability and brand reputation. Klaviyo's deliverability scoring penalises high-complaint, low-engagement sends within 72 hours. Aggressive suppression is the price of being able to email anyone at all.
CRM lifecycle is the highest-leverage place in the portfolio to live out the upstream contracts. Persona (WS-04): every email is written toSarah & Mark · The Established SEQ Homeowner — never to a generic list.Category (WS-01): every nurture email reinforces theWhole-of-Home Stewardship frame and the custodian-not-tradespersonpositioning. Promise (WS-02): "Built like it's our own home"is the closing line of every Welcome (CR-01a) final email, every Post-Sale Onboarding (CR-01f) handover, and every Review Request (CR-01h). Economics (WS-05): the 30× cross-LOB LTV ratio is what justifies the investment in nine named flows for a "small" home-services brand — the second-LOB conversion alone recovers the full CRM build. KPI (WS-11): every flow has F1/F2/F3 tagging on each send and MEDDPICC scoring updates on each engagement, so the CRM is a measurement engine, not just an email tool. All three LOBs are explicit: Termite (55% of mix · reactive trigger flows), Pools (30% · longer consideration-cycle flows), Unit Renovations (15% · investor-segment flows).
This document does not invent strategy. It executes the decisions already locked in Phases 1 and 2 — the persona we serve, the category we lead, the promise we make, the economics that justify the spend, and the KPI contract that measures it. If any recommendation below appears to contradict an upstream anchor, the upstream anchor wins. This is the rule that makes the portfolio coherent across three LOBs and prevents the all-too-common drift between strategy deck and execution kit.
The Established SEQ Homeowner. 42–58, owner-occupier or 2–4-property investor, $1.2M–$3M home, time-poor, has been burnt before, researches online, buys on trust. Every line below is written to them, not to a generic audience.
View WS-04 JTBD →The category YMT designs and leads. Enemy: the transactional trades market. Lexicon: stewardship · custodian · sleep at night · built like our own home. Every page, ad, email below reinforces this category frame.
View WS-01 Category →The portfolio brand promise. Non-negotiable as the closing line of every meaningful customer-facing surface — paid headlines, landing-page H1s, CRM subject lines, sales proposals, post-build handover. One brand. Three LOBs. One promise.
View WS-02 Brand →Cross-LOB 10-year customer LTV is ~30× first-job revenue. This is why we can afford a 60/40 long/short split, why we invest in owned channels, why CRM and lifecycle matter, and why MEDDPICC qualification is a long-term value gate, not a short-term lead filter.
View WS-05 Bowtie →The single shared funnel language. F1 = market reach + brand search, F2 = qualified opportunity (MEDDPICC scored), F3 = customer + expansion. MMM as the truth-check. Every KPI cited below maps to an F-stage or to a MEDDPICC criterion.
View WS-11 KPI Contract →The single highest-ROI flow in the Klaviyo benchmark: 11.7% conversion rate and $4.31 revenue per recipient at the 90th percentile for considered-purchase home services. This flow runs once per contact, sets brand expectation, and gates every downstream segment.
The flow that intercepts high-intent prospects who visited a service-page bottom-funnel URL (e.g. /termite-damage-repair, /pool-renovation-cost,/unit-renovation-process) but did not submit a form. Triggered only on identified contacts (already on the list). Klaviyo's data shows 4.2× conversion lift when this flow is operational versus relying on retargeting alone.
The longest flow in the stack — 28 days, 7 emails, 2 SMS. Triggered when a prospect submits the quote-request form but has not yet booked the discovery call. This is the highest-CPL acquisition cost moment to lose; lead-nurture flows lift booking conversion from a baseline of ~22% to 41-58% per Drift's 2024 benchmark for considered-purchase home services.
Triggered the moment a discovery call is booked. Goal: maximise show-up rate (industry average 67%; YMT target 88%), prepare both sides for a productive conversation, and pre-set the tone of the relationship. Drift benchmark: structured pre-meeting flows lift show-up rate 14 points and shorten time-to-quote by 2.3 days.
Triggered immediately after the discovery call is marked complete. Goal: get the scoped proposal in front of the prospect within 72 hours, answer the unspoken objections that emerged in the call, and convert from proposal to signed contract. Klaviyo data: 14-day post-consult cadence converts at 47% versus 19% baseline for single-touch quote delivery.
Triggered the moment the contract is signed. Goal: convert the anxious post-purchase "did I make the right decision?" moment into confident, advocacy-ready commitment. Bond Brand Loyalty 2024: structured 14-day post-purchase onboarding lifts customer lifetime value by 31% and post-build NPS by 18 points.
Active during construction. Goal: maintain communication cadence, reduce inbound "where are we?" support load, surface change-order moments early, and build the story that will drive review-request conversion at completion. Drift Conversational Marketing 2024: builds with ≥ weekly proactive update cadence drive 41% more 5-star reviews than those without.
Triggered at practical completion. Goal: convert satisfied customers into public reviews on Google Business Profile, Houzz, and ProductReview.com.au — the three platforms that compound WS-08 GEO/AEO authority. Klaviyo benchmark for considered- purchase home services: structured 21-day review-request flow lifts review conversion from 8% (organic) to 34-41%.
The portfolio's compounding-value flow. Triggered for two distinct populations: (a) lost prospects who declined a quote 90+ days ago, and (b) past customers who completed a build 18+ months ago. Goal: reignite consideration at the moment they are likely re-evaluating — and, critically, offer a cross-LOB next-best-action when the original LOB is not the current need. This is the Balfour growth loop applied to a multi-LOB home-services portfolio.
The segmentation matrix is the foundation under every flow. Without it, the nine flows above cannot target accurately and personalisation rules (CR-10) have nothing to lean on. We use a four-dimensional segment model — RFM × Lifecycle Stage × LOB × Lead Source — generating a finite, manageable set of high-fidelity segments rather than the thousands of low-signal segments that paralyse most CRMs.
| Tier | Recency | Frequency | Monetary (LTV) | Population % |
|---|---|---|---|---|
| Champions | < 6 months | 2+ projects | > $80K | 4-7% |
| Loyal | < 12 months | 1 project | $20K-$80K | 18-24% |
| At-Risk | 12-24 months | 1 project | $20K-$80K | 14-18% |
| Hibernating | > 24 months | 1 project | any | 22-31% |
| New Prospect | n/a | 0 projects | $0 | 30-42% |
| Segment Name | Definition | Used By |
|---|---|---|
| SEG-01 New-Prospect-TDR-PaidSearch | RFM: New · Stage: Cold · LOB: TDR-primary · Source: Paid-Search | Welcome Flow, Browse Abandon |
| SEG-02 Quote-Requested-POE-Organic | Stage: Quote-Requested · LOB: POE · Source: Organic | Lead Nurture (CR-01c) |
| SEG-03 At-Risk-UR-Past-Customer | RFM: At-Risk · LOB: UR · Stage: Past-Customer · Source: any | Win-Back Track B (CR-01i) |
| SEG-04 Champion-Multi-LOB | RFM: Champion · LOB: Multi-LOB · Stage: any post-build | Quarterly advocate cadence + cross-LOB referral |
| SEG-05 Hibernating-Any-Source-No-NPS | RFM: Hibernating · NPS not captured | NPS re-survey + Win-Back Track B alternate entry |
| SEG-06 Proposal-Sent-No-Decision-72h | Stage: Proposal-Sent · > 72h · No e-sign · No "lost" tag | CR-01e Email 03 reference unlock + manual call alert |
| SEG-07 Detractor-Any-LOB | NPS 0-6 captured in last 90 days · suppressed from review request | PM personal follow-up · suppressed from broadcast |
| SEG-08 Active-Build-Week-N | Stage: Active-Build · current week of build (1-26) | Build-in-Progress weekly status routing |
Total segments in active use: 32-38 (driven by combinations of the four dimensions). Segments are reviewed monthly — any segment with population < 50 contacts is collapsed into a parent segment to avoid statistical noise per Klaviyo's minimum-viable-segment guidance.
The lead-scoring algorithm decides who YDT's account managers call versus who stays in self-serve flows. Without it, manual outreach time is allocated by gut instinct — the worst possible allocation mechanism. The model below is calibrated to YMT's AOV of $18K-95K and the operational constraint of 1 PM hour per booked consult; MQL threshold is set so monthly MQL volume matches PM capacity.
| Behaviour | Points | Half-life |
|---|---|---|
| Email opened | +1 | 14 days |
| Email clicked (any link) | +3 | 21 days |
| Page viewed: blog/content | +1 | 14 days |
| Page viewed: service page (TDR/POE/UR) | +5 | 30 days |
| Page viewed: cost/pricing page | +10 | 30 days |
| Page viewed: case-study page | +4 | 30 days |
| Form submit: newsletter | +3 | permanent |
| Form submit: download (lead magnet) | +8 | permanent |
| Form submit: quote request | +40 | permanent (triggers MQL re-evaluation) |
| Calendar booking made | +50 | permanent (triggers SQL) |
| SMS opt-in | +5 | permanent |
| Replied to email (any inbox reply) | +15 | 21 days |
| Watched ≥ 75% of YouTube video | +6 | 30 days |
| Referred by an existing customer | +25 | permanent |
| Behaviour | Points |
|---|---|
| Email unopened across 4+ consecutive sends | −5 |
| Email marked as spam | −40 (auto-suppress per CR-08) |
| Unsubscribed from one preference category | −10 |
| SMS opt-out | −10 |
| No engagement event for 90 days | −15 |
| Bounce (soft, repeated) | −5 per bounce after 3 |
| Score Band | Tier | Routing |
|---|---|---|
| 0-9 | Cold | Self-serve flows only · no manual outreach · monthly broadcast eligible |
| 10-24 | Warm | Behaviour-triggered flows · automated personalisation · no PM time yet |
| 25-49 | MQL | YDT account manager outreach within 48h · LOB-specific call script |
| 50-89 | SQL | PM-direct outreach within 24h · scoped quote priority queue |
| 90+ | Hot | Carla escalation · same-day call · > $75K AOV likely |
The CRM is the system of record. But the same contact moves through marketing (Klaviyo), estimating (the quoting tool — Buildxact or similar), and finance (Xero). Without an explicit data contract, fields drift, attribution breaks, and lifetime value calculations become guesswork. This contract enumerates every field that crosses a system boundary, who owns it, when it updates, and what the downstream system can rely on.
| Field | System of Origin | Klaviyo | Estimating | Finance (Xero) |
|---|---|---|---|---|
| Form submit | Primary key | Read-only | Read-only | |
| first_name / last_name | Form submit | Owner | Read-only | Owner (legal name) — overrides Klaviyo for invoicing |
| mobile | Form submit / discovery call | Owner | Read-only | Read-only |
| address_full | Discovery call | Read-only | Owner | Owner (registered office) |
| suburb / state / postcode | Form submit (suburb) → Estimating (full) | Read-write (suburb only) | Owner | Read-only |
| lob_primary | Form submit / Email 02 reply | Owner | Read-only | Read-only |
| lob_secondary | Estimating / cross-LOB Win-Back | Read-write | Owner | Read-only |
| budget_band | Discovery call | Read-only | Owner | Read-only |
| lead_score | Klaviyo calculation | Owner | Read-only | N/A |
| lifecycle_stage | Klaviyo (driven by events) | Owner | Read-only · drives Estimating priority queue | Read-only |
| lifecycle_substage | Estimating · custom statuses | Read-only | Owner | Read-only |
| quote_value | Estimating | Read-only · drives CR-01e routing | Owner | Read-only (until contract signed) |
| contract_value | Estimating · upon e-sign | Read-only | Owner | Owner (becomes invoiced amount) |
| build_status | Estimating / PM tracker | Read-only · drives Build-in-Progress flow | Owner | Read-only |
| build_complete_date | Estimating | Read-only · triggers Review Request | Owner | Owner (becomes final invoice trigger) |
| final_payment_received | Xero | Read-only · gates Review Request | Read-only | Owner |
| nps_score | Klaviyo (Email 01 of CR-01h) | Owner | Read-only · drives PM follow-up priority | Read-only |
| referral_source | Form submit / Discovery call | Owner | Read-only | Read-only (drives referral payouts) |
| customer_ltv | Finance roll-up (nightly) | Read-only · drives Champion segment | Read-only | Owner |
| warranty_expiry_date | Estimating · per LOB | Read-only · drives 18-month Win-Back | Owner | Read-only |
What gets measured drives what gets resourced. The lifecycle metric stack below is the contract between the CRM function and the CFO (Carla). It connects every flow to revenue, every segment to retention, and every customer to lifetime value — providing the operating board pack for the marketing function.
CLTV is the central financial metric tying the marketing function to YBMT portfolio strategy. The formula is intentionally simple at the customer level (sum of all signed contracts attributed to a single customer record) and sophisticated only at the cohort-rollup level (where channel-attribution decay and cross-LOB lift are modelled). The simpler customer-level formula prevents manipulation and aligns with Carla's CFO-grade requirement: every CLTV figure in a board pack must be reconcilable to Xero invoices within 5%.
Email design is not decoration; it is the visual implementation of the WS-02 brand system in every inbox interaction. Three templates cover 100% of YMT's outbound — each with explicit rules on what changes and what stays locked.
Use cases: Quote delivery (CR-01e Email 01), contract signed confirmation (CR-01f Email 01), build milestone events, payment receipts.
Use cases: Welcome series, lead nurture, browse abandon, post-consult, review request, win-back. All nine flows above default to this template.
Use cases: Monthly market update, seasonal LOB content (pre-summer pool tips, pre-winter termite advisory, autumn renovation timing).
SMS is a high-trust, high-attention channel — Klaviyo's 2025 data shows a 98% read rate within 3 minutes — and therefore must be used sparingly to retain that trust. Aggressive SMS strategies that work in DTC retail (4-6 sends per week) are catastrophic for considered-purchase home services where SMS opt-out can damage the entire relationship. The rule: SMS is for time-sensitive coordination, not promotion.
SMS opt-in is captured only at quote-request and discovery-booking forms — never at lower-intent capture points. Double opt-in (Welcome SMS 01 reply YES) is required before SMS frequency cap unlocks beyond 1 per 14 days. ACMA-compliant unsubscribe via REPLY STOP processed instantly.
Suppression is the cost of being allowed to email at all. Klaviyo's deliverability algorithm — and the spam filters at Gmail, Outlook, and Apple Mail — penalise senders who continue to send to low-engagement contacts. Aggressive suppression protects every other contact's deliverability. The seven rules below are non- negotiable; YDT operates them automatically inside Klaviyo.
Suppressed permanently from the first hard bounce. No retry. The address is invalid; sending again damages sender reputation. Klaviyo handles this automatically.
Suppressed for 90 days, then a single re-validation email. If that bounces, permanent suppression. Soft bounces often indicate mailbox-full or temporary issues, hence the recovery path.
Suppressed permanently. Suppress within 60 seconds of the complaint webhook. This is the most damaging signal to deliverability — one complaint per thousand sends is the Gmail tolerance ceiling.
Suppressed from broadcast and nurture flows. Eligible for a single sunset email ("Are you still here? Reply YES to stay") at day 120. If no reply within 14 days, suppressed for 180 days. This is the largest single deliverability protector.
Suppressed permanently from the unsubscribed channel (email or SMS). Preference-centre unsubscribe is per-category (broadcasts vs flows vs transactional) — transactional emails (quote delivery, payment receipts) survive any unsubscribe per ACMA-permitted exemptions.
Suppressed from review-request flow only (CR-01h). Not suppressed from other flows. The rule prevents asking unhappy customers for public reviews — which is both ethically right and protective of platform reputation.
Suppressed from broadcast and win-back flows for the duration of an active build + 30 days. The customer is receiving 1-2 PM updates per week already; additional marketing email damages the relationship and the trust the PM is building.
Deliverability is the foundation under every other metric in this manual. If emails don't reach the inbox, no flow converts, no segment matters, no test runs. Three workstreams own deliverability: sending-domain warmup, ongoing list hygiene, and content/structure spam-trigger avoidance.
mail.ymtgroup.com.au — never the root domain. Protects the corporate domain from any spam-folder risk.p=none for week 1-2 monitoring, escalates to p=quarantine by week 4, and p=reject by month 3.Personalisation is only an asset when it is accurate. Inaccurate personalisation — "Hi {first_name|default:there}" — actively damages trust. The rule is: only use a personalisation token if the underlying data is verified, and gracefully degrade when not. The schedule below tells YDT exactly where each token can be used and what the fallback is when data is missing.
| Token | Where used | Fallback | Confidence threshold |
|---|---|---|---|
first_name | All emails greeting, SMS opener | "Hi there" | Email-validated form submit only |
suburb | Browse Abandon Email 02 (case-studies-near-you), Lead Nurture Email 04, Win-Back Track B | "in your area" / soft generic | Validated against Australia Post API or self-declared in form |
lob_primary | Welcome Email 03 (LOB branch), Browse Abandon, Lead Nurture, all post-sale flows | n/a — gate the email instead | Self-declared OR Klaviyo Viewed Product event on 2+ LOB pages |
pm_first_name | Pre-meeting Email 03, Post-Sale Onboarding, Build-in-Progress, Review Request | "your project manager" | Set manually by Estimating when assigned |
project_scope_summary | CR-01e (Post-Consult) emails 01 and 02 | n/a — gate the email instead | Populated by PM in CRM during/after discovery call |
quote_value | CR-01e Email 04 ("X-dollar quote awaiting your decision") only when band > $50K | "your quote" | Estimating field, real-time webhook |
last_engagement_date | Win-Back Track A Email 01 ("Three months on...") | "a while back" | Klaviyo native field |
warranty_expiry_date | Win-Back Track B Email 01 | n/a — gate the email instead | Set by Estimating per LOB warranty terms |
recent_case_studies | Lead Nurture Email 04, Browse Abandon Email 02 | Generic top-3 case studies fallback | 3 case studies within 8km of suburb token; falls back to LOB-only if fewer than 2 within range |
build_status | Build-in-Progress weekly status (template variable) | n/a — gate the email instead | Set by PM in tracker |
The "gate the email" principle: When the data is not available to support meaningful personalisation, the correct response is to not send the email — not to send a generic version with awkward fallback. The schedule above tagged "gate the email instead" means the flow waits for the data, exits the contact from the flow, or routes to a different, more generic email entirely.
A test backlog turns CRM into a learning function rather than a static system. The twelve tests below are sequenced by expected lift × ease of execution × statistical detectability. Each is sized to reach 95% confidence within ≤ 4 weeks at YMT's send volume. YDT runs one at a time within each flow (parallel tests across flows are permitted) to avoid contamination.
Hypothesis: founder-signed lifts open + click 25%+. Variables: from name, signature block. Sample size: 4 weeks at ~600 new subs/wk = 2,400. Detectable lift: 4pp difference in click. Decision: keep winner, reroll loser to graveyard.
"Still thinking about [topic]?" vs. "[Topic] typically costs $X-$Y." Hypothesis: cost-led wins open rate but question-led wins click. Decision logic: optimise for click (closer to revenue).
Three pre-selected slots (1-click confirm) vs. full Calendly. Hypothesis: pre-selected wins by friction reduction. Decision: 4-week test, winner becomes default.
Three buttons (sign / need-time / lost) vs. single CTA + reply prompts. Hypothesis: three buttons lifts decision-capture rate by 30pp because it normalises "no".
Opt-in checkbox shown at discovery-call form only vs. both forms. Hypothesis: limiting to higher-intent moment improves SMS engagement quality.
One open prompt vs. three structured prompts. Hypothesis: three structured prompts lift review length by 3× per Bond data — confirm in YMT's cohort.
When to surface the cross-LOB pivot. Hypothesis: Email 03 wins because contact has been re-warmed; Email 01 feels like bait-and-switch.
Calibration test. Hypothesis: threshold of 25 maximises booked-consult-per-PM-hour. Test by routing 33% of contacts to each threshold for 6 weeks, measure downstream conversion.
Day-of-week test. Hypothesis: Friday wins because customers want closure-for-the-week; Monday loses because it competes with work-mode inbox triage.
Tonality test. Hypothesis: direct-stay-or-go lifts long-term list health but may lift unsubscribe in the short term. Decide by 90-day RPR of remaining cohort.
Hypothesis: surprise welcome pack lifts NPS materially; pre-announced lifts perceived value-for-money. Trade-off test.
Hypothesis: 18 months is the sweet spot where the original project has settled but the next project is becoming top-of-mind. Critical for portfolio CLTV — test budget approved.
Test governance: Each test must have a written hypothesis + minimum detectable effect (MDE) + decision criterion locked before launch. No "let's see what happens" tests — they waste sample and create noise. Test results enter the YMT learning log (a shared doc updated quarterly by YDT) so the CRM accumulates institutional learning rather than re-running the same tests every 18 months.
Every risk register below is paired with an explicit hedge. Hedges that depend on capabilities outside YDT's remit are escalated to Carla for resource decisions.
Webhook fails for > 1 hour → Build-in-Progress and Review Request flows stall, NPS collection breaks, lifecycle stage drifts.
One newsletter with poor subject line or wrong segment can spike spam complaints, drop sender reputation 15+ points in a week.
Weekly status emails are PM-written. Style varies wildly → some customers feel cared for, others abandoned.
NPS gate fails (data not captured, sync drift) → low-NPS customer asked for public review → bad review on Google.
Win-Back Track B surfaces POE to a customer who is talking to YMT directly about a TDR issue → confusing, can lose both.
Imported list (e.g. from acquisition or trade show) hits an unwarmed segment → high complaint rate → Klaviyo throttles or suspends.
Token rendering bug or data missing → "Hi {first_name}" goes out raw → trust damaged.
YDT lead leaves → tribal knowledge of segment definitions, test history, flow logic lost.
WS-10 does not stand alone. Six explicit handshakes connect this CRM manual to the rest of DOC 3. If any of these connections breaks, the lifecycle engine starts running on stale data or wrong assumptions.
Every contact arrives with a lead_source tag set by the channel layer (WS-06 source taxonomy). The CRM segment matrix (CR-02 Dimension 4) reuses these tags exactly — same naming, same definitions. No translation layer.
The 80-piece content map (WS-08) is the asset library for every flow's CTAs. Welcome Email 03, Browse Abandon Email 02, Lead Nurture Email 04, Win-Back Track A Email 02 all link to WS-08 GEO content. The CRM stack does not produce new content — it deploys existing.
WS-09 PM-11 specifies the offline conversion workflow. CRM provides the truth events (form_submit, calendar_book, contract_sign, build_complete) back to Google Ads + Meta + LinkedIn — the data that turns paid platforms from "click optimisation" into "revenue optimisation".
The three email templates (CR-06) implement the WS-02 brand system exactly: Navy/Timber/Aqua/Cream palette, Fraunces + Inter typography, founder-signed voice rules. No template variation permitted that contradicts WS-02.
The CRM lifecycle stages (CR-02 Dimension 2) map 1:1 to the WS-05 bowtie funnel: Cold subscriber → Quote-Requested = left lobe; Consult-Booked → Active-Build = neck of bow; Past-Customer → Multi-LOB = right lobe (expansion). Same model, same names.
CR-05's eight lifecycle metrics feed directly into the WS-11 KPI contract. Email LTV, Cross-LOB rate, Retention curves, NPS-by-stage are not separate marketing measures — they are line items in the same CFO board pack that tracks revenue and gross margin.
All marketing email and SMS comply with the Spam Act: clear sender identification, functional unsubscribe processed within 5 business days (YMT processes within 60 seconds via Klaviyo), explicit consent at capture. Transactional emails (quote, contract, build coordination) operate under the inferred-consent exemption.
Privacy collection notice on every form. Personal information stored in Klaviyo (EU + US regions) under EU SCCs. Data retention: contacts not engaged for 36 months are archived (not retained for marketing). Right-to-erasure requests processed within 30 days per APP 13.
SMS opt-in is double-confirmed before frequency cap unlocks. All SMS sends include sender identifier and REPLY STOP unsubscribe. Sends only 9am-7pm local time. Premium-rate SMS never used.
No purchased lists. No imported contacts without verifiable opt-in. Sender reputation monitored weekly via Klaviyo Deliverability Hub. Any complaint rate spike triggers immediate broadcast pause + forensic review.
Warranty terms surfaced in CR-01f Email 03 (welcome pack) and CR-01i Track B Email 01. No marketing claim contradicts the contractual warranty. Reviews requested only from contracts that have reached final-payment-received status (CR-01h Critical Filter).
YDT operates the Klaviyo account on YMT's behalf with: weekly metric review, monthly flow performance report, quarterly playbook update, and 4-hour emergency response for deliverability or compliance incidents. Named cross-trained backup required at YDT to hedge key-person risk (CR-12 Risk 08).