Strategy and positioning · Answered by Golden Section from more than 400 B2B software companies observed
Translate it in four linked steps, each with a named owner. Write a one-page plan stating the three-year picture, this year's goals and what you will not do. Break the year into three to five quarterly priorities, each with one owner and a written definition of done. Build the budget from those initiatives, so each carries its cost and expected revenue, and check the revenue against a sales efficiency the team has actually achieved. Then wrap a weekly scorecard of five to fifteen numbers and a fixed meeting rhythm around it, so the plan is read every week rather than once a year. Product strategy is the same chain applied to engineering: the roadmap should be the budgeted sequence of the company's priorities, not a separate wish list, with about 10% of engineering capacity held for reliability and other non-roadmap work. Start with the one-page plan and the not-doing list.
A strategy has become an operating plan only when every priority has one owner, a budget line, a number on the weekly scorecard and a date. Where any of the four is missing, the priority is still an intention.
| Metric | Value | What it means | Source |
|---|---|---|---|
| Weekly scorecard | 5–15 numbers | weekly, mostly leading measures, each with one owner and a targetif populating it takes one person more than an hour on Monday, it is the wrong scorecard | Golden Section playbookExecution Operating System play |
| KPIs per leader | no more than 2 | KPIs each leader owns on the dashboard, each with an acceptable range and a pre-agreed actiona KPI without an obvious action is a vanity metric | Golden Section playbookKPI Dashboard Creation play |
| Budget realism check | top quartile struggles to beat $0.75 | total sales and marketing expense per $1 of new ARRthe play's example management team planned on $0.45 in its most pessimistic case | Golden Section playbookBudget Creation play |
| Roadmap review cadence | at least quarterly; monthly at early stage | roadmap meeting where sales, support, engineering and leadership compete for priorityreliability gets its own swim lane; no unit wider than three sprints | Golden Section playbookProduct Management Process play |
| Reliability reserve | about 10% | share of engineering capacity reserved for reliability and non-roadmap workits own swim lane on the roadmap, so it is planned rather than borrowed from priorities | Golden Section operating viewGolden Section operating view |
Most plans fail at the handoff from the offsite to the calendar. The strategy is sound, but nobody owns the pieces, the budget was built from last year's spreadsheet and the roadmap was settled in a separate meeting with its own priorities. Six weeks later the company is running on whatever the loudest customer asked for.
The chain has to be continuous. Executive execution sets the vision and the strategic plan; the execution operating system turns it into seats, quarterly priorities and a weekly meeting; budget creation prices each initiative and holds the revenue to realistic efficiency; the KPI dashboard gives every leader the numbers that show whether their part is working. The product roadmap is where product strategy joins: it should read as the engineering sequence of the same priorities, with the reliability work the company needs alongside; we reserve about 10% of engineering capacity for it. Which planning framework carries the chain matters less than running one consistently.
The payoff is not only execution. Our KPI and strategic meetings play makes the point that minutes and scorecards collected over many months are the evidence a buyer looks for that the company runs on systems rather than on the founder.
The numbers are fictional. A $6M company's strategy is to become the system of record for mid-size firms in its vertical. The plan names three priorities for the quarter: ship the accounting integration, cut median onboarding to 45 days and add two account executives. The budget prices each one, and the revenue line assumes $0.80 of sales and marketing per dollar of new ARR, the company's trailing figure, rather than the $0.50 the sales lead wanted. The roadmap gives the integration its own swim lane and pushes two requested features to next quarter. The weekly scorecard carries integration milestones hit, days to onboard and qualified pipeline per AE, each with one owner.
A team of under ten people does not need the full apparatus. A weekly meeting with a fixed agenda, five numbers with owners and three priorities a quarter is enough until someone other than the founder manages people.
From the Golden Section mistakes list, each paired with the play that prevents it.
Without a named operating system, strategy never becomes what somebody does on Tuesday.
A priority with two owners or none is the most common reason a plan stalls.
A vague roadmap is where product strategy and company strategy quietly separate.
In the order we would run them. Each is on its own page, most with a free Excel template.
Sets the vision and strategic plan that everything downstream is measured against.
Turns the plan into seats, quarterly priorities, a scorecard and a weekly meeting.
Prices each initiative and keeps revenue assumptions realistic.
Gives each leader the numbers and pre-agreed actions for their part of the plan.
Connects product strategy to the company plan as a sequenced, owned document.
Executive plays The full planning sequence from vision and mission to budget, KPIs and the meeting rhythm.
Product strategy is the company strategy expressed as an engineering sequence. The roadmap should show the company's priorities in build order, with reliability work in its own lane taking about 10% of engineering capacity, and be reviewed at least quarterly with sales, support and leadership in the room. A roadmap set by sales or by engineering alone drifts away from the strategy.
We do not mind which. The framework matters less than running one consistently: a written plan, quarterly priorities with single owners, a weekly scorecard and a fixed meeting rhythm. EOS, Scaling Up and OKR-based systems can all supply that; OKRs on their own are a goal-setting method and still need the meetings, seats and issues list built around them. Pick one and run it straight for four quarters.
Score it weekly through the scorecard, review the financials monthly against budget, reset priorities quarterly and rebuild the plan annually. Systems rarely die at the weekly meeting; they die the first time a quarterly session is postponed and not rescheduled.
About 10% of engineering capacity, as our operating view. Give it its own lane on the roadmap so it is planned, not squeezed in, and so the remaining 90% can be held to the company's priorities without bugs and infrastructure work quietly eating the plan.
An operating plan tied to a budget and a scorecard is also what a growth investor diligences, because it shows whether new capital would be spent against a plan. Build it first; raise against it if the plan needs a change the business cannot fund itself.
Growth equity →Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-10-22. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.