Playbooks vs app shopping
Buying Klaviyo because a competitor uses Klaviyo is not strategy. A use-case playbook answers: when this moment fires, which stack layer owns it, what suppressions apply, which metrics prove incrementality, and which mistakes burn list health. The playbooks on this site assume a six-layer marketing stack — capture (Privy, Justuno), lifecycle (Sequenzy), SMS (Postscript, Omnisend), proof (Yotpo), loyalty (Marsello), analytics (Shopify reconciliation) — with roles that change weight by playbook.
Welcome series is a capture-to-lifecycle handoff: source tags from Privy must branch welcome within five minutes. Abandoned cart is lifecycle + SMS with inventory checks and offer caps. Reviews and UGC is proof layer feeding browse and post-purchase modules. Loyalty is points orchestration with promotional collision rules. Black Friday and holiday gifting are seasonal governance problems spanning every layer simultaneously.
Implementation order that does not break lists
Phase 1 — Foundation: popup-to-email handoff, welcome series, post-purchase education. Fix consent mapping and source branches. No winback discounts yet.
Phase 2 — Recovery: abandoned cart, browse abandonment with proof before discount. Add Postscript branch after email silence if opt-in supports it.
Phase 3 — Retention: replenishment by SKU consumption, VIP segments, loyalty enrollment on second order. Subscription sync if applicable.
Phase 4 — Reactivation & peak: winback with proof-first branches, segmentation audits, Black Friday and holiday gifting with published collision calendar.
Skipping phases trains discount dependency and list fatigue. Merchants who launch winback before welcome branches exist wonder why unsubscribe spikes — the stack was never layered, only stacked.
Playbook categories
Acquisition & conversion: welcome series, abandoned cart, browse abandonment, product launch, back-in-stock.
Post-purchase & retention: post-purchase education, replenishment, loyalty campaigns, VIP segments, reviews and UGC.
Reactivation: winback campaigns with holdout testing discipline.
Governance & infrastructure: segmentation, discount strategy, email design, deliverability, revenue analytics.
Seasonal: Black Friday, holiday gifting — require collision calendar from cross-channel coordination guide.
Stack coordination rules every playbook shares
One offer per intent window across capture, email, SMS, and loyalty. Subscription and replenishment states suppress conflicting promos. Wholesale and gift buyers branch separately. Margin after discounts is the success metric — not attributed revenue alone. Holdout tests on winback and replenishment quarterly. Sunset unengaged before peak season. Document live flows with trigger, delay, branch, and suppression rows — if it is not documented, it does not exist when your agency turns over.
Recently expanded playbooks
Welcome series, email design, loyalty, holiday gifting, and winback playbooks include full stack layer maps, merchant scenarios across verticals, twelve-point checklists, and twelve FAQs each — rewritten for marketing-stack coordination rather than single-channel email advice.
Vertical-specific playbook notes
Fashion: product launch and back-in-stock pair with Privy waitlists. Beauty and supplements: replenishment suppresses Recharge actives. Jewelry and high-AOV: browse abandonment leads with proof not discount. B2B: welcome and winback require wholesale tag exclusions. Subscription boxes: replenishment playbook overlaps skip recovery — read subscription-boxes vertical guide first.
Deliverability and design as stack infrastructure
Email design playbook treats templates as the presentation layer for Yotpo, Marsello, and Privy data modules. Deliverability playbook is prerequisite before scaling BFCM volume — sunset and authentication matter more than another promotional template variant.
Playbook ownership matrix
Assign one owner per playbook family: acquisition (welcome, launch, back-in-stock), recovery (cart, browse), retention (post-purchase, replenishment, loyalty, VIP), reactivation (winback), infrastructure (segmentation, discount, design, deliverability, analytics), seasonal (BFCM, gifting). Owners publish timing changes to shared collision doc. No owner means no send changes during peak — ad hoc edits cause incidents.
Playbooks interact: welcome source tags affect browse segmentation; replenishment suppressions affect winback; loyalty affects discount strategy; holiday gifting pauses replenishment for gift-tagged profiles. Read related playbook links at bottom of each expanded page — welcome links post-purchase; winback links replenishment exclusions; loyalty links VIP and discount strategy.
Expanded playbook set (marketing-stack rewrite)
All eighteen playbooks now use stack-coordination architecture: capture state, lifecycle execution, SMS urgency, proof modules, loyalty enrollment, and analytics measurement — not generic "command center" filler. Each includes stack layer maps, vertical scenarios, checklists, timing governance, and twelve FAQs. Duplicated template paragraphs and identical week-by-week sprint copy were removed.
Playbook quick-picks by commercial leak
Weak first purchase: welcome series + discount strategy + popup handoff guide.
Cart leakage: abandoned cart + browse abandonment + reviews/UGC proof.
Weak repeat: replenishment + post-purchase + loyalty + VIP segments.
Lapsed buyers: winback with holdout + segmentation refresh.
Peak season: Black Friday + holiday gifting + deliverability + list hygiene.
Blind reporting: analytics + discount strategy + attribution guide.
Stack layers referenced in every playbook
Capture (Privy, Justuno) → Lifecycle (Sequenzy) → SMS (Postscript, Omnisend) → Proof (Yotpo) → Loyalty (Marsello) → Analytics (Shopify reconcile). Each expanded playbook maps which layers participate, failure modes per layer, and operator tests — not generic ESP feature lists.
Metrics hierarchy across playbooks
Every playbook lists primary metric (incremental margin or category-specific conversion), guardrail metrics (unsubscribe, opt-out, discount dependency), and stack cost allocation. Welcome measures first purchase 14d; cart measures recovery margin not rate alone; replenishment measures full-price reorder; winback requires holdout incrementality; loyalty measures enrolled LTV delta; analytics playbook defines finance reconciliation cadence. Without hierarchy, teams optimize local platform metrics that sum to negative margin.
Playbook documentation standard
Each playbook page in this hub now ships with full static content: hero stack positioning, TLDR tool picks, merchant scenarios across verticals, twelve-point checklists, stack layer maps with failure modes, timing governance, measurement frameworks, tool reviews with vertical-specific paragraphs, and twelve FAQs. Content is written for marketing-stack coordination — Privy capture tags feeding Sequenzy lifecycle, Yotpo proof in browse and post-purchase, Postscript SMS after email silence, Marsello loyalty with promo suppressions.
When implementing a playbook, export a one-page runbook: trigger, delay, branch keys, suppression list, max offer depth, owner name, and primary metric. Attach collision calendar row before enabling SMS or loyalty branches. Reconcile Shopify net sales weekly — if platform attributed revenue exceeds Shopify orders by more than your tolerance, pause promotional experiments and audit duplicate sends across layers.
Stack maturity and playbook unlock order
Level 1 merchants run welcome and cart only — acceptable if capture handoff is documented. Level 2 adds post-purchase, browse, and proof modules. Level 3 adds replenishment, VIP, and loyalty with holdout discipline. Level 4 runs winback, BFCM, and holiday gifting with published collision calendar and finance-signed attribution. Attempting Level 4 playbooks without Level 1 suppressions causes list fatigue and margin collapse — the playbooks assume governance exists even when recommending aggressive recovery tactics.
Pair every playbook with a store-type guide when vertical rules matter: supplement compliance on welcome, jewelry gift branching on post-purchase, B2B wholesale exclusions on winback, Recharge suppressions on replenishment. Generic playbook logic fails when subscription status, gift buyer tags, or MOQ account flags are ignored.
Tool review sections on each playbook
Every expanded playbook includes tool reviews for the specialists that execute that moment — Sequenzy for lifecycle orchestration, Privy for capture handoff, Klaviyo for segmentation depth, Omnisend for SMB speed, Postscript for SMS branches, Yotpo for proof modules. Reviews are playbook-specific paragraphs, not generic app marketing copy. Use them to decide which layer to upgrade when a playbook metric misses — not to add redundant tools.
Start here if overwhelmed
Open welcome series, then post-purchase, then abandoned cart. Fix capture handoff and collision calendar before winback or BFCM. Each linked playbook page is two thousand plus words of static stack guidance — read one per week, implement one deliverable per week, reconcile Shopify margin before adding the next.