TLDR
An ideal customer profile, or ICP, describes the kind of customer your startup is choosing to serve first. For a B2B company, it usually describes the account: its situation, the work it needs to do, and the conditions that make your product a sensible fit. The people involved in buying belong alongside that account description.
For a bootstrapped or pre-seed team, a useful profile can fit on one page. Include the customer situation, important problem, current approach, reason to consider change, buying roles, requirements you can meet, reasons to say no, and evidence behind the choice.
Use the profile to decide which conversations deserve attention this week. Keep fit separate from buying readiness. A company can match your intended audience and still have no current reason to buy. Another can be enthusiastic and willing to pay while needing a product you cannot responsibly deliver.
This guide includes a copyable template, two fictional examples, a practical way to sort accounts, and a review routine for founders with little customer data. The examples illustrate decisions; their numbers are not market benchmarks.
Start with a provisional profile, test it against real situations, and keep the unknowns visible. A polished description is a working choice about where to learn and sell. It becomes more useful when evidence changes that choice.
Quick Verdict
Your first ICP should help two founders make the same decision about a potential customer. If one calls an account ideal and the other cannot explain why, the profile needs clearer criteria.
Begin with the work and circumstances that make your offer relevant. Add industry, company size, location, or technology only when those attributes explain a meaningful difference in need, adoption, or your ability to serve the account.
Keep a small set of essential conditions and a short list of questions that remain open. Avoid a detailed score that makes uncertain assumptions look measured. An explicit “we do not know yet” is more useful than a fabricated budget or urgency rating.
The one-page document should change an action: who you contact, which example you show, what you build next, or which request you decline. If it never affects those choices, it is describing your aspirations rather than guiding your work.
What Is an Ideal Customer Profile?
An ideal customer profile is a description of customers for whom your offer is a strong fit and whom your business can serve well. In this guide, the focus is an early B2B startup choosing its first repeatable customer situation.
HubSpot Academy's ICP worksheet frames the profile around attributes needed for customer success and distinguishes a B2B company-level profile from a B2C market segment. It also recommends grounding the profile in customer information and shared sales and marketing judgment.
For a team of three, those functions may belong to the same founders. The underlying question still matters: can this customer get a worthwhile result from the offer you can deliver today, through a buying and implementation process you can support?
For example, “small businesses that want to grow” offers little guidance. “Small implementation consultancies that repeatedly hand a signed project from the founder to a delivery lead and lose important scope details during that handoff” gives you a specific situation to investigate.
The narrower statement does not prove that those consultancies will buy. It tells you where to look for evidence and which alternative situations to keep separate. That is enough for a useful first version.
ICP, Buyer Persona, and Sales Qualification Serve Different Decisions
The ICP answers which accounts belong in your focus. A buyer persona or role description answers which people inside those accounts care about the work, evaluate a change, or approve spending. Qualification asks whether a particular opportunity is worth pursuing now.
A consultancy may fit your profile because it runs several simultaneous client implementations and has a recurring handoff problem. Its founder may approve the purchase, while a delivery lead uses the tool and a project manager helps evaluate it. Those roles should not be collapsed into one imaginary buyer.
That same account may have no active opportunity because its team is busy with an existing rollout. Keep it in the appropriate relationship context without pretending that company fit means buying intent. A sales stage should describe observed progress with that account.
A target market is broader still. It can describe an industry or group you might eventually serve. Your first ICP is the portion you choose to prioritize with your current offer, team, and learning capacity. It is reasonable for the long-term market to be wider than this month's operating focus.
This distinction prevents a common planning problem: using a broad market slide as the rule for daily prospecting, then wondering why every conversation needs a different product demonstration.
Choose the Offer and the Decision First
A profile is difficult to write when the offer changes every time someone asks what you do. State the current job your product or service helps a customer complete, the scope you can deliver, and the result you want to investigate.
For a fictional handoff product, the offer might be: help a small consultancy transfer agreed scope, open questions, and kickoff responsibilities from sales into delivery. It does not yet manage the entire project, replace accounting, or build a customer portal.
That boundary matters. A large account needing a full project platform could be attractive in the abstract while being a poor first customer for this offer. Your profile should reflect the product you can support, not the roadmap you might eventually build.
Then write the decision the profile will guide. “Choose the next group of companies for founder conversations” is a practical starting point. “Decide whether to focus the next release on consultancy handoffs or internal agency approvals” is a different decision and may require comparing two separate profiles.
Give the document a date and owner. Record which offer it describes. When the offer changes materially, revisit the profile instead of applying yesterday's criteria to a different product.
Start with the Evidence You Actually Have
If you have customers, review more than the accounts with the largest contracts. Consider who adopted the intended workflow, what helped them reach a useful result, what support they needed, and whether the relationship remained workable after the sale.
Include customers who struggled, left, or decided against buying. They may reveal missing conditions: someone had to own setup, the customer needed a capability you lacked, or the original problem was less important than it sounded during evaluation.
Keep these accounts as individual cases before looking for patterns. Record the sequence and context. A customer who joined through a founder's personal network may have bought because of trust that your next prospect will not share.
If you have no customers, start with a hypothesis grounded in what you can observe. You might know the workflow from relevant work experience, have spoken with potential users, or have a prototype that addresses a specific task. State the basis and its limits. Do not invent a history of successful accounts to fill the template.
Use three evidence labels: observed directly, reported by a participant, and assumed by the team. These labels are a simple editorial convention for your document. They are not a formal certainty scale. Link to the supporting note and say what remains unanswered.
The One-Page Ideal Customer Profile Template
Copy the following outline into a document. Keep each answer short enough to use during a conversation or account review. Put detailed research in linked notes so the profile stays readable.
- Version and owner: Date, responsible founder, and current offer.
- Customer situation: The type of organization and the relevant workflow or operating condition.
- Problem worth investigating: What goes wrong, for whom, and why the consequence matters.
- Current approach: How the customer handles the work today and what that approach does well.
- Reason to consider change: An observed event or condition that could make a new approach relevant.
- People involved: Who does the work, who evaluates a change, and who can approve it.
- Conditions for success: What must be true for the customer to adopt and benefit from the current offer.
- Reasons to set an account aside: Requirements or circumstances outside the current scope.
- Evidence and uncertainty: Supporting cases, contradictions, assumptions, and the next question to test.
- Operating decision: Who you will focus on next, what you will do, and when you will review the choice.
Summarize the profile in one sentence: “We are focusing on [customer situation] dealing with [specific work or problem], where [conditions for success] are present; we are setting aside [important exclusions] while testing [remaining uncertainty].”
The sentence helps the team remember the choice. The fields explain how to apply it. Keep both; a memorable sentence alone can conceal important exceptions.
How to Fill In the Fields
1. Describe the customer situation in observable terms
Use words that let another founder recognize a possible fit. “Operationally mature” is difficult to evaluate consistently. “A delivery lead takes over after the founder closes a project” describes an operating arrangement you can ask about.
Add an industry or size range if it helps identify that arrangement. Explain why the attribute matters. Headcount might be a rough way to find companies with a separate sales and delivery role; it is not the underlying need.
Do not let a convenient search filter become an unquestioned requirement. If a smaller company has the same workflow, decide whether it belongs in the profile rather than excluding it because it falls outside a round number.
2. Name the problem and its consequence
Write the problem as something that happens during work. “Poor collaboration” is broad. “Delivery begins before the agreed exclusions and customer responsibilities have reached the project lead” gives you a situation to examine.
Then record the consequence you have evidence for: repeated clarification, a delayed kickoff, or a disagreement about what was promised. Keep estimates attached to their source and context.
Different consequences may imply different audiences. A handoff that is inconvenient once a quarter is not the same situation as repeated confusion across several active projects. Investigate frequency and importance without assuming that every instance deserves a new tool.
3. Understand the current approach, including its strengths
Your customer already has some way of getting the work done, even if it involves conversation, a document, and memory. Describe that method without treating manual work as inherently broken.
A founder may prefer a live handoff because it exposes ambiguity before work begins. A new tool that removes the conversation could make the process worse. Your offer may need to preserve the discussion while improving the information that supports it.
Record what the customer would lose by switching: familiarity, flexibility, existing records, customer participation, or a useful review habit. This keeps the profile connected to adoption rather than only to dissatisfaction.
4. Separate a change trigger from a convenient news event
A new hire, an increase in simultaneous projects, or a repeated handoff failure might create a reason to reconsider the process. A public funding announcement does not automatically mean a company needs your offer.
Write the causal connection you expect, then check it. “The founder is delegating delivery for the first time, so scope transfer may now need a more explicit process” is a hypothesis with a question behind it.
Keep the trigger provisional until the account confirms the situation. Use public signals to choose what to ask, rather than as proof of private priorities or permission to make a personalized claim you cannot support.
5. Map the people and the actual decision process
Identify who experiences the problem, who would use the offer, who needs to approve it, and who can block adoption. In a very small company, one person may cover several of these roles.
The UK Space Agency's customer profiling guidance distinguishes technical, executive, and end-user perspectives and includes adoption readiness. Its context is space-sector growth; the transferable lesson here is to investigate the different roles involved rather than assume one job title explains the whole purchase.
For your own profile, record what you need to learn about the decision. “Founder approves; delivery lead evaluates a real handoff” is more useful than a detailed fictional biography with no connection to how the account buys.
6. Write the conditions your current offer requires
List what must be present for adoption to work. The handoff product might need a named delivery owner, access to the agreed project scope, and a willingness to use the same brief at kickoff.
Include practical delivery constraints your team can verify. If the offer cannot support an essential integration or deployment arrangement, that limitation belongs in the account decision before someone promises a rollout.
Distinguish a firm requirement from something you are willing to test. A founder-assisted setup may be acceptable for an early evaluation. A permanent custom implementation for every account may conflict with the business you are trying to build.
7. Define exclusions without turning them into permanent rules
An exclusion explains why an account is outside the current focus. It might need a different core workflow, require a feature you do not offer, or lack anyone able to own the change.
State the reason precisely. “Not a fit because they require full project accounting before adoption” is actionable. “Too enterprise” hides the actual constraint and may cause you to overlook a manageable opportunity later.
Separate a structural mismatch from timing. “No implementation owner available this month” may justify a later conversation. “The central job is outside our offer” requires a different decision. Neither should disappear into a generic lost category without explanation.
8. Preserve the evidence that could change your mind
Attach the relevant case or note to important criteria. If you believe a separate delivery lead is necessary, show what led you to that belief and whether you have seen a counterexample.
Use short statements: “Reported in two interviews; not yet observed during a live handoff.” This makes the basis inspectable without pretending that a small sample establishes a market-wide pattern.
End with the uncertainty that matters most to the next decision. You may need to learn whether the handoff problem repeats, whether the delivery lead can adopt a new brief, or whether the founder will allocate time to a trial. Those are different questions.
Worked Example: A Software Startup with No Paying Customers
The following company and evidence are fictional. Imagine two founders building a focused handoff tool for small B2B implementation consultancies. They have a prototype and a few exploratory conversations, but no paying customers.
Their initial audience was “service businesses with five to fifty employees.” That description included solo-led agencies, consultancies, outsourced support teams, and companies whose main problem was scheduling field staff. Each conversation pulled the product in a different direction.
They write a provisional profile around a narrower workflow:
- Current offer: A shared brief that carries agreed scope, exclusions, open questions, and kickoff responsibilities from sales to delivery.
- Customer situation: A small implementation consultancy where a founder closes work and a separate delivery lead takes responsibility for execution.
- Problem: Important context has to be reconstructed after the sale, before the team can begin confidently.
- Current approach: A proposal, messages, and an informal founder handoff. The live conversation is useful and should remain.
- Possible trigger: The founder begins delegating several overlapping projects and can no longer personally explain every detail.
- People: Founder as possible buyer, delivery lead as daily user, project manager as a participant in evaluation.
- Success conditions: An owner for the handoff and access to an agreed scope; willingness to try the brief on one suitable project.
- Exclusions for now: Companies seeking a full project-management replacement or essential accounting features.
- Evidence status: Interview reports only; adoption and willingness to pay remain untested.
- Next decision: Investigate whether a real handoff can use the brief without adding duplicate administration.
This profile changes the next week of work. The founders seek people who have actually handed projects from sales to delivery. They prepare a demonstration around scope transfer. They postpone a scheduling feature that belongs to a different customer situation.
It also makes failure informative. If delivery leads already receive complete context and the real delay is customer availability, the founders have a specific assumption to reconsider. They do not need to reinterpret every polite interview as support for the original idea.
Worked Example: A Small Service Business with Mixed Clients
Consider a second fictional business: a three-person studio offering a fixed-scope customer onboarding redesign. It has completed several different projects and wants to choose a repeatable service focus.
The largest engagement looked impressive but required extensive custom work outside the original scope. A smaller client had a clear owner, access to the existing onboarding flow, and a specific adoption problem the studio could address. Contract size alone would have pointed toward the more difficult engagement.
The studio reviews its cases and writes an initial profile: B2B software teams with a live self-service onboarding flow, someone responsible for activation, access to the relevant product context, and capacity to implement a focused change after the engagement.
Its exclusions are tied to the offer. Teams seeking an entire product redesign are outside scope. Teams without a working onboarding flow need a different engagement. Teams unable to allocate implementation time may be suitable later, but are poor candidates for the current service.
The studio keeps price acceptance separate from delivery fit. A company may be able to pay while lacking the people or access needed to use the work. The profile helps the founders surface that issue before writing a proposal.
The next test is whether another suitable account can complete the same basic engagement without major reinvention. That question is more useful than declaring a winning segment from a handful of unrelated projects.
Sort Accounts into Focus, Investigate, and Set Aside
A small team can apply its profile without building a complicated lead score. Use three working groups and a brief reason for each account. These labels are suggested process conventions, not a required software configuration.
Focus: The essential conditions are supported by current evidence, no known exclusion applies, and there is a sensible next action. This does not mean the account is guaranteed to buy.
Investigate: The situation looks relevant, but a material fact is unknown. Record the one question that would change the decision. Unknown implementation ownership should not quietly become either a positive assumption or a rejection.
Set aside: A known requirement conflicts with the offer, or the situation belongs to a different workflow. Keep the reason and, where useful, the condition under which you would revisit it.
For the fictional handoff product, an account with a founder-to-delivery transition and an agreed evaluation could belong in Focus. An account with a similar structure but no confirmed handoff problem belongs in Investigate. A company mainly seeking field-staff scheduling belongs outside this product's current focus.
Keep a separate note for readiness: active evaluation, future timing, or no commercial discussion. This prevents the account group from becoming a substitute for an honest sales pipeline.
Test Whether Two Founders Apply the Profile Consistently
Before expanding a prospect list, have each founder independently review a few of the same account descriptions using the current profile. Compare the decisions and the reasons, not just the labels.
If one founder focuses on industry and the other focuses on workflow, clarify which criterion actually matters. If both assume buying authority from a job title, add the missing verification question. If every account lands in Investigate, decide whether the profile is too vague or your account information is simply incomplete.
Use the disagreements to improve wording. “Has a delivery team” might become “a named person other than the salesperson is responsible for starting the project.” The second description is easier to discuss with an account.
A solo founder can perform a similar check after a short interval: reread the cases without the original label and explain the decision again. The purpose is consistent reasoning, not a numerical reliability claim from a tiny exercise.
Keep one owner responsible for updating the document. Shared input helps, but several competing versions create different prospecting rules and make later results difficult to interpret.
Turn the Profile into Better Outreach and Demonstrations
The profile should give you a reason to start a conversation. Connect an observable situation to a question you can honestly ask. Avoid declaring that a company has a private problem solely because it matches your chosen industry or size.
For example: “You mentioned moving more project delivery to team leads. We are exploring how small consultancies transfer agreed scope at that point. How does your team handle the handoff today?” This is a fictional illustration of a relevant opening, not a claim about a particular company.
Use the same focus in a demonstration. Show the one workflow the account wants to evaluate, with its requirements and limitations clear. A broad tour can conceal whether the product solves the specific problem that made the account relevant.
Keep the conversation open to correction. The delivery lead may explain that handoffs are fine and that the real difficulty is changing scope later. Record the difference instead of forcing the account into your chosen story.
For a deeper interview structure, use the customer discovery questions guide. The ICP chooses a useful starting audience; discovery helps you understand what is actually happening within it.
Let the Profile Inform Product Choices Without Becoming a Veto
When a feature request arrives, ask which customer situation it serves and what evidence supports the need. A request from an account in your focus deserves examination, but it is not automatically the next feature to build.
Consider whether the request helps complete the central workflow, reduces an adoption obstacle, or creates a different product. For the handoff example, making unresolved scope questions visible may support the core job. Building a payroll system would require a separate case.
Requests from outside the profile can still reveal an opportunity. Keep them in a separate learning note with their context. That preserves the information without allowing every interesting conversation to rewrite the current plan.
If you choose an exception, name the tradeoff. State what the work will teach you, how much capacity it uses, and which commitment it displaces. An explicit experiment is easier to review than an accidental change in customer focus.
Use the profile to sharpen decisions while leaving room for evidence. A document that cannot be revised becomes another assumption the team defends instead of testing.
A Practical First-Month Test
Treat the first month as a learning plan, not a promise that the profile will be validated within thirty days. Recruiting, procurement, and product readiness can take longer. Keep dates as review points rather than substitutes for results.
Week one: Write the current offer and provisional profile. Review available customer cases or interview notes. Separate observed facts from assumptions and choose the uncertainty that most affects the next decision.
Week two: Find a manageable set of relevant accounts and investigate the actual workflow. Record how each account was selected so a convenient channel does not silently define your whole audience. Include a case that could challenge the profile.
Week three: Where appropriate, test the current offer in a concrete evaluation. Agree on what the customer will try, who will own it, and what would make the exercise useful. Keep research participation distinct from a buying commitment.
Week four: Review the cases together. Decide whether to continue, narrow, split, or replace the profile. Write the evidence behind the decision and the next uncertainty. The founder sales pipeline guide can help keep commercial next steps clear during this work.
Do not compare two groups as though only the customer segment changed if one received warm introductions and the other received unfamiliar outreach. Keep channel, offer, relationship, and product changes visible when interpreting results.
Review Outcomes Beyond the First Yes
An early sale is useful evidence about one buying decision. It does not tell you whether the customer will adopt the workflow, get the intended result, or remain a sensible account to serve.
Review the path after agreement: whether setup began, whether the intended user participated, what prevented progress, what assistance was required, and whether the offer was used in the situation you expected.
Keep those outcomes tied to individual cases while your sample is small. “Two accounts completed the handoff evaluation; one stopped because the delivery owner changed” is more informative than a percentage without context.
Also record the work your team supplied. A customer may appear successful because a founder manually performed a hidden service. That can be a useful early experiment, but it should not be mistaken for a repeatable product experience.
Use the result to revise the success conditions. Perhaps the profile needs an implementation owner or a better-defined starting event. Perhaps the product needs to improve before the customer definition changes. Do not attribute every adoption problem to the wrong audience.
When to Narrow, Split, or Change the ICP
Narrow when one identifiable situation repeatedly explains a better fit and the difference matters to your next actions. Narrowing should preserve a meaningful reason, not simply reproduce the characteristics of your favorite customer.
Split when two groups require materially different buying conversations, workflows, or delivery conditions. Keep separate hypotheses so evidence from one does not imply success in the other. A small team may still choose to work on only one group at a time.
Change when a central assumption no longer holds or the current offer has changed enough to serve a different situation. Preserve the previous version and the reason for moving on.
Continue learning when the evidence is too thin to distinguish a segment problem from an execution problem. Silence after a weak message is not conclusive evidence that the audience lacks the need.
A useful revision note has four lines: what changed, which evidence prompted it, which operating decision changes now, and when you will review the new version. This keeps revisions connected to work rather than to a new round of document polishing.
How Wave Supports the ICP Routine
Wave CRM provides Contacts, Companies, and Deals, giving the team separate places for people, accounts, and opportunities. Its Companies view includes company ownership, lifecycle status, size, revenue information, and interaction logs. These can support the relationship context around your customer-profile work.
Use a company record to keep the account recognizable and an owner responsible for the next step. Keep the actual reasons for fit and the evidence behind them in a concise shared note or document your team can find. Do not infer fit from a populated revenue or size field alone.
The Focus, Investigate, and Set aside groups in this guide are process suggestions. They are not claims about a built-in Wave ICP scoring system, and they should not overwrite the meaning of your existing lifecycle or sales stages.
As a real buying conversation develops, keep its next action distinct from the general customer hypothesis. The Wave CRM feature guide explains the product's account and opportunity workflow in more detail. Start with the records and responsibilities you need; add structure when it helps the team act consistently.
Use AI to Check the Document, Not Invent the Customer
AI can help identify unclear criteria or organize notes you are permitted to use. Give it the current offer, the profile, and the supporting evidence. Ask it to point out gaps rather than complete them with plausible details.
A useful prompt is: “Review this provisional ICP against the supplied notes. Identify criteria supported by evidence, assumptions, contradictions, and questions that would change our account selection. Do not infer budget, authority, private business conditions, or willingness to buy. Keep each observation tied to its source.”
Check the output yourself. A fluent explanation can combine unrelated accounts or turn a founder's interpretation into a customer fact. Preserve original notes and do not publish synthetic personas as real customer research.
Use AI suggestions as a review aid. The founders remain responsible for deciding which customers to serve and for understanding the evidence behind that decision.
Common Mistakes
Listing attributes without explaining them. Industry, headcount, and software stack can help locate accounts, but each should connect to need, adoption, or delivery. Remove fields that do not change a decision.
Choosing the biggest potential contract automatically. Consider whether your current offer can meet the account's needs and whether the relationship requires work your team can sustain.
Confusing fit with urgency. A suitable company may have no current evaluation. Keep timing and commercial progress separate from the account profile.
Defining success from friendly feedback. Positive reactions can encourage further investigation. They do not establish adoption, price acceptance, or a repeatable customer pattern.
Changing the profile after every conversation. Record exceptions, then review the cases together. Frequent undocumented changes make it difficult to know what you tested.
Keeping the same profile after the offer changes. A new delivery model or essential capability can change who is a good fit. Update the document's scope and evidence accordingly.
Collecting personal details that do not help the decision. Focus B2B criteria on the account, relevant roles, and work. A detailed personal biography rarely explains whether the company can use your offer successfully.
A Checklist Before You Use the Profile
- Does it name the current offer and the decision it supports?
- Can another founder recognize the customer situation?
- Does the problem have a concrete consequence?
- Have you recorded what the current approach does well?
- Are buying roles and adoption conditions explicit?
- Do exclusions explain a real constraint?
- Are assumptions and contradictory cases visible?
- Can an unknown account stay in investigation without being forced into a yes or no?
- Does the profile change outreach, evaluation, or product work?
- Is there an owner, a version date, and a review point?
If the document cannot answer these questions, improve the specific gap before making it longer. The goal is a small set of useful choices that the team can apply and revise.
Final Takeaway
Your first ideal customer profile is a practical commitment about where to focus the next round of learning and selling. Describe a real customer situation, state the conditions your offer needs, and make the reasons to set an account aside clear.
Use the template to keep evidence and uncertainty close to the decision. Apply it to a few real cases, compare what happens, and revise the profile when the evidence or offer changes.
When you need a shared place for the relationships around that work, explore Wave. Keep the setup small enough that maintaining it helps the next customer conversation.
FAQ
How do I create an ICP before I have customers?
Write a provisional profile around a specific workflow and the current offer. Label what comes from relevant observations, what potential users have reported, and what your team assumes. Choose the next investigation that could change the profile. You can begin with uncertainty as long as you preserve it.
How detailed should an ideal customer profile be?
Keep the working version short enough to use during account selection. A page with clear criteria, exclusions, and evidence links is a useful starting point. Store longer research separately. Add detail when it changes a decision, rather than because another template includes a field.
Is an ICP the same as a buyer persona?
For B2B work, the ICP usually describes the account and situation. Buyer roles describe the people who use, evaluate, influence, or approve the purchase. Keep both visible, but do not assume that the right job title makes the whole company a good fit.
Should company size be a strict requirement?
Only when size explains a real condition your offer depends on. Otherwise it can be a useful search hint. Check the workflow directly and allow evidence to challenge the range. A company outside the range may still have the exact operating situation you intended to serve.
Can a startup have more than one ICP?
Yes, especially when different offers serve different situations. Keep the profiles and evidence separate. For a small team, consider whether you can run distinct sales and delivery processes without losing focus. You can document an additional hypothesis while choosing only one to pursue actively.
What should I do with an interested account outside the ICP?
Understand why it is interested and what serving it would require. You can decline, revisit later, or run a bounded experiment. Record the exception and its cost to the current plan. Interest alone should not silently redefine the product or the customers you are prioritizing.
How often should I update the profile?
Review it at a regular decision point and when meaningful evidence or offer changes appear. A small team can begin with a monthly review while capturing new observations as they arrive. Preserve earlier versions so you can explain which criteria changed and why.
Does a completed ICP prove product-market fit?
No. The profile organizes a hypothesis and the evidence around it. Actual buying decisions, adoption, outcomes, and the ability to serve customers sustainably require further observation. Use the document to direct that learning rather than as proof that the market has been validated.



