The Revenue Operating System Playbook

At SaaS Kitchen, Manuel Hartmann, Founder and CEO of SalesPlaybook, presented five customer cases built around one promise: more revenue output without automatically adding more people.

The numbers are attention-grabbing. But the useful lesson is not that every team should cut headcount and buy more software. Across the cases, the results came from redesigning how demand, data, decisions and sales execution work together.

Five cases, one recurring pattern

Results shown above are reported in SalesPlaybook’s keynote and customer stories. They describe individual projects, not guaranteed outcomes.

The common mistake: starting with the stack

Clay can enrich accounts. HubSpot can route leads. AI can summarise research and suggest next actions. None of them can decide which market deserves attention, why a buyer should care or whether a sales team trusts the process enough to use it.

The order matters. When teams start with tools, they often automate a process that was never clearly defined. The result is faster activity, not necessarily better revenue.

A five-layer Revenue Operating System

1. Market narrative: create a reason to care

Calibo’s LinkedIn motion started with positioning and executive content, not an automation. The leadership team became a distribution channel because there was a clear point of view worth distributing.

Operating question: Can a target buyer understand the problem, our position and the cost of doing nothing within two minutes?

2. Demand signals: create a reason to act now

Engagement, hiring, technology changes, funding and account behaviour are useful only when they change prioritisation. A signal that never affects the next action is just another field in the CRM.

Operating question: Which three signals genuinely increase the probability of a relevant conversation?

3. Data and routing: make the next owner obvious

The node.energy case replaced manual research, incomplete records and delayed lead assignment with automated enrichment, scoring and routing. The value was not more data. It was less time between signal and action.

Operating question: When a qualified signal appears, does the right person know within minutes what to do next?

4. Sales rhythm: turn information into decisions

sipgate’s result was supported by leadership across the funnel: identifying the right leads, working them better and improving every step. Dashboards do not create that rhythm. Pipeline reviews, deal coaching and clear escalation paths do.

Operating question: Which decisions are made weekly, by whom, and using which evidence?

5. Adoption: make the system survive its builder

A workflow is not operational because it ran once. It becomes part of the operating system when the team understands it, uses it and can maintain it without depending on the consultant or RevOps builder.

Operating question: Could the team run and improve this process next quarter without the person who built it?

“Every step is getting better, and it doesn’t stop.”

SUSE HAGEDORN · CRO, SIPGATE · SOURCE: SALESPLAYBOOK

Dominic’s take: zero headcount is not the objective

“More output with zero additional headcount” is a powerful commercial headline. But it becomes dangerous when leaders turn it into a universal management principle.

The target should not be the smallest possible team. The target should be the least wasteful system that still produces quality, learning and customer trust.

This distinction matters because the economics of AI are changing. Usage-based pricing, credit models and growing stacks mean that reduced payroll does not automatically translate into lower total cost. A smaller team can still become an expensive operation if it depends on too many tools, fragile workflows and constant maintenance.

A workflow is efficient only if the full system becomes cheaper, faster or more effective. Saving 20 hours of manual research has little value if the team spends those hours fixing data, reviewing weak AI output or managing another disconnected tool.

What to automate, and what to keep human

The 30-day implementation playbook

Score your current revenue system

Give each statement zero, one or two points: zero means untrue, one means partly true, two means consistently true.

The final question

The most useful question in Manuel’s keynote was not which tool to buy. It was where the revenue system currently loses growth.

That loss may sit in demand creation, account selection, routing, CRM design, pipeline leadership or team adoption. Find the constraint first. Then decide whether the answer is better positioning, a clearer process, stronger leadership, automation or additional people.

Do not scale the org chart before you understand the system. But do not mistake a smaller org chart for a better system either.