The question comes up constantly in hiring conversations, agency pitches, and org-design meetings: what is a marketing team's general size and structure? It sounds like a question with a clean, benchmarkable answer, something like three to five people for an early-stage company or a ratio of one marketer per certain amount of revenue.

But that framing belongs to a different era. The moment a team starts building and using AI programs and tools, the concept of a headcount-based answer starts to break down. The video opens by posing this question directly, then immediately signals that the real answer requires a rethink.

The speaker calls it a trick question, and the trick is this: the question assumes that output scales with headcount. In a pre-AI marketing environment that assumption was reasonable. Writers wrote, designers designed, developers built, and you needed enough of each to cover the workload. Adding output meant adding people.

That assumption no longer holds for teams that have integrated AI into their daily work. When the tools themselves generate drafts, build assets, and automate distribution, the bottleneck shifts from labor to direction and judgment. A team of three people with the right AI programs in place can outproduce a team of thirty operating on legacy workflows. Calling it a trick question is the speaker's way of flagging that any benchmark you compare against is probably measuring the wrong thing.

The speaker is specific: it is not that the team has one AI specialist or one automation engineer. All of the marketing team has AI and programs and tools that they have built. The phrase 'we've built' matters here. These are not off-the-shelf subscriptions clicked together. They are custom programs developed for the team's specific workflows, which means the productivity advantage compounds over time as the tools improve.

Building in-house also means the tools fit the exact content formats, brand voice, distribution channels, and approval workflows the team actually uses. A generic tool helps everyone a little. A custom-built tool helps your team a lot, because it encodes your specific process and can be iterated on as that process evolves.

The takeaway for anyone structuring a marketing team today is that the infrastructure question, what AI and tools does each person have access to, is at least as important as the headcount question.

The speaker gives two concrete benchmarks to make this tangible. One intern or marketing team member might create a whole website in an afternoon. The same person might create hundreds of videos in that same timeframe. These are not edge cases or best-case scenarios presented as averages. They are normal outputs for someone working inside an AI-enabled production environment.

Creating hundreds of videos in an afternoon would have required a production company, a multi-day shoot, and significant post-production budget under traditional workflows. Building a whole website in an afternoon would have required a designer, a developer, and a project manager at minimum. The fact that one intern can now do either of these things in a few hours is a direct measure of how much the tools have shifted the production equation.

For anyone making staffing or budget decisions, these benchmarks reframe where investment should go. The leverage is in the tools and the systems, not in adding more junior headcount to run legacy workflows.