Product and ICP training

Product and ICP training should teach a learner to recognize a customer problem, judge whether it matters for an account, and connect it to a useful product outcome. Start with the customer and the situation, then use product detail only when it helps the conversation. Use territory tiering as part of the lesson because it teaches the learner how the organization defines its ICP.¹ A learner who can describe a product but cannot identify what is wrong or why the account should care is not ready for outbound. Training should leave the learner with decisions they can make and questions they can ask.

Customer and ICP

Start with the customer's world. Give the learner enough context to recognize a fit before asking for product language.

Give new representatives time to learn the buyer persona during onboarding.² The first onboarding step should help a new hire understand customers well enough to develop the empathy needed for sales success.³

Run a workshop on company characteristics, persona characteristics, responsibilities, daily work, concerns, problems, and how the product helps.⁴ Then have each learner reconstruct the profile from the accounts they will work. Call the exercise "build your own ICP".⁵

Have the learner sort accounts into priority groups and explain each choice. Ask what makes the fit stronger, what would weaken it, and what the learner needs to learn before reaching out. Move on when the learner can explain the profile through account conditions instead of repeating a label.

Problems and personas

Once the fit is clear, focus on the problem the customer is living with. Product language is easier to use when the learner knows what needs to change.

Salespeople should receive problem training because many focus on describing the product.⁶ Ask each learner, "What are the top three problems you solve?"⁷ Have them map each problem to its pain and impact for each persona.⁸

A learner should know the problems they solve and the questions that uncover those problems.⁹ Listen for questions that investigate the situation behind the problem. If the learner can name a problem but cannot form a question that would reveal it, stay here before adding more product detail.

Use the learner's own words to test the map. Ask what the problem causes, who feels the effect, and what would make the issue worth discussing now. The answers should change with the persona while keeping the underlying problem clear.

Product relevance

Connect product knowledge to account reality. A product explanation should answer why this customer has this problem and what changes after action.

Understanding the prospect's business and product relevance helps representatives excel.¹⁰ Teach the business problem the company solves, the cost of doing nothing, signals of urgency, and expected customer outcomes.¹¹ The manager leading onboarding should teach representatives how to sell the product.¹²

Ask the learner to explain the product through a customer situation, then ask what happens if that situation remains unchanged. Follow with a question about why the product fits this persona. Move on when the learner can connect product capability to a customer outcome without reciting a feature list.

Account judgment

Use live account work to make the profile specific and usable. The learner turns customer knowledge into a reason to prioritize one account over another.

Study inbound leads and current customers, then inspect what was happening at the account before it came inbound.¹³ Ask: "Were there new hires? What tech were they using? What was happening internally?"¹⁴

Have the learner apply those questions to the accounts in the territory. The goal is to spot conditions that make a conversation timely and explain why those conditions matter. If the learner selects an account only because it resembles the profile on paper, ask what changed inside the account and what problem that change could create.

Keep the exercise close to the work. Use the account explanation to shape the first question the learner would ask, then check whether that question follows from the account conditions they named.

Observable proof

The learner explains

The learner states

The learner asks

The learner connects

The learner identifies

• The learner explains
• The learner states
• The learner asks
• The learner connects
• The learner identifies

End each lesson with a performance check. A topic can be discussed in a room without becoming usable behavior, so the signoff needs something another person can inspect.

Every checklist line should be something a manager can watch happen, listen to, or read.¹⁵ If an item cannot be verified in one of those ways, leave it off the checklist.¹⁶

Write checks such as:

• The learner explains why an account fits the profile.
• The learner states the problem and its impact for the persona.
• The learner asks a question tied to that problem.
• The learner connects the product to the outcome the customer wants.
• The learner identifies when to continue alone and when to involve support.

Use a written account brief, a spoken explanation, or a call exercise to collect the proof. Mark the item complete only when the learner produces the behavior without a prompt. Keep the wording of each check stable so a later review tests the same skill.

Field support

Product knowledge will have edges in live conversations. Give the learner a clear route to help so a gap in technical detail does not stop useful customer work.

Sales leaders and other support resources can bridge a rep's product knowledge gap.¹⁷ Support can bridge the technical product gap when reps know whom to involve and understand the problems the company solves.¹⁸

Teach the learner to name who they would involve, what context they would pass over, and what question still needs an answer. The BDR manager should learn and teach the ICP, the relevant persona, competitors, and product differentiators.¹⁹ Make those handoffs part of the practice instead of waiting for a live call to expose the gap.

What not to do

Keep the failure modes visible when you review training. They show up as a signoff problem or a targeting problem, and each requires a different correction.

• Do not treat attendance as proof that a rep can perform. A checklist that records attendance tells a manager nothing when it matters.²⁰
• Do not coach a rep on objection handling until you have isolated whether the rep is reaching the right people.²¹
• Do not train a rep into a system that does not yet exist.²²

Hand the learner an unfamiliar account and ask for an explanation of why it fits and what problem to test. When that answer is clear and verifiable, the learner has a practical basis for starting outbound and asking for help when product detail runs thin.