Prepare sales talking points for a specific prospect
This workflow connects public information about a prospect with your product’s value. It supports preparation for a tailored B2B pitch.
How this works
This workflow connects public information about a prospect with your product’s value. It supports preparation for a tailored B2B pitch.
Build a prospect-specific conversation aid that connects verified business context to plausible product relevance. Label hypotheses as questions so sales staff do not present guessed needs as facts about the prospect.
Before you start
Defined operating scope
Salespeople tailor pitches using public facts about each target account.
Required source material
Obtain Company name and website; Your product’s value proposition. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A public source describes an old strategy. Date it and seek current confirmation before using it as present context.
Prepare the inputs
- prospect_identity
- Required
Company and official domain
Resolve subsidiaries and similarly named entities.
- product_facts
- Required
Capabilities, limits and evidence
Use approved positioning and claims.
- research_scope
- Required
Relevant topics and freshness window
Exclude unrelated personal information.
- call_objective
- Required
Meeting stage and desired outcome
Choose talking points appropriate to discovery or evaluation.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check prospect_identity, product_facts, research_scope, call_objective before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected prospect_identity and any missing required fields.
Read the prospect’s website
- Read official product and company pages to establish what the prospect actually does.
- Verify each factual bullet against its source and retrieval date.
Checkpoint: A saved intermediate result for: Read the prospect’s website.
Find news, job openings, and public market context
- Collect relevant public developments and hiring evidence with dates, distinguishing active roles from archived listings.
- Check that objection responses stay within approved capabilities and separate assumptions from confirmed needs.
Checkpoint: A saved intermediate result for: Find news, job openings, and public market context.
Draft talking points and possible responses to objections
- Connect each product capability to a stated business context and draft a discovery question where the need remains hypothetical.
- Verify each factual bullet against its source and retrieval date.
Checkpoint: A saved intermediate result for: Draft talking points and possible responses to objections.
Save the brief in a shared document
- Assemble a concise battlecard with facts, relevance hypotheses, objection responses and source dates for salesperson review.
- Check that objection responses stay within approved capabilities and separate assumptions from confirmed needs.
Checkpoint: A saved intermediate result for: Save the brief in a shared document.
Package the result and unresolved work
- Verify facts and distinguish assumed needs from problems the client has confirmed.
- Research professional business context only.
Checkpoint: A document with company context and draft talking points. Unresolved items remain visible in the review record.
Decisions along the way
A public source describes an old strategy.
Date it and seek current confirmation before using it as present context.
Product relevance depends on an unconfirmed need.
Frame it as a question, not a diagnosed pain point.
The company identity is ambiguous.
Resolve the official domain and entity before adding research.
What you will produce
prospect-sales-battlecard-result.json
JSONA document with company context and draft talking points. Label proposed and completed states separately.
Include: prospect_id · verified_facts · relevance_hypotheses · discovery_questions · objection_responses · source_dates · status · evidence_reference · review_note
prospect-sales-battlecard-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving call_objective.
Include: source_reference · question · owner · next_action
Check the result
- Verify each factual bullet against its source and retrieval date.
- Check that objection responses stay within approved capabilities and separate assumptions from confirmed needs.
- Inspect prospect_identity and product_facts in both the original and output; confirm that record identity and interpretation survived the transformation.
- Verify facts and distinguish assumed needs from problems the client has confirmed.
When something goes wrong
A public source describes an old strategy.
Date it and seek current confirmation before using it as present context. Retain the affected evidence and recovery status.
Product relevance depends on an unconfirmed need.
Frame it as a question, not a diagnosed pain point. Retain the affected evidence and recovery status.
The company identity is ambiguous.
Resolve the official domain and entity before adding research. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare sales talking points for a specific prospect for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Prospect P-2 publicly operates three service locations. The offer supports shared scheduling; no source establishes scheduling problems.
Expected result
Synthetic expected result: Talking point: ask how scheduling is coordinated across locations. Do not claim the prospect has missed shifts or predict savings.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure preparation time per reviewed battlecard; unsupported prospect claims removed.
Stop or revise
The company identity is ambiguous. Pause affected records and apply this recovery: Resolve the official domain and entity before adding research.
Keep the scope clear
- Research professional business context only.
- The battlecard is preparation; outreach and commercial promises remain the salesperson’s responsibility.
Check before using
Verify facts and distinguish assumed needs from problems the client has confirmed.
Business activities
- Find and approach prospects
- Run sales conversations and proposals
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Company name and website · Your product’s value proposition
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow