Operations sits in the seat between revenue, marketing, and sales, which means it sits in the path of every team’s requests. On the Let’s Talk Marketing podcast, revenue operations leader Mira Wise told Sophie Steffen how she decides which of those requests gets built, which gets postponed, and how to deliver that verdict without becoming either a pushover or an obstacle.
The Request That Arrives Pre-Solved
There is the familiar friction between sales and marketing, the eternal squabble over who deserves credit for a given win. Wise acknowledges it exists. But the friction specific to operations is quieter and more interesting. It is the request that turns up already wearing its own answer.
“They sometimes come with a solution instead of a problem. They have an idea of how it should work, and then revenue operations has to kind of be the bearer of bad news.”
A colleague wants a particular data point tracked, or a particular automation built, and they have already decided in their head how the whole thing should function. They are not bringing a problem to operations. They are bringing a specification, and the specification is frequently more complicated to deliver than the person realizes. Operations then has the unenviable job of explaining that the elegant idea in someone’s head is, in technical reality, a four-week build.
The mistake would be to treat this as a simple yes-or-no transaction. Wise does neither. She treats the pre-solved request as a prompt to find the actual problem hiding underneath it, then lays out the genuine options with their costs visible. The conversation shifts from “can you build my idea” to “here is what each path actually involves, and here is the one that probably serves you best.”
Revenue Is the Tie-Breaker
Pushing back is only credible if it rests on something firmer than instinct, and Wise’s something is revenue. The first question applied to a request is how much revenue it stands to generate. An experimental campaign with no revenue estimate attached does not get four weeks of build time, because nobody can justify the investment against an unknown return.
“We’re not gonna spend four weeks building something for an experimental campaign that we don’t know how much revenue is actually going to bring us versus something where we could put a revenue dollar on that dollar amount.”
The second filter is strategic alignment. Some projects are visibly priorities at the very top of the organization, the goals C-level cares about and multiple teams are already driving toward. Wise’s concrete example is a current company-wide push to move customers from monthly plans onto yearly plans. A campaign that feeds that goal has its priority effectively pre-approved, because the business has already decided the outcome is worth paying for. A request that serves no current primary KPI has to clear a much higher bar, and often should not be a focus at all.
Between them, those two filters (projected revenue and alignment with declared company goals) turn what could be an endless negotiation into something closer to a decision rule. Requests stop being judged on how persuasively they are argued and start being judged on what they are actually worth.
The Scaled-Down Version as a Negotiating Tool
The most useful idea in this part of the conversation is the escape hatch Wise uses when a request is promising but unproven. Rather than rejecting it outright or committing the full four weeks on faith, she offers a scaled-down version. Build the smaller experiment, see whether it produces business impact, and let the result settle the argument.
If the small version works, the follow-up conversation with leadership becomes almost trivial to have. You are no longer asking for budget on the strength of a hypothesis. You are pointing at evidence and saying the experiment drove impact, so the full investment is now justified. The scaled-down build converts a speculative pitch into a proven one, which is a far stronger position to negotiate from.
It also quietly protects the relationship. The stakeholder does not hear a flat no. They hear a smaller yes with a clear path to a bigger one, contingent on results they can influence. Operations gets to protect its build capacity without becoming the department that says no to everything, and the decision ends up made by data rather than by whoever lobbied hardest. For a function that has to keep working with every team it pushes back on, that is not a minor benefit.
For the full interview breakdown, see our complete Expert Insight with Mira Wise.
Related Content
Marketing Operations Behind the Scenes: Expert Insights with Mira Wise
Mira Wise, a revenue operations leader in B2B SaaS, breaks down the systems, breakages, and team politics that decide whether a marketing department can actually trust the numbers on its own dashboards.
Why Perfect Attribution Tracking Is Ending
Privacy rules and AI-driven discovery are quietly retiring the dream of tracking every digital touchpoint. Mira Wise explains why B2B marketing must learn to measure uplift and trends instead.
When Cross-Domain Tracking Silently Breaks
An alarming spike in direct traffic looked like a privacy story. Mira Wise explains how it turned out to be broken cross-domain tracking, and how splitting the number into thirds rescued leadership trust.
