A system, not a library.
Sales Enablement with a Purpose
I built enablement that made the right content show up at the right moment, structured around how sales actually sell, by customer type, challenge, and stage.
Role
Context
Disciplines
Responsibilities
- — Showpad architecture
- — Evergreen asset development
- — Campaign-to-enablement alignment
- — Rep onboarding content
i. The business question
Marketing produced plenty. Sales used some of it. The gap between marketing activity and sales follow-up was the problem worth solving.
The goal wasn't asset volume. It was usability, timing, and trust.
ii. The thinking
Structure before assets.
Showpad was organized by audience, use case, and sales stage, so reps could find what they needed in seconds.
One source of truth.
The content promoted externally was the same content enabled internally.
Evergreen first.
Core assets were built to last, updated incrementally instead of replaced every quarter.
Campaign-aligned, not campaign-dependent.
Enablement supported launches without breaking when campaigns ended.
iii. The work
- A Showpad library mirroring the sales conversation, not marketing campaign names.
- Modular, reusable assets tied to real conversations happening in the field.
iv. What it accomplished
- Reduced ad hoc content requests
- Increased confidence in what sales shared with prospects
- Shortened the gap between marketing activity and sales follow-up
- Repeatable enablement new reps could onboard into quickly
v. What I took from it
“What changed wasn't just access to content. It was adoption.”Original write-up ↗
Related
Next case study · 05