event-market-fit

Validates demand for technical events using pre-launch, mid-sale, and post-edition signals.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-market-fit-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-market-fit
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-market-fit
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-market-fit-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Event organizers routinely commit venues, budgets, and reputations to conferences, meetups, and hackathons without knowing whether real demand exists. This Skill reads demand signals at three moments - before launch, while tickets are on sale, and after an edition - and composes them into a go, hold-and-fix, pivot, or stop call, separating genuine demand gaps from marketing-execution or pricing problems. ## Core Features & Use Cases - Pre-launch demand validation: Establishes a baseline from local meetup draw (2-3x multiplier), verified community-size thresholds, and saturation scans, then runs intent-filtering instruments like deposit-backed waitlists and CFP probes with pre-declared pass thresholds. - Mid-sale pace diagnosis: Instruments the sales curve weekly against a checkpoint ladder or pace index, and runs a differential to distinguish marketing-execution gaps, price misfit, and true demand gaps before any verdict. - Post-edition recur/scale reads: Tracks attendee return rate, sponsor renewal rate, and sellout-speed trend as three separate axes, catching events that acquire well but fail to retain. - Use Case: Your meetup draws 45 people and you want to launch a 250-seat paid conference. The Skill resets the expectation to roughly 90-135 seats, rejects free interest-form counts as curiosity rather than intent, and prescribes a CFP probe or deposit-backed waitlist with declared thresholds before any venue commitment. ## Quick Start Ask the assistant to validate whether there is enough demand to turn your local meetup into a paid conference, providing your meetup attendance, community size, and any existing sales or waitlist data.

Frequently Asked Questions about event-market-fit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate demand for a tech conference before booking a venue?

Start with a baseline of 2-3x your best local meetup draw, run a saturation scan of competing events, then use intent-filtering instruments like a CFP probe (2-3:1 oversubscription target) or a deposit-backed waitlist. Declare each instrument's pass threshold before opening it, since free RSVPs and interest forms measure curiosity, not intent.

How do I know if my conference ticket sales are on pace?

Compare sales against the checkpoint ladder: roughly 15% of expected sales at early-bird close, plus 10% at speaker announcement, and 40-50% one month out, always net of comp tickets. From edition two onward, judge against your event's own prior sales curve using a pace index, and read from week two rather than launch day.

What is a good sponsor renewal rate for a tech conference?

High-performing events aim for at least 70% sponsor renewal per edition, a sourced benchmark. The single highest-leverage renewal action is sending a 72-hour post-event ROI report to every sponsor, which serves as both the measurement vehicle and the retention lever.

Does a sold-out event mean it has market fit?

Not by itself. Sellout speed can be manufactured through batch ticket releases, and an edition can sell out while sponsor renewal collapses. Read attendee return rate, sponsor renewal, and sellout-speed trend as three separate axes, and scale only when at least two of three are green.

Why are slow first-edition ticket sales not always a demand problem?

Slow early sales often reflect a skipped marketing push (checkpoints landing at 25-30% instead of 40-50%) or price misfit (healthy page traffic with low conversion), not absent demand. First editions also face anxiety about unproven events, so run the failure differential before issuing any pivot or stop verdict.

When should I not use this demand-validation approach?

Do not use it for launch scoping, pricing decisions, marketing plans, or growth levers - those belong to sibling skills and this one only reads signals. It also does not apply to non-event product validation such as SaaS product-market fit surveys.