B2B sales enablement workshop / 5 MIN READ
Help the buyer prepare for the meeting you will not attend
Build a compact internal evaluation package around the questions colleagues will ask.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
An internal advocate needs material they can understand, adapt and challenge in their own organization. Preparing for their meeting means respecting their purpose and decision process rather than handing them a disguised seller pitch.
What you will leave with: A champion meeting pack with the decision request, verified facts and unresolved questions.
Use this when
- A buyer contact will present the evaluation to colleagues.
- The seller is not invited to the internal decision meeting.
This does not authorize impersonating the buyer, contacting their colleagues directly or claiming they endorse a recommendation they have not accepted.
Ask what the internal meeting must accomplish
Salesforce’s strategic-selling guidance identifies an internal advocate in the buying organization. Ask that person what decision their colleagues actually need to make.
The meeting may authorize technical evaluation, allocate staff or compare approaches rather than approve a purchase. Confirm who will attend and what concerns are likely, using only information the buyer chooses to share. Ask what format would help them. A brief speaking outline may be more useful than a branded presentation, and the buyer should control how the material enters their internal process.
Build around the questions they expect
Organize the pack by likely decision questions: the problem being addressed, available options, relevant fit, required effort and unresolved conditions. Keep the supporting evidence close to the claim, but avoid flooding the advocate with every case study the seller owns.
Provide a short explanation they can use in their own words and a route to deeper approved material. Distinguish your supplied facts from the buyer’s internal assumptions. Do not invent organizational priorities, savings or implementation capacity to make the story sound complete. Flag any estimate as an estimate and identify who would need to validate it.
Prepare for reasonable challenges
Ask the advocate which question they would find hardest to answer. Provide an accurate response, a clear limitation or an offer of a later specialist discussion. Give them permission to say the answer is still unknown. They should not have to defend a seller’s unsupported commitment in front of colleagues.
Include alternatives and the consequences of waiting when those are genuinely relevant, without manufacturing urgency. Avoid scripting attacks on internal reviewers or competitors. A good package helps colleagues evaluate the choice fairly. If the product does not meet a mandatory requirement, show that gap rather than coaching the advocate to steer around it.
Agree the follow-through without taking over
Ask whether the buyer wants to review the pack together and what, if anything, they would like afterward. Make any contact with colleagues contingent on their explicit request and the appropriate authorization. Do not demand an internal meeting transcript as the price of helping.
After the meeting, invite the buyer to share the outcome and open questions they want addressed. Update the evaluation plan to reflect actual decisions rather than treating the meeting’s occurrence as approval. Retire outdated versions of the pack from the active path, and preserve the buyer’s edits instead of restoring seller language they intentionally removed.
Make the reasoning concrete.
A fictional operations manager plans to ask colleagues for time to evaluate a scheduling service. The seller sends a purchase-approval deck with projected savings the buyer has not checked.
Use the purchase deck unchanged
Opening: Ask the manager to present the seller’s full business case.
Hypothesis: The seller’s preferred story remains consistent.
Risk: The package asks for the wrong decision and contains unsupported internal assumptions.
Prepare the actual meeting request
Opening: Create a concise evaluation-time request with known fit, required staff input and open questions.
Hypothesis: Colleagues can decide whether further evaluation is worthwhile.
Risk: Purchase approval remains a later, separate decision.
The manager edits the outline and uses only the verified technical facts. The seller waits for the actual evaluation decision and answers requested follow-up questions through the agreed contact.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Meeting decision
What authority or resource is the buyer asking colleagues for?
Audience questions
Which concerns must the advocate be ready to address?
Fact boundary
Which statements come from the supplier and which need internal validation?
Unknown
What can the advocate honestly say remains unresolved?
Follow-through
What help has the buyer requested after the meeting?
Watch for the wrong conclusion.
- Preparing a purchase pitch for an evaluation-planning meeting.
- Inventing the buyer’s internal savings or capacity.
- Bypassing the advocate after helping prepare their meeting.
Your next action
Ask one buyer champion what decision their next internal meeting is meant to make, then remove material that serves a different decision.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Salesforce: Strategic Selling →Primary vendor practitioner guidance · Supports: The article identifies an internal advocate within a buying organization; the champion meeting package is original analysis.