Milestone 13. Strategic Plan

15 min read

Milestone 13. Strategic Plan

Build the Revenue Architecture every revenue decision runs through, so the CRO stops chasing every deal and starts filtering them against one documented strategy.

Phase 2 (Build) · Module 5 (Predictable Revenue) · Milestone 13 of 27

The owner’s question

Can your revenue leader explain your ICP, your winning position, and your offer-to-segment math in 90 seconds without you in the room, and would the document filter at least one of the last five opportunities you pursued?

If the answer is “we serve a few different segments” or “we win on customer service,” you’re not at a 3 yet.

TL;DR

Most owners can’t name one ideal customer, default to vague reasons people choose them, and end up with a CRM full of opportunities that don’t fit. Milestone 13 ends the vague answer. You build the Revenue Architecture document, a five-section strategic specification (Brand, Market, Customer, Competitive Positioning, Offer Structure) that names one ICP, locks one winning position that passes the opposite rule, quantifies your TAM with tiering, and maps every offer to every segment with a knock-you-out sentence. Once installed, the architecture is the filter the CRO uses to say no, which is what makes the rest of Module 5 (customer journey, CAC, forecast) actually work.

Why this matters

Ask most owners who their ideal customer is. They give you three. “Mid-market manufacturers in the upper Midwest. Plus services firms with an aging founder. Plus the occasional distributor.” Three bests. Kim Clark, who runs revenue inside iBD, has a story she uses on this. Her daughter once told her she had three best friends. Kim’s response was simple. “You can’t have three bests. Best is a superlative. You have three great friends. But only one best.” You have one ideal customer. Everyone else is a degree of distance from that ideal, and that distance matters.

Now ask why customers choose them. “We provide excellent customer service. Our people are our greatest asset.” Greg Meredith, the strategic planning advisor inside the OS, runs a test on this from A.G. Lafley. The opposite rule. If the opposite of your strategy sounds ridiculous, you don’t have a strategy. You have a preference. Nobody says “we provide terrible customer service.” It is not a choice. It is table stakes.

This is where revenue strategy fails before any tactic gets executed. The CRM is full. Pipeline is busy. Some quarters hit, some miss. Nobody can quite explain why. The owner becomes the only person in the building who can credibly close a deal, because the owner is the only person who has the full strategic context in their head. Revenue stays tethered to one person.

I lived this in the copier business. For years we chased anything that walked in the door, then wondered why margins were inconsistent and the sales team was always overwhelmed. The moment we wrote down who we actually served (integrated multi-service contracts at the 50-to-500-employee professional services tier), what we actually won on (deep integration on a long contract, not price), and which opportunities to refuse (one-off transactional jobs), the whole engine stabilized. The filter was worth more than any campaign we ran.

Milestone 13 ends the drift. You install the Revenue Architecture document, the strategic filter every revenue decision runs through. Brand, Market, Customer, Competitive Positioning, Offer Structure. Documented in one place. Specific enough that anyone on the team can read it and immediately know whether a deal fits.

What this looks like when it’s installed

The owner of Advanced Solutions entered Year 1 chasing every lead that came in the door. $10M revenue. Top customer at roughly 35 percent of revenue. No documented ICP. The reason “people chose us” was personal trust the owner built over 15 years, which is real but not transferable to a CRO or a buyer. After M10, M11, and M12 installed in Y1, the Q4 90-Day Game Plan™ locked M13 as the One Thing. The owner sat with Kim Clark and Greg Meredith over a three-week sprint and built the Revenue Architecture: ICP locked at $8M-$25M services firms with an aging owner-CEO and revenue concentration over 25 percent with the largest customer. Anti-customer locked at anything below $5M or any prospect wanting a fixed-bid one-time engagement. Winning position locked at integration, the same lesson the owner had to learn the hard way years earlier.

By Year 3 the architecture had filtered out two RFPs in Q4 of Year 1 that would have consumed 200 hours of capacity and $200K in SG&A. A fractional CRO got hired in Year 3 and walked into Kim’s articulation test on day one. By Year 5 revenue grew to $20M, customer concentration dropped below 18 percent, and the multiple expanded from 4.52× to 6.67×, in part because the revenue base became defensibly diversified and the strategy was now written down in a way a buyer could read. That’s what “installed” looks like for M13. Not a marketing plan in a binder. A five-page strategic specification the CRO runs the engine from. Full walkthrough: see the Case Study Reference.

Score yourself

Score yourself honestly against where you are right now. The verification test at the bottom is what separates a real 3 from a wishful 3.

0 (Not Started). You haven’t engaged with the material. You can’t name your single ideal customer. The reason customers choose you sounds like the reason customers would choose anyone in your industry. Default starting point.

1 (Learning). You can articulate the four components of a revenue architecture (ICP, winning position, TAM, offer structure). You can explain the opposite rule. You can name Greg Meredith’s five winning positions (relative scale, integration, operational potency, preferred offerings, exclusivity). No document drafted yet.

2 (In Progress). Revenue Architecture document drafted at the section level. ICP defined but still describes more than one segment or lacks the psychographic layer. Winning position written but hasn’t been pressure-tested with the opposite rule, or fails it. TAM estimated but not tiered. Offer-to-ICP matrix started but knock-you-out sentences are vague (“we are better at this”) instead of quantitative. The document exists but hasn’t been used to make a real strategic decision.

3 (Installed). Revenue Architecture document locked at five to eight pages. One ICP defined with the demographic layer (firmographics, decision-maker role, buying structure) and the psychographic layer (core goal, motivators, demotivators, anxieties, buying behaviors). Anti-customer locked with specific exclusion criteria. Winning position passes the opposite rule with quantitative evidence. TAM quantified and tiered (Tier 1 ideal, Tier 2 strong, Tier 3 opportunistic) with actual company counts. Offer-to-ICP matrix populated with knock-you-out sentences per intersection (the data-backed, specific reason a customer in this segment should choose this offer over alternatives). Architecture has been used to make at least one explicit decision in the last quarter, saying no to an opportunity, killing or refining an offer, or repositioning a segment. The articulation test passes (your revenue leader can close the document and explain the ICP and winning position in their own words). Reviewed annually at the Annual Owner’s Reset.

The verification test. Hand the Revenue Architecture document to your revenue leader (fractional CRO, internal sales lead, or whoever owns revenue). Ask them to close it and explain in their own words who your ideal customer is and why people choose you. “Walk me through the ICP including the firmographic profile and the buying psychology. Tell me one customer segment we recently said no to and why. Name our winning position and one quantitative piece of evidence that backs it. Pick any offer and tell me which ICP tier it’s mapped to and what the knock-you-out sentence is.” If they can do that in 90 seconds with specifics, you’re at a 3. If they fumble, hedge, or open the document to read off it, you’re at a 1 or 2.

Build these five things

Five deliverables. Roughly 30 to 50 hours of focused work the first time, spread across 3 to 5 weeks. M13 is the foundational milestone of Module 5 because nothing downstream (Customer Journey in M14, Forecast in M15, KPI Dashboard in M14) works without it. Run by the owner with a fractional CRO, or by an internal revenue lead if one exists. The owner sets the direction. The CRO maintains the document quarterly. The full canonical Exercise templates and AI Interview Protocols that walk you through each one live inside the Member version of the iBD Ownership OS™ that paying clients fork.

#DeliverableWhat it does
1Revenue Architecture DocumentThe integrated five-section strategic spec (Brand, Market, Customer, Competitive Positioning, Offer Structure). Five to eight pages. The single source of truth the revenue function runs against.
2ICP DefinitionOne profile, two layers. Demographic (firmographics, decision-maker, buying structure) plus psychographic (core goal, motivators, demotivators, anxieties, buying behaviors). Plus the anti-customer definition (who you say no to and why).
3Winning PositionThe specific, defensible reason customers choose you over alternatives. Pressure-tested with the opposite rule. Mapped to one of Greg Meredith’s five winning positions. Backed by quantitative evidence (retention, turnaround, referral percentage).
4TAM + Sub-Market TieringQuantified market count plus Tier 1 / Tier 2 / Tier 3 segmentation with actual company counts. The denominator for market penetration math and the budget allocation guide for Milestone 14 CAC work.
5Offer-to-ICP Mapping MatrixProducts and services × ICP tiers. Fit (yes / partial / no), value proposition, and knock-you-out sentence (the data-backed, specific reason a customer in this segment should choose this offer over alternatives) per intersection.

Run them in this order:

  1. ICP Definition first. Pull 3 to 5 years of historical revenue data by segment, offer, customer, and channel. Note which segments grew, which shrank, which were profitable, which were not. Then build the ICP with the demographic layer and the psychographic layer. Use Taki Moore’s Magic Model or Bob Moesta’s Jobs to Be Done framework to push the psychographic layer deeper. Lock the anti-customer. Resist the temptation to define two or three ICPs. You have one ideal. Everyone else is degrees of distance.
  2. Winning Position second. Where do you actually win today, not where you wish you won. Pressure-test with the opposite rule. Document with quantitative evidence (turnaround time, retention percentage, referral percentage, customer concentration in the segment). Identify which of Greg Meredith’s five winning positions you are climbing toward.
  3. TAM + Sub-Market Tiering third. Get the actual count of companies that match your ICP using industry databases, association data, your CRM, or LinkedIn Sales Navigator. Then tier it. Tier 1 ideal (matches on every dimension). Tier 2 strong (matches on most). Tier 3 opportunistic (might buy, not who you are designed for). Write the tiers with company counts. The result becomes the denominator for the CAC budget allocation in M14.
  4. Offer-to-ICP Mapping Matrix fourth. Build the matrix. Rows = products and services. Columns = ICP tiers. For each intersection, document fit (yes / partial / no), the value proposition, and the knock-you-out sentence. If you can’t fill in the competitive advantage, that’s the signal. Either the offer is wrong for the segment, or the work hasn’t been done yet.
  5. Revenue Architecture Document fifth. Assemble. Five sections, five to eight pages. Brand (positioning + voice + promise), Market (where you play and where you don’t), Customer (ICP + anti-customer + buying triggers), Competitive Positioning (winning position + quantitative evidence), Offer Structure (the mapping matrix output). The other four deliverables feed into this document.

And then the move that separates a 2 from a 3. Take one strategic decision in the next 30 days and explicitly run it through the architecture. A new prospect, an offer expansion, a market entry, a hire request. Document the decision and the reasoning, citing which section of the architecture drove it. The architecture either supports the decision or it filters the decision out. Either outcome counts. That’s the test that proves the document is operating as a system instead of sitting in a binder.

Take your next action

At Level 0 (Not Started). Get exposure to the revenue architecture framework first. The fastest path is the iBD Ownership OS™ Workshop — three hours, $100, walk out with your Velocity Score™ baseline and a working introduction to the four components plus the opposite rule.

At Level 1 (Learning). Block 90 minutes on your calendar this week. Sketch your ICP with the demographic layer plus a first pass at the psychographic layer. Pressure-test your stated winning position with the opposite rule. The full canonical templates and the AI Interview Protocols live in the Member version of the OS that paying clients fork; the Workshop gives you working drafts to start.

At Level 2 (In Progress). Lock the opposite-rule-tested winning position. Quantify the TAM with tiering. Build the offer-to-ICP matrix with knock-you-out sentences. Assemble the five-section document. Run the articulation test on your revenue leader and the filter test on the last five opportunities you pursued.

At Level 3 (Installed). Maintain. Review the Revenue Architecture annually at the Annual Owner’s Reset. Spot-check at every Quarterly Boardroom (is the ICP still right? has the market shifted?). Re-rate yourself if a major market shift, a new offer category, or a competitive entry forces a refresh.

Where this lives once it’s running

The Revenue Architecture is the longest-cycle document in Module 5. The customer journey (M14) and the forecast (M15) move quarterly and monthly. The architecture moves annually, with quarterly spot-checks for material market shifts.

Weekly. The CRO references the Architecture when triaging inbound. The ICP filter applies to every new pipeline opportunity. Anything outside the anti-customer line gets routed to “polite no” templates instead of consuming sales capacity.

Monthly Tuesday flywheel. Wk1 is the CRO functional review. Revenue is reviewed against architecture-driven targets (Tier 1 vs Tier 2 vs Tier 3 mix). Drift between the architecture’s promises and actual revenue mix gets flagged. The CRO presents at the MOM Financial Signal Review.

Quarterly. Spot-check at the Quarterly Boardroom. Is the ICP still right? Has the market shifted? Are the offer-to-ICP knock-you-out sentences holding up against competitor moves? Strategic priorities feed the next 90-Day Game Plan™.

Annually. Full Revenue Architecture reassessment at the Annual Owner’s Reset. Market shifts. Competitive changes. New opportunities. New ICP segments. Architecture refreshed alongside the Annual Budget rebuild and the forecast re-rate.

If you don’t have the cadence built yet (you’re working M13 for the first time and M7/M8/M9 haven’t been installed), run your own quarterly review against the architecture. Pull the document. Walk through the last 10 opportunities. Count how many fit the ICP cleanly versus how many are off-profile. Make at least one decision (kill a pursuit, refocus a segment, refine an offer). The cadence formalizes later. The discipline of running revenue from the architecture starts now.

How this fits in the OS

Prerequisites. Milestone 10: Three-Statement Model, Milestone 11: Annual Budget, and Milestone 12: 5-Year Forecast & Valuation. Module 4 produces the financial system that consumes Module 5’s revenue forecast. Without M10 you can’t model the cash impact of an ICP choice. Without M11 you can’t size the CAC budget against architecture-driven targets. Without M12 you can’t trace ICP × TAM × penetration × offer mix back to a 5-year valuation. M13 also tethers to Milestone 2 and Milestone 3 from Phase 1, because the architecture has to produce the cash flow targets the owner committed to in M2 and the enterprise value trajectory the owner committed to in M3.

What this feeds. Everything in Module 5 and onward. Milestone 14: Customer Journey & CAC designs the customer journey for the ICP defined here. The CAC budget in M14 is allocated against the Tier 1/2/3 split locked here. Milestone 15: Revenue Systems & Forecasting builds the bottom-up forecast on top of the ICP × TAM × penetration math from this milestone. Milestone 16: Target Gross Margins uses the offer-to-ICP mapping to drive per-line gross margin discipline. Milestone 19: 3 Functional Leaders defines the CRO seat against the revenue function installed here.

Where it sits. First milestone of Module 5 (Predictable Revenue). M13 sets the strategy. M14 makes the strategy operational through the customer journey and CAC discipline. M15 makes the strategy accountable through systems and the bottom-up forecast. Together, M13 + M14 + M15 turn revenue from the owner’s personal effort into a CRO-run engine that produces a defensible top line.

Want help getting from a 1 to a 3?

The iBD Ownership OS™ Workshop is the paid filter where you experience the OS for yourself. Walk out with your Velocity Score™ baseline across all 27 milestones, a working introduction to the Revenue Architecture, and a sense of whether your stated winning position survives the opposite rule.

Join the next workshop →

← Back to Module 5: Predictable Revenue · ← Milestone 12: 5-Year Forecast & Valuation · → Milestone 14: Customer Journey & CAC

Graph View

Backlinks