Revenue operations is often described as a systems discipline. Aparna Muralidharan's career makes a stronger case: the best operators do not merely analyze data or configure tools. They turn complexity into a story that helps another person make a better decision.
That ability was not the result of a perfectly planned RevOps career. Aparna moved through healthcare interests, finance during the 2008 crisis, publishing analytics, graduate study, and seller-support roles before reaching revenue operations leadership. Each stop added a different part of the operating toolkit: quantitative rigor, comfort with change, commercial empathy, and the ability to explain what the numbers mean.
Data becomes valuable when someone can act on it
Aparna describes the analytical work that first captured her attention in unusually human terms:
I really liked taking large amounts of data and distilling them into short stories.
The phrase matters. A dashboard can report what happened, but a RevOps leader still has to decide which movement deserves attention, what probably caused it, and what the business should do next. That is the difference between producing analysis and creating operating clarity.
Her training in research methodology and quantitative methods made the underlying work more rigorous. But the objective was never technical sophistication for its own sake. She invested in those skills while working because better analysis made her more useful in the roles she already held.
For RevOps teams, the lesson is practical: do not stop at accurate reporting. State the decision the analysis supports, the assumptions behind it, and the action that should follow.
Nonlinear careers can create stronger operators
Aparna originally considered dentistry. She later worked at Merrill Lynch during the financial crisis, where she experienced six managers in a short period. She moved into publishing and analytics, continued her education while working, and eventually found her way into technology and revenue operations.
None of those steps looks like a standard RevOps ladder. Together, however, they created the breadth the role demands.
Revenue operations sits between functions. The job requires enough analytical depth to interrogate data, enough commercial awareness to understand the field, and enough organizational judgment to see how a change in one team will affect another. A narrow career can build expertise. A varied one can build translation skills.
Aparna's experience also shows why career pivots should not be treated as lost time. Earlier roles become useful when an operator can recognize the capability each one developed.
Fast pivots require a close relationship with sellers
At Medidata, Aparna supported sellers through changes in pricing, enablement, and compensation. When something was not working, the organization sometimes had to adjust quickly.
Her response was to stay close to the people expected to execute the change. She developed direct relationships with sellers, listened to what was happening in the field, and tried to evaluate new rules from their point of view.
That relationship is essential. RevOps can create a technically sound process that fails because it adds friction, arrives without context, or ignores how salespeople actually work. Conversely, field feedback cannot become an automatic veto over every operating decision.
The operator's job is to distinguish between resistance to change and evidence that the design is flawed. That judgment is much easier when trust existed before the difficult decision arrived.
Fairness is an operating requirement
Compensation and pricing changes make the stakes especially visible. Aparna describes asking a basic question before putting a policy in front of sellers: is this fair?
Fairness does not mean every person receives the outcome they want. It means the rules are explainable, consistently applied, and connected to a legitimate business objective. When that standard is missing, people stop debating the policy and start questioning the system behind it.
This applies beyond compensation. Territory changes, routing rules, forecasts, and account assignments all require the same discipline. A RevOps team should be able to explain what changed, why it changed, what data informed the decision, and how exceptions will be handled.
Clarity is not cosmetic communication after the real work. It is part of the real work.
Leadership changes the unit of impact
Aparna's transition from individual contributor to manager initially brought a simple relief: she finally had help. Over time, the more important shift was realizing that leadership allowed her to increase the impact of other people.
That is now one of the parts of the job she finds most rewarding. Developing a team is not separate from delivering operational results. It is how a function stops depending on one person to solve every difficult problem.
Strong RevOps leaders therefore need two operating systems. One governs data, tools, and processes. The other develops judgment inside the team: how to frame a problem, communicate a recommendation, work with the field, and recognize when a design needs to change.
The practical lesson for RevOps leaders
Aparna's career points to a useful model for modern revenue operations:
- Build enough analytical depth to challenge the first explanation.
- Translate findings into a short, decision-ready story.
- Stay close to sellers before a major change requires their trust.
- Test policies for fairness as well as technical correctness.
- Treat team development as a core operating responsibility.
The best RevOps work makes complexity manageable. It gives leaders a clearer decision, gives sellers a fairer system, and gives the operations team enough shared judgment to keep improving both.
About the guest
Aparna Muralidharan is Senior Director of Revenue Operations at dscout. Her background spans finance, publishing analytics, quantitative research, technology, and revenue operations leadership. She is also a musician and writer whose creative work reflects the same interest in turning complex material into a story people can understand.
