The Half-Life Problem
Every year, companies spend billions on sales training. Workshops, offsites, certification programs, keynote speakers, role-play exercises. The energy in the room is high. Reps leave feeling motivated. Managers feel like they have invested in their team. And within 90 days, almost all of it is gone.
This is not a criticism of training. Good training introduces important concepts. The problem is that concepts, without infrastructure, decay. A rep who learns a new discovery methodology in a workshop will use it for two weeks, then gradually drift back to whatever habits they had before. Not because they lack discipline. Because the system around them — the CRM, the deal stages, the meeting cadence, the management review process — was never rebuilt to support the new behavior.
The Difference Between Training and Process
Here is the simplest test: if the consultant leaves, does the system keep running? If the answer is yes, you have built a process. If the answer is no, you bought training.
Training lives in people's heads. Process lives in the workflow. Training depends on individual memory and motivation. Process depends on infrastructure and habit. Training is an event. Process is architecture.
The companies that build durable revenue engines are the ones that invest in process infrastructure, not just knowledge transfer. They build systems that make the right behavior the default behavior, so that reps do not have to remember what they learned in a workshop. They just follow the workflow that is in front of them every day.
What Embedded Process Looks Like
This is not abstract. There are specific, concrete artifacts that distinguish a real sales process from a training program. Here is what they look like in practice:
Meeting Objectives in Calendar Invites
Every meeting a rep books with a prospect should have a stated objective in the calendar invite. Not "intro call" or "follow-up discussion." Something like: "Confirm the three business priorities driving this initiative and identify the economic sponsor." This is a small change that has an outsized effect. It forces the rep to think about what they need to accomplish before the meeting starts. It sets the buyer's expectation. And it gives the manager a concrete artifact to review.
If your reps are booking meetings without objectives, they are improvising. And improvisation does not scale.
Discovery Questions in CRM Fields
If discovery is important — and it is the most important part of the sales process — then it should be a required field in your CRM. Not a text box labeled "notes." Specific fields: "What is the business problem?" "What is the economic impact of not solving it?" "Who else in the organization is affected?" "What happens if they do nothing?"
When these fields are required before a deal can advance to the next stage, discovery stops being optional. It becomes structural. A rep cannot move a deal forward without completing it, which means every deal in your pipeline has been through a real discovery process.
Plan Letters as Deal Artifacts
After discovery, the seller should produce a plan letter: a one-page document that summarizes the buyer's problem, the economic impact, the proposed solution, and the expected outcome. This is not a proposal. It is a mutual understanding document. The buyer reviews it and either confirms or corrects the seller's understanding before any proposal is drafted.
Plan letters serve two functions. First, they force the seller to articulate the buyer's problem in economic terms, which is the foundation of a large deal. Second, they create an artifact that lives in the deal file. When a manager reviews the pipeline, they can read the plan letter and immediately assess whether the deal is real and properly scoped.
Mutual Action Plans as Deal Governance
A mutual action plan is a shared document between the seller and buyer that outlines every step between "today" and "signed contract." It includes milestones, owners, dates, and dependencies. Both sides agree to it.
The mutual action plan is the single most reliable predictor of whether a deal will close. Deals with mutual action plans close at dramatically higher rates than deals without them. The reason is simple: a buyer who agrees to a mutual action plan has committed to a process. A buyer who has not is still browsing.
More importantly, mutual action plans survive personnel changes. If a rep leaves, the next rep picks up the MAP and knows exactly where the deal stands. If a champion changes roles internally, the MAP is the institutional memory of the deal. This is process that outlasts individuals.
The Consultant Test
When we work with a company at Jozu, we build all of this into the system before we leave. The CRM fields are configured. The deal stages are gated. The meeting templates are in place. The plan letter format is standardized. The MAP template is built.
Then we apply the test: if we walk away tomorrow, does the system keep running? If a new rep is hired next month, can they follow the process without anyone explaining it to them? If the answer is yes, we have done our job. If the answer is no, we have more work to do.
This is what separates revenue architecture from sales training. Training gives your team new ideas. Architecture gives your team new infrastructure. Ideas fade. Infrastructure compounds.
Where to Start
If you are evaluating your own sales organization, here is a quick diagnostic:
- Open your CRM. Are there required discovery fields that gate deal progression? If not, your process is optional.
- Look at the last ten meeting invites your reps sent to prospects. Do they have stated objectives? If not, your meetings are unstructured.
- Pull up a deal that closed last quarter. Is there a plan letter in the file? If not, you do not know why it closed at that size.
- Find an active deal in late stage. Is there a mutual action plan? If not, you do not know if it will close on time.
Every "no" on that list is a place where training is substituting for process. And every place where training substitutes for process is a place where revenue is leaking.
Jeff Aragon, Founder — Jozu Consulting Group