The Head of Growth as we knew it is ending. Not because growth matters less, but because the team it used to manage is being rebuilt around agents. The Growth-Origin Model is the structure that replaces it, from seed to Series B. It covers everything built to acquire, activate and retain customers. The core product stays with product and engineering, where it belongs.
In 2004 I was working on a new idea in affiliate marketing. It was not an instant success. But thinking about scale and the network effect led us to launch a marketplace, and with it some tools nobody was offering publishers back then. That work created a massive opportunity, and it led to an exit in 2010.
The lesson I kept was not about affiliates. The best growth started with product and features. Ideas first. Then execution and testing on those ideas.
Then I moved into growth roles and the same pattern repeated. I built my own analytics dashboards. I learned along the way. I wrote requirements for the eng team. I was basically the product guy for one channel in the company.
At a B2B startup it happened again. Most of my conversations were about the data layer. Integrity, parity, working with product on features, reviewing MAU and the golden motions that led to retention. Only after that did those learnings feed the marketing execution layer and the campaigns.
That was slightly unusual back then. It was also when the big swings and wins happened.
Product thinking was maybe 10% of a growth leader's job, squeezed in around managing execution. AI removes the squeeze. The execution layer is now agents, and what's left is the product thinking. The person best positioned to hold it is not a PM learning growth. It's a growth person whose product instincts finally have room to run.
This is how software gets built in most companies: product decides, design draws, engineering builds, security checks, and each one hands the work to the next. Growth gets what's left at the end: optimize this. I lived on the receiving end of that chain for years, and so did every growth person I know.
For the core product, this line still makes sense. For everything built to acquire, activate and retain, it's dead.
Growth people always originated ideas. What we never owned was the origination of the surfaces themselves: the pages, flows and signups were born in the product backlog and built by other teams. That's what changes. For anything built to engage users, landing pages, signup flows, paid media pages, nurtures, the origination now sits with growth. Growth starts the work, agents fill the build roles, and the results feed the next decision. Core product stays outside and connects through one gate.
And notice where the loop starts: at Judgment, not at Signal. There is no signal until the Growth Architect ships something for the market to react to. Then the market responds, or it doesn't, and silence is a signal too. Learn is where that signal turns into knowledge, and Judgment is where knowledge turns into the next decision.
Growth loops describe how users compound. The Growth Origin Loop describes how the team operates.
At seed, the Growth Architect runs the entire Growth Origin Loop alone. Signal comes from founder-led sales, the judgment on what to build is theirs, and agents handle everything in the middle.
Owns the full loop. Decides what's worth building, holds the quality bar, orchestrates the agents.
Every GTM surface, with brand encoded as constraints in the agent config so the output is on-brand by default.
Two hours a week at the blast-radius gate for auth, payments and data models. Nothing else crosses their desk.
Advance when → surface volume outgrows one person's judgment, not their hands.
Velocity is about to 10x, and the point is loop speed, not surface volume: faster signal to live, faster learning, and more kills. Velocity without rails collapses exactly here, so the first dedicated hire is not another marketer. It's the person who makes speed safe.
Same role, sharper focus: prioritization and the quality bar. Stops building everything personally.
70% data layer: tracking schema, integrity, parity. 20% the blast-radius gate. 10% keeping bought tools glued. The rails are bought, not built, and the Rails Engineer never builds surfaces: if a surface ever blocks on them, the rails have failed.
Runs paid and lifecycle. Their main output into the pod is demand signal, not just managed spend.
Fill every middle role of the old line. Ship on the rails, at agent speed, on brand by default.
Advance when → one loop can't hold both acquisition and activation without one of them starving.
You don't grow the pod. You clone it. Two loops on shared rails, and one of the two architects steps up as Principal Growth Architect: they own the portfolio of loops and arbitrate what shares the rails and the gate.
And this is where the moat changes. By Series B, competitors can replicate any page you ship in a day. They can't replicate what people believe about you.
Owns trust as a portfolio: domain reputation, deliverability, security posture, proof and credibility inventory.
Advance when → a third loop earns its own P&L. Past that, you're a different company.
The title made sense when growth meant managing a layer of pure executors: designers, developers, agency hands. That layer is what disappears. People remain, fewer and faster, and every one of them runs agents of their own.
The role doesn't disappear either. It evolves. The head of growth as a pure leader of the growth team, with a product partner alongside, is no longer needed. Product skills used to be maybe 10% of the oversight. Now they're most of the job. Some could argue product should take the role. I think it's far more natural for a growth person to bring in the product expertise, because this role originates from the growth mindset and ways of doing things.
We tested this idea before. The full-stack growth person of the early 2010s failed because execution ate them alive, at B-minus quality. What used to be an idea, a test of a team, now becomes reality with A+ execution. It's the dream come true for growth hackers: something they were never able to fully do before, now they can.
The question is whether they lost their touch. Some did. Some were resilient, kept learning along the way, and didn't drown in the management role. Those are the ones this model is built for.
The concepts and the foundation are already there in a good growth operator. What they need to fully add is the product layer on top, and the discipline that comes with it.
Decides what's worth building. Kills weak ideas before agents make them cheap to ship anyway.
Reads signal, understands channels and conversion mechanics from real reps, not frameworks.
Directs Claude and MCPs like a build crew. Documentation is the medium: the spec becomes the prompt, the decision log becomes the memory.
You describe where the numbers are and where they should be. We'll tell you which layer is the problem, honestly, including when the answer isn't us.
We reply from a real address, usually same day. Your details go to our CRM and nowhere else, and we don't add you to a list you didn't ask for.