Meridian
A Hypothetical Enablement Case Study
Built for a fictional company, Meridian, to show these frameworks working as one program, not standalone pieces. Each is linked as you go. The problems mirror ones from my own sales experience, given a concrete scenario instead of an abstract claim.
Company Profile
Meridian sells market and competitive intelligence to enterprise organizations, tracking competitor moves, market sizing, and industry trends. Trials center on a 1:1 session with an expert, a high-touch sale that's easy to run inconsistently.
Leadership’s strategy was clear: grow net new accounts, lean into the expert-on-demand differentiator, shorten the cycle. What they lacked was proof the field was executing it. Trials varied by AE. Qualification depended on who you asked. Onboarding worked, just not fast enough for this market. AEs ran the full cycle from prospecting to close, then handed off to a small Customer Success and Account Management team.
Leadership knew the strategy. The sales floor didn't consistently reflect it. That gap is where this program starts.
What We Learned From the Company
Leadership described the strategy. Reps described something else: trials run ad hoc, qualification inconsistent, onboarding too slow. Marketing’s messaging didn’t always match what reps said on calls.
Every conversation followed a Stakeholder Conversation Framework, full discovery sequence for deep relationships, a shorter version for quick check-ins. Notes ran through a Stakeholder Interview Coding Agent, patterns across dozens of interviews were surfaced on their own instead of losing them in transcripts.
What We Learned From Customers
Internal conversations showed what the team believed. Customers showed what actually landed. Every closed deal, won or lost, got the same Win/Loss Interview Framework, so outcomes could be compared on equal terms.
The Pattern: Deals won when reps led with the differentiator early, and lost on cycle length when they didn’t. Customer signal confirmed the internal read, and gave it a number.
How We Put It Together
Internal and customer signal agreed on one problem: a real strategy not reaching the field. That became an Enablement Strategy Report, current state, the gap, the initiatives to close it, what leadership needed to do. It turned leadership from approving a hire into co-owning a direction.
The Report's highest-leverage initiative became a Program Charter, scoped down: what enablement owned, how success would be measured. Shared early, as a starting point, not a decree.
How We Built the Program
AEs needed consistent qualification first: a Discovery Questioning Framework unifying Sandler, MEDDPICC, Challenger, and Miller Heiman into one conversation any rep could run.
Qualified opportunities then entered a Trial Framework Blueprint, a five-stage playbook (intake, trial launch, expert session, final review, decision) replacing whatever each AE improvised. Every opportunity moving through it was scored by an Opportunity Grading Agent, so pipeline health meant more than stage and probability.
AEs ramped into this through an Onboarding Program, built on Meridian’s Training Program, teaching the standard and the Blueprint as one system from day one. Every rollout followed the sameAdoption Loop: the case for change, made personal, an early win banked, checkpoints to stop it sliding back.
Closing the loop
The Blueprint's five stages end at a defined commercial outcome, Closed/Won included. But nothing carried what the trial had already learned, success criteria, the stakeholder map, what almost went wrong, into the relationship that followed.
The Handoff Framework closes that gap: what an AE hands off, how CS and AM work together to deliver on it, and how a retained customer becomes an advocate, feeding directly back into the Win/Loss Interview Framework.
Same discipline, applied to a boundary the program hadn't crossed yet: enablement builds the system, CS and AM run the relationship.
How We Measure, and What the Future Holds
Beyond activity metrics, we tracked ramp time, conversion by stage, and pipeline quality. The Grading Agent's own record, how a grade shifted over time, became a signal for what needed reinforcement.
As the program matured, the same discipline built tools to scale it: the Grading Agent expanded to document full CRM records automatically, and a Pipeline Automation tool gave leadership a weekly, hands-off read on deal health.
The program didn't end at a finished playbook. It kept listening, diagnosing, and building the next thing Meridian actually needed.