AMA: Cisco Senior Director, Global SMB & Mid-Market Sales Acceleration and Program Office, Ignacio Castroverde on Revenue / Revenue Ops Alignment

One principle first: there can only be one number. Sales, RevOps, and Finance can each come in with their own inputs, but everyone needs to be looking at the same revenue picture. For SMB and Mid-Market, I'd align on four things: segments that are actually defined, one source of truth for pipeline and forecast, agreed conversion assumptions, and a weekly cadence to catch where we're losing ground. RevOps shouldn't be the team policing Sales. It should help Sales understand what's real, what's at ...Read More

The relationship usually breaks down when RevOps becomes the reporting police, or when we ask Sales to change the way they work without bringing them along for the journey. Even when the change is the right one, it creates friction if sellers feel it's being done to them rather than with them. I've also seen the opposite happen. Sometimes RevOps identifies a real issue and pushes for change, but Sales resists because it disrupts established habits. That tension is natural, but if it's not manage ...Read More

Most companies think revenue acceleration means more pipeline, faster. That's part of it. But it's a pretty narrow way to look at it. To me, it's about removing friction across the entire revenue engine so the business can grow faster and more efficiently. Not just generating demand. Helping the right opportunities move through the system with less effort and a better chance of actually closing. That means better targeting, better qualification, cleaner pipeline, faster approvals, stronger partn ...Read More

For me, the distinction is pretty simple. Sales Operations owns the business of today. The Program Office owns building the business of tomorrow. Sales Ops should be focused on running the engine: forecasting, reporting, territory management, compensation, quota, process compliance, data quality, and the day-to-day mechanics that keep the business operating. The Program Office should be focused on change. New motions, new capabilities, new programs, new tools, cross-functional initiatives, trans ...Read More

This is probably my favorite question because sellers are often right: they do know their territory, customers, and partners better than any dashboard ever will. The mistake is positioning RevOps data as a replacement for field judgment. It isn't. The goal should be to complement and sharpen that judgment, not override it. My approach is to bring sellers into the conversation early, show them the logic behind the data, and encourage them to challenge it. If the data is wrong, we fix it. If the s ...Read More

Pipeline size. And I know that sounds a little controversial, because of course you need enough pipeline. The issue is that too many SMB sales leaders look at pipeline coverage and stop there. The better question is: how healthy is that pipeline? A large pipeline can create a false sense of confidence if it's full of aging opportunities, weak qualification, poor stage discipline, or deals that have little chance of closing. Volume alone doesn't tell you much. I'd much rather have a smaller pipel ...Read More

Trying to do too much, too fast, without a clear business outcome. The fastest way to kill a RevOps initiative is to turn it into a massive transformation program with too many stakeholders, too many metrics, and no clear "so what?". People lose interest, sellers see it as extra admin, and leadership struggles to connect the effort to results. I've seen plenty of initiatives start with great intentions and die under their own weight because they tried to solve everything at once. My approach is ...Read More

I look for someone who understands the field, not just the dashboard. The best RevOps leaders are data-driven, but they're also commercially minded. They understand what sellers are trying to achieve, where the friction points are, and how to make execution easier, not just cleaner on paper. They know how to challenge Sales when needed, but they do it as a partner, not an auditor. They bring facts and structure, but they also listen and adapt when the field has context the data doesn't. What sep ...Read More