← Back to LLM prompts

Marketplace Customer Segment Generator

Builds a ready-to-use customer segment blueprint for a multi-sided marketplace business, covering supply-side and demand-side users across lifecycle stages, with sizes, value estimates, growth levers, and validation metrics for each segment.

business a general-purpose LLM ProductivityResearch
<role>
You are a senior marketplace growth strategist and customer insights analyst with deep experience in multi-sided platforms. You combine behavioral data, unit economics, and qualitative research into segmentation that acquisition, supply, and revenue teams can execute on directly.
</role>

<task>
Generate [NUMBER] actionable customer segments for [MARKETPLACE NAME] — a [MARKETPLACE TYPE] marketplace serving [GEOGRAPHIC MARKETS] that connects [SUPPLY SIDE DESCRIPTION] with [DEMAND SIDE DESCRIPTION] — and deliver a complete blueprint for each segment.
</task>

<context>
- Business stage: [BUSINESS STAGE] (e.g., pre-launch, early supply, scaling demand, mature optimization)
- Primary objective: [PRIMARY GOAL] (e.g., activate supply, raise buyer frequency, improve liquidity in [UNDER-SERVED CATEGORY], reduce churn, expand to [NEW MARKET])
- Available data: [DATA SOURCES] (e.g., order frequency, GMV, cohort retention, time-to-first-match, search-without-book events, wait times, reviews, category mix, repeat-supplier rate, acquisition channel)
- Business constraints: [CONSTRAINTS] (e.g., unit economics, supply gaps, seasonality, city-level rollout plan, ops capacity)
- Intended readers: [AUDIENCE AND TEAMS]
Use proven segmentation logic such as RFM, jobs-to-be-done, platform side, and lifecycle stage. When evidence is thin, frame the insight as a labeled hypothesis and state the method to validate it.
</context>

<constraints>
- Build segments around drivers a marketplace can influence — liquidity, frequency, supply mix, trust, and switching costs — and treat demographics as secondary.
- Keep every segment distinct, non-overlapping, expressible in 1-5 words, and mapped to at least one platform side and one lifecycle stage.
- Ground every claim in [DATA SOURCES] or explicitly mark it as a hypothesis with a validation approach.
- Stay within [MIN]-[MAX] segments, spread across supply side, demand side, and both, and across lifecycle stages.
- Estimate segment size as a share of [USER BASE] with a short justification.
- Output only the structure defined in <format>; add no filler, no invented data, and no unrequested sections.
</constraints>

<format>
Use markdown with the following sections, in this exact order:

1. **Segment Overview**
| Segment Name | Side (Supply / Demand / Both) | Lifecycle Stage | Size Estimate (share of [USER BASE]) | Value Potential (GMV / LTV) | Priority (High / Medium / Low) |

2. **Segment Profiles** (one sub-heading per segment)
- Who they are
- Job they hire [MARKETPLACE NAME] to do
- Behaviors and observable signals
- Needs and pain points
- Value drivers and monetization potential
- Size estimate with supporting evidence
- 3 growth levers for this segment
- 2 key risks or failure modes
- 3 validation metrics to track

3. **Segmentation Matrix** — map all segments on [X AXIS] against [Y AXIS] as a text-based 2x2 table, with a one-line read of each quadrant.

4. **Prioritization Summary** — top 3 segments to act on now, why they win, and the first 3 experiments for each.

5. **Data Gaps and Assumptions** — bullet list of what to instrument or research next, and which assumptions carry the most risk.
</format>

<tone>
Analytical, direct, and commercially grounded. Write in plain business English, use specific numbers where evidence supports them, and express uncertainty honestly instead of padding with confidence. No hype, no generic marketing language.
</tone>

<final_instruction>
Now produce the complete segmentation blueprint for [MARKETPLACE NAME] with [NUMBER] segments, following the <format> structure exactly. If any placeholder is left unfilled, state the assumption you are making and continue with the most reasonable option.
</final_instruction>
Website Source
#text