Why should AI not generate the pain library itself?

Because LLMs are optimized for fluency, not truth. They produce plausible-sounding pain points that do not match what real customers experience, and a persona that reads well but performs poorly is the most common failure mode of AI-generated outreach.

How many customer interviews do you need per role?

3 to 5 per role usually surfaces the dominant pain archetypes. Beyond 5, marginal returns drop sharply because role-specific pains tend to cluster into 3 to 5 shapes. Fewer than 3 risks anchoring on a single customer's idiosyncrasies.

How often should the pain library be refreshed?

Quarterly is the working cadence. Roles change, market conditions shift, and a year-old pain library produces openers that miss the version of the role the prospect is actually living through this quarter.

What does the QA check for role-pain mapping?

The QA confirms the pain matches the role's actual accountability, the proof point matches the pain, and the rendered language reflects customer-interview phrasing rather than marketing-team paraphrase.

What is the 3P framework?

Pain (the role-specific problem), Persona (the role's decision shape and authority), and Proof Points (the credibility anchor that makes the claim land). Without all three, AI-generated messages become noise.

Role-Based Pain Messaging: How AI Should Map Pain to the First Touch

AI maps pain to the first touch correctly when it pulls from a human-curated pain library, anchors on the one pain the role actually owns, and lands inside the 3P framework. 82% of companies using personas improved their value prop when those personas were built around real problems.

Building The Pain Library

List 4 to 6 roles, interview 3 to 5 customers per role, cluster into 3 to 5 pain archetypes, map each pain to a measurable proof point, and pass the library to the AI as a prompt template. Refresh quarterly.

How AI Maps Pain

Identify the prospect's role, match to a pain archetype, render in customer-interview language, anchor with a proof point, and validate before send. AI assembles, humans curate.

3P Framework

Pain (role-specific problem from the library), Persona (decision shape and authority), Proof Points (measurable customer outcome). All three present means AI-generated cold email lands; any one missing means it breaks down.

Common Mistakes

Letting AI invent pain points, skipping customer interviews, mapping pains to the wrong role, using pain without proof, and letting the library go stale.