Your reps know the process. They've sat through the training, opened the playbook, watched the Loom. The reason they skip discovery on a $40K deal isn't ignorance. It's that the rule lives in a wiki, the deal lives in HubSpot, and the moment of decision is in between. Below: the data, the methodology Supered teaches to close the gap, and the playbook that installs it in two weeks.
It's why every sales org has the same stack: an LMS, a content library, a quarterly enablement session, a Loom for the new playbook, and a Slack channel where the head of enablement posts reminders. None of it has moved adoption past 36%, the average rate at which reps actually follow the process their company designed (per The State of Sales Enablement). The training-harder model has been running this experiment for a generation. The result is the same every time.
None of these numbers come from a sales enablement vendor. They come from Gartner, Salesforce's own State of Sales, and the Bridge Group SDR benchmark. Read them in order. The picture forms.
Knowledge enters the rep on Monday. By Friday, behavior is unchanged. The retention curve is real, and the four leaks underneath it are predictable. Once you see them, every training program you've run starts to make sense.
Every leak is a place where the rule and the rep are in different surfaces.
Adoption is a real-time guidance problem, not a remembered-knowledge problem.
Both reps walked into the same Monday training. By week 12, only one of them is still running the process. The variable isn't memory. It's whether the rule was in the deal.
Once you see this, you cannot un-see it. Most sales process work tries to make the rule live in the rep's head. Adoption that compounds puts the rule on the deal.
A three-principle framework for closing the Sales Execution Gap. The Behavior Layer sits above your CRM and turns the process you wrote into the process every rep actually runs. Same three principles, regardless of which job you're hiring it to do (adoption, onboarding, or change management).
Enablement budget is typically a depreciating cost. You spend it, the value decays, you spend it again next quarter. The Behavior Layer flips that. The longer it runs, the more compliance compounds, and the more your top rep's process becomes everyone's process.
Training retention drops 50% in 24 hours. New playbooks get reinvented in three weeks. Content libraries get stale. Doc views go to zero. You repeat the cycle every quarter and the adoption number stays flat.
The rule fires every relevant deal, every week, indefinitely. Top-rep behavior gets captured in the system, not in a person. When a rep leaves, the way they sold stays. The adoption number goes up the longer you run it.
This is the framework Supered runs with every customer. It works whether you adopt Supered or rebuild it yourself. The order matters.
Don't start by writing a playbook. Start by listing the 8 to 12 moments in your deal cycle where reps make a decision that varies between top reps and bottom reps. Discovery question, MEDDIC qualifier, recap email, demo opener, pricing handoff, close plan. Those moments are your adoption surface, not the doc.
The Pareto rule applies. Three of the moments you mapped are responsible for most of the variance between deals that close and deals that don't. Usually: a discovery skip, a stage advance with a missing field, and a closing motion without a mutual close plan. Those three are your launch set. The rest can wait.
For every rule, the question is: which stage of the deal is this rule actually about? Discovery skip belongs at "Demo Scheduled". Mutual close plan belongs at "Verbal Yes". The rule fires inside the deal record at that stage, not in a separate tool. The rep should never have to context-switch to comply.
The metric is whether the rep ran the rule, not whether they read the doc. Build a daily report that shows: rule fired, rule complied, rule skipped, by rep, by deal. Compliance becomes a number on a dashboard. Variance becomes coaching fuel. The wiki becomes archival, not operational.
Once the rules fire and the data flows, manager time gets reallocated. They stop chasing field hygiene and start coaching the deal where the rule fired but the rep skipped it. That's the only conversation that moves a number. Adoption stops being a manager-effort problem and starts being a rep-skill problem you can actually fix.
This is what step 3 of the playbook looks like running live. The rep is in HubSpot. A deal has just moved to Demo Scheduled. The discovery questions weren't answered. Supered surfaces the rule on the deal itself, with one click to comply. The rep doesn't switch tools, doesn't open the wiki, doesn't get a manager nudge an hour later. The decision happens in the moment.
For sales process adoption, three Supered features carry the load. Process Boards is the visibility layer. Process Rules is the compliance engine. Sidekick is the surface where reps comply. Together they install The Behavior Layer in two weeks.
The visibility layer. For the first time you can see where every rep is in the process, deal by deal, stage by stage. Adoption stops being a vibe and starts being a number on a board you can show the CRO on Tuesday.
See how it works →The compliance engine. Required fields, qualification gates, stage prerequisites. Rules fire on the deal at the moment the rep would have skipped them. Configured by RevOps, no code, no engineering ticket.
See how it works →The rep-facing surface, sitting next to the HubSpot or Salesforce deal record. Surfaces the rule, walks the rep through it, logs the run. One click to comply, one click to override (with a reason that goes to the manager).
See how it works →The board asks for the adoption number on Tuesday. You have it. The number went up the last six weeks in a row. You spent four hours total on it.
The four questions every VP Sales asks before they pick a system. Direct answers, no hedging.
Sales process adoption is the share of deals where reps actually run the sales process the company designed. It's measured rule by rule, deal by deal. A team of 30 reps with 5 process rules and 200 active deals has 1,000 adoption events to measure each week.
The industry baseline, per The State of Sales Enablement 2026, is that 89% of teams have a defined process and 36% see it followed as designed. The 53-point gap between those numbers is the adoption problem.
For each rule, count three things at the deal level: (1) how many times the rule should have fired, (2) how many times the rep complied, (3) how many times the rep skipped. Divide complied by fired, average across rules, and you have a single adoption percentage you can put on a dashboard.
The wrong way to measure adoption: training completion rates, doc views, manager check-in counts. None of those touch behavior. The right metric is what happened in the deal at the moment the rule was relevant.
Training transfers knowledge. Adoption is about behavior in the moment of decision. Those are different problems with different solutions. Even great training loses about 50% retention in 24 hours and most of the rest in two weeks. By the time a rep has a real deal in front of them, the training has decayed below the threshold where it can compete with habit.
The fix isn't more training. It's putting the rule where the deal lives, so memory becomes optional.
CRM hygiene is whether fields are filled in. Process adoption is whether reps ran the right play in the right order at the right stage of the deal. The first is data quality. The second is rep behavior. AI is going to commodify the first within 12 months. The second is the moat.
Supered embeds rules in the deal record itself. When a deal hits a stage that has a rule attached, Supered fires it on the deal in real time. Reps see it where they already work. RevOps configures rules in Supered's admin (no code), and the audit log captures every fire and every skip.
Implementation is typically 2 weeks. Average team reaches 90%+ adoption by week 4.
Two weeks to first rules live, four weeks to 90%+ adoption on those rules. The bottleneck is almost never the tooling. It's deciding which 3 moments to launch with. The framework above is designed to compress that decision into a single working session.
A 30-minute demo, your three highest-leverage moments mapped, and a clear plan to install adoption inside HubSpot or Salesforce in two weeks.