From Order Taker to Growth Architect: The RevOps Shift with Dave Watson

The Silent Failures Hiding Inside Your RevOps Stack With Dave Watson

Introduction

Dave Watson has spent 30 years across B2B technology, gaming, and entertainment, and now works as a Fractional CMO across Europe and North America, currently based in Munich and working with Euphonic on go-to-market growth. On this episode of Ops in Motion, he joined Kawal and Shiv to talk through how RevOps has shifted from a support function into a strategic one, why storytelling matters as much as dashboards in operations, and what it actually takes to keep CRM data trustworthy over time.

Who should read this: RevOps and marketing operations leaders trying to explain operational complexity to stakeholders, or struggling to keep CRM data reliable as their tech stack grows.

Key takeaways

• RevOps has moved from a support function managing a handful of systems to a strategic one navigating 50, 80, or even 100 interconnected platforms. That shift changes what the role is actually responsible for.
• Dashboards alone don’t help stakeholders understand operational complexity. Storytelling does, especially when it surfaces the “silent failures,” the friction and lost opportunities nobody’s tracking.
• Tech stack optimization works in a specific order: audit first, then integration and data hygiene, then adoption. Skipping straight to adoption or buying more tools doesn’t fix an unaudited stack.
• CRM data quality depends on clear governance, defined ownership, and regular audits, because data quality naturally degrades over time even after a thorough cleanup.

RevOps has moved from order-taker to architect, and most teams haven’t caught up to that shift

Dave’s read on the last seven or eight years is a straightforward complexity story. Where companies once ran on a handful of systems, RevOps functioning largely as the team that kept things running and pulled reports on request, most organizations now manage 50 to 100 interconnected platforms across revenue, marketing, sales, finance, and IT. That complexity is what pushed RevOps from the sidelines into the center of the business.

The opportunity in that shift is real, but it requires a different mindset than the role used to demand: moving from order-taker or firefighter into architect and strategist. Shiv’s experience auditing B2B organizations backs this up directly. Companies that invest heavily in technology and automation frequently still fail to get the results they expect, and the audit almost always turns up the same pattern: disconnected processes, conflicting automations, fragmented data, and poor alignment across teams. Revenue growth only happens when people, process, technology, and data are actually working together, which is exactly why the RevOps function has to operate as both architect and strategist rather than a systems caretaker.

The real value in RevOps is often hidden a few layers beneath the dashboard

Dave’s framing for why storytelling matters in an analytical function like RevOps is a nesting doll. On the surface, a RevOps professional is responsible for systems, dashboards, and reporting. Peel back one layer and you find people, whether teams are actually aligned around shared goals and processes. Peel back another and you find systems, whether platforms are actually communicating with each other. Another layer down is data: are silos eliminated, is it consistent, can anyone actually trust what a report is telling them.

At the very center of all of it are what Dave calls silent failures, the friction, inefficiencies, and lost opportunities that never show up on a dashboard because nobody’s specifically looking for them. Storytelling is what makes those layers visible to stakeholders who don’t live inside the spreadsheets every day. Instead of handing someone a dashboard and expecting them to infer the underlying problem, a narrative gives that same information context, connecting an operational fix directly to the business outcome it’s actually driving.

“Storytelling helps teams understand these interconnected layers. Rather than overwhelming people with spreadsheets and dashboards, a narrative creates context and helps stakeholders see how operational improvements contribute to business growth.”

— Dave Watson

Tech stack optimization follows a specific order, and most teams skip straight to the wrong step

Shiv’s approach to tech stack optimization starts with something teams consistently underinvest in: regular audits. Before adding anything new, identify redundancies, cut unnecessary complexity, and confirm every platform in the stack is tied to a clear business outcome. The benefits of a marketing tech stack audit usually show up exactly here, in what a company discovers is duplicated or unused once someone actually looks.

Integration and data hygiene come next. If systems aren’t connected and the data moving between them isn’t reliable, every decision built on top of that data inherits the same unreliability. Adoption is the final piece, and it’s the one that gets skipped most often: even the most powerful platform creates zero value if people aren’t actually using it consistently. Every component of the stack should tie back to something measurable, pipeline growth, conversion rate, revenue impact, rather than existing simply because it seemed useful at the time it was purchased.

Good CRM data requires ownership, not just a cleanup project

Dave was direct about what makes CRM data trustworthy over time: it has to be complete, consistent, and actionable, and getting there requires more than a one-time cleanup. Clear data governance policies come first, followed by defined ownership. The gap he sees most often isn’t a lack of effort, it’s the absence of anyone actually accountable for data quality. Without a named owner, maintaining any standard becomes close to impossible.

Automated validation and regular audits are the third piece, and they matter because data quality degrades continuously, not just occasionally. Even a genuinely thorough cleanup effort loses its value over time without ongoing maintenance behind it. Dave’s underlying point ties back to mindset: treat data as a strategic business asset, not a byproduct of daily activity. When CRM data quality is approached that way, it becomes a foundation teams can actually build growth on, instead of a recurring source of friction every time someone tries to run a report.

Action items

FAQs

Talk to Digital DI Consultants

If your tech stack hasn’t been audited in a while, or your CRM data quality keeps slipping without a clear owner, see how we approach a martech stack audit and CRM database management, or talk to our team about your setup.