You’ve seen marketing evolve through every major digital shift. What’s one marketing rule you’ve stopped believing, and what’s one that’s only become more important?
I have stopped believing that “more” is better.
AI has made average content abundant — more content, more channels, more campaigns, more touches. However, abundance is not the same as attention, and activity is not the same as impact. When anyone can produce credible-looking material at scale, the volume of output stops being a meaningful advantage.
What has become more important is distinctiveness backed by proprietary learning. The model may be the same, but the advantage comes from what you teach it, where you apply it, and what your organization learns each time you use it.
This accumulated knowledge is not a by-product of marketing. It is a business asset and should be documented, governed, protected, and improved deliberately.
Every enterprise wants to move faster, but speed often creates new complexity. How does R Systems help customers accelerate engineering without sacrificing quality, governance, or long-term scalability?
Speed is useful only if the whole system can absorb it.
If one engineering activity becomes faster while approvals, testing, data, or deployment remain unchanged, the bottleneck just moves somewhere else.
At R Systems, we start with two questions: What must improve, and what cannot be compromised?
We identify the business outcome, whether that is cycle time, quality, customer effort, cost, or resilience, and then examine the complete workflow around it. This includes data dependencies, decision points, controls, hand-offs, and exceptions.
Governance is then built into the flow of work. We define where AI or automation can act independently, where human judgment must remain, what happens when the system is uncertain, and how performance will be measured over time.
This requires discipline at the beginning, but creates an engineering system that can sustain speed without accumulating hidden operational, quality, or governance debt.
What’s one transformation mistake you see repeated across industries, regardless of company size? How do you help customers avoid that trap?
Buying a tool and calling it transformation.
I regularly see companies license a platform, run a pilot, and announce an AI initiative without changing the process around it. The result is often a faster version of the old workflow, not a better way of working.
Useful automation still has value, but transformation requires more than adding technology to an existing sequence of tasks. It could require redesigning the workflow, changing decision rights, improving the data foundation, and reconsidering where human judgment creates the most value.
At R Systems, our first question is not, “Which technology should we use?” It is, “Which business outcome should move?”
For our customers, the outcome might be revenue, cost, cycle time, quality, customer effort, resilience, or risk. Once the outcome is clear, we work backwards to determine what to eliminate, automate, augment, or redesign.
If we cannot define what should change and how we will recognize success, the technology decision is premature.
Enterprise buyers have changed. They’re more informed, more skeptical, and far less patient with generic messaging. What’s one thing that simply doesn’t work anymore?
Generic messaging can create awareness, but in a complex enterprise sale, it rarely creates preference.
Buyers don’t need another vendor telling them that AI improves efficiency or that digital transformation is important. They want to know whether you understand their business, their technology environment, and the specific change they are trying to make. And increasingly, AI is changing the economics of this.
In our own GTM operation, an account-research cycle that previously took 54 hours now takes 21. AI handles 61% of the underlying research workflow, and we completed 200 research cycles over six months. After that level of repeated use, this is no longer a promising pilot, but a new way of working.
The value is giving people more time to interpret what matters: account priorities, relevant buying context, and a point of view the buyer hasn’t already heard elsewhere.
AI should not remove human judgment from enterprise marketing. It should create more room for it.
The CMO’s job today stretches well beyond marketing. Which conversations do you find yourself spending far more time in than you would have five years ago?
I spend much more time in three conversations: where we should compete, where we should invest, and what capabilities the company needs to build next.
My conversations with our CFO are no longer only about defending a marketing budget. They are about the strength of the investment thesis and what we believe, how quickly we can test it, what evidence would justify investing further, and what would tell us it is time to stop.
Our internal account-intelligence program is one example. It automated 61% of the research workflow, reduced a typical cycle from 54 hours to 21, and achieved an estimated payback period of approximately three months. That changed the quality of the conversation. We were no longer discussing a collection of marketing activities, but a measurable business capability.
I am also involved much earlier in market and portfolio decisions. Marketing sees changes in customer priorities, competitor behavior, and category dynamics, often before those shifts become visible in financial reporting.
My perspective is most valuable before the strategy is fixed, not after capital has already been committed and marketing is asked to communicate the decision.
As AI becomes everyone’s baseline, what do you think customers will value most from tech partners over the next few years? How is R Systems evolving to stay ahead of that shift?
Almost every technology company can now describe an AI capability, but customers increasingly want answers to more difficult questions: Where have you used it? What changed? What failed? What did you have to govern? And did the economics hold beyond the pilot?
Where a use case is relevant to our own operations, we make R Systems the first customer — our “Customer Zero” approach.
Internal deployment exposes the questions that an external pilot can avoid. Will people actually use the system? Will the controls hold when exceptions occur? Can it integrate with existing workflows? And does it continue to create value when it moves from a pilot into regular operations?
Across our internal Customer Zero portfolio, live workflows in GTM, presales, finance operations, and talent acquisition have produced effort reductions ranging from 40% to 80%. However, internal success doesn’t automatically establish readiness for every client, industry, security architecture, or regulatory environment.
Customers will increasingly trust partners that are willing to disclose not only the outcome, but also the controls, trade-offs, limitations, and lessons behind it. At R Systems, our strongest AI claim is not “we can build it.” It is “we have run it, measured it, and learned where it breaks.”
Ten years from now, when someone looks back at this phase of R Systems’ journey, what’s the one thing you hope they’ll say the company got absolutely right, long before everyone else caught on?
I hope they say R Systems understood early that the durable advantage in AI was never the model alone.
Today’s leading technology will eventually become standard. What will last is an organization’s ability to combine engineering discipline, domain understanding, proprietary learning, and human judgment into systems that produce repeatable business value.
This requires an organization that can learn quickly, test honestly, govern responsibly, and distinguish between a persuasive demonstration and a sustainable operating model.
I would like this period to be remembered as the moment we made evidence a habit: when every important claim was expected to connect to a working system, a measurable result, and a lesson that could be applied for a customer.
