Revenue teams spend an enormous amount of time thinking about pipeline.

How do we generate more leads? How do we create more opportunities? How do we improve conversion rates? How do we help sales close more business?

Those are important questions. But they can distract organizations from another source of growth hiding much further down the revenue lifecycle: protecting the revenue they have already earned.

In a recent episode of Pipeline to Profit, Revenue Ops founder and CEO Heather Davis Lam sat down with Jason Rieckewald-Schmidt of Salesforce to discuss revenue leakage, the evolution from Salesforce CPQ to Agentforce Revenue Management (formerly known as Revenue Cloud), and what companies need to do today to build a revenue engine capable of scaling tomorrow.

The conversation highlighted an uncomfortable reality for many organizations. Closing the deal doesn’t necessarily mean the company successfully captures all the value associated with it.

Between the quote and the cash hitting the business, there can be dozens of processes, systems, and human handoffs. Every one of them creates another opportunity for friction, delays, additional costs, and ultimately lost revenue.

Revenue Leakage Doesn’t Start and End With Sales

Revenue leakage can be easy to overlook because most organizations don’t have a line item on a dashboard labeled “lost revenue.”

Instead, it shows up across the business.

A contract has to be rebuilt manually. Someone re-enters order information into an ERP. Billing doesn’t match the original quote. Finance manually reconciles bookings. A renewal depends on a salesperson remembering to initiate it. An amendment requires multiple teams to intervene.

Individually, these may look like operational inconveniences.

Collectively, they can become a significant financial problem.

During the episode, Rieckewald-Schmidt discussed estimates that roughly 5% to 15% of revenue can be lost in post-quote processes, particularly when disconnected systems and manual intervention become part of routine transactions.

The problem isn’t necessarily the people performing that work. In many cases, employees are compensating for systems that were never designed to work together.

That’s an important distinction.

The goal of automation shouldn’t simply be eliminating human involvement. It should be eliminating unnecessary human effort caused by disconnected technology and poorly designed processes.

The Hidden Cost of Manual Handoffs

One of the clearest warning signs of revenue leakage is the number of times people have to intervene in a transaction.

Imagine a salesperson closes an opportunity.

From there, someone reviews the quote. Someone else validates the contract. Another employee transfers information into an ERP. Finance reconciles the transaction. Billing checks the terms. Someone notices an error and sends it back. The record gets updated in Salesforce. Then another person verifies the correction.

No individual step sounds catastrophic.

But repeat that process hundreds or thousands of times and the economics change quickly.

Manual intervention increases the cost to serve while also introducing opportunities for errors, inconsistent data, delayed billing, unnecessary discounting, and margin erosion. The episode describes these issues as compounding across the revenue lifecycle rather than existing as isolated operational problems.

That also changes the way executives should think about growth.

If a company believes it needs 15% more sales to reach its financial targets, the natural reaction may be to hire more salespeople, generate more pipeline, or increase deal sizes.

But what happens if the organization is already losing a meaningful percentage of the revenue moving through its existing systems?

Improving revenue capture may sometimes provide a faster path to profitable growth than simply placing additional pressure on the top of the funnel.

Stop Thinking About Quote-to-Cash as a Collection of Systems

Many organizations don’t intentionally design inefficient revenue processes.

They inherit them.

A new product gets introduced, so a workaround gets created. The company adds subscription offerings, but its ERP was originally designed around physical products. A new billing platform gets implemented. Finance creates a spreadsheet to reconcile something the CRM can’t handle. Deal desk adds another approval process.

Years later, the company technically has a quote-to-cash process, but it isn’t really one connected system.

It’s a collection of applications, spreadsheets, integrations, institutional knowledge, and human intervention.

That becomes especially dangerous when critical processes depend on one employee knowing how everything works.

As Rieckewald-Schmidt explained during the episode, organizations frequently have established quoting and billing platforms while the processes surrounding approvals, contracts, amendments, renewals, and other handoffs remain disconnected.

That architecture may work at today’s transaction volume.

The better question is:

What happens if sales doubles?

If doubling revenue also requires doubling deal desk, finance, operations, or administrative headcount, the business doesn’t have a scalable revenue engine.

It has a scalable sales target attached to an unscalable operating model.

Salesforce CPQ vs. Agentforce Revenue Management (formerly known as Revenue Cloud): Think Beyond Replacement

This becomes particularly relevant for organizations currently using Salesforce CPQ.

Companies have often invested significant time, money, and internal resources into getting CPQ implementations working properly. Moving to a new platform can understandably create hesitation.

But treating the transition to Agentforce Revenue Management simply as a CPQ replacement misses the larger opportunity discussed in the episode.

The shift creates an opportunity to reconsider how products, pricing, quoting, contracts, orders, commerce, automation, and customer buying experiences fit together.

Rieckewald-Schmidt specifically highlighted Agentforce Revenue Management’s API-driven approach and the broader move toward headless architecture as important differences when thinking about the next generation of revenue technology.

Instead of asking:

“How do we rebuild our existing CPQ implementation?”

Organizations should be asking:

“How should our revenue engine operate over the next three to five years?”

Those are very different projects.

The first preserves existing processes on new technology.

The second examines whether those processes should exist at all.

Build the Revenue Engine Before You Need to Scale It

AI makes this conversation even more important.

There’s enormous excitement around AI-generated quotes, automated selling experiences, intelligent approvals, and autonomous revenue processes.

But AI can’t magically fix a fragmented operating model.

If pricing is inconsistent, product relationships aren’t defined, contract information lives across disconnected systems, and routine transactions depend on institutional knowledge, adding AI won’t suddenly create a scalable revenue engine.

The underlying infrastructure still matters.

The episode emphasizes scale as one of AI’s biggest opportunities. Organizations trying to grow 3x, 6x, or even 10x cannot assume headcount will grow at the same rate. They need infrastructure that allows significantly more transactions to move through the business without requiring equivalent increases in manual effort.

That means today’s Agentforce Revenue Management decisions aren’t only about improving today’s quoting experience.

They’re about creating the foundation for tomorrow’s automation.

Revenue Transformation Has to Become an Executive Initiative

One of the most important points from the conversation was that successful Agentforce Revenue Management projects can’t live entirely inside Revenue Operations.

When revenue transformation is treated as an operational technology project, the conversation tends to revolve around tactical improvements:

Make quoting faster.

Reduce deal desk frustration.

Fix pricing rules.

Improve approvals.

Those outcomes matter, but they’re rarely enough to drive major organizational change.

Successful initiatives connect revenue technology to executive priorities such as margin, EBITDA, growth, cost to serve, customer experience, and scalability.

Rieckewald-Schmidt noted that the more successful projects he has seen are treated as corporate initiatives to build the company’s next-generation revenue engine. When the project is tied to larger revenue or margin goals, it receives the executive attention and resources necessary to address the full lifecycle instead of solving one department’s immediate problems.

The CRO sees an opportunity to scale without proportional headcount.

The CFO sees margin and operational leverage.

The CTO sees an opportunity to simplify the technology stack.

RevOps sees better processes and governance.

Sales sees less friction.

And customers experience an easier buying process.

That’s when quote-to-cash stops being a back-office technology project and becomes a business transformation initiative.

A Metric Worth Tracking: Human Touches per Revenue Transaction

So where should companies begin?

One of the most practical recommendations from the episode is surprisingly simple:

Measure human touches per revenue transaction.

Start when a quote becomes a closed-won opportunity and follow that transaction through the rest of the revenue lifecycle.

Every time someone has to manually transform data, validate information, reconcile records, re-enter information, correct something, or move the transaction to another system, count it.

Rieckewald-Schmidt suggests that organizations approaching double-digit human interactions per revenue transaction should see that as a significant warning sign.

You don’t necessarily need sophisticated software to perform the first audit.

Take a representative transaction and trace it.

Where does the information go?

Who touches it?

What does that person do?

Why is their involvement necessary?

Could the system handle that step automatically?

Could employees manage exceptions instead of manually processing every transaction?

The answers can quickly reveal where the revenue lifecycle has accumulated unnecessary complexity.

And importantly, the goal doesn’t have to be replacing every system at once. The audit creates visibility. From there, leadership can prioritize the processes creating the greatest financial or operational impact.

The Future of RevOps Is More Strategic

As revenue technology becomes more intelligent, the role of Revenue Operations will change with it.

Instead of spending as much time troubleshooting individual quotes, resolving pricing-rule errors, or managing routine exceptions, RevOps teams can increasingly focus on designing the policies and guardrails that govern automated revenue processes.

That means answering questions such as:

How should discounts affect margin and compensation?

Which transactions can be automatically approved?

When should humans intervene?

How should products be packaged?

What buying experiences should be self-service?

How should AI agents operate within established pricing and approval policies?

The episode predicts a RevOps function that becomes less transactional and more strategic, using increasingly granular revenue data to establish policies while automation handles more of the repetitive work.

That’s an important evolution.

The value of RevOps won’t come from being the team that knows how to work around every limitation in the revenue engine.

It will come from designing a revenue engine that doesn’t require those workarounds in the first place.

Protect the Revenue You’ve Already Earned

Companies will always need pipeline.

They’ll always need talented sellers, effective marketing, strong products, and new customers.

But profitable growth isn’t only about putting more opportunities into the top of the funnel.

It’s also about making sure the revenue you’ve worked so hard to create actually makes it through the business efficiently.

As Heather summarized at the end of the episode, sometimes the fastest path to growth isn’t simply generating more pipeline. It’s protecting the revenue already moving through the organization and building systems capable of capturing every dollar the company has earned.

For companies evaluating Salesforce CPQ, Agentforce Revenue Management, commerce, billing, or the broader quote-to-cash lifecycle, that’s a useful place to start.

Don’t just ask whether your quoting system works.

Ask how many people have to touch a transaction after the quote.

Ask what would break if transaction volume doubled.

Ask how much manual work exists because your systems can’t communicate.

And most importantly, ask whether the revenue engine you’re operating today is capable of supporting the company you want to become tomorrow.

Because the next generation of revenue operations won’t just be measured by how much pipeline a company creates.

It will be measured by how efficiently it turns that pipeline into profit.