Build an ICP to Guide Product, GTM & Fundraising Strategy

Stop building for everyone. Learn to create a data-driven Ideal Customer Profile (ICP) that defines your product roadmap, go-to-market plan, and hiring.

A powerful Ideal Customer Profile (ICP) goes beyond demographics to define the behaviors, pains, and goals of your best customer. Build it by interviewing your happiest users to understand their 'job to be done' and buying process. Use this data to focus your product roadmap, marketing, and sales efforts, and prove to investors you have a deep market understanding.

Key takeaways

Your Product Is Failing Because You’re Building for a Ghost

Most failed startups die from the same cause: they didn’t truly know their customer. They had a demographic sketch and a vague value proposition, but they were building for a ghost. An Ideal Customer Profile (ICP) is the exorcism.

An ICP is not a fluffy persona named "Mid-Market Molly." It's a rigorous spec sheet that defines your most valuable, successful, and profitable customer. This isn't a marketing exercise. It’s a strategic document that dictates your product roadmap, your go-to-market, and your hiring plan. When investors ask, "Who is your customer?" they’re testing you on this. A sharp ICP is proof that you have an obsessive, specific understanding of the person you're serving and the market you'll win.

Why Most ICPs Are Useless

Most founders create an ICP that's a list of demographics: "Our customer is a 25-35 year old urban professional making $80k a year." This tells you nothing about their needs, motivations, or buying triggers. A powerful ICP is behavioral and psychographic. It explains why they buy, not just what they look like.

A weak ICP describes attributes. A strong ICP describes motivations and context.

The Anatomy of a High-Signal ICP

Ditch the generic templates. A useful ICP is a living document built from customer interviews that answers these questions with extreme specificity. For B2B, you are profiling both the company (firmographics) and the person (the buyer/user) inside it.

1. Firmographics & Demographics (The ‘Where’ and ‘What’)

For B2B: Company Size (Employees & Revenue), Industry/Vertical, Funding Stage, Geography, and current tech stack. (e.g., US-based, 100-250 employees, Series B, $10-25M ARR, uses Salesforce and Marketo ). · For B2C: Age, Income Level, Location, Family Status, Career Path. (e.g., 30-40, household income $150k+, lives in a major suburb, has young children, works in a demanding professional job ).

2. Role & Responsibilities (The ‘Job Title’ vs. The ‘Actual Job’)

Go beyond the title on their LinkedIn. Understand their professional world.

Official Title & Seniority: e.g., Senior Product Manager, an individual contributor. · Core KPIs: What metrics are on their dashboard? What does their boss hold them accountable for? (e.g., User engagement, feature adoption, reduction in churn ). · Reporting Structure: Who do they report to? Who reports to them? This reveals internal pressures and influence.

3. The Job To Be Done (JTBD)

This is the most critical concept. Customers "hire" your product to make progress in their lives. What is the underlying job they are trying to get done? It’s never just "to use your software."

A founder doesn’t hire Stripe to "process payments." They hire it to "offload the complexity of PCI compliance so I can focus on my product," "increase conversion by offering Apple Pay," and "look professional to my first customers." They are buying back time and credibility.

4. Quantified Pains & Negative Consequences

"Wasting time" is not a pain. "Spending 8 hours a week manually copy-pasting data between spreadsheets, which caused a critical error in last month's CEO report" is a pain. Connect the frustration to a real consequence.

What task makes them feel inefficient or amateur? · What is the specific, quantifiable cost? Aim for hard numbers. (e.g., "$5k/month in wasted ad spend on the wrong keywords," "2 engineering sprints per quarter lost to debugging a legacy system" ). · What is the career or social consequence of failure? (e.g., "Losing credibility with the sales team," "My boss thinks our team isn't data-driven" ).

5. Desired Gains & Positive Outcomes

What does success look like for them ? This is the "after" state. It's what they’ll put on their resume or mention in a performance review.

The "Hero Scenario": What would make them look like a rockstar to their boss or their team? (e.g., "Shipping a project 2 weeks ahead of schedule," "Finding a key insight that doubles a conversion rate" ). · Personal Aspirations: How does this help them personally? (e.g., "Get promoted from Senior PM to Group PM," "Finally get home by 6 PM instead of 8 PM" ).

6. Watering Holes & Influencers

"Social media" is useless. "Arguing about log4j in the r/sysadmin subreddit and listening to the Acquired podcast" is actionable. Where do they go to learn and who do they trust?

Online: Specific newsletters (e.g., Lenny's Newsletter), podcasts, Slack/Discord communities, subreddits, and specific people they follow on Twitter/LinkedIn. · Offline: Which conferences do they actually attend (or aspire to)? What local meetups? · Trust Signals: Who has their ear? (e.g., "Recommendations from other VPs of Engineering," "Positive reviews on G2," "Analyst reports from Gartner").

7. Buying Process & Decision Criteria

Especially in B2B, you are not selling to one person. You have to map the full journey from trigger to purchase.

Trigger Event: What makes them start looking? (e.g., "Just got a new headcount," "Q4 budget planning," "A painful security audit" ). · The Buying Committee: Who is involved? Identify the Champion (who advocates for you), the Economic Buyer (who owns the budget), the User (who uses the tool day-to-day), and the Blocker (e.g., IT Security, Legal). · Budget & Approval: Get real numbers. (e.g., "Can expense up to $100/mo on a corporate card without approval," "Needs VP sign-off for anything over $10k/year," "CFO must approve all new software contracts" ). · Non-Negotiables: What are the absolute must-have features or certifications? (e.g., "Must have a SOC 2 Type II certification," "Must integrate natively with our existing Salesforce setup"). · Alternatives: What are they comparing you to? This always includes "build it in-house," "use a messy spreadsheet," or "do nothing and live with the pain."

The Anti-ICP: Who You Actively Repel

Just as important as who you serve is who you don't serve. An Anti-ICP is a clear definition of the customers who are a bad fit—they cost too much to acquire, are difficult to support, and are likely to churn. This focus is a sign of strategic maturity.

Examples: companies that are too large (need enterprise features you don't have), too small (can't afford your product), in the wrong vertical (have unique needs you can't meet), or teams that lack technical sophistication (will drain your support team).

Stating your Anti-ICP explicitly saves your sales team time and sharpens your positioning.

How to Build Your ICP (Without Lying to Yourself)

Your ICP must be built on evidence from the real world, not from assumptions in your boardroom.

Step 1: Identify Your "Believers"

If you have customers, find your best ones. Don't guess. Look at the data: Who has the highest usage, retention, and satisfaction? Who has referred other customers? Select 10-15 of these accounts to analyze.

Step 2: Conduct Customer Discovery Interviews

Reach out to people who fit your "believer" profile. Your only goal is to learn, not to sell. Use this template:

I'm the founder of [Your Company]. I'm doing some research to better understand the world of [their job, e.g., product managers at scale-ups].

You've been a fantastic customer, and I was hoping to ask you a few questions about how you handle [problem area]—not about our product, just your process.

Would you be open to a 20-minute chat sometime next week? It would be a huge help.

During the call, use open-ended questions about their past experiences:

"Walk me through the last time you had to [deal with this problem area]." · "What was the most frustrating part of that?" · "What other solutions have you tried? What was wrong with them?" · "What does success look like for you when it comes to [problem area]?" · "Where do you typically learn about new tools for work?"

Crucially: Record and transcribe these calls (with permission). Their exact phrasing is your most valuable source for future marketing and sales copy.

Step 3: Synthesize and Find Patterns

After the calls, block 3 hours to fill out the ICP framework above for each interview. Look for recurring words, pains, desired outcomes, and tools mentioned. The patterns that emerge across 5-10 interviews are the foundation of your v1 ICP.

Founder Mistakes to Avoid

The "Aspirational" ICP: Profiling the customer you wish you had (e.g., selling to C-level) instead of the one who is actually buying and using your product today (e.g., a manager-level champion). Be brutally honest with the data. · The "Frankenstein" ICP: Mashing two distinct segments (e.g., solo founders and enterprise teams) into one vague profile. If you serve multiple segments, they need separate ICPs. Pick one to dominate first. · The "Set It and Forget It" ICP: Your market will evolve, and your understanding will deepen. Your ICP is a living document. Challenge and update it every 6-12 months, or after any major product or market shift.

How to Apply This This Week

An ICP is only useful if it forces action. Here is your plan for this week:

Draft your v1 ICP Hypothesis: Spend 1 hour filling out the framework based on your current assumptions. This is your starting point. · Schedule 5 Customer Interviews: Use the email template above to reach out to your "believers" or prospects who fit your hypothesis. Get calls on the calendar. · Synthesize Your Notes: After each call, take 15 minutes to pull out key pains, desired gains, and direct quotes. Look for patterns. · Define One "Anti-ICP" Trait: Based on your research, identify one clear characteristic of a bad-fit customer. Write it down and share it with your team. · Rewrite Your Homepage Headline: Take the #1 pain point you just validated and use the powerful language your customers used to describe it. Change the headline.

Stop building for a generic "everyone." A sharp, specific ICP is the first step to building a product that a specific someone truly needs and loves.

Frequently asked questions

What's the difference between an ICP and a marketing persona?
An ICP is a strategic definition of the *company* and *buyer* that gets the most value from your product. A persona is a fictional character sketch used to represent a user segment. Always start with the ICP to define strategy before creating personas for marketing.
How many interviews are enough to build an ICP?
Start with 10-15 conversations with people who represent your hypothesized best customer. You're looking for recurring patterns; you can stop when you can reliably predict what they're going to say.
Should I have more than one ICP?
No, not at first. Serving two distinct ICPs is like building two different companies. Focus ruthlessly on winning one specific segment first before you even consider expanding to a second.
What if I'm pre-product and have no customers?
Your first ICP is a *hypothesis*. Your job is not to analyze existing customers, but to run discovery interviews with 15-20 people in your target market to validate that the problem you *think* they have is real and urgent.

Related fundraising guides (24)

The decks these companies actually used (1)

Recently published pitch deck teardowns (12)

Real pitch decks, broken down slide by slide (12)

Browse by topic (1)

Fundraising library · Pitch deck examples · Investor directory · Founder database