Turn Pricing Docs and Battlecards into Live Sales Answers with SalesGhost

September 6, 20269 min readBy SalesGhost Team

Set up SalesGhost with a pricing brief and battlecards, rehearse real buyer questions, and keep live answers current. Includes copyable examples and a test checklist.

To get useful live answers from SalesGhost, start with a current pricing document and a small set of battlecards, add them in Settings, then test the questions buyers actually ask. The document supplies the facts. The battlecards help explain how to handle a situation. Rehearsal tells you whether the combination is useful before you rely on it in a customer conversation.

This walkthrough uses a fictional software company to make the setup concrete. Its prices, policies, buyer questions, and suggested wording are illustrative, not SalesGhost pricing or a transcript of a measured product test.

What belongs in a document, and what belongs in a battlecard?

Material Put it here Example buyer question
Plan prices, included services, limits, and billing terms Knowledge document "Does that price include implementation?"
Discount approval rules and conditions Knowledge document "What changes if we pay annually?"
A short way to explain a pricing objection Battlecard "Your competitor is cheaper."
Approved competitor positioning and its supporting facts Reference document plus a short battlecard "Why would we switch?"

Keep the factual policy in a clear reference document. A battlecard should help the rep use those facts without introducing a different price, guarantee, or permission to discount.

You can start small. A current pricing brief and two useful cards are a better rehearsal setup than an archive of conflicting proposals. Check your plan's current knowledge limits before preparing a larger collection.

Step 1: Write a pricing brief that answers questions

A pricing page often explains what a product costs. A rep also needs to know what the price includes, where an exception requires approval, and what must be confirmed before making a commitment.

Use this as a starting document. Replace every example with your own approved information before uploading it.

Pricing brief: ExampleCo
Owner: Sales Operations
Reviewed: 6 September 2026
Applies to: New Growth-plan customers paying in USD

What is the price?
$80 per user per month, billed monthly.
Minimum purchase: five users.

What is included?
Product access and standard onboarding.
Standard onboarding means one remote setup session.

What is separate?
Custom data migration is scoped and quoted separately.
Do not promise migration before the implementation team reviews it.

Can we offer an annual discount?
An annual quote requires Sales Operations approval.
Reps must not promise a percentage discount in advance.

How do we handle an unsupported request?
Explain what the standard plan includes.
Record the extra requirement and confirm it with the owner.

The conditions matter as much as the headline price. "Onboarding included" is easy to overstate if the actual policy covers a setup session but excludes migration. Put that distinction next to the answer instead of in a separate appendix.

A review date and named owner are maintenance notes for your team. They do not create an automatic approval or document-refresh workflow in SalesGhost.

Step 2: Add the brief to SalesGhost

Open the knowledge section in desktop Settings and upload the document. SalesGhost supports PDF, DOCX, TXT, and Markdown. Wait for processing to complete before testing it on a call. The adding-sources guide explains uploads and website sources.

For this first test, a short text or Markdown file is convenient because you can inspect exactly what it contains. If the answer lives on your public website, a website source is another option. Avoid adding two versions of the same policy unless their differences and applicability are explicit.

Check the source's sharing settings. Material intended for a team needs to be shared with the people who should use it; do not assume a personal upload is available to a colleague. Test with the intended user's account before a team rollout.

If you already supplied company context during setup, make sure its description of your offer still agrees with the pricing brief.

Step 3: Create a short pricing battlecard

In Settings, open Battle cards and create a card for a situation you hear repeatedly. Describe the objection clearly and keep the response short enough to read while listening.

For the fictional ExampleCo policy above, the card's content could be:

Situation: The buyer says another vendor is cheaper.

Ask: "What does their quote include for onboarding and migration?"

Explain: Our monthly price includes product access and one remote
setup session. Custom migration is quoted separately.

Boundary: Do not offer an unapproved discount or claim that the
competitor excludes a service unless we have verified their quote.

Next step: Compare the same scope before discussing an annual quote.

This is sample content to adapt, not a special import format. Use the card's available fields to give the situation and response a clear home. See creating and maintaining battlecards.

The question gives the rep a useful next move without pretending to know the competitor's commercial terms. A good card can acknowledge that another offer may fit the buyer better.

Step 4: Rehearse the workflow on a test call

Install SalesGhost on the Mac or Windows computer you will use for meetings, complete its audio setup, and start a test call with a colleague. Follow the quick-start instructions if you have not captured a call before.

Have the colleague ask the questions naturally, in different words. Watch whether a useful suggestion appears during the conversation and compare its content with the source document. The live presentation differs between macOS and Windows; evaluate it on the platform each rep actually uses.

Use this checklist for the fictional policy:

Buyer question What a useful answer should preserve What would be a failure?
"What's the starting monthly cost for five people?" Five users at $80 each is $400 per month Quoting the per-user price as the total
"Will you migrate our old system as part of setup?" Migration needs separate scoping and a quote Treating all implementation work as included
"Can you give us 20% off for annual payment?" An annual quote needs approval Accepting the requested discount as policy
"Another vendor is cheaper. Why pay more?" Ask about comparable scope and explain verified inclusions Inventing a weakness in the competitor
"Can you guarantee a two-day migration?" The brief contains no such guarantee Making up a delivery commitment

These are acceptance criteria for your rehearsal, not guaranteed outputs. Live guidance is generated, and it can be late, incomplete, or wrong. An answer that sounds fluent still needs to preserve the actual policy.

Include the unsupported question deliberately. Do not assume the assistant will always stay silent when a source is missing. The rep must recognize an unresolved fact and confirm it rather than turn a suggestion into a promise.

Step 5: Fix the source of an unhelpful answer

Keep a small manual record of the question, the suggestion, and why it helped or failed. You do not need a complicated dashboard for the first rehearsal.

Symptom What to check
The answer is vague Does the document answer that exact question, including conditions?
The answer uses an old price Is an outdated upload, website page, or context note still available?
It works for you but not a teammate Has processing finished, and can that teammate access the source?
The card feels awkward to say aloud Shorten it and write it in the rep's normal speaking style
The suggestion is correct but too late Record the timing and scenario; do not assume rewriting the document will solve a runtime problem

The answer-quality guide covers common source problems. If the document is correct and accessible but retrieval still fails, preserve the example for support rather than repeatedly adding duplicates.

Step 6: Maintain the answers when your offer changes

When pricing or terms change, replace the old uploaded document with the current version and revisit any battlecards that repeat those facts. An uploaded file is a snapshot; editing the original file on your laptop does not update the copy already in SalesGhost.

After the replacement finishes processing, repeat the affected questions in a new test session. For a shared setup, have a teammate check the answer too. This verifies that the people who need the change can use it.

Review missing questions after real calls. Sometimes the fix is a clearer document. Sometimes the business has not decided the answer yet. Send that question to the policy owner rather than filling the gap with a plausible response.

Frequently asked questions

Can I upload my own pricing PDF?

Yes. SalesGhost accepts PDFs as well as DOCX, TXT, and Markdown. A short, clearly structured pricing brief makes it easier to check whether a suggestion preserved the right details.

Do battlecards replace the knowledge base?

They serve different purposes. Reference material supplies the facts and conditions; a battlecard provides a short approach to a recurring situation. Keep them consistent.

Does adding a document guarantee the right answer on every call?

No. Audio capture, transcription, retrieval, and generation all affect the result. Rehearse representative questions, including ones your sources cannot answer, and keep the rep responsible for commitments.

Will SalesGhost update an uploaded pricing sheet automatically?

Editing your local original does not update an uploaded copy. Replace the old source, wait for processing, and test the changed facts again.

Download SalesGhost and start with one pricing brief and the questions you hear most often.

References
Share this article

Try SalesGhost with full product access

Real-time AI coaching on Mac and Windows. No credit card required.