Proprietary Methodology:The Five Moves Behind EOS and SAFe
Proprietary methodology lessons from EOS, SAFe, StrengthsFinder and 7 Habits: five moves that turn personal expertise into a business that outlives its founder.
Don Clifton died in 2003. The business built on his research — the StrengthsFinder assessment and the coaching ecosystem around it — didn't stall. It kept expanding, year after year, without the man whose interviews created it.
Sit with that for a second. Most consultancies, agencies, and coaching firms can't survive their founder taking a long holiday. Clifton's survived his death. The difference wasn't talent. It was architecture, in the form of a proprietary methodology.
And Clifton wasn't a one-off. Gino Wickman, a business coach in Detroit, built EOS. Dean Leffingwell, a software engineer in Colorado, built SAFe. Stephen Covey, a professor in Utah, built what became FranklinCovey. Four people, four fields, four different decades. No collaboration, no shared advisors, in all likelihood no contact at all. Yet trace the history of each business and you find the same five moves, executed in the same order.
Biologists have a term for this: convergent evolution. When independent actors facing the same pressures arrive at the same design, the design itself is the lesson. What follows is that design for a proprietary methodology, move by move — and what each move asks of a founder who sells expertise.
Move One: Stay in the Room to Build a Proprietary Methodology
The Unscalable Years Are Where the IP Comes From
None of the four began with a framework. They began with hands-on, unscalable, founder-delivered work — and stayed in it long enough for the repetition to teach them something.
Wickman coached Detroit-area companies one at a time, in the room, testing and adjusting his approach with each engagement. Leffingwell took custom consulting engagements helping individual enterprises make agile work at scale, with every recommendation shaped by that client's situation. Clifton did the slow academic work of interviewing people about their talents, study after study, until patterns surfaced across thousands of conversations. Covey taught effectiveness principles to university students for years; The 7 Habits of Highly Effective People, published in 1989, was the distillation of decades spent teaching the material directly.
During this phase, the economics were what they always are for a solo expert: revenue capped by hours, nothing compounding, nothing that scales. It's tempting to read this as wasted time. It isn't. The frameworks that later carried each business were being mined here, one engagement at a time.
The lesson for an expertise founder is uncomfortable but clear: you can't shortcut this move. A methodology that wasn't earned through repeated delivery is a guess with a logo. The repetitions are the research.
Move Two: Convert an Approach Into a Proprietary Methodology
The Name Is the First Asset
Each founder eventually noticed the same signal: they were repeating themselves. The same questions, the same frameworks, the same sequence producing results across very different clients. That repetition is the cue for the second move — turning a personal approach into a named, standardized offering.
Wickman organized everything he'd learned into six components — Vision, People, Data, Issues, Process, and Traction — and attached a concrete tool to each: the V/TO, the Accountability Chart, the Scorecard, the Issues List, Process Documentation, and Rocks. The result was no longer one coach's style. It was the Entrepreneurial Operating System.
Leffingwell did the equivalent for enterprise agile: named practices, defined roles, specific ceremonies, measurable outcomes — the Scaled Agile Framework. Clifton converted open-ended research conversations into a structured instrument, the Clifton StrengthsFinder. Covey restructured his teaching into a workshop with set exercises, materials, and facilitation guides: the 7 Habits Workshop.
Notice what the name does. "Our consulting approach" is a description; nobody can buy it, license it, or protect it, and it walks out the door with you. A named proprietary methodology is property. It can be positioned in a market, defended legally, and — critically for everything that follows — delivered by someone who isn't you.
The substance of the work barely changes at this move. The packaging changes everything: bespoke advice becomes a product with fixed scope and fixed price.
Move Three: Document Until You're Optional
Gerber's Question Is the Quality Bar
A proprietary methodology without documentation is just marketing. For the system to run without its creator, every step has to be written down at a depth where a trained practitioner gets consistent results with the founder nowhere in sight.
This is where the four case studies get specific. Wickman built the EOS Toolbox — per-component documentation including facilitation scripts, decision trees for common situations, and quality standards. Not just the what, but the how, and what to say when the session goes sideways. Leffingwell went further than almost anyone: he published SAFe as an enormous, detailed public website — effectively an operations manual that practitioners anywhere on earth can implement from. Covey's organization produced facilitator guides, participant workbooks, and video material so that a certified trainer in any location could deliver the workshop to a consistent standard.
Michael Gerber gave this move its acid test decades ago: "Could someone with no prior experience follow this and deliver an acceptable result?" While the answer is no, you own a practice that depends on you. Once the answer is yes, you own the foundation of a platform.
Most expertise founders stall exactly here — not because documentation is hard, but because being needed feels like job security. The four founders in this story treated being needed as the bug, not the feature.
The Tool All Four Built: A Diagnostic
Front Door, Data Engine, and Moat in One Artifact
Within the documentation move sits one artifact so consistent across the four cases that it deserves its own section: every single one of these businesses built an assessment.
EOS has the Organizational Checkup. Gallup has the StrengthsFinder itself — Clifton's instrument standardized data collection and produced comparable results across millions of respondents, turning research into a product any trained coach could administer and interpret. SAFe has maturity assessments. FranklinCovey has effectiveness diagnostics.
The diagnostic earns its place because it does four jobs simultaneously. It's the entry point — the lowest-friction way for a prospect to engage. It's the data generator — every completion standardizes what you know about your market. It's the moat — accumulated results become benchmarks competitors don't have. And it manufactures recurring need, because an assessment taken once invites reassessment later.
If you build one scalable asset before any other, build this one. The pattern across four unrelated businesses isn't subtle.
Move Four: Certify Others — Then Get Out of Their Way
Where Revenue Stops Being Linear
Everything up to this point still has the founder delivering. Move four breaks that: the founder shifts from doing the work to certifying the people who do.
The numbers show what that unlocks. EOS today counts more than 700 certified implementers serving over 200,000 companies; Wickman hasn't personally run an implementation in years. SAFe has certified upwards of 18,000 practitioners through a tiered system in which SPCs train other agilists — the network enables itself faster than any individual could. Gallup runs thousands of certified coaches across every continent, interpreting an assessment the founder no longer can — and the business has grown in the two decades since his death. FranklinCovey delivers the 7 Habits Workshop hundreds of times a month across dozens of countries and multiple languages, through certified facilitators who are very much not Stephen Covey.
In each case the founder's personal genius wasn't diluted by the network — it was replaced by a system that produces consistent outcomes through trained people following documented method. Ordinary practitioners, extraordinary results, at scale: Gerber's franchise prototype standard, passed four times over by four founders who never compared notes.
"Only after eliminating custom consulting did enterprise clients embrace the recurring model." — John Warrillow
Warrillow's warning points at the real difficulty of this move, and it isn't designing a certification program. It's the founder genuinely exiting delivery. Keep selling bespoke engagements after the model is proven and you're competing against your own practitioners — what Warrillow calls the "half-pregnant mistake." A platform that also undercuts its network is neither.
Move Five: Put Software and Data Under the Method
The Asset No Competitor Can Rebuild
The final move is technology — not as a gadget bolted onto the proprietary methodology, but as the layer that standardizes delivery and accumulates the data asset.
Gallup is the clearest illustration. More than 30 million people have taken StrengthsFinder. The resulting dataset — correlations, patterns, benchmarks across industries and demographics — is something a rival could only match by rebuilding the entire network from zero. And it compounds: every additional assessment deepens the moat.
SAFe's platform tracks implementation progress and organizational maturity and lets an enterprise see how it compares to thousands of peers — so adopting SAFe means joining a data ecosystem, not just picking a framework. EOS built EOS One to let implementers and their clients run the EOS process digitally, adding stickiness and consistency. FranklinCovey has extended into digital learning platforms and technology-enabled assessment alongside in-person facilitation.
This move is also where the valuation math turns over. A service firm living on project revenue tends to trade around 1-2x revenue. A technology platform with recurring revenue, network effects, and proprietary data trades more like 8-15x. Identical expertise, identical methodology — radically different enterprise value, purely because the architecture changed.
The Differentiator Was Never the Ideas
Here's the part worth tattooing somewhere visible: none of these four won on raw insight. Detroit had other business coaches when Wickman started. Enterprise agile had other consultants when Leffingwell started. Psychology had other researchers studying human strengths. Leadership shelves were already full of books when Covey published his.
What separated these four was the sequence. They codified what the unscalable years taught them. They named it. They documented it past the point of personal necessity. They built the diagnostic. They certified a network and stepped out of delivery. They put software and data underneath it all. And at each step, they made the trade most experts refuse: less identity as the brilliant deliverer, more leverage as the designer of the system.
For a founder running a consultancy, agency, or coaching firm today, that's the practical takeaway. You don't need a once-in-a-generation idea to build a proprietary methodology. You need the discipline to run a sequence that four strangers, in four industries, across four decades, independently proved out.
Convergent evolution already drew the map. Your only decision is whether to follow it.