Download worksheet
In this guide
  1. Use ICP as a decision rule
  2. Separate company fit and person relevance
  3. Build the worksheet
  4. Treat signals as hypotheses
  5. Prioritize reachable accounts
  6. Example of a useful rejection
  7. Validate against real conversations
  8. Ramp Year’s free-research fit
CompanyCan the product help?

Use case and delivery constraints define plausible fit.

BuyerCan we reach the decision?

Roles and approval requirements identify the path.

EvidenceWhat is confirmed?

Keep observed facts separate from assumptions.

Use ICP as a decision rule

An ideal customer profile describes which organizations are plausible customers for a product and why. It should help a seller include or reject an account. Firmographics are useful filters, but a company size or funding round does not establish a problem the product can solve.

Separate company fit and person relevance

Describe company characteristics, product use case, technical dependencies and delivery constraints. Then identify the people involved in the buying decision. A persona describes a role; the ICP describes an organization. A relevant job title alone does not mean its owner controls the budget or experiences the problem.

Build the worksheet

Record industry and use case, scale, operating model, trigger, current approach, plausible pain, annual economics, implementation dependencies, buying roles and explicit disqualifiers. Give each statement an evidence status: observed, buyer-confirmed or untested. Record the source and date so another seller can audit the reasoning.

Treat signals as hypotheses

Expansion, fundraising, hiring and software usage can suggest a useful question. They do not prove intent to purchase. Write “may need to investigate” where the evidence supports investigation. A seller tests the business impact in conversation rather than presenting an inference as private knowledge.

Prioritize reachable accounts

Two companies can match the same profile but differ in buyer access, urgency and implementation capacity. Prioritize an account with a specific use case and a reachable relevant stakeholder over one that merely looks prestigious. Retain the reason for the choice; a score without explainable inputs is hard to improve.

Example of a useful rejection

A hypothetical product requires access to event-level usage data. A prospect matches the industry and headcount filters but cannot provide the data and has no plan to do so. It may belong in the broad market while remaining unsuitable for the present campaign. Disqualifying it protects both buyer time and sales capacity.

Validate against real conversations

Compare assumptions with discovery evidence and lost-decision reasons. If several suitable companies do not recognize the problem, revisit the use case rather than increasing outreach volume. If they recognize it but cannot implement, inspect delivery dependencies. Keep evidence of successful and unsuccessful conversations to reduce survivorship bias.

Ramp Year’s free-research fit

Our free research is for B2B companies that are funded or have at least $1 million ARR and sell annual deals of $5,000 or more. That is a screening rule for our offer, not a universal ICP template. Paid engagement approval also depends on product readiness, sales cycle, economics and reachable market.

Method and limitations

This is Ramp Year’s original operating framework, not an empirical benchmark or client case study. Examples are hypothetical and are labeled accordingly. The worksheet supports a working discussion; it does not establish buyer demand. For related evidence, read our OpenAI enterprise analysis, Cursor adoption analysis and Clay ecosystem analysis.