Transparency selling
Skill LeadMagic/gtm-skills/skills/sales-revops/transparency-selling
Execute Todd Caponi's Transparency Sale methodology — lead with flaws, build the "Our Flaws" slide, negotiate with radical honesty, use the 4.2-4.5 effect in positioning. Use when building pitch decks, handling objections, negotiating, or designing sales process. Triggers on: "transparency sale", "lead with flaws", "Todd Caponi", "radical honesty", "transparent selling", "our flaws slide".From its SKILL.md
npx -y skills add LeadMagic/gtm-skills --skill transparency-sellingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
8.7 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it
Transparency Sale (Todd Caponi)
Overview
The Transparency Sale by Todd Caponi flips traditional sales on its head: instead of hiding flaws and presenting perfection, you LEAD with your weaknesses. This builds trust faster, shortens sales cycles, increases win rates, and makes competing against you nearly impossible — because you've already said what competitors would try to weaponize.
Core Principle
Transparency sells better than perfection. Products with average ratings between 4.2 and 4.5 convert better than perfect 5.0 ratings. Buyers don't buy when they're convinced — they buy when they can predict. Leading with your flaws accelerates prediction and builds trust that perfection never could.
Arthur Dunn's Law (1919): "If the truth won't sell it, don't sell it."
When to Use
- "Build a transparency-based pitch"
- "Our Flaws slide"
- "Todd Caponi methodology"
- "Lead with weaknesses"
- "Radical honesty in sales"
- "Transparent negotiation"
Authoritative Foundations
- Todd Caponi — The Transparency Sale. Research on the 4.2-4.5 rating effect, the buying brain's resistance to influence, prediction over persuasion, and why negative reviews increase conversion.
- Arthur Dunn — Scientific Selling (1919). The original insight that truth is a sales methodology, not just a value. "If the truth won't sell it, don't sell it."
- Daniel Kahneman — System 1/2 thinking. Buyers' fast brains detect bullshit instantly. Transparency engages the slow brain productively.
Step-by-Step Process
Phase 1: Build Your Flaws Inventory
Before you can lead with flaws, you need to know them. Inventory honestly:
- Feature gaps: What does a competitor do that you don't? Be specific.
- Use case limits: What types of companies/use cases are you bad for?
- Customer complaints: What do real customers say in negative reviews?
- Pricing objections: Where are you genuinely more expensive, and why?
- Implementation friction: What's hard about getting started with you?
- Industry segments: Where do you consistently lose deals?
For each flaw, map: the flaw → who it matters to → who it DOESN'T matter to. One person's dealbreaker is another's irrelevance. Context transforms flaws into qualifiers.
Phase 2: Build the "Our Flaws" Slide
Every pitch deck should include a slide titled "When We're Not the Right Fit" or "Our Flaws" before the product tour:
Our Flaws
1. We're not the best fit if you need [X specific capability].
→ Our competitor [Name] does this better. If this is critical,
we'll tell you and help you evaluate them.
2. Customers tell us [Y] could be better.
→ Here's what we're doing about it: [specific timeline/plan].
3. Our pricing isn't the cheapest in the market.
→ Here's why: [specific value justification]. If budget is the
primary driver, [Alternative] may be a better fit.
4. We lost deals when [Z specific scenario].
→ If your situation looks like this, let's talk about whether
this is the right fit.
Rules for the Flaws slide:
- Must be REAL flaws, not humblebrags ("We work too hard!")
- Must include at least one thing a competitor does better
- Must include at least one genuine customer complaint
- Must include the context of who it matters to and who it doesn't
Phase 3: Transparency Throughout the Sales Cycle
Discovery Call:
- "Before we dive in — here are 3 situations where we're probably not the right fit. If any of these sound like you, I'll tell you honestly and we can save each other time."
Demo:
- Show the product warts-and-all. If a feature is clunky, say "This isn't our best feature yet — here's the plan to improve it." Don't skip the ugly parts — they'll find them anyway. Finding them WITH you builds trust; finding them WITHOUT you builds suspicion.
Objection Handling:
- Agree first: "That's a fair concern."
- Validate: "Other customers felt the same way initially."
- Contextualize: "Here's what they found after 90 days..."
- The key: never deflect. Acknowledge the objection is REAL before you address it. Buyers know when you're dodging.
Pricing Conversation:
- "Here's the price. Here's exactly what drives it. Here's why we don't discount. If budget is tight, here's the light version that might work."
- No hidden fees. No "let me check with my manager." No discount theater. Pricing transparency is the fastest trust-builder in B2B.
Phase 4: Transparent Negotiation
Caponi's negotiation principles:
- No surprises. If discount is needed, discuss it early — don't spring a price change at the end. Surprises at closing kill deals.
- Single offer. Don't negotiate against yourself. Present your best offer once. "This is the best we can do. Here's why. If it doesn't work, I understand."
- Trade, don't concede. Every discount gets a trade: "We can reduce price by X if you're willing to [annual commitment / case study / reference call / faster implementation]."
- Walk-away price. Know your floor. If they can't meet it, walk away warmly. "I wish we could make this work. If your situation changes, I'd love to reconnect."
- Post-agreement reinforcement. After the deal closes, reinforce why it was the right decision. Buyer's remorse peaks 48-72 hours after signing. A transparency call during this window reduces churn.
Phase 5: Building a Transparency Culture
Transparency isn't a tactic — it's an operating system:
- Pipeline reviews: "Which deals should we NOT be pursuing?" is as important as "Which deals are closing?"
- Loss reviews: Celebrate fast losses. "We disqualified this deal in 2 weeks because we were honest about our gaps" is a WIN.
- Customer feedback: Publish NPS scores internally. Share negative reviews with the whole company. The fastest way to fix problems is to make them visible.
- Sales hiring: Hire for honesty over confidence. The rep who says "I don't know, let me find out" will outsell the one who has an answer for everything.
Output Format
Transparency Sale playbook with: flaws inventory, "Our Flaws" slide, sales cycle transparency map, negotiation playbook, and culture checklist.
Quality Check
- Flaws are REAL, not humblebrags
- At least one competitor is named as better at something
- At least one real customer complaint is included
- Context is provided for each flaw (who it matters to, who it doesn't)
- No discount theater — pricing is transparent
Common Pitfalls
-
Humblebragging as transparency. "We care too much" is not a flaw. "Our reporting module lags behind Looker" is a flaw. If you can't name a specific competitor who does something better, you're not being transparent.
-
Leading with flaws but not context. "We're expensive" without "here's why" is just bad marketing. Every flaw must include: who it matters to, who it doesn't, and why your customers still choose you.
-
Transparency as a phase, not a system. Doing transparency in the first call and then reverting to traditional selling destroys trust. Consistency is the mechanism — one inconsistency erases ten consistencies.
Execution Artifacts
references/framework-notes.md— Named frameworks and reference tablestemplates/output-template.md— Deliverable shell for agent outputscripts/check-output.py— Lightweight deliverable validator
Related Skills
- buyer-psychology: The decision science behind why transparency works
- pitch-deck-builder: Build the deck that includes "Our Flaws"
- objection-handling: Transparency-based objection responses
- deal-desk: Transparent pricing and negotiation
- competitive-intel: Honest competitive positioning
- battlecard-builder: Build battlecards that acknowledge competitor strengths
What ships with it: 3 files
2.2 KB alongside SKILL.md, 1 of them executable
references/
- framework-notes.md563 B
scripts/
- check-output.pyruns863 B
templates/
- output-template.md829 B