# Decision Memo: Right-sized planning checklist for 30-guest weddings

Full report: https://ideanavigatorai.com/ideas/wedding-planning-software-for-30-guest-ceremonies/
Recorded: Not recorded

## Decision
- Team verdict: Park
- Validation verdict: Research (57/100)
- Confidence: 52%
- Recommendation: Keep this parked until the team has evidence for the next validation step: Recruit ten couples planning ceremonies of roughly 30 guests, walk them through the scaled-down checklist manually, and measure completion and willingness to pay versus using a free generic planner.

## Team rationale
No team rationale recorded yet.

## Reviewers
- No named reviewers recorded.

## Source anchors
- Buyer: Couple planning a micro-wedding of around 30 guests
- Market: Wedding planning software
- Problem: Mainstream wedding planners assume 150-plus guests with vendors, seating charts, and budgets that overwhelm a couple hosting an intimate 30-person ceremony who just need a simple, scaled-down checklist.
- Thesis: Right-sized planning checklist for 30-guest weddings should be tested as a narrow first-win workflow for Couple planning a micro-wedding of around 30 guests.
- Source: https://en.wikipedia.org/wiki/Wedding
- Source: https://www.theknot.com/

## Validation rubric
Rubric version: INAV-VALIDATION-2026-06-04

### Demand signal - 4.6/10 (24% weight)
Demand looks weak because the report has 2 source-backed signal(s), an editorial confidence of 52/100, and a defined buyer in Wedding planning software.

- Micro-weddings of around 30 guests have grown as a deliberate choice for cost and intimacy.
- Target buyer: Couple planning a micro-wedding of around 30 guests

### Problem severity - 5.3/10 (22% weight)
Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

- Mainstream wedding planners assume 150-plus guests with vendors, seating charts, and budgets that overwhelm a couple hosting an intimate 30-person ceremony who just need a simple, scaled-down checklist.
- Micro-weddings of around 30 guests have grown as a deliberate choice for cost and intimacy.

### Willingness to pay - 6/10 (20% weight)
Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

- One-time fee for the full planning checklist and timeline.
- Recruit ten couples planning ceremonies of roughly 30 guests, walk them through the scaled-down checklist manually, and measure completion and willingness to pay versus using a free generic planner.

### Competitive saturation - 5.7/10 (18% weight)
Competitive room is reduced by 1 recorded alternative(s); the wedge must stay narrow and differentiated.

- Recorded alternative: Zola
- Competitive score rewards a narrow wedge, not absence of research.

### Feasibility - 7.8/10 (16% weight)
Feasibility is strong for a low build if the MVP is limited to the first measurable workflow.

- Recruit ten couples planning ceremonies of roughly 30 guests, walk them through the scaled-down checklist manually, and measure completion and willingness to pay versus using a free generic planner.
- The micro-wedding niche may be too small or too one-time to sustain recurring revenue.

## Market gap
Underserved segments:
- Couple planning a micro-wedding of around 30 guests who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in Wedding planning software that feel the pain weekly but are too narrow for broad incumbents.
- New adopters who need guided proof before committing to a larger platform.

Feature gaps:
- A narrow workflow that reaches value without configuration-heavy onboarding.
- A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
- A handoff path from manual concierge service to repeatable software.

Differentiation levers:
- Use specificity as the wedge: one buyer, one workflow, one measurable result.
- Show proof earlier than broad competitors with before-and-after examples and small pilot data.
- Keep implementation lighter than incumbent suites or generic AI assistants.

## Roast and risks
Interesting hypothesis, but it needs sharper demand evidence before build time.

Blind spots:
- The micro-wedding niche may be too small or too one-time to sustain recurring revenue.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
- The first release can become a generic dashboard if the job is not named tightly.

Hard questions:
- Who wakes up already trying to solve this?
- What do they stop paying for or stop doing when this works?
- What proof would make a skeptical buyer trust it in one screen?
- What is the smallest paid version of this idea?

## Kill criteria
- Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
- No buyer can name a current cost in time, money, risk, or reputation.
- The first demo does not produce a clear next step, paid pilot, or specific objection.

## Offer ladder
- **Lead magnet (Free)**: Right-sized Planning Checklist For 30-guest Weddings checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps Couple planning a micro-wedding of around 30 guests audit the painful workflow before buying software.
- **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted.
- **Core offer ($49-$499/month)**: Right-sized planning checklist for 30-guest weddings focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop.
- **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.
- **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.