The Synthesizer
Vol 13
This month, we’re diving into a quiet but costly truth across billing systems: modern billing systems don’t fail loudly, they fail slowly and silently. Volume 13 uncovers what months of BRM conversations revealed, and why the same patterns show up across every billing platform.
In This Edition
-
- The real reasons modern billing systems break (and why dashboards won’t warn you)
- What BRM teams told us about complexity and accountability
- How healthy billing environments transform finance, IT, and revenue outcomes
- The cross-platform truth behind billing systems problems
- 2026 outlook: Automation, usage-based billing, and the widening discipline gap
What 7 Weeks of BRM Conversations Taught Us
Our latest Oracle BRM series sparked responses from teams across telecom, SaaS, and media.
And the message was consistent:
“You just described our world.”
Turns out the problems aren’t unique to BRM. They show up in Zuora, Salesforce, BillingPlatform, Stripe, Conga, DealHub, everywhere.
The System Isn’t Broken, The Discipline Is
-
- Data models left untouched for years
- Indexing that never scaled
- Custom rules no one remembers
- Workarounds built on top of workarounds
- Patches replacing real architecture care
BRM doesn’t struggle because it’s old. It struggles because it was left unattended.
The healthiest BRM environments shared four traits: Structure. Ownership. Clean architecture. Operational discipline.
The struggling ones shared one cause, unmanaged complexity.
As one leader put it: “We thought we needed a replacement. We needed accountability.”
The Fix Isn’t Magic. It’s Foundations.
-
- Invoices stop failing
- Batch jobs stop crawling
- Finance trusts the numbers
- IT stops firefighting
- Customers stop escalating
- Revenue stabilizes
The biggest shift is the return of confidence.
We See the Same Issues Across All Platforms
-
- Zuora rebuilds
- Salesforce CPQ realignments
- BillingPlatform tuning
- Usage-based billing transformations
Everyone wants flexibility, dynamic pricing, clean revenue, faster change cycles.
But none of that is possible without foundational architecture.
Complexity isn’t the enemy. Unmanaged complexity is.
Why This Matters for 2026
Usage-based billing is outpacing teams’ readiness
Failures come from inconsistent data, not broken logic.
Automation is no longer optional
By 2026, over half of billing stacks will embed AI/automation,widening the gap between disciplined and patched systems.
Revenue leakage is finally becoming visible
It starts with thousands of micro-failures hidden inside messy architecture.
Leadership Insight: Listening Over Assumptions
He asked:
-
- What’s working?
- What’s slowing us down?
- Where are the silent risks?
- What can we fix today?
The themes matched what we heard from the BRM community:
Billing problems rarely surface in dashboards. They surface in the day-to-day reality of the people closest to the system.
Healthy operations start with listening, discipline, and ownership, regardless of platform.
Product Spotlight: Revenue Intelligence and Optimization (RIO)
RIO helps teams:
-
- Catch leakage early
- Turn lagging indicators into real-time signals
- Reduce manual reconciliations
- Bring visibility to complex stacks
- Strengthen trust across Finance, IT, and Ops
Organizations don’t lack tools. They lack visibility and discipline. RIO delivers both.
Next Month: Intelligent Automation in Billing
-
- What AI and automation actually do for billing
- Patterns across Zuora, Salesforce, BRM, and BillingPlatform
- What leaders must prioritize in 2026
- How to prepare teams for the next cycle of change
- Predictions for the year ahead
See you next month,
The Synthesizer Team