Productize Your Methodology:The Build Order in 5 Phases
Productize your methodology in the right order. This twelve month sequence shows what to build first, what each phase makes and why working out of order fails.
Ask a founder who has absorbed the whole playbook — positioning, pricing architecture, certification tiers, meeting cadences, content engines — why none of it exists yet, and you almost never hear "I don't understand it." You hear "I don't know where to start."
That answer deserves respect. When a system has a dozen interlocking parts and all of them look urgent, hesitation is rational. Start with the partner community? The proposal template? The technology? Pick wrong and you burn a quarter — so most founders pick nothing, or pick everything and scatter across six half-started workstreams that never connect.
If you want to productize your methodology, the cure is not more knowledge. It is build order. A service business assembles in a specific sequence, where each phase produces the raw material the next phase consumes. Below is that sequence — five phases across roughly twelve months — with the dependency logic behind each one made explicit, so you always know what to build next and what to ignore for now.
How to productize your methodology step by step
Order Is Load-Bearing. The Calendar Is Not.
Every phase in this sequence sits downstream of another. You cannot put a price on an offer you have never defined, so positioning has to precede pricing. You cannot run a sales motion through a partner network that does not exist yet, so practitioners come before sales training. You cannot scale a delivery system nobody has documented, so capture comes before growth. And you cannot optimize operations you have not yet installed.
That chain produces the single rule governing the whole year: never move into a phase whose prerequisite is incomplete. If a phase slips, let the calendar slip with it. A founder who needs fifteen months to finish the twelve-month sequence properly ends up with a stronger company than one who compresses it into nine and leaves gaps underneath.
Hold that rule as you productize your methodology and the rest is simple: each phase below names what you build, the reading that supports it, and the exit criteria that say it is safe to advance.
Phase One: Name It, Then Price It to Productize Your Methodology
Weeks 1-2 — The Artifacts Everything Else Consumes
The first week belongs to positioning. Work through the positioning canvas until you can compress the result into a single sentence: "I help [specific audience] [achieve specific result] using [your methodology]." Then stress-test it: would a stranger remember it ten seconds into a cocktail party, and instantly know whether they belong in your target audience? If not, narrow it again. Your reading for the week is Dunford's Obviously Awesome alongside Enns's Win Without Pitching Manifesto.
The second week belongs to money. Lay out the value ladder: three to four certification tiers, each with a defined scope and a defined price. Draft the three-option proposal template — good, better, best — you will use on every engagement. Set a minimum fee. Write down your discounting policy — in short, a discount is a last resort, offered only after every non-price alternative is exhausted. And even during a founding period where the fee is waived, send the invoice at full value — the document itself anchors what the work is worth. Pair Weiss's Value-Based Fees with Simon's Confessions of the Pricing Man.
Exit criteria for Phase One: a positioning statement you would defend in public, a tiered pricing architecture with a floor, and a reusable proposal template. All three are inputs to every later phase — recruiting, selling, content, conversion.
If they are not finished, do not advance. Recruiting or selling on top of fuzzy positioning and undisciplined pricing produces activity without direction.
Phase Two: Fill the Room Before You Pitch It
Weeks 3-4 — Practitioners Before Prospects
A partner-driven model has nobody to sell through until practitioners exist, so the ecosystem comes next. Week three is infrastructure: write the 66-day onboarding plan a new practitioner will follow, stand up the communication channel (Slack or equivalent), draft the agenda for the monthly partner call, and set explicit norms for attendance and contribution. Two books shape this work — Bacon's The Art of Community and Spinks's The Business of Belonging — and they will inform your community decisions for the next two years.
Week four is recruitment. The founding cohort should number 15 to 30 people, drawn from where trust already exists: former colleagues, past clients, peers with genuine interest in your methodology. The founding cohort is not a customer segment — it is a group of co-creators, and the invitation should say so plainly: you are building something new and want their help shaping it through the first year.
This is also the week the weekly L10 meeting begins — even if only two people sit in it. The rhythm gets installed before the team is fully assembled, not after. Read Wickman's Traction before the first session so the agenda, the IDS issue-solving protocol, and the scorecard review are familiar from day one.
Exit criteria for Phase Two: an active, populated channel; an onboarding plan ready to run; monthly calls on the calendar for the year; the first 5-10 practitioners moving through onboarding; and an L10 every week. The ecosystem is alive.
Phase Three: Teach the Network to Sell
Month 2 — One Shared Sales Language
Here is where theory touches revenue — and where a hard truth surfaces: most newly certified practitioners have never sold professional services. Weeks five and six are devoted to a unified sales methodology built from three sources. From Dixon's Challenger work: open by teaching the prospect something they did not know, then position your assessment as the diagnostic that follows. From Keenan's Gap Selling: put a number on the cost of the problem, so the fee for solving it looks small beside it. From Parinello: start every pursuit at the top of the organization, with a VITO letter template each practitioner can adapt. Round it out with a post-assessment guide that converts diagnostic findings into proposals.
Weeks seven and eight move from training to the field — and the founder goes first. Deliver the initial 3-5 assessments personally: it proves the methodology under live conditions, generates the first real data, and produces the case-study material practitioners will lean on in their own conversations. If the daily huddle has not started yet, start it now — it becomes indispensable as engagement activity multiplies.
Exit criteria for Phase Three: a trained cohort with tools in hand, 3-5 assessments delivered, the first client satisfaction data on record, and the first data-backed insights feeding the content engine.
Phase Four: Engineer Yourself Out of Delivery
Months 3-4 — Capture, Standardize, Publish
Month three is about transfer: this is where you productize your methodology so it leaves your head. Stand up the partner performance dashboard with simple red, yellow, and green states. Then begin Live Capture, the technique Michalowicz lays out in Clockwork: record yourself performing a task, hand the recording to someone else, and let them run it next time. Resist polishing SOPs before handing anything over — demanding perfect documentation before transfer is procrastination dressed as quality control.
Month four is about proof. Turn the early engagements into the first case studies. Watch for the first cross-referrals between practitioners. And publish your first content drawn from assessment data — the dataset is small, but 15-30 assessments already surface patterns worth saying out loud. A single finding — say, 75% of the companies in your first 20 engagements underestimating one dimension — is at once a LinkedIn post, the seed of an article, and a webinar topic.
Launch the content calendar in this phase on a four-week rotation — insight posts, articles, podcast episodes, webinars. Do not wait for some imagined threshold of "enough to say." If you build the habit of extracting insight from every engagement, the supply never runs out.
Exit criteria for Phase Four: 15-30 assessments complete, a dashboard in daily use, processes documented through Live Capture, case studies published, and the content flywheel through its first rotation. The proof of concept now exists in artifacts, not intentions.
Phase Five: The Back Half of the Year
Months 5-12 — Deepen, Convert, Celebrate
The remaining eight months follow a steady cadence. In months five and six, the cross-referral network starts firing, you run the first vacation test (a single day away), and the top and bottom performers become visible. Months seven and eight bring methodology v2 — revised from field feedback — plus the first published benchmark report and advanced coaching for your strongest partners. Months nine through eleven are conversion season: demonstrate each practitioner's individual ROI, communicate Year 2 pricing, and put underperformers on formal plans. Month twelve closes the arc with the annual summit, a recognition ceremony, a conversion target of 80% or better, and finalized criteria for Cohort 2.
The dependency rule still applies in the back half. If month-three work is unfinished, month-six work waits. Skipping ahead does not buy speed; it buys rework.
The Rhythm Running Underneath
Four Cadences That Keep the Sequence Honest
The operating rhythm assembles in layers: the weekly L10 in week four, the daily huddle in month two, and the full stack — daily huddle, weekly L10, monthly partner call, quarterly review — in place by month six. Those four cadences are the mechanism that turns this sequence from a plan you read into a system that executes week after week; remove them and good intentions dissolve into disconnected activity.
So the build order, compressed to one breath: positioning before pricing, community before sales, platform before scale, operations before optimization — each phase feeding the next.
To productize your methodology, the sequence has one entry point, and it opens on Monday. A positioning statement you can write in week one. A founding cohort you can invite in week four. A first assessment you can deliver in month two. The business that eventually runs without you begins with whichever of these you start this week — in order.