The Standard.

The conversation enablement leaders keep having about ramp is the same conversation, every quarter. The diagnoses change but the structure of the conversation doesn't. New methodology, new platform, new training calendar. None of them move the median. Something underneath is missing, and the purpose of this letter is to name what.

A manager coaching a rep is, mostly, sharing their own private interpretation of what should have happened. There is no shared rubric for "good discovery." No consensus on the order skills are mastered in. No auditable measure for promoting a rep from one tier to the next. Every manager invents a private version of all of it. Then they change jobs, and the next person starts again.

This isn't anyone's fault. Sales enablement grew up around methodologies, not standards. MEDDPICC, Sandler, narrative selling, the latest closing playbook — these describe what a rep should do, not what they should be good at. The taxonomy underneath was never written. Most enablement leaders are building on soil that has never been surveyed.

I lived this from every seat over fifteen years. I started as a cold caller, and I got better the only way available at the time: I built my own frameworks, one at a time, out of necessity — a way to open, a way to qualify, a way to hold my nerve when the deal got senior. As the roles grew — partnership sales, enterprise sales — the frameworks grew with them. And when I moved into the seats that coach others — sales leader, Head of Sales, VP, CCO, then fractional — I watched everyone else being coached the way I could never have improved from. The rep who became the manager's favourite was usually the one with style. The rep with rough mechanics was coached on plays they couldn't yet execute. The rep whose deals stalled was diagnosed in language no one could verify. Their close lacked confidence. Their discovery was thin. They didn't really qualify. Verdicts without rubrics. Judgments without appeals.

After enough quarters of this, the realisation set in.

So I kept building — this time for everyone else.

A standard for what good selling looks like, built in real time against real commercial outcomes inside the kind of fast-growing scale-ups where the question "is enablement actually working?" stops being abstract and starts being your performance review.

It wasn't built in a research project, an academic seminar, or a workshop. It was built call by call and deal by deal — first in my own seats, framework by framework, then across hundreds of teams, fifteen years of compounding feedback. The first time I knew the private toolkit had to become a standard was on a discovery call in 2019.

I started writing down what the difference between Foundation and Proficient actually looked like. Then the same exercise for Proficient and Advanced. Then for Advanced and Expert. Then for the next competency, and the one after that. After enough of those, the structure of a real standard started to appear.

Today, for sales alone, it has:

• Twenty-seven frameworks. Each one for a specific role and motion. Mid-Market AE. Enterprise AE. AE-led Outbound. Tech-Demo with SE. SDR → Founder hand-off. Twenty-two others. Choose the framework your team's motion fits; the standard tunes itself to it.
• Fifty-four observable competencies. Each one is a discrete craft skill — a specific thing you can watch happen on a real call. Not abstract concepts. Not "be a better closer." Specific, named, observable: Value Articulation & Positioning. Listening and Responsiveness. ICP Discovery. Initial Problem Identification. Objection Handling & Risk Mitigation. Closing & Commitment Securing. And forty-eight others.
• Three progression levels, four grading levels per competency. A rep is at Foundation, Enhanced, or Advanced level on a framework; each underlying competency is graded Foundation → Proficient → Advanced → Expert. Each cell of the three-by-four grid has a written, evidence-based criterion. A promotion is a documented event with a cited observation behind it.
• A dependency graph between competencies. Most skills don't exist in isolation. Value Articulation & Positioning requires Initial Problem Identification. Initial Problem Identification requires ICP Discovery and Listening & Responsiveness. Coaching efficiently means coaching in the right order — and the standard knows what that order is.

Below is a single thread cut from the standard. One framework, one competency, all four tiers, with the upstream dependencies and downstream unlocks named. It is an illustration. The standard's full content stays inside the engine, where it belongs.

A standard is only useful if something can operate it at scale. No human team can hold a twenty-seven-framework, fifty-four-competency taxonomy in their head — with twelve written rubric cells per competency — and apply it consistently to a sales floor. So I built an engine.

Peer is the AI infrastructure that runs the standard. Fourteen specialist agents observe your team's recorded calls — the ones you're already producing — score each observation against the rubric, track progression tier by tier, and surface the single mechanic each rep should work on this week. It runs continuously. It doesn't tire. It applies the same yardstick to your top performer and your newest hire. The full system tour is published in the Atlas.

ThinkWork is how the standard arrives in your business. We don't sell Peer. We install it on your behalf, train your enablement leader to read what it sees, run the first coaching cycle inside it, and stay on as the operator. By the end of an Install your team is operating inside the standard. The artefact you keep isn't a deck — it's a working enablement function.

The move I'd like sales enablement to make is to coach against a standard, not against opinions. The category has a name — Standard-Based Coaching — and part of why I'm writing this letter is to name it and invite enablement leaders into it.

What separates Standard-Based Coaching from what most enablement programs do today is not the volume of activity. It's the architecture underneath the activity.

• The standard exists outside the coach. It doesn't change when the coach changes job, when the playbook gets refreshed, or when the latest hire arrives with their own methodology. The yardstick survives the people using it.
• Promotion from tier to tier is auditable evidence, not manager opinion. When you promote a rep from Foundation to Proficient on Value Articulation & Positioning, there is a written, observable reason — a specific moment in a specific call. Anyone can see it. Anyone can dispute it.
• Coaching priorities are calculated from the graph, not chosen by guess. "What should we coach this week?" stops being a decision under uncertainty. The standard knows which mechanic is the highest-leverage move for each rep, and why.
• The standard is portable. A rep's mechanics credential travels with them when they change roles. Their career arc has a substrate. For the first time, what they're good at is something they take with them, not something their manager carries.

These are not small differences. They are the difference between coaching as a discipline and coaching as folklore.

Below is a slice of the dependency graph that the standard enforces — the relationships that decide what to coach in what order. This is what makes the standard active intelligence rather than a static framework.

Every category eventually gets a standard. The pattern is the same every time. Someone gets tired of the alternative, writes down the rules, and makes the rules visible. The new rules create a category that didn't exist before. The category becomes how people work in that domain.

I'm publishing this letter for three reasons. They build on each other.

First, the standard is too important to keep inside one firm. If it lives only inside ThinkWork's engagements, it changes twenty enablement functions in five years. If it lives in the category's working vocabulary, it changes how the profession is practiced. The strategic move for a founder building something this load-bearing is to publish what can be published — and to be open about what stays inside the engine.

Second, the conversation about AI in sales coaching is being dominated by tools that score deals, not coach people. Revenue intelligence categories are mature. People intelligence categories are not. I'd rather force the conversation about what coaching should actually measure than wait for the category to figure it out on its own. Someone has to set the bar.

Third, I'm building a firm to install this. Pretending to be neutral would be dishonest. ThinkWork's services exist because the standard is real. The standard exists because the problem it solves is real. If you're an enablement leader reading this, the path forward is yours to choose.

This letter is the first of a weekly publication. Here's what you can expect from it.

Every week I'll publish one short, opinionated essay on the standard, the category, or what I'm seeing inside engagements. Some weeks it will be a Standards Bench — I'll deconstruct a single anonymised sales call against the standard, naming what good looked like, what tier the rep is at, and what the highest-leverage next coaching move is. Some weeks it will be philosophy. Some weeks it will be data — quarterly, the standard's anonymised platform data turns into a State of Sales Coaching report I'll publish freely.

This is the public surface. The standard itself, the rubrics, and the engine that runs them stay inside Peer. What gets shared here is the thinking around them. If you've read this far, you're the kind of enablement leader the letter is written for.