a builder's codex
codex · operators · Kieran Flanagan · ins_flywheel-ai-cross-functional-pod

Cross-functional pod (product + eng + data + ops + marketing) is the org unit for agentic GTM

By Kieran Flanagan · Lead, Agentic GTM & Systems group, HubSpot · 2026-05-01 · thread · I'm officially no longer a marketer — Flywheel AI pod

Tier A · TL;DR
Cross-functional pod (product + eng + data + ops + marketing) is the org unit for agentic GTM

Claim

Rebuilding GTM around AI requires a cross-functional pod that spans product, engineering, data science, operations, marketing technology, and digital experience — not a marketing team adopting AI tools. HubSpot calls this pod "Flywheel AI" (now "Agentic GTM & Systems group") and it produced 1,850% growth in qualified leads from ChatGPT/Perplexity, 82% inbound chat deflection, and a 13% win-rate lift via AI deal guidance.

Mechanism

Agentic GTM bets cross multiple traditional functional boundaries — an AEO bet needs marketing intent + engineering + data + content; an inbound-agent bet needs product + ops + support context. Putting decision rights inside one pod removes the queue between functions. Pass learnings back to the rest of the company as product features and playbooks rather than memos.

Conditions

Holds when: the company has enough scale to staff a cross-functional pod and the CEO/CMO will protect it from being absorbed back into functional silos.

Fails when: the pod is staffed only with marketers (becomes a marketing-AI-tools team), or when bets are evaluated by functional KPIs rather than pod-level outcomes.

Evidence

"We've created a talented group of people across areas like product, engineering, data science, operations, marketing technology, digital experience, and more. We call it the Agentic GTM & Systems group. The premise is to move fast, take bigger bets, find signals, and pass learnings to customers in the form of product and playbooks."

— Kieran Flanagan, LinkedIn, 2026-05-01

Signals

Counter-evidence

Smaller companies cannot staff this pod shape — the JTBD has to be embedded in the founder or a single GTM-engineer hire (see ins_principal-ic-is-force-multiplier.md).

Cross-references

Open the interactive view → View original source → Markdown source →