# User Conference Producer

> Produces the flagship user conference that deepens customer loyalty, generates expansion pipeline, and attracts new prospects. Use when asked to user conference producer. Suggest when relevant.

- Skill: `mittuled/user-conference-producer` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add mittuled/user-conference-producer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mittuled/user-conference-producer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: mittuled (https://skillmd.com/u/mittuled)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mittuled/user-conference-producer

---


# user-conference-producer

## Agent: Social Media Manager

L2 event marketing manager responsible for conference presence, sales kickoffs, user conferences, company offsites, and virtual events.

Department ethos: [ideal-marketing.md](../../../../departments/marketing/ideal-marketing.md)

## Skill Description

Plans and produces the annual user conference or customer summit, creating the flagship event that deepens customer relationships, drives expansion pipeline, and attracts new prospects through peer-to-peer learning.

## When to Use

- The annual user conference is on the calendar and production planning must start 6+ months in advance.
- The company reaches a customer base size that justifies a dedicated conference to strengthen community and drive retention.
- Leadership wants a marquee event to anchor the brand's position as a category leader.
- Customer success data indicates that conference attendees retain and expand at higher rates, justifying increased investment.

## Workflow

1. Define the conference vision with leadership using the design model in `references/framework.md`: theme, target attendance, audience mix (customers, prospects, partners), and business outcomes (retention, expansion pipeline, brand).
2. Secure the venue, negotiate hotel room blocks, and lock the date. Begin sponsor outreach using the sponsor tier model in `references/framework.md` for partners who want booth or session access.
3. Open the call for papers. Recruit customer speakers who can share success stories and recruit internal experts for product sessions. Use the programming framework in `references/framework.md` to target the right keynote/breakout/workshop mix.
4. Design the agenda: keynotes, breakout tracks by persona or use case, hands-on workshops, product roadmap sessions, networking events, and an expo hall. Apply the networking programming formats in `references/framework.md`.
5. Launch registration with tiered pricing and early-bird incentives. Build the promotional campaign across email, social, sales outreach, and partner channels.
6. Produce all event materials: speaker decks, signage, mobile app configuration, attendee guides, and branded swag.
7. Coordinate logistics: registration desk staffing, session room AV, catering, transportation, and on-site troubleshooting teams.
8. Execute the event: manage the run-of-show across multiple tracks, facilitate speaker transitions, monitor session attendance, and capture real-time feedback.
9. Run the post-event follow-up within 48 hours: thank-you emails, session recordings, survey, and sales follow-up on prospect leads captured.
10. Deliver the post-conference report using `assets/user-conference-plan-template.md`: attendance, session ratings, NPS (target ≥ 50 per `references/framework.md`), pipeline generated, sponsor revenue, budget actuals, and recommendations for next year. Use `references/checklist.md` to verify all post-event steps are complete.

## Anti-Patterns

- **Making the agenda entirely product-focused with no customer stories.** *Why*: Attendees trust peer experiences over vendor pitches; conferences without customer voices feel like extended sales presentations.
- **Underinvesting in networking and social programming.** *Why*: Peer connections are the top reason customers attend conferences; packed agendas with no unstructured time miss the primary value driver.
- **Launching registration without a promotional plan.** *Why*: "Build it and they will come" does not work for conferences; attendance targets require sustained multi-channel promotion over months.
- **Skipping post-event sales follow-up orchestration.** *Why*: Prospects who attend the conference are high-intent leads; every day of delayed follow-up reduces conversion probability.
- **Treating sponsors as afterthoughts.** *Why*: Sponsor revenue offsets event costs and sponsors expect defined value; poor sponsor experience kills renewals and future partnerships.

## Output

**Success artifacts:**
- Conference brief with theme, agenda, budget, and promotional plan
- Speaker roster with session abstracts and production requirements
- Post-conference report with attendance, NPS, pipeline attribution, and budget reconciliation
- Follow-up campaign sequences for attendees, no-shows, and prospect leads

**Failure reporting:**
- Flag registration pace shortfalls against target at the 50% and 75% time marks
- Escalate speaker cancellations, venue issues, or budget overruns exceeding 10% to marketing leadership immediately

## Related Skills

*No related skills defined yet.*
- [`conference-presence-manager`](../conference-presence-manager/SKILL.md) — sibling skill under the same agent — combine with conference-presence-manager for end-to-end coverage
- [`event-calendar-planner`](../event-calendar-planner/SKILL.md) — sibling skill under the same agent — combine with event-calendar-planner for end-to-end coverage
- [`sales-kickoff-producer`](../sales-kickoff-producer/SKILL.md) — sibling skill under the same agent — combine with sales-kickoff-producer for end-to-end coverage