Product and engineering · Answered by Golden Section from more than 400 B2B software companies observed
Hire a product manager when deciding what to build has become a full-time job and nobody is doing it well. The usual signs are a roadmap that changes after every sales call, engineers starting sprints without ready user stories, and a founder whose product time is crowding out selling and capital. Annual revenue is context rather than a trigger. In vertical software the first product manager should come from the industry, someone who knows the customer's workflow, rather than a generalist from a large software company. The founder keeps the product vision and the final call at the roadmap meeting and hands over the process: discovery, user stories, the roadmap file and its versions. Before you open the search, write down who actually decided the last ten things engineering built.
Hire a product manager when the work of researching and prioritizing what to build no longer fits beside the founder's other jobs. Hand over the process and keep the vision; a product manager who is expected to invent the strategy is being hired for the founder's job. Recruit the first product manager from the industry, and keep the final roadmap call with the founder.
| Metric | Value | What it means | Source |
|---|---|---|---|
| Product roadmap meeting cadence | at least quarterly; monthly at an early stage | the meeting where sales, support, engineering and the executive team argue for priorities and the product manager versions the roadmapthe meeting the product manager owns; if it is not happening, nobody is doing the job | Golden Section playbookProduct Management Process |
| Roadmap resolution | no more than 3 sprint cycles per unit | the time span one column of the roadmap covers, with a swim lane per module and one for reliabilitya test of whether the roadmap is detailed enough to manage against | Golden Section playbookProduct Management Process |
| R&D spend, private B2B SaaS median | 22% of ARR | research and development expense as a share of ARR2026 survey of more than 1,000 companies; 24% at $3M to $5M ARR; a check on the size of the whole product and engineering budget, product management included | External benchmarkSaaS Capital, 2026 Spending Benchmarks for Private B2B SaaS Companies |
| R&D spend | under 20% of revenue | research and development expense as a share of revenuea ceiling for the whole product and engineering budget, product management included | Golden Section operating viewGolden Section operating view |
A small product organization has two jobs. Product management decides what to build and product engineering decides how to build it, or in the language of the product management play, building the right thing and building the thing right. When the first job has no owner it does not go undone. Sales fills it with the features that would have closed last week's deal, or engineers fill it with the technology they find interesting, and both produce a product that drifts away from the customers who pay for it.
The founder's role changes rather than ends. The founder writes and defends the product vision, and the founder arbitrates the roadmap meeting when the functions cannot agree. The product manager runs everything underneath: customer discovery, user stories, the roadmap file and its versions, and the feasibility conversations with the technical lead. The hire fails most often when the founder keeps rewriting user stories after handing them over, which takes the authority away and returns the job to the founder's desk. Put the roles in a RACI chart with the dev org chart before the first day.
The numbers are fictional. A vertical software company at $3M in annual revenue has seven engineers and a founder who runs product between sales calls. Reviewing the last ten features shipped shows six were requested by a single customer during a sale, and two were never adopted by anyone. The founder writes a one-page product vision, hires a product manager who spent eight years running operations at a customer in the same industry, and keeps the chair at a monthly roadmap meeting. The product manager owns discovery, user stories and the roadmap file. Two quarters later, the test is whether the share of shipped work requested by more than one core customer has risen, and whether sprints start with stories ready.
A founder who came from product and wants to stay there can hire an operating leader for sales or the business instead and remain the product manager. And in heavily regulated verticals, where requirements carry compliance weight, a domain-expert product manager may be needed earlier than the workload alone suggests.
From the Golden Section mistakes list, each paired with the play that prevents it.
Without a product manager, sales becomes the default controller of the roadmap rather than one input to it.
The other default is engineers deciding what to build, which produces technically interesting features customers did not ask for.
The product manager's job is to keep industry knowledge in the room, which is the cure for building in a vacuum.
A founder who keeps rewriting stories after the hire takes back the authority the product manager needs.
In the order we would run them. Each is on its own page, most with a free Excel template.
Defines the vision document, the product manager's responsibilities and the line between product management and engineering.
Gives the product manager the artifact they own and the meeting that keeps it honest.
Places the product manager beside the analyst, technical lead and QA with a RACI chart so accountability is clear.
Runs the search against a weighted scorecard, with someone who knows the vertical in the tandem interview.
Development plays The product management, roadmap, engineering process and org chart plays that a product manager will run.
Owner of the product vision and the final word at the roadmap meeting, which stays with the founder after the hire. The founder should not be writing user stories, sizing sprints or versioning the roadmap once a product manager is in the seat. Stepping back into those after handing them off is how the hire fails.
Size it from the budget and the roadmap rather than from a ratio. A complete team carries a product manager, a business analyst, a technical lead, engineers and QA, and early on one person may sit in several of those seats. As a check, our operating view is to keep total R&D under 20% of revenue; private B2B SaaS companies report a median 22% of ARR, and equity-backed companies spend materially more than bootstrapped ones.
No. In vertical software the first product manager should come from the industry. The play describes the product manager as often an industry expert who understands the customer's workflow and common problems; technical feasibility comes from the technical lead and the architect, whom the product manager works with on every new project.
The product manager decides what is worth building and in what order. The business analyst turns those priorities into user stories that are ready for engineers and checks the result against them. On small teams the product manager often does both until the backlog outgrows one person.
A first product manager is an operating-budget decision rather than a reason to raise. Golden Section can also provide experienced product management talent to the companies we back, which helps non-technical founders plan properly without a costly executive search. Building a product and engineering leadership layer the company has never had, alongside a platform change, is the kind of structural change minority growth equity is meant to fund.
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.