Joris van Kappen recently shared something that caught my attention: "Everyone thinks marketing fails because of execution. Until they realize the role was never designed to make revenue repeatable." He followed with a line that should make any B2B SaaS leader pause: when responsibilities are unclear, "growth depends on luck."

That framing resonates because it challenges a common reflex. When pipeline dips, we look for better campaigns, sharper copy, more meetings, or a new channel. Joris is pointing to something upstream: the system design of the marketing function itself. If the Head of Marketing role is built to ship activities, you will get activities. If it is built to create compounding advantage, you can get repeatable revenue.

In this post, I want to expand on Joris's idea as if we were sitting down with the org chart, the KPI dashboard, and the weekly meeting calendar in front of us. Because "marketing execution" is rarely the real constraint. The constraint is whether your company has designed marketing as an operating system for growth.

Execution is not the bottleneck when the system is wrong

Joris described the symptoms of a role that is not designed for repeatability:

"Campaigns spike and fade"
"Channels work once, then stall"
"Reporting explains the past but cannot predict the future"
"Revenue shows up, but does not compound"

I have seen these exact patterns in B2B SaaS:

A paid search push delivers a strong month, then CAC climbs as soon as the easiest demand is captured.
A webinar series drives a few big deals, but nothing in the follow-up becomes reusable for Sales.
A content sprint increases traffic, but none of the insights make it into onboarding, objections handling, or product messaging.

Those are not necessarily execution failures. They are signs that the company is operating marketing like a project team instead of a system.

If you want repeatable revenue, you need repeatable inputs: a stable strategy, a shared narrative, a reliable channel mix, consistent enablement, and reporting that turns outcomes into decisions. That is what Joris is getting at when he says it is a "system design problem."

The Head of Marketing as an operating model, not a checklist

Joris mentioned building a guide "not as a checklist" but "as an operating model," and that distinction matters.

A checklist is: ship 3 campaigns, post 5 times a week, launch a webinar, redo the website.

An operating model is: define who decides the market and narrative, how messages are created and reused, how channels scale, how pipeline and retention are enabled, how measurement works, and how the team runs the system week after week.

Below is my expansion of the six responsibility areas Joris outlined, with examples of what "good" looks like in practice.

1) Strategy and direction: choose where repeatability starts

Joris wrote: "You decide which market, which ICP, and which narrative the company commits to. Without this, every win is accidental."

This is the foundation. If the company keeps shifting ICP, positioning, or ideal use case, marketing cannot compound learning. Every quarter becomes a reset.

Practical indicators that strategy is truly owned and stabilized:

One primary ICP with clear exclusion criteria (who you are not targeting).
A narrative that is consistent across homepage, deck, outbound, and demos.
A documented set of priority problems and triggers that Sales can qualify against.

Key insight: repeatability begins when choices stay chosen long enough to learn.

2) Content system: turn learning into shared memory

Joris called this "shared memory" and I like that phrase. Content is not just top-of-funnel. It is how the company stores and distributes what it learns about the buyer.

A real content system includes:

Core messaging assets (positioning, problem framing, proof points, objection responses).
Sales-facing formats (battlecards, call snippets, email templates, one-pagers).
Customer-facing formats (implementation guides, best practices, expansion playbooks).

A simple test: when a salesperson discovers a new objection on calls, does that insight become a reusable asset within two weeks? If not, you are producing content, but you are not building shared memory.

3) Channels and distribution: scale what works, not what is new

Joris's point that channels should distribute "proven messages" instead of inventing new ones every quarter is a direct shot at random acts of marketing.

Distribution becomes repeatable when:

Each channel has a job (awareness, demand capture, nurture, expansion).
The same narrative is adapted, not reinvented.
You have leading indicators (impressions, click quality, demo-to-opportunity rate) that show health before revenue arrives.

Example: if LinkedIn is your core channel, you should know which 2-3 angles consistently produce qualified conversations, and your paid, organic, and sales motions should reinforce those same angles.

4) Revenue enablement: remove friction so revenue does not reset

Joris wrote: "Marketing does not close deals. It removes friction across acquisition, retention, and expansion so revenue does not reset every cycle."

This is where many teams under-scope marketing. They stop at lead generation, even though friction often sits later in the lifecycle:

Acquisition friction: unclear value, mismatched ICP, weak proof.
Conversion friction: inconsistent qualification, messy handoffs, no enablement.
Retention friction: customers do not reach value fast enough.
Expansion friction: no packaged upgrade narrative, no cross-sell story.

In a repeatable system, marketing partners with Sales and CS to make outcomes easier. Think: tighter onboarding messaging, QBR materials that reinforce value, case studies mapped to specific triggers, and pricing-page clarity that pre-answers objections.

5) Operations and reporting: turn outcomes into inputs

Joris emphasized lifecycle definitions and consistent reporting so that "outcomes" become "inputs." That is the core of compounding growth.

Two common reporting traps:

Reporting that is only historical: it explains last month, but it does not guide next week.
Reporting that is not shared: Marketing has one dashboard, Sales has another, and Finance trusts neither.

A repeatable operating model typically includes:

Clear stage definitions (MQL, SQL, opportunity, pipeline, closed-won) that everyone agrees on.
Channel attribution rules that are consistent enough to compare decisions over time.
A weekly revenue meeting that focuses on leading indicators and bottlenecks, not vanity metrics.

If your reporting cannot change behavior, it is not an operating system. It is a post-mortem.

6) Leadership and team: keep the machine running when conditions change

Joris wrote: "Systems only repeat when people operate them consistently. Rituals, roles, and alignment keep the machine running when conditions change."

This is the quiet multiplier. Great strategy with chaotic execution still fails. But the fix is not hustle. It is leadership design:

Defined ownership: who owns ICP, messaging, lifecycle, enablement, and channel performance.
Rituals: weekly pipeline review, monthly narrative review, quarterly channel bets with explicit hypotheses.
Hiring and incentives aligned to repeatability (for example, rewarding pipeline quality and conversion, not just volume).

The uncomfortable truth: accountability without authority breaks repeatability

Joris highlighted the tension many Heads of Marketing feel:

"You can be accountable for repeatability while Product controls the roadmap"
"You can be accountable for consistency while the CEO keeps changing the message"
"You can be accountable for enablement while Sales is measured on a different logic"

This is where system design becomes organizational design.

If the company wants marketing to deliver repeatable revenue, marketing needs real authority over the levers that create repeatability. Not all of them, but the ones that define the system: narrative governance, lifecycle definitions, enablement standards, and the ability to say "no" to constant repositioning.

A useful exercise I take from Joris's post is to map each of the six areas to:

Owner (who decides)
Inputs (what they need)
Outputs (what they deliver)
Interfaces (who they must align with)

If you cannot clearly state those four things, you are relying on luck.

A quick sanity check for your B2B SaaS marketing system

If you want to pressure-test whether your growth can compound, ask:

Can we articulate a stable ICP and narrative in one page, and does Sales agree?
Do our best messages show up everywhere (site, outbound, demos), or only in marketing?
Do we scale channels by reusing proven signals, or by chasing novelty?
Are we removing friction across the full lifecycle, including retention and expansion?
Do we have shared definitions and reporting that drive weekly decisions?
Are roles and rituals designed so the system runs without heroics?

If you find gaps, the answer is not more execution. It is redesigning the role and the interfaces around it.

This blog post expands on a viral LinkedIn post by Joris van Kappen, Helping B2B SaaS founders decide what to scale | Founder @ Accelor Hub. View the original LinkedIn post →