- Analyze the Request:
- Product/Service: "Wedding Planner Crisis Playbook"
- Format: Markdown (headings, short paragraphs, bullet lists)
- Goal: email_signups
- Key Plan Elements:
- Publish free 'Wedding Crisis Checklist' as a gated blog post on owned site
- Promote via SEO keywords, Facebook groups, Instagram bio, partner newsletters
- Refresh checklist quarterly, A/B test lead magnet titles, track email metrics, iterate based on survey feedback
- Constraints:
- Be honest and specific about what it is and who it's for
- No fake testimonials, numbers, or claims
- Don't invent prices, links, or payment buttons
- Meta info: venture, stage, task (seems like internal tracking, I'll ignore or just note)
- Deconstruct the Offering:
- It's a free resource (priceUsd: 0)
- Called "Wedding Planner Crisis Playbook" / "Wedding Crisis Checklist"
- Target audience: Wedding planners (likely freelance, new, or those wanting to systematize emergency handling)
- Core value: Emergency protocols, vendor failures, day-of crisis management, checklists
- Lead generation goal: Email signups
- Distribution: SEO, social groups, newsletters
- Ongoing maintenance: Quarterly refreshes, A/B testing, feedback loops
- Drafting - Section by Section (Mental Outline):
- Headline/H1: Clear, compelling, honest
- Subhead/Explanation: What it is, who it's for
- What's Inside: Bullet list of crisis scenarios (honest, no fake numbers)
- Who It's For: Specific audience description
- How to Get It: Gate - email signup required, no price, just sign up
- Promise/Process: Quarterly updates, no spam, etc.
- Promotion/SEO mention: Maybe subtle, or just describe the resource
- Keep it markdown format with headings, short paragraphs, bullet lists
- Refining Content - Honesty & Specificity Check:
- What is it? A free digital checklist/playbook for wedding planners to handle common crises (vendor no-shows, weather, timeline breaks, etc.)
- Who is for? Wedding planners (freelance, aspiring, or those wanting better emergency protocols)
- No fake testimonials, no made-up stats
- Price: $0 (free)
- Gate: Email required
- Maintenance: Quarterly refreshes, A/B testing of titles, open/click tracking, subscriber surveys
- Distribution: SEO, Facebook groups, Instagram, partner newsletters (I can mention these as promotion channels without linking/inventing)
Must avoid:
- Invented prices (priceUsd is 0, I'll just say "free")
- Fake numbers ("500 planners joined last week")
- Fake testimonials
- Actual links (can say "link in bio" generically or just describe the gate)
- Payment buttons
- Drafting the Markdown (iterative refinement):
# Wedding Planner Crisis Playbook
A free emergency checklist and protocol guide for wedding planners who want to handle day-of disasters with confidence.
---
### What’s Inside
- Vendor no-shows or last-minute cancellations
- Extreme weather or venue issues
- Timeline breakdowns and key-party delays
- Vendor payment or contract disputes
- Guest count mismatches or dietary emergencies
- Equipment or décor failures
### Who This Is For
- Freelance wedding planners building their emergency-response toolkit
- New planners who want structured protocols from day one
- Senior planners looking to systematize crisis handling and reduce stress
### How It Works
Enter your email below to receive the “Wedding Crisis Checklist” instantly. No purchase required. No credit card.
Once subscribed, you’ll get:
- Immediate access to the downloadable PDF
- Quarterly updates with new vendor-failure scenarios
- Occasional emails about planner resources (you can unsubscribe anytime)
### Why This Exists
Planning a wedding involves countless moving parts. This playbook gives you a repeatable framework to protect your reputation, keep couples calm, and solve problems fast—without guessing.
### How We’ll Keep It Fresh
- Checklist refreshed every 3 months with real-world vendor failure scenarios
- A/B testing of lead-magnet titles and delivery formats
- Open and click rates tracked to improve content relevance
- Survey feedback from subscribers used to add new crisis scenarios
Wait, check constraints: "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims. Do not invent prices, links or payment buttons."
My draft looks honest. I used "quarterly updates" which is from the plan, but I shouldn't invent specific numbers like "every 3 months" if the plan says "Refresh checklist quarterly" - that's fine, it's describing the plan, not inventing a fake statistic. I'll keep it generic: "refreshed regularly" or "quarterly" is okay since it's part of the given plan.
I should make sure I don't say "500 planners" or anything. I'll remove any implied counts.
Also, "priceUsd": 0 means it's free. I'll state it's free, no price.
I'll avoid "link in bio" as an invented link, but I can say "via the signup form" or keep it descriptive. The prompt says "Do not invent prices, links or payment buttons." So I should not put a literal URL or "click here" button. I'll just describe the action.
Let restructure slightly to be purely markdown content, no fake calls to action with links.
Let me re-draft carefully:
# Wedding Planner Crisis Playbook
A free emergency protocol and checklist resource for wedding planners who need to manage day-of crises calmly and effectively.
---
### What You’ll Get
- Protocols for vendor no-shows or last-minute cancellations
- Steps to handle extreme weather, venue changes, or power outages
- Guidelines for timeline disruptions and key-party delays
- Language and templates for contract or payment disputes
- Checklists for guest-count mismatches and dietary emergencies
- Quick-reference cards for equipment or décor failures
### Who This Is For
- Wedding planners at any stage who want structured emergency frameworks
- New planners building their first crisis-response toolkit
- Experienced planners looking to systematize ad-hoc problem-solving
### How to Access
Enter your email address below to receive the “Wedding Crisis Checklist” PDF instantly. There is no cost, no purchase required, and no credit card information needed.
After signing up, you’ll receive:
- The downloadable checklist right away
- Periodic updates that refresh the content with new vendor-failure scenarios
- Email updates about planner resources, with an easy unsubscribe option at any time
### How We Keep It Current
- The checklist is reviewed and refreshed quarterly with real vendor failure scenarios
- Lead-magnet titles and delivery formats are A/B tested to improve reach and relevance
- Email open and click rates are tracked to refine content over time
- Subscriber feedback surveys shape new crisis scenarios and additions
Check against constraints:
- Headings: Yes (h1, h2/h3-like)
- Short paragraphs: Yes
- Bullet lists: Yes
- Honest/specific: Yes, describes exactly what it is, who it's for
- No fake testimonials/numbers/claims: Yes, no numbers mentioned except "quarterly" which is from the plan spec, not invented as a statistic
- No invented prices/links/buttons: Yes, I explicitly say "no cost, no purchase required, no credit card" without putting a URL or "click here". I say "enter your email address below" which is a generic action, not a specific invented link.
- Reflects the plan: GoalMetric email_signups, checkpointHours 168, killRule, boostRule, cloneRule, channel owned-site, priceUsd 0, distributionPlan, maintenancePlan all referenced or consistent with the content.
I should make sure the plan elements are implicitly honored but not necessarily spelled out verbatim, as the copy should be a web page, not a plan doc. But I can nod to the maintenance/refresh aspect.
One thing: "killRule":{"maxIterationsWithoutRevenue":3} - since price is 0 and it's a lead gen playbook, revenue isn't the immediate goal, but email signups. I won't mention iteration limits unless relevant. The prompt says "Be honest and specific about what it is and who it is for". I'll keep the copy focused on the value prop.
I think the draft is solid. I'll output it in markdown as requested. I'll make sure there are no real links, no price tags, no fake stats. I'll keep "quarterly" as it's part of the given maintenancePlan, but I won't say "every 3 months" to