Feedback to Segments

Input

• Product: Luma, a B2B event management platform (ticketing, registration, attendee tracking)
• Feedback source: 847 support tickets + NPS responses from the past 6 months, NPS = 32
• Sample verbatims: "We run 40+ internal training events a year and can't see who no-showed across all of them," "Need to restrict certain sessions to specific employee levels," "Our compliance team needs a downloadable attendance log for auditing," "Wish we could sync registrations directly into Workday," "We use this for customer conferences and the branding options feel too generic," "Can't figure out how to handle waitlists when we have tiered ticket pricing"
• Company context: Luma is growing 60% YoY but churn is concentrated in accounts with 500+ employees; current ICP is "event organizers at SMBs and agencies"

---

Output (abbreviated)

Feedback → Segments Analysis: Luma

---

Step 1 — /feedback-reframer

Raw Requests → Underlying Problems

Raw Request	Reframed Problem	Outcome Language
"See who no-showed across all events"	Lack of aggregate attendance intelligence across a recurring event program	"I need to measure participation trends across my entire training calendar, not just individual events"
"Restrict sessions to employee levels"	No access control model that maps to org hierarchy	"I need the platform to enforce our internal structure without manual workarounds"
"Downloadable attendance log for auditing"	Compliance workflows require verifiable, audit-ready records	"I need to prove who attended what, when, for regulatory or legal purposes"
"Sync registrations into Workday"	Event data lives outside the systems of record for HR	"I need event participation to flow into the tools my organization already runs on"
"Branding feels too generic"	External-facing events require brand fidelity that internal tools don't	"I need attendees to experience our brand, not our vendor's"
"Waitlists with tiered pricing"	Revenue and capacity management is too rigid for complex event structures	"I need to manage demand and monetization simultaneously without manual intervention"

Emerging Themes

Theme A — Corporate Training Operations Requests cluster around recurring internal events, org-hierarchy enforcement, compliance records, and HRIS integration. The underlying problem: large employers running Luma like an LMS but without the enterprise controls.

Theme B — External Brand Events (Conferences, Customer Summits) Requests cluster around white-labeling, complex ticketing economics, and attendee experience quality. The underlying problem: event teams using Luma for high-stakes external events that current SMB-oriented UX undersupports.

PM Decision Point: Theme A is directionally more interesting — it explains the churn concentration in 500+ employee accounts. Theme B may be a real segment but looks closer to existing ICP. Carry Theme A forward.

---

Step 2 — /segment-discovery-guide

Segment Hypothesis

Hypothesis: Mid-to-large enterprises (500–5,000 employees) running recurring internal training or enablement programs are systematically underserved by Luma's current feature set and support model — and are churning not because the core product fails, but because it lacks the compliance, HRIS integration, and access-control primitives that make it viable at scale inside their IT and HR governance structures.

Candidate Segment Name: Corporate Learning Operations Manager

Dimension	Description
Role	L&D Manager, Training Operations, HR Programs
Company size	500–5,000 employees
Event cadence	20+ internal events/year (onboarding, compliance training, leadership development)
Current stack	Workday or BambooHR for HRIS; likely using Zoom + spreadsheets for event tracking
Pain severity	High — audit failures and manual reconciliation are real operational costs

Research Design

Objective: Validate whether this segment has sufficient size, willingness to pay, and switching urgency to justify a product investment thesis.

Method 1 — Churned Account Interviews (n=8)

• Target: Luma accounts with 500+ employees that churned in the last 6 months
• Key questions:
  • What did you switch to, and why?
  • What would Luma have needed to do to keep you?
  • Who else was involved in the decision to leave?
• Signal to look for: Compliance and integration blockers cited as primary (not price or UX)

Method 2 — Current Power User Deep Dives (n=6)

• Target: Active accounts running 20+ events/year in the 500–2,000 employee band
• Key questions:
  • What workarounds have you built around Luma?
  • What's the one thing that would make this a no-brainer to expand internally?
  • Have you had to defend the tool to IT or HR leadership?
• Signal to look for: Evidence of internal friction, shadow processes, or blocked expansion

Method 3 — Competitive Teardown

• Products to audit: Cvent, Bizzabo, WorkRamp (as an adjacent LMS entrant)
• Focus: How do they position compliance, HRIS integration, and access control to enterprise buyers?
• Signal to look for: Whether this is a solved problem (bad for differentiation) or an underinvested category

Analysis Framework

                HIGH switching urgency
                        |
       Cvent too        |       Luma can win
       expensive -------|------- with targeted
                        |       investment
LOW willingness         |                HIGH willingness
to pay --------|--------|--------|------- to pay
                        |
       Not worth        |       Wait — monitor
       pursuing         |       for signal
                        |
                LOW switching urgency

PM Decision Point: Run interviews before building anything. If 5 of 8 churned accounts cite compliance/integration as primary blocker, the hypothesis is confirmed. If it's scattered, the segment may be too diffuse.

---

Step 3 — /10x-move-evaluator

Is This a 10x Opportunity or a 10% Optimization?

What a 10% move looks like here: Add an attendance export button and call it "compliance ready." Ship a Workday Zap. Close a few churn tickets. Net result: minor churn reduction, no repositioning, no new market.

What a 10x move looks like here: Reposition a product tier — Luma for Teams — as the lightweight alternative to Cvent for internal event programs. Own the "enterprise HR event operations" wedge before Workday or Rippling builds it natively. Create an integration-first architecture (Workday, BambooHR, Okta SSO) that makes Luma sticky inside IT governance. Land-and-expand motion: one L&D manager becomes a company-wide contract.

Evaluation

Criterion	Score (1–5)	Notes
Problem severity	5	Compliance and audit failures are non-negotiable blockers — not preference issues
Market size	4	~180K companies in the 500–5,000 band in North America; L&D spend is growing
Competitive white space	4	Cvent is overbuilt and overpriced; no clear lightweight enterprise winner
Strategic fit	3	Requires a new sales motion and pricing model — not just features
Switching urgency	4	Churn is already happening — demand signal exists, not hypothetical
10x trajectory potential	4	If the wedge works, it redefines Luma's ICP and unlocks enterprise ACV

Overall: 4.0 / 5 — Pursue with conviction, conditioned on interview validation

Verdict

This clears the 10x threshold if the research confirms that compliance and HRIS integration are the primary churn drivers — not symptoms of a broader product-market fit problem. The strategic case is strong: Luma is already inside these companies, the competition is either too expensive (Cvent) or too generic (Eventbrite), and the land-and-expand motion is credible.

Recommended next move: Greenlight the 8-interview churned account study. Set a 4-week timeline. Define a clear go/no-go gate: if ≥5 of 8 interviews cite integration or compliance as