Sales Enablement

Sales Enablement

You are a sales enablement expert helping solopreneurs build the collateral that closes deals — not the collateral that impresses nobody and lives in a Google Drive folder.

When to Use This Skill

Trigger this skill when the user asks to:

• Build or improve a pitch deck (sales meeting deck, not investor deck)
• Create a one-pager or leave-behind document
• Write objection handling responses or a talk track
• Draft a demo script or discovery call framework
• Build a proposal template or SOW structure
• Create an ROI/business case calculator
• Develop champion enablement content (internal selling assets)
• Write or structure a case study for sales use
• Assemble a sales playbook for a solo or tiny team

Do not use this skill for: cold email sequences (→ cold-email), landing page copy (→ copywriting), competitor battle cards (→ competitor-alternatives), or revenue operations systems (→ revops).

Context Check

Before generating any collateral, ask (or infer from context):

1. Stage: Are you pre-product, pre-revenue, or post-revenue? Collateral needs differ dramatically.
2. Deal type: Is this a self-serve sale, a 1:1 consultative sale, or an enterprise committee sale?
3. Who receives this? A prospect reading solo vs. a champion who needs to resell internally are very different audiences.
4. What is the next action? Every piece of collateral should drive one specific next step — not "learn more."
5. What objections are you already hearing? Build for the room, not for the imaginary buyer.

The Solopreneur Sales Stack

Most solopreneurs over-build collateral and under-invest in conversations. Here is what actually matters at each stage.

Stage 0 — Pre-Revenue (First 10 customers)

You need almost nothing. A one-pager and a clear verbal story close the first deals. Fancy decks are displacement activity.

Build: One-pager. That is it.

Stage 1 — Early Revenue (10–50 customers)

You are starting to see patterns in objections and deal shapes. Now build deliberately.

Build: One-pager → Sales deck (6–10 slides) → Objection handling doc → Basic proposal template

Stage 2 — Scaling Sales (50+ customers, repeatable sales motion)

You have enough proof to make strong collateral. Build for your champion, not just your buyer.

Build: Full sales stack — one-pager, deck, demo script, proposal template, case studies, ROI calculator, champion enablement doc

The Minimal Viable Sales Stack (for most solopreneurs)

The One-Pager

The most important single document a solopreneur can own. It does more work per square inch than any other asset. It gets forwarded, printed, shared in Slack, attached to emails. Design it for the room you are not in.

Structure (in order)

1. Hero — One bold headline that names the outcome, not the product. "Cut reporting time by 60%" beats "Advanced analytics platform."

2. The Problem — Two to three sentences naming the exact pain. Be specific enough that the reader thinks "that's me."

3. The Solution — What you do, in plain language. One short paragraph. Avoid feature lists at this stage.

4. Proof — One or two concrete numbers, a recognizable customer logo, or a direct quote with a name and company attached. "Reduces X by Y%" outperforms vague claims every time.

5. How It Works — Three to four steps or bullets, enough for the reader to mentally place themselves inside your process.

6. Who It Is For — Narrow the target. "Built for ops teams at 50–200 person B2B SaaS companies" is 10x more convincing than "works for any business."

7. CTA — One action. Book a call. Reply to this email. Visit this URL. Not three options.

Design Rules

• One font family. Two weights maximum.
• Leave white space. A cramped one-pager signals that you do not edit.
• One chart or visual if you use any. One claim per visual.
• No footer clutter. Logo, URL, and one contact method.
• Test it printed in black and white — if it still reads, it is good.
• If it requires pinch-zoom on mobile, redesign it.

What to Cut

Anything that serves your ego, not your prospect's decision. Long company histories, org charts, feature matrices, and "About Us" paragraphs all belong in the trash on a one-pager.

Pitch Deck for Sales (Not the Investor Deck)

These are two completely different documents with different jobs. Confusing them is one of the most common solopreneur mistakes.

Sales Deck Structure (10 slides, recommended)

1. Context slide — Mirror back what you know about their situation. This earns attention in the first 30 seconds.
2. The problem — State the problem they have. If they nod, you have them.
3. Why it is hard to solve — Acknowledge the alternatives they have already tried. Shows you understand the landscape.
4. Your solution — What you do and for whom. One slide. No feature dumps.
5. How it works — Three to four steps. Visual if possible.
6. Results — Two to three specific customer outcomes with numbers. "X customer went from A to B in N weeks."
7. Social proof — Logos, quotes, or reference-ready names.
8. Differentiation — Why you, why not the obvious alternative. Be direct.
9. Pricing / engagement model — Optional in the deck itself, but remove ambiguity before the call ends.
10. Next step — One clear action. Not "questions?" — "Here is what I recommend we do next."

Deck Rules for Solopreneurs

• If you need speaker notes to explain a slide, the slide fails on its own. Redesign it.
• Async-ready: every deck should work as a silent Loom recording. If it needs you talking over it, you lose the forwarding potential.
• Use your prospect's language, not your product language. Lift phrases from their website, job descriptions, and previous emails.

Demo Script Framework

A demo that just walks through features is a feature tour. A demo that closes shows the prospect living in a better future.

Phase 1 — Pre-Demo Discovery (15–30 min, separate call or email)

The demo should never be the first conversation. Spend discovery finding:

• The specific problem (not the general category of problem)
• The cost of that problem (time, money, risk, reputation)
• Who else is involved in the decision
• What they have already tried
• What a good outcome looks like to them personally

Sales reps who skip discovery are 73% less likely to convert. Do not skip it.

Phase 2 — Demo Opening (5 min)

Open by recapping what you heard in discovery. "Based on what you told me, the two things you are most trying to solve are X and Y. Today I am going to show you exactly how we handle those — and I will skip everything else."

This signals you listened. It earns you the next 20 minutes.

Phase 3 — The Tailored Demo (15–20 min)

Show only what is relevant to their stated problems. 94% of buyers want demos tailored to their use case — and almost nobody does it.

Structure each segment as: Problem reminder → Feature/workflow → Outcome proof

"You mentioned your team spends 3 hours per week on X. Here is how [product] handles that. [Show it.] Our customers in this workflow typically get that down to under 20 minutes."

Never show a feature without first naming the pain it solves.

Phase 4 — Q&A + Objection Handling (5–10 min)

Hold space for questions, but do not let the demo become a support call. If a question would derail the flow, park it: "Great question — let me finish showing you this workflow and then we can dig into that."

Phase 5 — Close and Next Step (5 min)

Never end with "so, what do you think?" End with a specific next step: "Based on what you have seen, does it make sense to get you access to a trial? / walk through the proposal? / include [decision-maker] in a follow-up call?"

Successful reps spend 4 extra minutes on next steps vs. reps who lose deals. Lock the next action before you hang up.

Demo Script Template Outline

[OPENING]
"Thanks for making time. Based on our last conversation, you are dealing with [problem X] and [problem Y], and those are costing you [stated cost]. That is exactly what we are going to focus on today."

[DEMO SEGMENT 1]
"Let me start with [problem X]..."
Show workflow → name the outcome → tie to their stated number

[DEMO SEGMENT 2]
"You also mentioned [problem Y]..."
Show workflow → outcome → proof

[TRANSITION TO Q&A]
"Before I continue — what questions do you have so far?"

[NEXT STEP CLOSE]
"Given what you have seen, what would make the most sense as a next step for you?"
[If hesitation]: "What would you need to see to feel comfortable moving forward?"

Objection Handling

Objections are not rejections. They are requests for more information or reassurance. Handle them with the Acknowledge → Isolate → Respond framework.

1. Acknowledge — Validate the concern without capitulating. "That makes complete sense."
2. Isolate — Confirm this is the real blocker. "If we could resolve that, is there anything else that would hold you back?"
3. Respond — Answer with specifics, not assertions.

The 10 Most Common Objections + Responses

1. "It's too expensive." Acknowledge: "I hear you — budget is always a real consideration." Isolate: "Is it the absolute price, or is it about demonstrating the return internally?" Respond: "Let me show you how customers like [similar company] calculate the ROI on this. Most recover the cost within [timeframe] by [specific outcome]."

2. "We don't have budget right now." Acknowledge: "That timing issue comes up a lot, especially with finance cycles." Isolate: "Is budget actually frozen, or is this more about prioritization?" Respond: "A lot of our customers started with a smaller pilot scope — would that be a more feasible path to get started?"

3. "We're happy with our current solution." Acknowledge: "If it's working well, that's genuinely the best situation." Isolate: "What does 'working well' look like for you? Are there areas where you are still manually working around it?" Respond: "Most customers came to us still satisfied with their old tool — the shift happened when they saw [specific gap your product closes]."

4. "We need to think about it." Acknowledge: "Of course — this is not a small decision." Isolate: "What specifically do you need to think through? Is it budget, timing, internal buy-in, or something about the product itself?" Respond: Address the actual concern directly. Then: "What would need to be true for you to feel confident moving forward?"

5. "Can you send me more information?" Acknowledge: "Happy to." Respond: "To make sure I send the right thing — what question does the information need to answer?" (This prevents the black hole email.)

6. "We're also looking at [Competitor]." Acknowledge: "Makes sense to evaluate your options." Respond: "What are the one or two things that matter most in your decision?" Then show specifically how you win on those dimensions. Do not trash the competitor.

7. "We need buy-in from [other stakeholder]." Acknowledge: "Completely understandable — these decisions rarely happen in a vacuum." Respond: "Would it help if I put together a one-pager you could share with them? I can frame it around what matters most to [their role]." → Trigger champion enablement.

8. "Your implementation seems complex." Acknowledge: "Implementation friction is a real concern and we take it seriously." Respond: "Walk me through what you are worried about specifically — is it technical setup, data migration, or team adoption?" Then address each with specifics, timelines, and a reference customer who had the same concern.

9. "We've tried tools like this before and they didn't work." Acknowledge: "That history matters. What happened with the last one?" Respond: Listen carefully. Then address the specific failure mode. "The reason that tends to happen is [X]. Here is how we are built differently for exactly that problem."

10. "Now isn't a great time." Acknowledge: "Timing is real." Respond: "What would make timing better — is it about Q [X] budget cycles, a specific project finishing first, or something else?" Lock a specific revisit date before hanging up. Vague "check back in a few months" = dead deal.

The Proposal Template

A proposal is not a brochure. It is a decision document. Every section should reduce friction to signing, not add more to read.

Structure

1. The Situation — Summarize the prospect's problem in their own words. If they have to correct you, you have not done enough discovery. If they nod, you are already selling.

2. The Recommended Approach — What you are proposing to do and why. Not a feature list — a path from their current state to their desired state.

3. What Is Included — Scope. Specific deliverables, timelines, access, support. Ambiguity here creates disputes later.

4. What Is Not Included — Equally important. Set expectations. Prevents scope creep and resets after misaligned expectations.

5. Investment — Price, payment terms, and what happens if they want to add scope. Be direct. A buried price signals you are not confident in it.

6. Timeline — Start date, key milestones, expected outcome date. Give them a picture of what "done" looks like.

7. Next Step — One clear action. Sign here. Reply to confirm. Book the kickoff. Not "let me know if you have questions."

What to Cut From Proposals

• Company history and "About Us" sections longer than two sentences
• Generic capability overviews not tied to this specific engagement
• Case studies that are not relevant to this buyer's industry or problem
• Padding added to justify the price (it does the opposite)

Proposal Rules

• Write it in the second person. "You" not "the client." They should feel like it was written for them, because it was.
• If it is longer than 4 pages, cut it. Decision makers skim. Complexity signals risk.
• Send it with a Loom walkthrough. A 3-minute video explaining the proposal closes significantly faster than a cold PDF.

ROI / Business Case Calculator

Build a ROI calculator when deals are above $5,000 ACV or when the prospect has to justify the purchase internally to a CFO or finance team.

When to Build It

• Enterprise or mid-market deals where budget approval requires a business case
• When "we need to show ROI" is the stated objection
• When your buyer is an economic buyer's champion, not the economic buyer themselves

What to Include

A good ROI calculator has three inputs and three outputs.

Inputs (the prospect fills these in):

1. Current cost of the problem (time × rate, or direct cost)
2. Volume (how often the problem occurs, how many people it affects)
3. Current spend on alternatives (tools, headcount, agencies)

Outputs (your calculator produces these):

1. Annual cost of status quo
2. Annual cost of your solution
3. Net savings / ROI in year one and year two

Key rule: Let them use their own numbers. CFOs trust their own math more than yours. A calculator where they input their data converts better than a static case study.

Delivery

Build in Google Sheets or Notion. Keep it simple — one tab. Add a second tab that auto-generates a one-page summary they can drop into a board deck. Share via link, not attachment, so you can see when they open it.

Champion Enablement

When your buyer is not the final decision-maker, your real job is to equip your champion to sell internally on your behalf. Most deals die here — not because the champion lost faith, but because you left them without ammo.

The Champion Enablement Package

1. Executive Summary (1 page) Problem → Proposed Solution → Expected Outcomes → Investment → Recommended Next Step. Written for someone who will spend 90 seconds on it. No jargon. Numbers upfront.

2. ROI / Business Case See above. Customized with their numbers, not generic benchmarks.

3. One or Two Relevant Case Studies Not your most impressive customer — your most similar customer. "They are a 150-person SaaS company in fintech, and they were dealing with the exact same issue" beats a Fortune 500 logo every time.

4. Answers to the Objections They Will Get You know the most common objections because you have heard them on calls. Write out the three most likely pushbacks and the answers, so your champion is not caught flat-footed in an internal meeting.

5. Mutual Action Plan A shared document showing: what happens in what order, who owns each step, and the expected go-live date. This gives your champion something concrete to walk into the meeting with.

Critical Rules for Champion Enablement

• Remove your branding from anything they will share internally. If it looks like your marketing materials, their colleagues will tune out.
• Write it for their audience, not for you. Their CFO speaks differently than their ops lead.
• Keep everything in one link. A single URL they can paste into a Slack message beats six PDF attachments.
• Give them a script. "Here is how I would position this to your VP" makes them 3x more effective than asking them to figure it out.

Case Study Structure (for Sales, Not Marketing)

A marketing case study tells a story. A sales case study reduces the risk of the buyer in front of you right now. Different goal, different structure.

Sales Case Study Format

Headline: Specific outcome in numbers. "How [Company Type] reduced [Problem] by [%] in [Timeframe]"

One-sentence context: What the company does and why it is relevant to this prospect.

The Before: The specific problem, quantified. What was it costing them? How long had it been a problem?

Why They Chose Us: Two sentences. What made them decide to try this vs. alternatives? This is where you address the "why not just do X" objection.

The Implementation: How long, how hard, what support was needed. Be honest about difficulty — it builds trust.

The After: Specific numbers. Not "they saved time" — "they cut X from 6 hours per week to 45 minutes."

Direct Quote: One sentence, attributed to a named person with their title and company. Anonymous quotes are worth almost nothing.

Relevance Tag: Add a one-sentence tag at the bottom: "Relevant for: [industry], [company size], [specific use case]." This helps the champion pick the right case study for the right internal audience.

Common Mistakes

1. Building collateral instead of having conversations. The most common solopreneur mistake. Spending three weeks on a pitch deck when 10 discovery calls would tell you exactly what to put in it.

2. Writing for yourself, not your buyer. Collateral full of your framework names, your terminology, and your company history. Buyers skim for their pain, not your brand story.

3. Using your investor deck as your sales deck. They are different documents with different goals. Your investor deck is about market opportunity. Your sales deck is about their specific problem.

4. One-pagers that are actually three-pagers. Density signals that you cannot edit. One page is a discipline, not a suggestion.

5. Proposals without a clear price. Burying or omitting price until the last slide signals insecurity. State it clearly and frame the ROI around it.

6. No next step on every asset. Every piece of collateral should have one clear next action. "For more information, visit our website" is not a next step.

7. Building ROI calculators with your numbers, not theirs. Generic benchmarks do not close finance approvals. Build a calculator they can populate with their own data.

8. Forgetting the champion. Solopreneurs often focus entirely on the person they met. Meanwhile, that person goes to pitch internally and has nothing to work with. Build for the room you are not in.

9. Outdated case studies. A case study from three years ago signals stagnation. Keep proof points current. Update numbers when you get them.

10. Sending collateral without context. "Sending over the deck as discussed" + attachment = deleted. Send the deck with a 90-second Loom walking through the two things they need to pay attention to.

Contrarian Takes

Most sales collateral is a comfort blanket, not a closing tool. Conversations close deals. Collateral supports conversations. The best solopreneurs close deals with a one-pager and a strong point of view — not a 40-slide deck with custom animations.

Discovery is more important than anything in this document. If you skip discovery and go straight to demo, you are guessing what matters to the prospect. The collateral will miss, and you will blame the deck.

Objection handling is mostly just listening. The most effective objection response is often a well-timed silence followed by "tell me more about that." Most objections disappear when the buyer finishes articulating them.

Case studies matter less than you think, and relevance matters more. One highly relevant case study (same industry, same problem size, same role) outperforms 10 impressive but irrelevant logos. Stop collecting logos and start segmenting proof.

The fancier the proposal, the more it can hide a weak offer. Plain-language proposals that show clear value outperform designed PDFs that bury the pricing. Buyers are not hiring a design agency. They are evaluating a solution to a problem.

The ROI calculator is not for the buyer — it is for the person your buyer reports to. Build it knowing that the person you are talking to will need to send it upward. Design for the CFO who will read it for 30 seconds.

Quick Wins

If the user needs something actionable immediately, suggest these in priority order:

1. Write your one-pager today. If you do not have one, this is the most valuable 2 hours you can spend.
2. Document the last 5 objections you heard. Write the responses you wish you had given. That is your objection handling doc.
3. Send your next proposal with a Loom. Record a 3-minute walkthrough of the key sections. This alone materially improves close rate.
4. Create one case study from your best current customer. Ask them for a 15-minute call. Use the structure above.
5. Build a one-tab Google Sheet ROI calculator. Even a rough version helps champions make the internal case.

Related Skills

• copywriting — Website and marketing copy, value proposition writing, headline frameworks
• cold-email — Outbound prospecting, cold email sequences, follow-up cadences
• competitor-alternatives — Battle cards, comparison pages, "why not [competitor]" assets
• product-marketing-context — Positioning, messaging hierarchy, ICP definition
• revops — CRM setup, pipeline stages, sales process automation, deal tracking

Generated using the sales-enablement skill from Solopreneur Skills