Sales Content Launch Toolkit

A starter kit for the first person (or first hire) inside a brand-new enablement function. It bundles the four assets every sales team asks for in month one — a battlecard, a proposal, a case study, and an objection script — plus the sequencing and governance to keep them alive past launch week.

---

1. Battlecard Template

[Competitor Name] Battlecard Last updated: _____ · Owner: _____ · Confidence level (High/Medium/Low — how recent is the intel): _____

Snapshot

• Who they are (2 sentences, no editorializing): _____
• Where they genuinely win: _____
• Where they genuinely lose: _____

Positioning Statement (fill in the blank)

"When prospects are choosing between us and [Competitor], we win because ___________, and we lose because ___________."

Landmines (plant these before the competitor comes up)

1. "One thing worth asking any vendor you're evaluating — ___________." (a question only your product answers well)
2. "Something that surprises people during the [Competitor] evaluation is ___________."
3. "The teams who've regretted their choice usually say the same thing: ___________."

Proof Points

Objection Responses (competitor-specific)

• "They said [Competitor] is cheaper." → "On sticker price, sometimes. Once you factor in [implementation time / hidden fees / the thing they charge extra for], most teams find total cost lands within [X]% of ours — and you get [differentiator] included. Want me to walk through the real math on your numbers?"
• "They said [Competitor] has more integrations." → "They do have a longer list. What matters is whether the 3-4 integrations you actually run through daily are solid — want to check those specifically instead of the full catalog?"
• "They said [Competitor] is the market leader." → "They've been around longer, that's true. Being the incumbent and being the best fit for where you are today aren't always the same thing — can I show you what changed for teams your size in the last 18 months?"

Traps to Avoid

• Never bash the competitor by name in writing (email, proposal) — verbal only, and always paired with proof, never opinion.
• Don't argue with a false claim directly — redirect to a differentiated proof point instead of a rebuttal.
• If you don't have current intel, say "let me confirm and get back to you" — a stale claim is worse than no claim.

---

2. Proposal Template

[Your Company] — Proposal for [Prospect Company] Prepared for: [Name, Title] · Prepared by: [Rep Name] · Date: [Date] · Valid until: [Date]

1. Where You Are Today (Situation Summary) [2-3 sentences reflecting back what was heard in discovery, in their words, not yours.]

2. What You Told Us Matters Most | Priority | Stated Goal | Source (call/date) | |---|---|---| | 1 | | | | 2 | | | | 3 | | |

3. Recommended Approach [2-3 sentence narrative of the recommended path — not a feature list.]

4. Solution Mapping | Your Priority | Capability We're Recommending | Business Outcome (ties to #2) | |---|---|---| | | | |

5. Investment | Tier | What's Included | Term | Investment | |---|---|---|---| | Recommended | | | | | Alternative | | | |

Payment terms: _____ · Included in year one: _____

6. Implementation Timeline | Week | Milestone | Owner (Us) | Owner (You) | |---|---|---|---| | 1-2 | Kickoff & data/access setup | | | | 3-4 | Configuration | | | | 5-6 | Training & rollout | | | | 7-8 | Go-live + early success review | | |

7. How We'll Measure Success | Metric | Baseline Today | 90-Day Target | 12-Month Target | |---|---|---|---|

8. Next Steps

• [Date] — Internal sign-off from [stakeholder]
• [Date] — Contract review with procurement/legal
• [Date] — Signature
• [Date] — Kickoff scheduled

Prepared by: _____ Accepted by: _____ Date: _____

---

3. Case Study Template

Title formula: "[Quantified Result] in [Timeframe]: How [Company Type] Used [Product] to [Outcome]" Example shape: "32% Faster Ramp in 90 Days: How a 40-Person SaaS Sales Team Cut New-Hire Time-to-First-Deal"

Snapshot — Industry: _____ · Company size: _____ · Use case: _____ · Results: [Stat 1] · [Stat 2] · [Stat 3]

The Challenge — [2-4 sentences: what was broken, what it was costing them, why now.]

Why They Chose Us — [2-3 sentences, ideally sourced from a direct quote.]

The Approach

1. [Step 1]
2. [Step 2]
3. [Step 3]
4. [Step 4, if needed]

The Results | Metric | Before | After | Change | |---|---|---|---|

"[Quote from economic buyer or champion — specific, not generic]" — [Name, Title, Company]

"[Quote from an end user — describes day-to-day impact]" — [Name, Title, Company]

What's Next for Them — [1-2 sentences on expansion/future plans — optional.]

[CTA: See if this applies to your team — Book a call]

---

4. Objection-Handling Script

Structure for every objection: Acknowledge → Reframe → Evidence → Commit-question.

1. "It's too expensive / we don't have budget."

• Acknowledge: "Totally fair — budget's one of the first things I'd want clarity on too."
• Reframe: "When you say 'expensive' — is that relative to the value, or bigger than what's currently allocated?"
• Evidence: "Most teams we work with find the cost of staying with the status quo — in lost deals, ramp time, or churn — runs 3-4x the investment in year one."
• Commit: "If we could show payback inside two quarters, would budget still be the blocker, or is there something else underneath it?"

2. "We're happy with our current solution."

• Acknowledge: "Good to hear — that tells me the fundamentals are already in place."
• Reframe: "Out of curiosity, what would 'even better' look like, if you had a magic wand?"
• Evidence: "A lot of the teams who talk to us start from exactly that spot — happy, not desperate — and the trigger ends up being a specific gap: [X]. Does that ever show up for you?"
• Commit: "If nothing changes in the next 12 months, are you fully confident you hit [their stated goal]?"

3. "We need to think about it / loop in the team."

• Acknowledge: "Makes sense — this shouldn't be a one-person call."
• Reframe: "So I don't waste your time chasing — will the team be weighing the approach, the price, or whether this is a priority at all?"
• Commit: "Can we put 20 minutes on the calendar with them while it's fresh, rather than let it go quiet?"

4. "Not a priority right now."

• Acknowledge: "Appreciate you being straight with me."
• Reframe: "Is it not a priority compared to other initiatives, or is the pain just not big enough yet?"
• Evidence: [cite your cost-of-inaction proof point]
• Commit: "What would need to be true for this to move up the list — and is that likely this half or further out?"

5. "Just send me some information."

• Acknowledge: "Happy to — I want what I send to actually be useful, not a generic deck."
• Reframe: "Two quick things so I tailor it: what's the #1 outcome you're chasing this year, and who else would read this?"
• Commit: "Once you've had a look, does a 15-minute follow-up Thursday or Friday work?"

---

5. Launch Sequencing Checklist (First 30 Days)

Week 1

• Interview 3-5 top reps on what they currently improvise without
• Draft battlecard for competitor #1 (whichever shows up most in deals)
• Identify best existing customer for case study #1; clear it with the customer/legal

Week 2

• Finalize battlecard #1; get sign-off from a senior AE + sales leader
• Draft proposal template; test it on one live deal
• Conduct case study interview #1

Week 3

• Ship objection-handling script; roleplay it live in a team meeting, not just email it
• Draft case study #1 from the interview; get customer approval
• Identify competitor #2 for the next battlecard

Week 4

• Publish the content governance page and assign owners
• Run a 30-minute "content library launch" session with the full team
• Put the review cadence on the calendar now, not later

---

6. Content Governance One-Pager

Feedback loop: any rep can flag stale or wrong content via [channel/form]; the owner has 5 business days to respond.