Content Selection Diagnostic: Buyer Belief-Gap Card
A single-page pre-send diagnostic that forces three written answers before any content asset is chosen or sent. Stops pattern-matching and keeps every piece of content tied to a specific belief gap in the deal.
How to use it
Complete the three diagnostic questions for the specific contact and stage before opening any content tool or library. Use the asset-to-objective table to match your identified belief gap to the right asset type, then run the accountability check before hitting send. Review the failure-mode column honestly if you find yourself reaching for an asset before you have finished writing the belief gap sentence.
What's inside
- Three mandatory diagnostic questions to complete before consulting any content tool
- Word-for-word sentence stem for capturing the precise belief gap
- Four-row asset-to-objective mapping table covering case studies, ROI calculators, battlecards, and technical FAQs
- Named failure-mode column for each asset type drawn from common skill-atrophy patterns
- One-question accountability check to confirm the choice is deal-led, not tool-led
- "When NOT to send anything" section covering two named expensive errors
- Quick-reference format sized for printing or pinning to a deal review doc
Before you open the content tool, answer these three questions in writing.
Not in your head. Written down. The discipline is the point.
The Three Diagnostic Questions
Q1. What does this specific contact believe right now?
Write it as a plain statement, not a gap or a problem. What is actually true in their head today?
Example: "She believes her current process is slow but thinks the fix is hiring, not technology."
Q2. What do they need to believe in order to progress to the next stage?
Be precise about the stage. "Progress" is not enough. Name the next commitment.
Example: "She needs to believe that technology can close the throughput gap without adding headcount, so she will agree to a scoping call with her operations lead."
Q3. Which single belief gap sits between Q1 and Q2?
Use the sentence stem below. If you cannot complete it, you are not ready to select content.
Belief Gap Sentence Stem
"[Contact name] currently believes [Q1 statement], but to move to [next stage], they need to believe [Q2 statement]. The specific gap is [name the gap in one phrase]."
Worked example:
"Priya currently believes the problem is a resourcing issue, but to move to a scoping call, she needs to believe the root cause is process, not headcount. The specific gap is cause misattribution."
If your gap phrase is vague ("she needs more information", "she's not convinced yet"), stop. Go back to Q1 and Q2 and sharpen them before choosing any asset.
Asset-to-Objective Mapping Table
Match your named belief gap to the asset type designed to close it. If your gap does not fit cleanly into one row, the gap is still imprecise or the right asset does not exist yet.
| Asset Type | The belief gap it closes | What it must contain to work | Named failure mode |
|---|---|---|---|
| Case study | "This works for organisations like mine" (relevance and proof gap) | A named customer in the same sector, same scale, with a quantified outcome tied to the specific problem, not the product | Sending a case study to prove capability before the buyer has acknowledged the problem the case study solves. The buyer reads it as a sales brochure. |
| ROI calculator | "The financial return is real and specific to my situation" (value quantification gap) | Input fields the buyer can edit themselves, an output tied to their stated success metric, and a methodology note so finance can validate it | Sending financial modelling to a contact who does not own or influence the budget. It creates no movement and signals you do not know who you are talking to. |
| Battlecard / competitive comparison | "The alternative I am evaluating is the wrong choice for my situation" (competitive preference gap) | A direct, honest comparison on the criteria the buyer has named as important, not the criteria you prefer | Sending competitive content before the buyer has acknowledged they are evaluating an alternative. It raises the competitor's name, creates defensiveness, and hands them a reason to go back to the other vendor. |
| Technical FAQ / solution brief | "I understand how it works well enough to support it internally" (technical confidence gap) | Answers to the exact objections or questions the technical contact has already raised, written for a practitioner, not a buyer | Sending a technical document to an economic buyer who has not asked a technical question. It signals you have misjudged their role and slows the deal. |
The Accountability Check
Before you hit send, answer this question out loud or in writing:
"Can I defend this content choice to my manager without mentioning the content tool I used to find it?"
If your honest answer is "I chose it because it came up first in the search" or "it seemed relevant", do not send it.
If your honest answer is "I chose it because Priya's gap is cause misattribution and this case study shows a company in her sector fixing a throughput problem without adding headcount", send it.
The test is not whether the asset is good. The test is whether you can connect it directly to the named belief gap in the deal.
When NOT to Send Anything
These are not edge cases. They are two of the most common and expensive content errors in a live deal.
Scenario 1: The buyer has not yet acknowledged they are evaluating a competitor.
Do not send competitive content, comparison grids, or battlecard-derived messaging until the buyer has confirmed, explicitly or through their own questions, that a specific alternative is on the table. Surfacing a competitor's name yourself introduces optionality the buyer may not have considered. If they are already evaluating, ask them to name the criteria that matter to them before you send anything comparative.
Scenario 2: The contact you are sending to does not own or influence the budget.
Financial modelling, ROI calculators, and business case templates are wasted on a technical contact who has no budget authority and no remit to build an internal case. Worse, a technical contact who receives financial content may share it upward in an uncontrolled way, with no context, before you have shaped the narrative. Confirm who owns the financial decision before sending anything quantified. If the technical contact asks for financial data, your next step is to get in front of the person who does own the budget, not to satisfy the request via email.
Self-Diagnosis: Are You Pattern-Matching Instead of Reading the Deal?
Check yourself against these signals. If two or more are true, go back to the three diagnostic questions.
- You chose the asset in under 60 seconds of opening the content tool.
- You cannot name the specific belief gap without referring to the asset description.
- The last three pieces of content you sent were the same asset type.
- You are sending content to fill a gap in the conversation rather than to move a specific belief.
- You know the asset is good but you are not certain this contact will recognise themselves in it.
- You have not spoken to or heard from the buyer since the last asset you sent.
Quick-Reference Summary
| Step | Action | Pass condition |
|---|---|---|
| 1 | Write Q1: current belief | One clear statement, not a problem description |
| 2 | Write Q2: required belief to progress | Tied to a named next stage or commitment |
| 3 | Complete the belief gap sentence stem | Gap is named in one precise phrase |
| 4 | Match gap to asset-to-objective table | One row fits cleanly |
| 5 | Check the asset's required content | It contains what the table says it must |
| 6 | Run the accountability check | You can defend the choice without citing the tool |
| 7 | Check the "when not to send" conditions | Neither scenario applies to this contact and this moment |
If any step does not pass, stop. Either sharpen your diagnostic or accept that the right asset does not currently exist and make a different move.
The thinking behind this
Your Content Tool Knows Which Battlecard to Surface. Your Rep Has Forgotten Why. is the argument this resource puts to work.