Strategy only matters
when it changes decisions.
Seven steps the work moves through regardless of which engagement (Audit · Sprint · Retainer) or which playbook (vertical · operating) is doing the carrying. Two operating principles underneath them. This is the deeper logic the architecture review asked to move off the Services hub — preserved here, one click deeper.
- 01
Start with the actual problem
Most companies over-diagnose symptoms and under-diagnose the operating system behind them. The first week is mostly about disambiguating which of the ten common problems is actually in front of you, and which two or three are dressing up as it.
- Disambiguate the named problem from the operating-system problem behind it
- Stakeholder + customer + lost-deal interviews (5–8 in the first week)
- Honest CRM read — pipeline math, reason codes, churn cohorts, NDR
- Existing strategy work read against, not over — no decks-on-decks
- 02
Diagnose the market
Read the commercial system end-to-end before designing any motion. Most stalls aren't a single-axis problem; they're a six-axis read on category maturity, buyer urgency, budget owner, partner ecosystem, competitive frame, and proof.
- ICP — primary, secondary, strategic partners, bad-fit segments
- Buyer — value prop, proof points, objection handling, market education
- Budget owner — line item · gate · veto · the room where it lands
- Competitive frame — direct, adjacent, substitution, the wedge
- Partner ecosystem — agencies · platforms · resellers · data · identity · measurement · supply
- Proof readiness — case, privacy, measurement, governance assets
- 03
Package the use case
A product that survives technical review doesn't survive procurement unless the use case is packaged like a procurement artifact. The "what" and the "why now" get tightened until a buyer can repeat them back without the deck.
- Buyer trigger + business value, in the buyer's vocabulary
- Proof package — case studies with reason codes, privacy posture, measurement evidence
- Pricing + packaging — procurement-friendly mechanics, expansion path, commercial guardrails
- Objection handling + discovery script, tightened against real calls
- Sales assets — one-pager, narrative deck, technical FAQ
- 04
Design the operating model
Strategy without an operating model is just a deck. The model puts ownership, decision rights, capacity, and cadence in writing — and ties capacity-to-revenue, not headcount-to-seats.
- Ownership + decision-rights matrix (founder owns 3–5 things; the org owns the rest)
- RACI for the full customer journey — Sales · CS · AM · Product · Finance
- Team topology — global / local · regional GMs · first-hire role specs + scorecards
- Capacity model — quota × ramp × attrition × manager-as-IC tax, reviewed monthly
- Cadence — weekly forecast · monthly capacity · quarterly board · 30-day reason-code review
- For post-sale: customer health scoring + expansion triggers + NDR cadence
- 05
Sequence the GTM motion
Most companies try to launch every channel and every region at once. The motion is sequenced — first accounts, first partners, first proof, first hire, first 90 days — and what to ignore is named as explicitly as what to do.
- First named-account list, ICP-graded and sequenced
- Partner sequencing — indie → mid-tier → holdco → strategic, with the wedge per phase
- First proof — the two or three case studies, privacy / measurement assets, and operating artifacts that gate enterprise deals
- First hire — role spec + scorecard + 90-day plan written before the search opens
- First 90 days — focus · sequence · proof · motion · accountability, decision owner named
- What to ignore — segments, partners, roadmap lines worth not running
- 06
Ship artifacts
Every engagement produces concrete operating artifacts — the kind a new hire can pick up on day one and use. Strategy that doesn't ship artifacts doesn't survive the next quarterly cycle.
- ICP matrix + buyer narrative
- 90-day GTM plan (focus · sequence · proof · motion · accountability)
- Partner sequencing map
- MSales SLA + stage gates + reason codes
- RACI tables (sales, CS, AM, product)
- Role scorecards (first commercial / first regional hire)
- Data collaboration canvas + readiness gates
- Customer-health scoring + expansion-trigger map
- Output policy, POC-to-production plan, sample dashboards
- 07
Create repeatability
The system has to outlast the engagement. Cadence, feedback loops, governance, and the next optimization loop are designed so the company can run the operating motion without external sponsorship — and graduate what works into the next quarter's playbook.
- Operating cadence (weekly · monthly · quarterly · annual)
- Reason-code review every 30 days — what to retire, what to graduate
- Customer / market feedback loop wired into CRM + product
- Governance — privacy, data, commercial, partner
- Next optimization loop — where the system's leverage will go in the next 90 days
- Handover plan + named internal owners
Two lines this method comes back to.
Start with the decision, not the platform.
Whether the question is clean rooms, CDPs, MMM, agentic protocols, or commercial hires — the platform conversation is downstream of the decision conversation. Most stalls happen because the order gets inverted.
Decisions in weeks, not quarters.
Every engagement has a defined scope, cadence, owner, and output. No open-ended advisory. If a read can't change a decision inside 30 days, the engagement is wrong-sized.
Three sideways moves from here.
The method above names how the work moves. These are the three surfaces around it — the problems it gets pointed at, the engagement shape that carries it, and the diagnostic that maps your current gaps to the right entry.
- Problems Ten common growth problems Where growth breaks — pipeline friction, unclear ownership, weak proof, partner gaps, post-sale leakage. Each problem routed to a best-fit playbook, engagement, and scorecard path. See common problems →
- Engagements Three ways to work together Market Entry Audit (2–3 weeks) · GTM & BD Sprint (6–8 weeks) · Advisory Retainer (3 / 6 / 12 months). Scoped, cadenced, owned. See engagements →
- Diagnostic Readiness scorecard Six paths · ~6–8 minutes · no email · browser-stored. Routes you to the right operating playbook based on your current gaps. Take the scorecard →
Want this applied to your operating motion?
Pick the engagement shape that fits where you are. Each one runs the method against a different time-horizon: Audit for a 2–3 week read; Sprint for a 6–8 week execution push; Retainer for ongoing operating partnership.