When to hire your first growth person

Hire your first growth person after product-market fit is evidenced and basic instrumentation exists, and not before. The consistent guidance across the practitioner canon places the hire around the point where a company has real revenue and flattening retention curves. Hiring growth earlier buys acceleration of an unverified system, which is the premature-scaling pattern the Startup Genome research flagged as the most common startup killer.

The three prerequisites

Evidence of fit: flattening cohort retention curves, or a Sean Ellis survey at or near the 40 percent very-disappointed threshold, or expanding usage inside existing accounts. Instrumentation: churn, activation, and channel-level acquisition cost measurable, because growth work on unmeasured ground produces motion rather than knowledge. And capacity to act: someone with authority to change product, pricing, or funnel, since a hire whose findings nobody can act on is an expensive document.

Missing a prerequisite does not mean do nothing; it names the actual first job. Pre-fit, the spend belongs in customer research and product iteration. Unmeasured, it belongs in instrumentation. Both cost less than a senior salary.

Which role to hire first

The constraint decides, which is why the diagnosis precedes the job description rather than following it. A retention constraint wants a growth product manager close to the product. An acquisition constraint with working economics wants a channel operator. A data constraint wants an analyst before anyone else. The recurring and expensive miscasting is hiring a senior growth leader as employee number eight to fix a retention problem: at that stage, retention problems are product problems, and the right spend is research, not leadership.

The market context is worth pricing in: a senior growth leader typically costs a low-to-mid six-figure package once equity and on-costs are counted, takes a quarter to find and another to orient, and tenure in growth leadership runs short, commonly reported around two years, often because expectations were set wrong at hiring.

The expectation calendar that makes the hire work

Write it down before the offer goes out. By week four: a diagnosis, with instrumented metrics, cohort curves read, the constraint named, and a prioritized backlog. By the end of quarter one: validated learning at honest velocity, a few shipped wins, several killed hypotheses, and a sharper model of the business. Movement in the compounding metrics, retention, payback, net revenue retention, by quarters two and three, because cohorts need time to age before their behavior can be read. A leader hired against a 90-day revenue expectation in a system needing two quarters of repair fails on schedule regardless of skill.

Frequently asked questions

Should the first growth hire be senior or junior?

Match the constraint and the founder’s bandwidth. A senior hire buys judgment and costs runway; a strong operator-level hire executes a named constraint at half the price. What never works is seniority purchased as a substitute for diagnosis.

Can founders run growth themselves at first?

They usually should: through fit-finding, the founder is the only person with the customer contact the work requires. The hire belongs at the point where the system is verified and the founder’s time is the bottleneck.

What should a growth hire deliver in 90 days?

A diagnosis, an operating rhythm, and validated learning, not transformed revenue. Compounding metrics move on a quarterly clock; anyone promising otherwise in the interview is describing a different job.

The job description is downstream of the diagnosis. Run the audit first, name the constraint, then hire the person built for that constraint.