LAST UPDATED: JULY 2026
This is a deeper dive on the same topic. There's no workbook question here, since you already answered it in the 101 lesson. Read for the extra detail, then continue to the next topic below.
Advanced MSP Sales Enablement and Battle Cards
The 101 lesson established the core sales library: discovery question bank, objection-handling scripts, service one-pagers, pricing talk tracks, and the foundational structure of a battle card. This lesson covers the advanced work: building battle cards from verified competitive intelligence rather than guesswork, systematically analyzing wins and losses to improve every future deal, and measuring your sales process well enough to know exactly where prospects are being lost.
Going Deeper
Battle Cards Built from Verified Intelligence
A battle card is only as valuable as the accuracy of its competitive data. A card built from what you assume about a competitor (their pricing, their service model, their weaknesses) can actively damage a sales conversation when the prospect has more accurate information than you do. A card built from verified sources, their actual website, their public job listings, their Google reviews, their LinkedIn team size, structured into Jackdaw's competitive report format, holds up under scrutiny and becomes a genuine sales tool.
The verified battle card structure: competitor name and positioning summary (how they describe themselves); their stated strengths and where those claims are credible; their verifiable weaknesses (drawn from public reviews, not supposition); the specific objections a prospect might raise when comparing you ("they said they're cheaper" / "they've been around longer"); and for each objection, a fact-backed response that doesn't require you to claim anything you can't verify. Jackdaw's competitive intelligence report provides this structured data on your actual local competitors. Use it as the source of truth for every card you build.
COMPETITIVE INTELLIGENCE FOR DEEPER BATTLE CARDS
Battle cards built on guesswork become liabilities the moment a prospect knows more than you do. Jackdaw's competitive report gives you verified positioning, pricing signals, service depth, and differentiation data on the MSPs you're actually competing against — so every card reflects reality. See a sample report at facjackdaw.com.
Win-Loss Analysis as a Learning System
Most MSPs track whether they won or lost a deal. Fewer track why. The difference is a compounding advantage: an MSP that analyzes every loss for the specific decision factor that broke the deal (price, timing, a specific competitor, a gap in the service offering, a proposal that didn't address the real concern) gets systematically better at closing each time. An MSP that just tracks the win/loss ratio watches its close rate fluctuate without learning what moves it.
Build a lightweight win-loss interview protocol: within two weeks of a decision, send a one-paragraph email to every prospect, both wins and losses, asking one specific question. For losses: "We'd love to understand what drove your decision, so we can keep improving. If you're open to it, could you share the main reason you went with another provider?" Most prospects answer honestly if the ask is brief, personal, and non-defensive. The answers over 20 to 30 deals reveal patterns that no amount of internal guessing surfaces.
Sales Velocity Metrics
Sales velocity measures how quickly revenue moves through your pipeline: the number of qualified opportunities × your average deal value × your close rate, divided by your average sales cycle length. This single calculation shows you that increasing close rate by 10 percentage points does the same revenue work as shortening the sales cycle by 20%, and helps you choose which lever to pull first based on what the data shows is currently the biggest constraint.
Track four numbers in your CRM or a simple spreadsheet: qualified opportunities created per month, average contract value of closed-won deals, close rate (won / total decided), and average days from first contact to signed contract. Review these monthly and quarterly. Most MSPs who track them for the first time discover their cycle is longer than they thought and their close rate is lower than they assumed — both are immediately actionable once you can see them.
Proposal Architecture That Accelerates Decisions
A proposal that requires a prospect to read fifteen pages before reaching a price is a proposal designed around the vendor's needs, not the buyer's. Most prospects read proposals in this order: executive summary → pricing → terms → the rest if needed. Write for that order: executive summary that names their specific problem and your specific solution, pricing that's clear and contextualized, terms that are plain-language, and detail sections that answer anticipated questions rather than dumping everything you know about your service.
The fastest-closing proposals include a section explicitly labeled "What Happens Next" that tells the prospect exactly what they need to do to move forward, what you do after they sign, and what they can expect in the first 30 days. Removing ambiguity about the next step removes the most common reason for a "let me think about it" non-decision.
- Build your first verified battle card on your most frequently named competitor, using their website, public reviews, and Jackdaw's competitive report as sources. Replace every assumption with a verified data point.
- Send win-loss emails to your last ten closed deals (wins and losses both) using a single-question protocol. Log the answers and look for the top two repeated factors.
- Track your four sales velocity metrics (opportunities, deal value, close rate, cycle length) for the last 90 days. Identify which metric, if improved, would most increase monthly revenue.
- Rewrite your proposal template with the executive summary first, pricing second, and a "What Happens Next" section at the end.