ICP & Persona Worksheet — Playbook
ICP & Persona Worksheet frameworks · scoring models · worked examples · fillable templates
Go-to-Market ICP Buyer Personas Segmentation Market Sizing
Most startups define their ICP as “anyone who could buy our product.” That’s not an ICP — that’s a wish list. A real ICP is a ruthlessly narrow definition of who you serve best, validated against actual customer data, that drives every downstream decision: messaging, channel strategy, content, cadence, and where your reps spend their time.
This worksheet walks you through building an ICP from scratch, defining the buyer personas inside those accounts, scoring and prioritizing accounts, and connecting it all to a messaging and content strategy. The frameworks are opinionated. The examples are concrete. The empty rows are for you to fill in for your company.
Who this is for: Founders building their first GTM motion, MBA interns assigned to market segmentation, and sales/marketing teams who suspect their targeting is too broad and want to tighten it.
══════════════ PART I: ICP ══════════════
Part I Ideal Customer Profile An ICP is a description of the company (not person) that gets the most value from your product, converts the fastest, retains the longest, and expands the most. Building it requires data, not assumptions.
01 What ICP Is and Isn’t
The Ideal Customer Profile is the narrowest possible definition of who you sell to. Not everyone who could buy. Not everyone who might benefit. The companies where your product solves a painful, urgent problem better than any alternative — and where the economics work for both sides.
ICP Is Not…
- Your TAM. TAM is everyone who could theoretically buy. ICP is the sliver of TAM where you actually win.
- A demographic description. “SaaS companies with 50–500 employees” is a filter, not an ICP. It tells you nothing about whether they need your product.
- Static. Your ICP at $1M ARR is different from your ICP at $10M ARR. It evolves as your product and market evolve.
- The same as a persona. ICP = the company. Persona = the person at that company. You need both, but they are different exercises.
Why Narrow = Better
Every founder’s instinct is to go broad. “Why would we exclude potential customers?” Because narrow targeting produces measurably better outcomes across every metric that matters:
| Metric | Broad Targeting | Narrow ICP | Why |
|---|---|---|---|
| CAC (Customer Acquisition Cost) | High | 40–60% lower | Messaging resonates. Less wasted spend on wrong-fit accounts. |
| Win Rate | 10–15% | 25–40% | You’re selling to people who actually have the problem you solve. |
| Sales Cycle | 6–9 months | 3–5 months | Less education needed. Urgency already exists. |
| Churn | 15–25% annual | 5–10% annual | Customers who fit your ICP get real value. They stay. |
| NRR (Net Revenue Retention) | 90–100% | 110–130% | Right-fit customers expand. Wrong-fit customers contract or churn. |
| Sales Rep Productivity | Low | 2–3x higher | Reps spend time on accounts that can actually close. |
You don’t grow by selling to everyone. You grow by dominating a narrow segment, then expanding to adjacent segments from a position of strength. Narrow first, expand later. The common mistake: “We can’t afford to be narrow — we need every deal we can get.” This is backwards. When you’re narrow, the deals you pursue close faster, stick longer, and cost less to acquire. You actually generate more revenue with fewer prospects because you stop wasting cycles on accounts that were never going to work.
02 The ICP Framework — Six Dimensions
Build your ICP across six dimensions. Each dimension is a filter. The intersection of all six is your ICP. If an account matches 5 out of 6, it’s close. If it matches 3 out of 6, it’s probably not your customer.
Dimension 1: Firmographic
The basic facts about the company. This is where most people stop — but firmographics alone are not an ICP. They’re the starting point.
| Attribute | Example (DevTools company) | Your Company |
|---|---|---|
| Company size (employees) | 50–500 engineers | Fill in… |
| Company size (revenue) | $5M–$100M ARR | Fill in… |
| Industry / vertical | B2B SaaS, fintech, healthtech | Fill in… |
| Geography | US, UK, DACH region | Fill in… |
| Funding stage | Series A through Series C | Fill in… |
| Business model | Product-led or hybrid sales-assisted | Fill in… |
| Growth rate | Growing headcount 30%+ YoY | Fill in… |
Dimension 2: Technographic
What’s in their tech stack? This matters because your product either integrates with, replaces, or depends on specific technologies.
| Attribute | Example (DevTools company) | Your Company |
|---|---|---|
| Core infrastructure | AWS or GCP (not on-prem) | Fill in… |
| Key tools / platforms | GitHub, Kubernetes, Terraform | Fill in… |
| Current solution (what you replace) | Homegrown CI/CD or Jenkins | Fill in… |
| Adjacent tools (integration points) | Datadog, PagerDuty, Jira | Fill in… |
| Tech maturity | Has a platform/infra team (not just app devs) | Fill in… |
Dimension 3: Behavioral
What triggers them to look for a solution? This is the most underrated dimension. Timing is everything. A perfect-fit company with no trigger won’t buy.
| Trigger Event | Why It Matters | How to Detect | Your Triggers |
|---|---|---|---|
| Funding round closed | Budget unlocked. Scaling starts. | Crunchbase, press releases | Fill in… |
| New executive hire | New leaders bring new tools. 60-day window. | LinkedIn alerts, job postings | Fill in… |
| Rapid hiring | Growing pains create the problem you solve. | Job boards, LinkedIn headcount | Fill in… |
| Product launch or expansion | New products expose infrastructure gaps. | Product Hunt, press, changelog | Fill in… |
| Compliance deadline | SOC 2, GDPR, HIPAA deadlines create urgency. | Industry calendar, job postings | Fill in… |
| Vendor churn | Dropping a competitor = actively looking. | G2 reviews, community forums | Fill in… |
| Public pain signal | Blog post, tweet, or talk about the exact problem. | Social monitoring, Google Alerts | Fill in… |
The trigger principle: An account that matches your ICP firmographically but has no active trigger belongs in Tier B (nurture). An account with a strong trigger but imperfect firmographic fit might close faster than the “perfect” account with no urgency. Always weight triggers heavily.
Dimension 4: Pain-Based
What specific problem must they have for your product to matter? If they don’t have this pain, they won’t buy — no matter how well they match on other dimensions.
| Attribute | Example (DevTools company) | Your Company |
|---|---|---|
| Primary pain | CI/CD builds take 20+ min, slowing every PR | Fill in… |
| Business impact of the pain | 30–60 min/day/engineer wasted. ~$500K/yr for 50 engineers. | Fill in… |
| Who feels the pain most | VP Engineering, Platform team lead | Fill in… |
| Current workaround | Throwing hardware at it, or devs working around slow CI | Fill in… |
| What happens if they don’t solve it | Shipping velocity drops. Engineers leave. Competitor ships faster. | Fill in… |
Dimension 5: Negative ICP
This is as important as positive ICP. Negative ICP defines who you explicitly DO NOT sell to. Closing a wrong-fit customer costs more than missing a deal: they consume support, churn within 6 months, leave bad reviews, and drag down your NRR. Every minute your team spends on a negative-ICP account is a minute stolen from a real prospect.
| Disqualifier | Example (DevTools company) | Why They Don’t Work | Your Disqualifiers |
|---|---|---|---|
| Too small | <10 engineers | Pain isn’t big enough. ACV won’t justify sales effort. | Fill in… |
| Too large | >5,000 engineers | 12-month procurement. Need enterprise features we don’t have. | Fill in… |
| Wrong industry | Government, defense | On-prem requirements. Air-gapped networks. Compliance we can’t meet. | Fill in… |
| Wrong tech stack | Fully on-prem, no cloud | Product is cloud-native. Integration isn’t possible. | Fill in… |
| Wrong use case | Agencies / consultancies | Short projects, low retention, no expansion revenue. | Fill in… |
| Wrong buying process | Requires 12+ month RFP | Sales cycle cost exceeds deal value. | Fill in… |
| Price-sensitive buyers | Companies that only buy the cheapest option | They’ll churn the moment a cheaper alternative appears. | Fill in… |
Build a “do not sell” list and enforce it. If a negative-ICP account inbounds, disqualify them fast and point them to a better alternative. Your team’s time is your most expensive resource — protect it.
Dimension 6: Economic
Can they afford you, and is the deal worth pursuing? Economic fit is often overlooked until it’s too late — you’re 3 months into a deal and discover they have $5K budget for a $50K product.
| Attribute | Example (DevTools company) | Your Company |
|---|---|---|
| ACV range | $30K–$150K/year | Fill in… |
| Budget authority | VP Engineering or CTO can sign up to $100K without board approval | Fill in… |
| Procurement process | Security review + legal review. 2–4 weeks typical. | Fill in… |
| ROI expectation | 3–6 month payback period | Fill in… |
| Expansion potential | Price per seat/usage. Grows as team grows. | Fill in… |
| Payment terms | Annual upfront preferred. Net-30 acceptable. | Fill in… |
03 ICP Scoring Model
Once you’ve defined your ICP dimensions, you need a way to score individual accounts. This prevents arguments about which accounts to prioritize and gives SDRs a clear, data-driven system.
The Scoring Framework
Score each account 1–5 across each dimension. Multiply by the weight (because not all dimensions are equally important). Total score determines the tier.
| Dimension | Weight | 1 (Poor Fit) | 3 (Partial Fit) | 5 (Perfect Fit) |
|---|---|---|---|---|
| Firmographic | 2x | Wrong size, industry, or geo | Right industry, slightly outside size range | Exact size, industry, geo, funding stage |
| Technographic | 2x | Incompatible stack | Some overlap, missing key integration | Uses exact tools you integrate with |
| Behavioral (Trigger) | 3x | No trigger detected | Indirect signal (hiring generally) | Strong trigger (funding, new exec, public pain) |
| Pain-Based | 3x | No evidence of the problem | Likely has the problem based on profile | Publicly stated the exact pain you solve |
| Negative ICP | Pass/Fail | If any negative-ICP flag is present, the account is disqualified regardless of score. | ||
| Economic | 2x | Budget far below ACV | Budget exists but tight | Budget confirmed, authority clear |
Score ranges:
- 48–60 points — Tier A. Work these accounts now.
- 35–47 points — Tier B. Good fit, nurture until trigger appears.
- 22–34 points — Tier C. Partial fit. Low priority.
- Below 22 — Tier D. Disqualify. Don’t spend time here.
Worked Example: 10 Accounts Scored
Scenario: You sell a CI/CD performance tool to engineering teams at mid-market SaaS companies.
| Account | Firmographic (x2) | Technographic (x2) | Trigger (x3) | Pain (x3) | Economic (x2) | Total | Tier |
|---|---|---|---|---|---|---|---|
| Ramp | 5 (10) | 5 (10) | 5 (15) | 5 (15) | 4 (8) | 58 | A |
| Neon | 5 (10) | 5 (10) | 4 (12) | 4 (12) | 4 (8) | 52 | A |
| Resend | 4 (8) | 5 (10) | 5 (15) | 4 (12) | 3 (6) | 51 | A |
| Linear | 5 (10) | 4 (8) | 3 (9) | 5 (15) | 4 (8) | 50 | A |
| Loom | 4 (8) | 4 (8) | 3 (9) | 3 (9) | 5 (10) | 44 | B |
| Notion | 3 (6) | 4 (8) | 3 (9) | 3 (9) | 5 (10) | 42 | B |
| Drata | 4 (8) | 3 (6) | 4 (12) | 2 (6) | 4 (8) | 40 | B |
| Webflow | 3 (6) | 3 (6) | 2 (6) | 3 (9) | 4 (8) | 35 | C |
| Local bakery SaaS (5 devs) | 1 (2) | 2 (4) | 1 (3) | 1 (3) | 1 (2) | 14 | D |
| Defense contractor (on-prem) | NEGATIVE ICP FLAG: on-prem only, no cloud | DQ | DQ |
What the scoring reveals: The top 4 accounts (Tier A) all share something: strong triggers + confirmed pain. Ramp just raised a round and has public CI complaints. Neon is scaling fast on GitHub Actions. The bottom accounts either lack the pain or have a disqualifying attribute. The scoring makes prioritization objective, not gut-feel.
Blank Scoring Sheet — Your Accounts
| Account | Firmographic (x2) | Technographic (x2) | Trigger (x3) | Pain (x3) | Economic (x2) | Total | Tier |
|---|---|---|---|---|---|---|---|
| Account 1 | |||||||
| Account 2 | |||||||
| Account 3 | |||||||
| Account 4 | |||||||
| Account 5 | |||||||
| Account 6 | |||||||
| Account 7 | |||||||
| Account 8 | |||||||
| Account 9 | |||||||
| Account 10 |
04 How to Validate Your ICP
Your ICP is a hypothesis until you validate it against real data. The validation method is simple but powerful: look at your best customers and your worst churned customers, and find the pattern.
Step 1: Analyze Your Best 10 Customers
“Best” = highest NRR, fastest close, lowest support burden, most enthusiastic reference. Pull these 10 and fill in:
| Customer | Industry | Size | Tech Stack | Trigger That Started the Deal | Primary Pain | ACV | Time to Close |
|---|---|---|---|---|---|---|---|
| Customer 1 | |||||||
| Customer 2 | |||||||
| Customer 3 | |||||||
| … |
Now look for patterns: What do these 10 have in common? Usually it’s 2–3 attributes that show up in 7+ of the 10. That cluster IS your ICP.
Step 2: Analyze Your Worst 10 Churned Customers
“Worst” = churned within 12 months, required excessive support, never expanded, or actively complained. Same exercise:
| Churned Customer | Industry | Size | Tech Stack | Why They Churned | Warning Signs (in Retrospect) |
|---|---|---|---|---|---|
| Churned 1 | |||||
| Churned 2 | |||||
| Churned 3 | |||||
| … |
Now look for patterns in the churn: What do these 10 have in common? Those shared attributes form your Negative ICP.
Step 3: The Intersection
Best customers had in common:
- 50–300 engineers
- Series A–C funded
- Using GitHub + Kubernetes
- Experiencing scaling pain from rapid hiring
- VP Eng or CTO was the champion
Churned customers had in common:
- Under 15 engineers (pain wasn’t big enough)
- No dedicated platform team
- Bought because of a discount, not a pain
- On-prem or hybrid infrastructure
- Champion left the company
The best-customer patterns become your ICP. The churn patterns become your Negative ICP. This isn’t theory — it’s your own data telling you where to focus. Update this analysis every quarter as you get more data.
══════════════ PART II: PERSONAS ══════════════
Part II Buyer Personas ICP tells you which companies to target. Personas tell you which people at those companies to reach, what to say to them, and how they make decisions. A great ICP with wrong-persona targeting still fails.
05 Personas vs ICP — You Need Both
| Dimension | ICP (Ideal Customer Profile) | Buyer Persona |
|---|---|---|
| Unit of analysis | The company / account | The individual person at that company |
| Describes | Firmographics, technographics, pain, triggers | Role, goals, fears, decision process, language |
| Answers | “Which companies should we target?” | “Who at those companies should we talk to, and what do we say?” |
| Example | B2B SaaS, 50–500 eng, Series B, using GitHub | VP Engineering who cares about shipping velocity and is measured on deployment frequency |
| Changes when | Your product/market evolves | Your product adds features that serve new roles |
For most B2B companies, you need 3–5 personas across two categories:
- The Champion — the person who discovers you, advocates internally, and pushes the deal forward. Usually mid-level (Director, Sr. Manager). They have the pain.
- The Economic Buyer — the person who signs the check. Usually VP or C-level. They care about business outcomes, not features.
- The Blocker — the person who can kill the deal. Usually IT/Security, Legal, or Procurement. You need to neutralize their objections.
- The End User — the person who uses the product daily. Their opinion matters for adoption and renewal. They care about UX and workflow fit.
Common mistake: Building personas based on demographics (age, gender, education). That’s consumer marketing. B2B personas are defined by role, goals, metrics, pain, and buying behavior. A 28-year-old VP Eng and a 52-year-old VP Eng behave identically in a buying process. Their age is irrelevant.
06 The Persona Template
For each persona, answer every field below. If you can’t answer a field, you don’t know this persona well enough yet — go talk to 5 customers in this role.
| Field | What to Capture | Why It Matters |
|---|---|---|
| Title & role | Exact title(s) and scope of responsibility | Determines targeting in LinkedIn, email, ads |
| Reports to | Who they report to (this person is often the economic buyer) | Understand the approval chain |
| Responsible for | Their top 3–5 KPIs or goals this quarter | Your pitch must connect to what they’re measured on |
| What keeps them up at night | Their top 3 fears, frustrations, or anxieties | This is where emotional resonance lives |
| How they’re measured | Specific metrics their performance is judged on | Your ROI story must use their metrics |
| Where they get information | Podcasts, newsletters, Slack communities, conferences, influencers | Determines content distribution and co-marketing |
| How they buy | Self-serve? Need manager approval? Committee? RFP? | Determines sales motion and deal complexity |
| Common objections | The top 3–5 reasons they say no or stall | Prepare counter-narratives for each objection |
| Language they use | Technical? Business outcomes? Financial? Jargon? | Mirror their language in messaging. Don’t say “ROI” to engineers. |
| Messaging that resonates | 2–3 sentences that would make this persona stop scrolling | The actual words you use in emails, ads, and landing pages |
Blank Persona Template — Fill In for Your Company
Persona: [Title] Champion / Economic Buyer / Blocker / End User
Title & Role Fill in… Reports To Fill in… Responsible For (KPIs) Fill in… What Keeps Them Up at Night Fill in… How They’re Measured Fill in… Where They Get Information Fill in… How They Buy Fill in… Common Objections Fill in… Language They Use Fill in… Messaging That Resonates Fill in…
07 Four Complete Persona Examples
Below are four fully worked personas for a hypothetical B2B SaaS company selling developer infrastructure tools. Study the level of detail — this is the bar for your own personas.
Persona 1: VP of Engineering
VP of Engineering Champion + Economic Buyer
Title & Role VP Engineering, Head of Engineering, SVP Engineering. Owns the entire engineering org (50–300 engineers). Reports to CTO or CEO. Responsible for shipping product on time, engineering culture, and technical infrastructure decisions. Reports To CTO or CEO (at smaller companies, may report directly to CEO). Responsible For (KPIs)
• Shipping velocity (features delivered per sprint/quarter)
• Engineering headcount efficiency (revenue per engineer)
• System reliability (uptime, P0 incident count)
• Developer satisfaction / retention (eng turnover rate)
• Time-to-production for new engineers (onboarding speed)
What Keeps Them Up at Night
• “We’re hiring fast but shipping slower than when we were half the size.”
• “Our best engineers are leaving because the tooling and infrastructure frustrate them.”
• “The board expects 2x output but I can barely keep the lights on.”
• Fear of a P0 incident that makes the news.
How They’re Measured DORA metrics (deployment frequency, lead time for changes, MTTR, change failure rate). Feature velocity vs plan. Eng team retention. Infrastructure cost as % of revenue. Where They Get Information Hacker News, The Pragmatic Engineer newsletter (Gergely Orosz), LeadDev, StaffEng.com, QCon / KubeCon talks, CTO Craft Slack community, engineering blogs from Stripe, Linear, and Vercel. How They Buy Can sign up to $100K without board approval at Series B+. Will ask a platform team lead to evaluate the tool first. Needs a technical proof-of-concept (1–2 week pilot). Decision process: engineer evaluates → team lead recommends → VP approves budget → security review → sign. Common Objections
• “We can build this ourselves.” (Most common. Counter: show the opportunity cost of 2 engineers for 6 months.)
• “Not a priority right now.” (Counter: quantify the cost of inaction — $X/month in wasted eng time.)
• “We tried something similar and it didn’t work.” (Counter: ask what failed and show how your approach differs.)
• “I need to see it work in our environment.” (Counter: offer a free pilot with clear success criteria.)
• “Security needs to review it.” (Counter: have SOC 2 report ready. Don’t make them ask.)
Language They Use Technical but outcome-oriented. Uses terms like “developer experience,” “shipping velocity,” “platform engineering,” “build times,” “CI/CD,” “developer productivity.” Avoids business jargon. Do NOT say “synergy,” “leverage,” or “best-in-class” to this person. Messaging That Resonates “Your engineers are spending 45 min/day waiting on CI. That’s 3 engineers’ worth of output lost every month. We cut that to under 5 min for teams running monorepos on GitHub Actions — no migration required.”
Persona 2: VP Sales / CRO
VP Sales / CRO Economic Buyer
Title & Role VP Sales, Chief Revenue Officer, Head of Revenue. Owns the entire revenue org: SDRs, AEs, SEs, and sometimes CS. Responsible for hitting the number. Reports to CEO. Reports To CEO. Presents pipeline and forecast to the board quarterly. Responsible For (KPIs)
• Quarterly and annual revenue target (ARR, bookings)
• Pipeline coverage (4x+ is healthy)
• Win rate by segment and deal size
• Sales cycle length
• Quota attainment across the team (% of reps at or above quota)
• CAC and CAC payback period
What Keeps Them Up at Night
• “Pipeline is thin and the board meeting is in 3 weeks.”
• “Half my reps are below quota and I don’t know if it’s a people problem or a process problem.”
• “We’re losing to [competitor] on deals we should be winning.”
• “My top AE just got poached and the pipeline goes with them.”
How They’re Measured Revenue vs target. Pipeline generation. Win rate. Average deal size. Sales cycle length. Rep ramp time. Revenue per rep. Where They Get Information SaaStr (conference + podcast), Pavilion (formerly Revenue Collective), The Revenue Formula podcast, Jacco van der Kooij (Winning by Design), Lenny’s Newsletter (for PLG), LinkedIn (very active), closed-door CRO dinners. How They Buy Fast decision-maker. Will pilot quickly if the ROI case is clear. Needs to see impact on win rate or pipeline within 30–60 days. Can sign $50–$200K depending on company stage. Will involve RevOps for evaluation. Common Objections
• “We already have [competitor tool].” (Counter: we’re not replacing, we’re augmenting. Here’s the gap.)
• “Show me the ROI first.” (Counter: run a 30-day pilot on one team, measure win rate before/after.)
• “My team won’t adopt another tool.” (Counter: show adoption rates from similar teams + onboarding time.)
• “Not in the budget this quarter.” (Counter: show the cost of one lost deal per month vs your price.)
Language They Use Business and financial. “Pipeline,” “quota attainment,” “win rate,” “deal velocity,” “ARR,” “bookings.” Understands and responds to ROI calculations. Wants numbers, not features. Do NOT lead with technical capabilities — lead with revenue impact. Messaging That Resonates “Lattice’s mid-market team went from 18% to 31% win rate after fixing their discovery process. That’s 13 points — equivalent to hiring 4 more AEs without the ramp time. We can show you exactly where your deals are stalling and why.”
Persona 3: CFO
CFO / VP Finance Economic Buyer (Final Approver)
Title & Role CFO, VP Finance, Head of Finance. Owns financial planning, budgeting, reporting, and compliance. At Series B+, they own the board deck and the path to profitability narrative. Reports to CEO. Reports To CEO. Presents financials to the board. Responsible For (KPIs)
• Gross margin (especially cloud/infra costs as % of revenue)
• Burn rate and runway
• Path to profitability / Rule of 40
• Budget accuracy (forecast vs actual)
• Vendor spend management
• Audit and compliance readiness
What Keeps Them Up at Night
• “Cloud costs are growing faster than revenue and the board is noticing.”
• “We have 200+ SaaS vendors and I can’t tell which ones are actually being used.”
• “We need to show a path to profitability by next board meeting.”
• “I don’t trust the revenue forecast because the sales team’s pipeline data is unreliable.”
How They’re Measured Gross margin improvement. Burn multiple. Budget vs actual variance. Successful audit completion. Vendor cost reduction YoY. Where They Get Information CFO Connect (Andreessen Horowitz community), SaaS Metrics by David Skok, Bessemer’s Cloud Index, Meritech Capital reports, board members, peer CFOs at portfolio companies, Big 4 advisory partners. How They Buy Needs a clear, quantified business case. Won’t pilot without seeing projected ROI. Decision criteria: payback period (<6 months), implementation risk, vendor stability. Will involve procurement and legal. Expects annual contract with clear SLAs. Common Objections
• “What’s the payback period?” (Counter: show 3–6 month payback with specific dollar savings.)
• “We can do this with a spreadsheet.” (Counter: you can, until you can’t. Show the error rate and time cost of manual processes.)
• “This isn’t in the budget.” (Counter: this pays for itself. Show the savings exceed the cost within Q1.)
• “How do I know you’ll be around in 2 years?” (Counter: share funding, customer count, retention rate, and reference customers.)
Language They Use Financial. “Gross margin,” “unit economics,” “burn rate,” “payback period,” “Rule of 40,” “vendor consolidation,” “budget variance.” Responds to dollar amounts and percentages, not features or technology. Every claim must have a number attached. Messaging That Resonates “Your cloud spend is 22% of revenue. Benchmark for your stage is 14%. That gap is $1.8M/year in gross margin you’re leaving on the table. We can identify the waste in 2 weeks with zero engineering effort — and the typical payback period is 6 weeks.”
Persona 4: CMO
CMO / VP Marketing Champion or Economic Buyer
Title & Role CMO, VP Marketing, Head of Growth. Owns demand generation, brand, content, product marketing, and increasingly revenue attribution. Reports to CEO. Reports To CEO. Often in tension with the CRO over pipeline attribution and lead quality. Responsible For (KPIs)
• Marketing-sourced pipeline and revenue
• CAC and CAC payback by channel
• MQL/SQL conversion rates
• Brand awareness and share of voice
• Content performance (organic traffic, engagement, conversion)
• Marketing ROI / efficiency ratio
What Keeps Them Up at Night
• “Sales says the leads suck. I say sales can’t close. The CEO is tired of the argument.”
• “CAC is rising and I can’t tell which channels are actually working.”
• “We need to compete with companies that have 10x our marketing budget.”
• “Attribution is broken and I can’t prove marketing’s impact.”
How They’re Measured Pipeline sourced by marketing. Marketing-influenced revenue. CAC by channel. Website conversion rate. Content ROI. Brand lift metrics. Where They Get Information Lenny’s Newsletter, Demand Curve, Marketing Against the Grain (HubSpot podcast), CMO Coffee Talk (Pavilion), SaaStr, First Round Review, Twitter/X marketing community, peer CMOs at portfolio companies. How They Buy Will trial self-serve tools without approval. For larger purchases ($30K+), needs CEO or CFO sign-off. Wants to see impact within 30 days. Heavily influenced by what competitor marketing teams are using. Will ask their team to evaluate before committing. Common Objections
• “We already use [competitor].” (Counter: show the gap in their current stack with specific data.)
• “We don’t have the bandwidth to onboard another tool.” (Counter: show time-to-value <1 week with comparable teams.)
• “Prove it works before I commit budget.” (Counter: offer a free trial with clear success metrics defined upfront.)
• “Marketing is getting cut, not expanded.” (Counter: show this tool reduces spend elsewhere, net savings.)
Language They Use Mix of business and creative. “Pipeline,” “CAC,” “attribution,” “funnel conversion,” “content engine,” “demand gen,” “brand.” More narrative-driven than CFO. Responds to competitive intelligence (“here’s what [competitor’s marketing team] is doing”). Do NOT be overly technical. Messaging That Resonates “Your top 3 competitors are outranking you on 78% of your target keywords — and their content production rate is 4x yours. We can help you close that gap without hiring more writers. One customer went from 12 to 50 published pages per month and doubled organic pipeline in 90 days.”
══════════════ PART III: PUTTING IT TOGETHER ══════════════
Part III Putting It Together ICP without action is an exercise in strategy theater. This part connects ICP and personas to concrete decisions: what you say, where you say it, how you prioritize, and how you size the market.
08 ICP → Persona → Messaging Matrix
The combination of ICP segment + buyer persona determines everything downstream: the message, the channel, the content format, the cadence, and the CTA. This matrix maps each combination to a specific go-to-market approach.
| ICP Segment | Persona | Primary Message | Channel | Content Format | Cadence |
|---|---|---|---|---|---|
| Series B SaaS, 50–200 eng | VP Engineering | “Your build times are costing you $500K/yr in eng productivity.” | Cold email + LinkedIn + Hacker News | Benchmark report, technical case study | 4 emails over 18 days |
| Series B SaaS, 50–200 eng | CTO | “Platform engineering shouldn’t require 5 dedicated engineers.” | Cold email + warm intro via investors | Architecture diagram, peer comparison | 3 emails over 14 days + intro |
| Mid-market SaaS, $10–50M ARR | VP Sales / CRO | “Your win rate is 15%. Benchmark is 28%. Here’s why.” | Cold email + LinkedIn + event | Win/loss analysis template, ROI calc | 4 emails over 18 days |
| Mid-market SaaS, $10–50M ARR | CFO | “Cloud is 22% of revenue. Benchmark is 14%. That’s $1.8M/yr.” | Cold email + CFO community intros | Benchmark data, ROI calculator | 3 emails over 14 days (shorter) |
| Series A SaaS, fast-growing | CMO | “Competitors are outranking you 4:1. Your content velocity is the gap.” | LinkedIn DM + cold email + community | Competitor teardown, SEO audit | 4 emails over 18 days |
Why this matters: Notice how the same product is positioned completely differently for each persona. VP Eng hears “build times.” CRO hears “win rate.” CFO hears “gross margin.” Same solution, different language, different metrics, different proof points. This is what persona-specific messaging looks like in practice.
Blank Messaging Matrix — Your Company
| ICP Segment | Persona | Primary Message | Channel | Content Format | Cadence |
|---|---|---|---|---|---|
| Segment 1 | |||||
| Segment 1 | |||||
| Segment 2 | |||||
| Segment 2 | |||||
| Segment 3 |
09 Account Prioritization — The Tier System
Not all ICP accounts are equal. A Tier system prevents the most dangerous GTM mistake: treating all prospects the same. Your best reps should spend their best hours on Tier A accounts. Period.
| Tier | Definition | % of Target List | Accounts per Rep | Effort per Account | Approach |
|---|---|---|---|---|---|
| Tier A | Perfect ICP fit + active buying signal (trigger detected) | 10–15% | 20–30 | High — 15–30 min research per account | Hyper-personalized multi-channel. Custom first line. Phone + email + LinkedIn + warm intro. Track every signal. |
| Tier B | Good ICP fit, no active trigger yet | 25–35% | 50–80 | Medium — 5–10 min research per account | Personalized email cadence. LinkedIn connection. Monitor for triggers. Move to Tier A when trigger appears. |
| Tier C | Partial ICP fit (matches 3–4 of 6 dimensions) | 30–40% | 100–200 | Low — templated with light personalization | Semi-personalized email sequence. No phone. No LinkedIn. Re-evaluate quarterly. |
| Tier D | Poor fit or negative ICP match | N/A — remove from list | 0 | Zero | Disqualify. Do not contact. Remove from CRM sequences. If they inbound, disqualify in discovery. |
The math that matters: A rep with 20 Tier A accounts at 8% meeting rate = 1.6 meetings/month from top accounts alone. A rep with 200 Tier C accounts at 2% meeting rate = 4 meetings/month — but those meetings close at half the rate and churn at 2x the rate. 4 Tier A meetings are worth more than 8 Tier C meetings. Allocate time accordingly. Every quarter, audit your reps’ account distribution. If more than 30% of their time is going to Tier C accounts, your prioritization system is broken. The #1 job of a sales leader is protecting Tier A time.
10 The TAM / SAM / SOM Exercise
Your ICP directly determines your market size. TAM/SAM/SOM is not a theoretical exercise for pitch decks — it’s a practical planning tool for headcount, territory design, and revenue forecasting.
Definitions
| Term | Definition | Analogy |
|---|---|---|
| TAM (Total Addressable Market) | Total revenue opportunity if you had 100% market share in every possible segment | The entire ocean |
| SAM (Serviceable Addressable Market) | The portion of TAM your product can actually serve today (filtered by your ICP) | The fishing zone you have a license for |
| SOM (Serviceable Obtainable Market) | The realistic portion you can capture in 12–24 months given your sales capacity and competitive position | The fish you can actually catch with your boat and crew |
Worked Example
Scenario: You sell a CI/CD performance tool at $50K ACV to mid-market SaaS companies.
| Step | Method | Data Source | Result |
|---|---|---|---|
| 1. Count total companies | All SaaS companies globally with 50+ engineers | LinkedIn Sales Navigator, ZoomInfo | ~28,000 companies |
| 2. TAM | 28,000 companies × $50K ACV | Calculation | $1.4B |
| 3. Apply ICP filters | Filter: 50–500 eng, Series A–C, US/UK/DACH, cloud-native, using GitHub | LinkedIn Sales Nav + BuiltWith + Crunchbase | ~4,200 companies |
| 4. SAM | 4,200 companies × $50K ACV | Calculation | $210M |
| 5. Apply realism filters | Accounts your team can reach in 12–24 months. 3 SDRs × 200 accounts/quarter × 8 quarters = 4,800 touches. At 5% conversion = 240 customers. | Internal capacity model | 240 customers |
| 6. SOM | 240 customers × $50K ACV | Calculation | $12M |
Why this matters: TAM ($1.4B) is what you put on the pitch deck to show investors the opportunity is big enough. SAM ($210M) is what you use for strategic planning — it’s the actual addressable universe given your product and ICP. SOM ($12M) is what you use for next year’s revenue plan and hiring decisions. Most startups only calculate TAM. The companies that win calculate all three and hire/spend based on SOM.
Data Sources for Market Sizing
| Source | What It Gives You | Cost |
|---|---|---|
| LinkedIn Sales Navigator | Company count by size, industry, geography, growth rate. Headcount by function. | $80–$150/mo |
| ZoomInfo | Firmographic + technographic data. Revenue estimates. Org charts. | $15K+/yr |
| Crunchbase | Funding data, investor info, growth signals. | $29–$49/mo |
| BuiltWith | Technographic data: what tools/tech a company uses. | $295+/mo |
| Census Bureau / BLS | Industry-level data (total establishments, employees by NAICS code). | Free |
| Gartner / IDC / Forrester | Market size reports for your category. Useful for TAM validation. | $5K–$30K per report |
| G2 / TrustRadius | Competitive landscape. Number of companies evaluating your category. | Free (basic) |
Blank TAM/SAM/SOM — Your Company
| Step | Your Method | Your Data Source | Your Result |
|---|---|---|---|
| Total companies (unfiltered) | |||
| TAM | |||
| ICP-filtered companies | |||
| SAM | |||
| Reachable in 12–24 months | |||
| SOM |
11 ICP Review Cadence
Your ICP is not a one-time exercise. It’s a living document that should be reviewed and refined quarterly based on actual performance data. The companies that do this outperform the companies that set-and-forget their ICP by a wide margin.
Quarterly Review Framework
| Question | Data Source | Action if Answer is Negative |
|---|---|---|
| Which ICP segments had the highest win rate? | CRM: closed-won by segment | Double down on the winning segment. Increase Tier A allocation. |
| Which ICP segments churned the most? | CRM: churned accounts by segment | Tighten the ICP. Move this segment to Negative ICP or Tier C. |
| Which personas converted fastest? | CRM: sales cycle by initial contact persona | Shift outreach to the faster-converting persona. |
| What triggers predicted conversion? | Closed-won analysis: what trigger started the deal? | Build signal detection for the strongest triggers. Automate alerts. |
| Which accounts expanded the most? | NRR data by ICP segment | This is your best ICP. Weight expansion potential higher in scoring. |
| Which accounts consumed the most support? | Support tickets by account segment | If high-support accounts share ICP traits, add those to Negative ICP. |
| Are new segments emerging? | Inbound analysis: who’s finding you organically? | If a new segment is converting well, add it to the ICP and test outbound. |
The ICP maturity model:
Level 1 (Seed – Pre-revenue): ICP is a hypothesis based on founder intuition and 5–10 customer conversations. Review monthly.
Level 2 (Series A – $1–5M ARR): ICP is validated against 20–50 customers. You know what works. Review quarterly.
Level 3 (Series B – $5–20M ARR): ICP is segmented (you have 2–3 ICP segments with different personas and messaging). Review quarterly with data.
Level 4 (Series C+ – $20M+ ARR): ICP is predictive. You use data models to score accounts automatically. ICP informs product roadmap, not just sales targeting. Review monthly with RevOps.
The One-Page ICP Summary
After completing this worksheet, distill your ICP into a one-page summary that every person on the GTM team can reference. It should answer:
ICP One-Page Summary
WHO WE SELL TO [company type, size, stage, industry]
WHO WE DON’T [negative ICP: too small, wrong industry, wrong stack]
THE PAIN WE SOLVE [specific problem, in their words]
THE TRIGGER [what event makes them ready to buy]
WHO WE TALK TO [primary persona: title, role]
WHAT WE SAY [one sentence that makes them stop scrolling]
HOW WE PROVE IT [named customer + specific result]
ACV TARGET [$X — $Y per year]
SOM (12-MONTH) [$X based on Y reachable accounts]
Last updated: [date] · Next review: [date + 90 days]
The ICP is the single most important document in your GTM stack. Everything else — messaging, content, cadence, hiring, territory design, comp plans — flows from it. Get this right and everything downstream gets easier. Get it wrong and no amount of execution will save you.