ICP, Positioning
& Messaging
Playbook

01 / Start with evidence

Your ICP is a decision about where you can win.

An ideal customer profile describes the organization or customer situation most likely to gain meaningful value from your offer and sustain a workable commercial relationship. A persona describes the people inside that situation. Keep the two connected and distinct.

1. Review the full customer pattern. Compare retained and expanded customers with stalled, lost, and poor-fit opportunities. Include delivery effort, time to value, and reasons for leaving. A familiar logo or large contract alone does not establish fit.
2. Define the value-producing conditions. Record the recurring problem, current workaround, use case, operating complexity, technical environment, and implementation capacity that make your solution useful.
3. Write inclusion and exclusion rules. State what must be true, what makes the account a poor fit, and which facts remain unknown. Choose size or revenue boundaries only when evidence explains why they matter.
4. Separate fit from readiness. A high-fit company may have no current project. A funding announcement, new leader, or website visit is a research signal. Validate the priority, buying path, and timing.
5. Test a defined segment. Compare qualified conversations, wins, adoption, retention, and cost to serve by segment. Update the profile when evidence contradicts it.

02 / Map the people

Buyer, KDM, and user are responsibilities.

In this guide, the buyer coordinates the evaluation and purchase; the key decision-maker (KDM) has authority to approve or reject a material part of the decision; and the user works with the product or service. Ask how the purchase actually works. One person can hold several roles, and several people can share approval authority.

Ask directly: Who owns this problem? Who will use the solution? Who evaluates it? Who controls funding? Who can block the purchase? What must happen before approval? Record answers and unresolved access gaps.

03 / Customer-centered messaging

Lead with the change your customer needs.

The customer should be able to recognize their situation, see a worthwhile improvement, and understand why your offer is a credible route to it. Start the public message with that benefit. Use product capabilities and service deliverables to explain how you make it possible.

An internal positioning statement helps the team agree on the customer, problem, alternatives, difference, and evidence. Customer-facing copy then translates that strategy into a relevant reason to care. “We do X for Y who need Z” may organize the strategy, but the headline still needs to make the customer’s benefit clear.

Ask “so what?” twice. What does this capability let the person do differently? Why does that change matter to their work, their customer, or the result they own? A vague promise to “unlock insights” needs another translation into the decision or improvement those insights support.

Write from the customer’s situation.

If [customer situation] is making it hard to [important goal], [achieve a specific outcome] without [relevant burden or tradeoff]. [Company / offer] helps you do that through [credible mechanism], supported by [relevant evidence]. [Useful next step].

Use that structure to think, then write naturally. Lead with the strongest relevant benefit instead of forcing every message to carry every element. Explain the product category where it helps the customer understand what they are evaluating.

Make the benefit specific. Quantify it when supported.

Illustrative arithmetic, not a product claim: A recurring task taking four hours is reduced to one hour in a measured comparison. That is three hours saved, or a 75% reduction in time for that task. The message could say: “Imagine getting those three hours back each week for customer work.” Explain who was measured, the task, the period, and any limits before applying that result to a real offer.

A research benchmark can establish the cost of the customer’s current problem. It does not, by itself, establish the improvement your product will deliver. Support a speed or savings promise with relevant product or service evidence, keep conditions explicit, and distinguish measured results from estimates. When numbers are unavailable, use a concrete, defensible qualitative benefit.

1. Customer: Does the opening describe their priority or desired change?
2. Benefit: Can the person explain what becomes better and why it matters?
3. Difference: Is the proposed improvement meaningfully different from the current alternative?
4. Belief: Does relevant evidence support the claim and its scope?
5. Alignment: Can Marketing, Sales, Product, and Customer Success deliver and explain the same promise?

04 / Worked example

One solution. Three different conversations.

Illustrative example, not a client result: A B2B onboarding platform serves software companies with repeated cross-team implementation delays. Its core promise is a visible, coordinated path from signed agreement to first customer value. The example assumes the described capabilities exist; validate them for your own offer.

Before: “An innovative platform for streamlined onboarding.” After: “Help new customers reach their first useful outcome with a clear owner for every implementation step.” The persona layer explains why that change matters to each person.

05 / Align the teams

Give the message an owner and a place to work.

Name one narrative owner. Maintain a dated message brief with ICP, roles, promise, differentiators, approved evidence, objections, and sample copy. Review one campaign, one discovery call, one demo, and one onboarding handoff together. Repair contradictions before increasing distribution.

06 / Your working canvas

Build a message your team can apply.

These fields are for your working notes. They are not submitted to AMG or permanently saved by this page. Copy your answers before leaving or refreshing.

07 / Interpret the evidence

Measure understanding before scaling the message.

• If people cannot explain who the offer is for and why it matters, simplify the core narrative.
• If users engage but evaluation owners do not, investigate the business priority and purchase path before adding more feature copy.
• If evaluators are interested but implementation stalls, clarify feasibility, ownership, and rollout effort.
• If messages attract poor-fit interest, tighten audience criteria and exclusions.
• Compare comprehension, qualified responses, accepted opportunities, and adoption by role and segment. Use consistent time windows and small-sample caution. Clicks alone do not establish purchase intent.