Org design for product-led growth

PLG isn't decided at an offsite.

It's hundreds of small daily decisions — which means it has to be in the org structure or it doesn't happen.

Pod 01 Signups PM · engineer · designer · data scientist +38% signup volume, quarter to date

Pod 02 Onboarding PM · engineer · designer · data scientist −11% activation rate, same quarter

Pod 03 Notifications PM · engineer · designer · data scientist +4% re-engagement, same quarter

Every pod hit its number. The gaps between them are where the users went. Nobody's name is on the gaps.

Step one

Pick a growth team model.

Three shapes are in use across product-led companies. They differ in what a pod owns — headcount, a flow, or a metric.

Select a model to see its shape and reporting line

Model 01

Dedicated growth team

5–10 people, rolls up to the CEO, with a PM + designer core. Add engineers and data scientists as it grows.

Right for most companies starting out

CEO

VP of GrowthOwns the number and the seams

Growth PM + designerThe permanent core, 2 people

Engineers + data scientistsAdded as the team scales to 5–10

The failure mode

Every model breaks in the same place.

Pods optimize their own number and wreck the experience between them. Signups floods a funnel Onboarding isn't staffed for; users bounce.

Monthly signups from the Signups pod

4,000

Activation rate today

35%

Activation rate with the handoff owned

50%

Annual value per activated user

$1,200

What the seam costs you

Users lost in the gap, monthly 600

Revenue left in the gap, per monthly cohort $720,000

Cost per point of activation $48,000

4,000 signups × 15 points of activation left on the table = 600 users a month. 600 × $1,200 a year each = $720,000 a year, from one month's signups.

Move the sliders to your own numbers. The arithmetic is deliberately simple so you can check it — no attribution model, no assumed lift curve.

That's what the VP of Growth is for. Not to run a team — to catch the handoffs. Metrics flow into each other; someone has to own the seams.

Where growth sits

Separate from product, but adjacent.

Product builds long-term. Growth reacts to engagement data. They intersect in four places, and each one is a different kind of handoff.

01 Layer on top Growth adds the prompts and guides on what product ships. Same feature, discovered by more users.

02 Validate, then hand over Growth proves a hypothesis with a hack, then hands it to product to be built properly.

03 Remove friction Product ships something users can't swallow. Growth takes the friction out of the path to it.

04 Accelerate adoption Something good already shipped. Growth pushes it in front of the users who'd benefit fastest.

Culture and incentives

Measure the thing you want.

Aggressive ship-learn-ship cadence. Hack after hack to prove a theory. Perfect is BS. Then pay on the number you actually want moved — Deputy bonuses its squad on percentage improvement in conversion rate.

Growth squad scoreboard — conversion-rate lift, quarter to date Bonus pool tied to lift, not shipped count

Signups17 experiments shipped +18.4% 1.8×

Onboarding11 experiments shipped +9.1% 1.0×

Notifications23 experiments shipped +3.6% 0.4×

Trial-to-paidShared target, all squads +12.7% 1.3×

Notifications shipped the most and moved the least. On a shipped-count incentive it wins the quarter; on a lift incentive it doesn't. What you measure is what you optimize for.

The over-rotation

Don't build a funnel nobody sells.

Going all-in on product and engineering has a predictable cost, and a known fix. Both are worth putting in writing before you reorganize.

The warning Too product-and-engineering-centric alienates the rest of the go-to-market org. Sales, marketing and customer success get designed around instead of designed with. You end up with a beautiful funnel nobody sells. Jeff Diana

The fix Shared revenue targets across leadership. When the whole business shares a goal, the silos don't form. One number on every leader's page, not one number per function. Hiten Shah

While you're in the org chart

Move marketing budget from acquisition to retention.

Product updates, education, training, onboarding. Marketers should care as much about trial-to-paid as they do about traffic.

Before — acquisition-weighted

Points go on the board when a lead arrives.

Acquisition 78%

Retention and education 22%

After — retention-weighted

Points go on the board when users become paying, active, and vocal.

Acquisition 45%

Retention and education 55%

Rewire the org

The structure decides whether PLG happens.

We build and run the system that turns demand into revenue — including the reporting lines, the pod charters and the seams between them.

→Model picked and written down, with headcount and reporting line. →Seams named — every handoff between pods has one owner. →Growth adjacent to product, with the four intersections agreed. →Bonuses on conversion-rate lift, not on experiments shipped. →One shared revenue target across every leader in the business. →Marketing rebalanced toward trial-to-paid, not traffic.

PLG isn't decided at an offsite.

Pick a growth team model.

Dedicated growth team

Organized by flows and features

Organized by metrics

Every model breaks in the same place.

Separate from product, but adjacent.

Measure the thing you want.

Don't build a funnel nobody sells.

Move marketing budget from acquisition to retention.

Points go on the board when a lead arrives.

Points go on the board when users become paying, active, and vocal.

The structure decides whether PLG happens.

Services

Company

Resources

Industries