Use this when a client needs to define, refine, or formalize their audience segments for marketing, product, or sales purposes. Works for both B2B and B2C, whether the client has rich customer data or is building segments from market intuition and early signals.
How it works
- You provide a description of customer data, the business model, any current segments, and relevant context
- The skill builds a multi-dimensional segmentation model covering behavioral, demographic, psychographic, and firmographic dimensions, with activation criteria and channel preferences per segment
- It returns segment cards the client's marketing, sales, and product teams can use immediately for targeting, messaging, and prioritization
Prompt
You are building an audience segmentation model for a Kate Makrigiannis consulting engagement. Kate helps clients move from vague "we target everyone" positioning to sharp, actionable segments that drive real marketing and product decisions. Before writing, read knowledge/voice-tone-guide.md -- use the client-facing voice.
Inputs I will provide:
- Customer data description: {{CUSTOMER_DATA}} (what data is available -- e.g., "CRM export with 2,000 customers, usage analytics, NPS survey results," or "we have 50 customers and some anecdotal patterns," or "pre-launch, working from market research and interviews")
- Business model: {{BUSINESS_MODEL}} (how the business makes money -- e.g., "B2B SaaS, $50K ACV, 12-month contracts," "DTC subscription, $29/month," "marketplace with buyer and seller sides")
- Current segments (optional): {{CURRENT_SEGMENTS}} (existing segmentation, formal or informal -- e.g., "we loosely target SMBs and enterprise," "we think of our users as power users and casual users")
- Context (optional): {{CONTEXT}} (why this work is happening now -- e.g., "preparing for GTM launch," "CAC is rising and we need to focus," "launching a new product line," "sales team keeps saying all leads look the same")
Step 1: Assess available data and choose segmentation approach
Evaluate the inputs and determine the right segmentation methodology:
| Data Richness | Approach |
|---|---|
| Rich data (CRM, usage analytics, purchase history) | Data-driven segmentation: cluster analysis patterns, behavioral cohorts, value-based tiers |
| Moderate data (some customers, qualitative research) | Hybrid approach: pattern recognition from data + market logic |
| Thin data (pre-launch, few customers) | Hypothesis-driven: build segments from market research, competitor analysis, and jobs-to-be-done |
State which approach you are using and why: "Based on the available data, I'm using [approach] because [reason]."
If data is thin, flag:
Step 2: Identify segmentation dimensions
Analyze the data across four dimensions:
Behavioral Segmentation
- Usage patterns (frequency, depth, features used)
- Purchase behavior (AOV, frequency, recency)
- Engagement signals (content consumption, support tickets, community participation)
- Adoption stage (evaluating, onboarding, active, power user, churning)
Demographic Segmentation
- For B2C: age, income, education, location, life stage, household composition
- For B2B: job title, department, seniority, team size, decision-making authority
Psychographic Segmentation
- Values and motivations (efficiency-driven, innovation-seeking, risk-averse, status-conscious)
- Attitudes toward the product category (early adopter, pragmatist, skeptic)
- Pain point intensity (acute vs. mild, urgent vs. eventual)
- Information preferences (data-driven, peer-influenced, expert-guided)
Firmographic Segmentation (B2B only)
- Company size (employees, revenue)
- Industry vertical and sub-vertical
- Company stage (startup, growth, mature, enterprise)
- Technology stack and maturity
- Budget authority and procurement process
Geographic & Linguistic Segmentation (if multi-market)
- Primary language and secondary languages spoken
- Cultural context (individualist vs. collectivist markets, communication style preferences, formality expectations)
- Regulatory environment (data privacy, compliance requirements by region)
- Payment preferences and purchasing power parity
- Content consumption habits by region (preferred channels, platforms, formats)
- Local competitors and market dynamics
Step 3: Define segments
Based on the dimensional analysis, define 3-6 distinct segments. More than 6 is usually too many to activate meaningfully. Fewer than 3 suggests the market is not well understood.
For each segment, create a full segment card:
Segment [N]: [Segment Name]
[One-sentence description of who this segment is in plain language]
Size estimate: [Approximate percentage of total market or customer base, and absolute numbers if available]
. Validate with market sizing data if available.]`
Profile
| Dimension | Detail |
|---|---|
| Behavioral markers | [How they use the product or engage with the market] |
| Demographics / Firmographics | [Who they are] |
| Psychographic profile | [What drives them, how they think] |
| Adoption stage | [Where they are in the customer journey] |
| Language / Locale | [Primary language, region, cultural context -- if multi-market] |
Needs and Pain Points
| Priority | Need / Pain Point | Intensity |
|---|---|---|
| 1 | [Primary need] | [Acute / Moderate / Mild] |
| 2 | [Secondary need] | [Intensity] |
| 3 | [Tertiary need] | [Intensity] |
Behavioral Triggers
Events or conditions that make this segment ready to buy, engage, or upgrade:
- Trigger 1: [event or condition] -- [how to detect it]
- Trigger 2: [event or condition] -- [how to detect it]
- Trigger 3: [event or condition] -- [how to detect it]
Activation Criteria
How to identify this segment in your data:
| Signal | Source | Threshold |
|---|---|---|
| [Signal 1] | [CRM / analytics / survey / external data] | [specific criteria] |
| [Signal 2] | [Source] | [Threshold] |
Messaging Guidelines
- Key message: [The primary value proposition for this segment, one sentence]
- Proof points to lead with: [2-3 proof points most relevant to this segment]
- Tone adjustment: [How messaging shifts for this segment -- more technical, more outcome-focused, more aspirational]
- Words that resonate: [3-5 terms or phrases this segment responds to]
- Words to avoid: [Terms that alienate or confuse this segment]
Channel Preferences
| Channel | Effectiveness | Rationale |
|---|---|---|
| [Channel 1] | [High / Medium / Low] | [Why this channel works or doesn't for this segment] |
| [Channel 2] | [Effectiveness] | [Rationale] |
| [Channel 3] | [Effectiveness] | [Rationale] |
Best channel mix: [Top 2-3 channels for reaching and converting this segment]
Recommended Tactics
- Acquisition: [Specific tactics to attract this segment]
- Activation: [How to get first value]
- Retention: [How to keep them engaged]
- Expansion: [Upsell or cross-sell opportunity]
Segment Economics
| Factor | Estimate | Confidence |
|---|---|---|
| Expected LTV | [$X range] | [High / Medium / Low] |
| Expected CAC | [$X range] | [High / Medium / Low] |
| LTV:CAC ratio | [X:1] | [High / Medium / Low] |
| Payback period | [X months] | [High / Medium / Low] |
Repeat for each segment.
Step 4: Segment prioritization
Segment Priority Matrix
| Segment | Market Size | Revenue Potential | Acquisition Ease | Strategic Fit | Priority |
|---|---|---|---|---|---|
| [Segment 1] | [S/M/L] | [$/$$/$$$] | [Easy / Moderate / Hard] | [High / Medium / Low] | [P1 / P2 / P3] |
| [Segment 2] | [Size] | [Revenue] | [Ease] | [Fit] | [Priority] |
Recommended primary segment: [Segment name] because [1-2 sentence rationale grounded in data]
Recommended secondary segment(s): [Segment name(s)] because [rationale]
Step 5: Activation playbook
Immediate Actions (Next 30 Days)
- [Specific action to start activating the primary segment]
- [Action to validate segment hypotheses]
- [Action to set up tracking for segment-specific metrics]
Medium-Term Actions (30-90 Days)
- [Build segment-specific campaigns]
- [Test messaging variations by segment]
- [Refine segment definitions based on early data]
Data Gaps to Close
| Gap | Impact | How to Close |
|---|---|---|
| [Missing data point] | [Why it matters for segmentation] | [Survey / interview / analytics setup / purchase external data] |
Related skills: Pairs with
/ideal-customer-profilefor deeper profiling of the primary segment. Feeds into/email-campaign-builderfor segment-specific campaigns. Feeds into/brand-messaging-frameworkfor audience-tailored messaging. Uses/marketing-roi-analyzerfor validating segment economics with real spend data.
Example Output
Input
- Customer data description: CRM export with 1,800 customers, 14 months of product usage analytics (login frequency, feature adoption, session depth), NPS survey with 340 responses, and sales call notes tagged by deal size and objection type
- Business model: B2B SaaS, project management and resource planning platform for professional services firms, $18K–$120K ACV depending on seat count, 12-month contracts with annual renewal, occasional multi-year deals at enterprise end
- Current segments: "We loosely split SMB and mid-market by headcount — under 50 employees is SMB, 50–500 is mid-market. Sales team treats them almost identically and keeps saying the leads all look the same."
- Context: CAC has increased 34% YoY, the sales cycle has lengthened from 38 to 61 days on average, and the board has asked for a focused GTM plan ahead of a Series B raise in Q3. Leadership wants to stop spreading budget across too many channels and audiences.
Output (abbreviated)
Segmentation approach: Hybrid data-driven + market logic. CRM and usage analytics provide behavioral and firmographic signals; NPS and sales call notes fill in psychographic texture. Some confidence gaps in budget authority data will be flagged.
Segment 1: The Scaling Agency Operator
Mid-sized digital or marketing agency (25–120 employees) growing fast enough to have outgrown spreadsheets but too lean for a dedicated ops function.
Size estimate: ~38% of current customer base (~680 accounts); estimated 12,000–18,000 firms in the addressable market
Profile
| Dimension | Detail |
|---|---|
| Behavioral markers | Logs in 4–6x/week; heavy use of resource allocation and utilization tracking; frequently exports reports to PDF for client delivery; opens in-app templates regularly |
| Demographics / Firmographics | 25–120 employees; $3M–$20M revenue; agency or consultancy vertical; ops managed by founder, COO, or first ops hire |
| Psychographic profile | Efficiency-obsessed, time-starved, slightly skeptical of "enterprise software" — wants power without complexity; motivated by margin and billable hour recovery |
| Adoption stage | Active to power user — converts from trial quickly when utilization pain is acute |
Needs and Pain Points
| Priority | Need / Pain Point | Intensity |
|---|---|---|
| 1 | Can't see who's over-allocated until it's too late — projects slip, staff burns out | Acute |
| 2 | Reporting to clients takes hours of manual work each week | Acute |
| 3 | No single source of truth across projects, especially after hiring sprint | Moderate |
Behavioral Triggers
- Trigger 1: Headcount crosses 30 employees — detectable via LinkedIn company size or firmographic enrichment at signup
- Trigger 2: Two or more missed deadlines flagged in support tickets or NPS verbatims — detectable via support tagging
- Trigger 3: Founder or ops lead starts a free trial after searching "resource planning agency" — detectable via UTM source + job title at signup
Activation Criteria
| Signal | Source | Threshold |
|---|---|---|
| Agency or consultancy industry tag | CRM / Clearbit enrichment | Present at account level |
| Utilization report feature opened within first 7 days | Product analytics | ≥ 2 sessions on utilization module |
| ACV at renewal | CRM | $18K–$45K range |
Messaging Guidelines
- Key message: Recover billable hours you're losing to scheduling chaos — without adding an ops headcount.
- Proof points to lead with: Average 11% utilization lift in first 90 days; client reporting time cut by 4 hours/week; setup in under a day
- Tone adjustment: Direct, outcome-first, low jargon — this buyer has no patience for feature lists; lead with time and margin saved
- Words that resonate: "billable hours," "utilization," "margin," "without the overhead," "your team, not your spreadsheets"
- Words to avoid: "enterprise-grade," "transformation," "ecosystem," "robust"
Channel Preferences
| Channel | Effectiveness | Rationale |
|---|---|---|
| LinkedIn (job title targeting: COO, Ops Director, Agency Owner) | High | Decision-makers are active; agency ops is a hot conversation topic |
| G2 and Capterra review categories | High | High intent; this segment searches by category before engaging sales |
| Agency-focused newsletters and communities (e.g., Bureau of Digital, MYOB) | Medium | Trusted peer channels; warm referrals convert faster than cold outbound |
| Broad Google Display | Low | Too diffuse; wastes budget on non-decision-makers |
Best channel mix: LinkedIn paid + G2 review presence + community sponsorships in agency-specific networks
Segment Economics
| Factor | Estimate | Confidence |
|---|---|---|
| Expected LTV | $54K–$90K (3–5 year retention at $18K–$22K ACV) | High |
| Expected CAC | $4,200–$6,800 | Medium |
| LTV:CAC ratio | ~10:1 | Medium |
| Payback period | 8–12 months | High |
Segment 2: The Enterprise PMO Lead
Ops or PMO leader inside a professional services firm with 300–2,000 employees, navigating complex procurement and multi-stakeholder buy-in.
Size estimate: ~22% of current customer base (~396 accounts); highest ACV concentration — this segment represents ~41% of current ARR
Profile
| Dimension | Detail |
|---|---|
| Behavioral markers | Longer evaluation cycle (45–90 days); heavy use of permissions, org hierarchy settings, and integrations (Salesforce, Jira, SSO); invites 8–15 stakeholders to trial |
| Demographics / Firmographics | 300–2,000 employees; VP of PMO, Director of Operations, or IT Procurement lead; multi-office, often multi-country; formal procurement process with RFP in some cases |
| Psychographic profile | Risk-averse, compliance-conscious, peer-influenced — wants validated vendors with proven implementations; motivated by audit readiness, standardization, and executive reporting |
| Adoption stage | Evaluating to onboarding — slow start, but extremely sticky once embedded |
Needs and Pain Points
| Priority | Need / Pain Point | Intensity |
|---|---|---|
| 1 | Needs executive-level dashboards that roll up across 10+ project teams | Acute |
| 2 | Current tools don't integrate with existing stack (Salesforce, Workday, Jira) | Acute |
| 3 | Can't demonstrate ROI of resource planning investments to CFO | Moderate |
Behavioral Triggers
- Trigger 1: Annual planning cycle (September–November) — detectable via inbound spike in Q4 or "annual planning" language in demo request forms
- Trigger 2: New PMO hire or restructure — detectable via LinkedIn job postings for PMO Director at target accounts
- Trigger 3: Existing tool contract expiry — enrichment services or sales intel (e.g., G2 Buyer Intent) can flag this
Messaging Guidelines
- Key message: Give your PMO a single command center that your CFO can read and your project leads will actually use.
- Proof points to lead with: SOC 2 Type II certified; Salesforce and Jira native integrations; case study from comparable firm (size and vertical match matters most to this buyer)
- Tone adjustment: Formal, evidence-heavy, peer-validated — white papers, case studies, and ROI calculators outperform punchy ad copy for this segment
- Words that resonate: "standardization," "executive visibility," "audit-ready," "portfolio view," "enterprise security"
- Words to avoid: "fast setup," "no IT required," "plug and play"
Segment Economics
| Factor | Estimate | Confidence |
|---|---|---|
| Expected LTV | $360K–$600K (4–6 year retention at $80K–$120K ACV) | High |
| Expected CAC | $28,000–$45,000 | Medium |
| LTV:CAC ratio | ~10:1 | Medium |
| **Payback |