The COO Mindset: Why Revenue Leaders Need to Think in Systems

When I became CRO at Venntro Media Group, I thought my job was to grow revenue. When I became COO, I realised that had always been the wrong framing. The job was never to grow revenue. The job was to build the system that grows revenue — and then make sure every part of the business is aligned behind it.

That distinction sounds subtle. It's not. It's the difference between pushing harder and building something that pulls.

Most revenue leaders I talk to are stuck in the pushing phase. They're optimising campaigns, coaching reps, chasing deals, negotiating renewals. They're deep in the work, and they're good at it. But they're operating inside the system rather than designing it. And there's a ceiling to how far that takes you.

The system is the strategy

At Venntro, I was responsible for delivering revenue, margin, and adjusted EBITDA. That's not a sales target — that's a business outcome. Hitting it required me to think about the company as a machine with interconnected parts: acquisition, activation, monetisation, retention, cost management, and partner operations. Pull one lever and it affects three others.

When revenue was down, the answer was rarely "do more outbound." It was usually something structural — a pricing issue creating churn downstream, a product change that disrupted a key partner segment, a cost line that had crept up and was compressing margins. You can't see those things if you're only looking at the pipeline.

This is what I mean by systems thinking. It's not a buzzword. It's a discipline. It means stepping back far enough to see how the pieces connect, and then designing processes, incentives, and feedback loops that make the whole thing work together.

Revenue is an output, not an input

One of the biggest mindset shifts I went through was understanding that revenue is an output. You can't directly control it. You can control the inputs that produce it — the volume and quality of leads, the conversion rate at each stage, the pricing and packaging, the retention mechanics, the partner economics, the cost of acquisition.

When you frame it this way, your job changes. You stop asking "how do we sell more?" and start asking "which input, if we improve it by 10%, has the biggest impact on the output?" That's a fundamentally different conversation, and it leads to fundamentally different decisions.

At the CRO level, I was mostly focused on the top and middle of the funnel — acquisition, activation, conversion. At the COO level, I was responsible for the full picture, including the cost side. And that's where it gets really interesting, because you quickly learn that a pound saved on cost often has a bigger impact on EBITDA than a pound earned on revenue. Not always, but often enough that ignoring the cost structure is a serious mistake.

What this looks like in practice

Let me give you a concrete example. At Venntro, we had a large B2B affiliate and partner network — over 1,500 relationships generating the majority of our revenue. Managing those relationships well required systems: tiered engagement models, automated reporting, clear SLAs, structured QBRs for top-tier partners, and self-serve tools for the long tail.

If you approached that as a pure sales problem — "let's hire more account managers" — you'd burn cash and still miss things. But if you approached it as a systems problem — "how do we design processes that ensure every partner gets the right level of attention at the right time without linear headcount growth" — you could scale the operation sustainably.

That's what we did. And it's the same principle I now apply to B2B GTM automation at Lucennio. The question is never "how do we do more of what we're already doing?" The question is "how do we redesign the system so the output increases without the input scaling linearly?"

The COO lens

The COO role forced me to hold two things in my head simultaneously: the commercial ambition and the operational reality. You want to grow 30%? Fine — show me where the capacity comes from. Show me the unit economics. Show me what breaks at that scale and how we prevent it.

That tension is productive. It stops you from making promises the business can't keep and stops you from being so conservative that you miss the opportunity. Good revenue leaders live in that tension. They don't just set targets — they architect the path to hitting them, including the operational infrastructure, the team structure, the technology stack, and the reporting cadence that keeps everything on track.

I think every CRO should think like a COO, even if they never hold the title. Because the moment you start seeing revenue as a system rather than a number, you make better decisions. You invest in the right things. You catch problems earlier. And you build something that compounds over time instead of resetting to zero every quarter.

Why this matters now

The tools available to revenue leaders in 2026 are extraordinary. AI can automate research, outreach, reporting, and analysis. Workflow platforms can connect every system in your stack. Data is more accessible than it's ever been.

But tools without systems thinking are just expensive noise. I've seen companies spend six figures on automation platforms and get nothing from them because nobody designed the process first. The technology worked perfectly — it just automated a broken workflow.

The COO mindset starts with the process. What are we trying to achieve? What are the steps? Where are the bottlenecks? What can be automated? What requires human judgement? How do we measure whether it's working? Only then do you choose the tools.

That's the order of operations. Strategy, system, process, tool. Not the other way around.

---

David Adams is the Founding Partner of Lucennio Consultancy. He previously served as COO and CRO at Venntro Media Group, where he was responsible for revenue, margin, and EBITDA delivery across a global dating SaaS platform.