Marketplaces spent the last decade chasing scale. The next decade belongs to orchestration. Discover how AI, connected data, and autonomous agents are reshaping seller growth, retail media, monetisation, and platform operations.
Last week, together with our partners at Salesforce, Trigg Digital had the privilege of bringing together an exceptional group of leaders from across retail, marketplaces, classifieds, travel, payments, and digital commerce for an invitation-only executive lunch in London.
Hosted at Lucky Cat by Gordon Ramsay, the goal was deliberately simple: no presentations, no sales pitches, and no corporate theatre—just an honest conversation about where the next wave of marketplace growth is really coming from.
What followed was one of the most commercially grounded and strategically honest discussions we’ve had in some time. While every organisation around the table was at a different stage of maturity, one theme surfaced repeatedly throughout the afternoon:
For many years, marketplace growth was measured largely through volume. More sellers, more products, more categories, and more traffic were seen as the primary indicators of success. While scale still matters, scale alone is no longer enough. Today, scale is expected. The real differentiator is how effectively businesses orchestrate data, relationships, monetisation models, and increasingly, artificial intelligence.
One of the most relatable observations of the day came early in the discussion:
Every successful platform begins somewhere. In the early stages, spreadsheets, shared inboxes, manual approvals, and operational workarounds often provide the flexibility needed to move quickly. In fact, as we explored in our recent article, Seller Management: The Hidden Engine Behind Marketplace Growth, many marketplace businesses reach an inflection point where seller operations, onboarding, and partner workflows become just as critical as customer acquisition.
The challenge arises when these temporary processes become permanent infrastructure.
At a certain point, what once enabled growth begins to constrain it. Seller onboarding slows, approvals become fragmented, reporting becomes inconsistent, and operational visibility declines. The businesses scaling most effectively are recognising the moment when operational flexibility must evolve into platform maturity.
Another strong theme centred around strategic focus.
As marketplaces grow, there is often pressure to expand into adjacent categories, launch new services, or pursue every possible revenue opportunity. However, some of the strongest perspectives shared during the event reinforced a different approach.
The most successful marketplace businesses are not trying to own every category. Instead, they are doubling down on areas where they already possess customer trust, supply-side advantage, audience density, and commercial differentiation. Sustainable growth does not always come from doing more. In many cases, it comes from doing fewer things—exceptionally well.
Perhaps the strongest operational theme of the afternoon was data.
Retail media, dynamic pricing, personalisation, forecasting, and AI-driven decision-making all depend on trusted signals. Without clean, connected, and governed data, monetisation stalls, customer experiences become inconsistent, and commercial teams struggle to act with confidence.
Data quality is no longer an IT initiative. It is increasingly becoming a core revenue strategy.
The conversation also challenged a long-standing marketplace obsession with acquisition.
Historically, marketplace businesses have focused heavily on bringing in new sellers, new buyers, and new inventory. Yet the leaders around the table repeatedly returned to a more difficult truth: sustainable growth comes from retention.
Seller loyalty, advertiser renewal, customer lifetime value, and partner expansion are becoming just as important as acquisition. The strongest businesses are not simply growing faster—they are compounding smarter.
As organisations scale, complexity inevitably follows.
Every leader in the room acknowledged the same challenge. Growth creates more workflows, more integrations, more teams, more approvals, and more exceptions.
Left unmanaged, complexity quietly becomes technical debt.
The organisations scaling most effectively are not necessarily the largest. They are the ones building operating models that can scale with complexity, rather than against it.
Perhaps the boldest statement of the afternoon came during a discussion on artificial intelligence.
This is not because AI itself is the problem. The risk comes when organisations deploy disconnected AI initiatives without trusted data, clear ownership, or governance.
Duplicate tools, fragmented decision-making, inconsistent outputs, and overlapping automation can quickly create complexity rather than advantage.
The marketplaces that will win over the next decade will not simply deploy AI. They will operationalise intelligence—built on trusted data, connected workflows, platform governance, and business ownership.
If one thing became clear throughout the day, it is that the future of marketplace growth sits at the intersection of data, CRM, monetisation, and agentic AI—not as separate initiatives, but as one connected operating model.
At Trigg Digital, we call this The Intelligent Marketplace.
Because the question is no longer:
How big can your marketplace become?
The real question is:
How intelligently can it scale?
Special thanks to our partners at Salesforce and to every leader who contributed so openly throughout the day. The conversations reinforced just how much opportunity still lies ahead.
Re-thinking your marketplace growth strategy?
If you’re scaling a marketplace, retail media platform, or partner ecosystem, book a strategy conversation with Trigg Digital.
Seller management has quietly become one of the most powerful growth levers in modern marketplaces. Not because marketplaces list more products, but because—when seller participation is designed and managed well—they generate a continuous flow of high-quality, first-party signals. These signals increasingly shape discovery, conversion, engagement, and long-term growth.
This shift matters now more than ever. As marketplaces layer in retail media, promotions, fulfilment commitments, and monetisation models, growth increasingly depends on the quality and timeliness of seller-generated signals—not just the size of the catalogue.
In many organisations, seller management still sits in the background. Teams often treat it as a functional necessity that covers onboarding, catalogue uploads, compliance checks, and support tickets. In practice, however, seller management now plays a far more strategic role. It directly influences marketplace liquidity, data quality, and scalability.
As marketplaces mature and evolve into broader platforms, the way sellers are managed—and empowered—becomes decisive. Increasingly, it determines whether a marketplace compounds or plateaus.
Traditional ecommerce models optimise within a single organisation. Marketplaces operate very differently. Control is distributed across independent sellers, and outcomes emerge from how effectively participation is coordinated.
As a result, successful marketplaces no longer win by simply aggregating supply. Instead, they win by orchestrating participation.
Every seller interaction creates signals. Onboarding decisions, pricing updates, availability changes, and promotional activity all generate data points. Over time, these signals become immensely valuable. They influence search relevance, ranking logic, assortment quality, fulfilment reliability, and buyer trust.
For this reason, leading marketplace operators no longer talk about “seller operations” alone. They increasingly think in terms of seller ecosystems.
When designed well, a seller ecosystem improves participation quality and reduces friction for buyers. It also creates more consistent patterns of behaviour across the marketplace. By contrast, poorly designed seller management introduces noise. Inconsistent pricing, unreliable availability, and stale data quietly undermine trust and constrain growth.
As marketplaces scale, competitive advantage shifts. Surface-level features matter less, while the quality of underlying signals matters more.
In marketplace environments, sellers act as active participants in the data economy. Their pricing strategies, responsiveness, promotional behaviour, and inventory decisions feed directly into the signal layer that powers marketplace performance.
In practice, these signals show up in everyday seller actions, such as pricing updates, promotion participation, inventory accuracy, fulfilment reliability, and responsiveness to demand. Individually, each action seems minor. Collectively, they determine how effectively a marketplace matches intent, maintains trust, and scales sustainably.
Over time, this dynamic compounds.
More engaged sellers generate richer behavioural signals. In turn, richer signals enable better discovery, more accurate matching of intent, and more consistent buyer outcomes. As a result, participation and performance begin to reinforce one another.
However, this flywheel only works when seller data remains clean, timely, and consistent. Crucially, seller management determines whether that condition holds.
As marketplaces grow, manual seller operations break down quickly. Ticket queues lengthen. Changes lag behind reality. Data quality deteriorates. Gradually, the marketplace begins optimising against outdated information.
This is why self-service is not a convenience feature. Instead, it acts as a scaling mechanism.
When sellers can onboard themselves, manage catalogues, adjust pricing, control availability, and participate in promotions directly, two things happen. First, operational friction drops. Second—and more importantly—signal quality improves.
Self-service introduces immediacy into the signal layer. Prices reflect intent. Inventory reflects reality. Promotions reflect strategy rather than backlog. As a result, the marketplace stops reacting after the fact and starts responding in near real time.
At scale, seller management determines whether self-service strengthens signal quality or simply accelerates inconsistency.
Many marketplaces still rely on static optimisation cycles. Rules update periodically, performance reviews happen retrospectively, and interventions arrive with delay. While these models can support early growth, they struggle as complexity increases.
By contrast, adaptive marketplaces operate differently. They ingest signals continuously and respond dynamically. Pricing, availability, ranking, and participation mechanisms evolve alongside seller and buyer behaviour rather than lagging behind it.
Crucially, this shift is not primarily a technology challenge. Instead, it is a design challenge. It begins with how organisations onboard sellers, define participation rules, and govern activity over time.
Marketplaces that treat seller management as an administrative layer will eventually stall. Those that treat seller management as a strategic engine—designed around participation, signal quality, and adaptability—create the conditions for sustained growth.
This article is the first in a series exploring how modern marketplaces really scale. Rather than focusing on features alone, the series examines the systems and decisions that shape behaviour at scale.
At Trigg, we spend a great deal of time working with organisations navigating this shift in practice. If you are navigating marketplace complexity — seller scale, signal quality, or participation design — this series is written for you.
Every Enterprise Resource Planning (ERP) vs Agentforce Revenue Management (ARM) revenue control debate eventually lands in the same place:
“Shouldn’t ERP just handle this?”
It’s a logical instinct, because fewer systems feel safer and control feels clearer.
In practice, this assumption is one of the most common reasons revenue transformations stall.
ERP systems are built to protect the business. They deliver accounting accuracy, compliance, and auditability. They create financial truth.
They are not designed to govern commercial decision-making.
When ERP is pushed into roles it was never built for — dynamic pricing, deal flexibility, customer-specific exceptions — organisations pay the price in slow change, brittle customisation, and frustrated commercial teams.
This isn’t a technology failure.
It’s an ownership failure.
We see this pattern repeatedly in large-scale commercial programmes, particularly where ownership of pricing and deal logic is unclear — a theme we explore further in Why Most CPQ Programmes Fail at Scale.
This is the core misunderstanding at the heart of the ERP vs ARM revenue control conversation.
At its core, revenue operates across two distinct domains.
One is commercial: intent, negotiation, flexibility, speed.
The other is financial: recognition, compliance, certainty.
As a result, trying to force both into a single control point creates tension rather than clarity. Sales teams push for agility. Finance teams push for control. The system becomes the point of conflict.
What boards experience as “complexity” is often simply unclear ownership inside the architecture.
This is why revenue is no longer just a workflow — it is an operating model in its own right, as outlined in Revenue Is No Longer a Process — It’s an Operating System.
In practice, the most effective revenue organisations separate responsibility cleanly.
CRM captures demand and customer context.
ARM governs commercial intent, pricing logic, and policy.
ERP executes financial truth.
Each system does what it’s best at — no more, no less.
This separation reduces delivery risk, accelerates change, and builds trust between commercial and finance teams. It also avoids the downstream failures that often appear when billing and recognition are forced to absorb commercial complexity — a breakdown we unpack in Billing Is Where Revenue Transformations Go to Die.
In an ERP vs ARM revenue control model, this separation is what allows speed and governance to coexist.
As organisations introduce AI and agent-led workflows, ambiguity becomes a liability.
By design, agents move fast. If logic is duplicated or ownership is unclear, errors scale quickly and accountability becomes harder to trace.
In this world, ARM acts as the control plane — ensuring decisions remain within defined commercial guardrails before execution in ERP.
ERP remains the system of record, while ARM becomes the system of decision.
That distinction is what enables speed without sacrificing control.
Some organisations extend their existing stack. Others replace specific components. Many land somewhere in between.
The right answer depends on how your business sells, how much flexibility you need, and where governance must sit.
At Trigg, we help leadership teams design revenue operating systems that reflect reality — complementing existing technology where it works, and replacing it where it doesn’t.
The goal is not consolidation for its own sake. Instead, it is clarity.
Ultimately, ERP is essential to revenue transformation.
However, it is not the control plane.
Treating it as such slows innovation and increases risk — the opposite of what leaders intend.
The goal is not fewer systems. Rather, it is clear responsibility, governed autonomy, and a revenue operating model built for scale.
Every organisation starts from a different place.
Some need clearer ownership across CRM, ARM, and ERP.
Others need to modernise legacy commercial layers.
Many need an operating model that is ready for AI-driven execution.
At Trigg, we help organisations define and implement revenue operating systems that scale — with governance designed in from day one.
If you’re reassessing revenue architecture, start with clarity — not consolidation.
Most revenue transformations don’t fail in technology.
They fail in behaviour.
New platforms go live. Automation works. Dashboards light up. Yet months later, the same patterns reappear: sales teams bypass the system, deal desks quietly return, finance runs shadow controls, and AI agents are switched off or ignored.
This isn’t resistance.
It’s what happens when organisations fail to design change properly.
At Trigg, we see revenue transformation fail not because the platform is wrong — but because decision ownership, autonomy, and governance are never designed together.
Software executes decisions. Behaviour determines whether those decisions stick.
Modern transformation programmes are very good at shipping systems.
They are far less effective at reshaping behaviour.
Dashboards lighting up does not mean teams have changed how they make decisions.
Automation running does not mean teams trust the system.
AI can make recommendations, but people won’t follow them without trust.
What breaks isn’t the tooling — it’s the gap between how decisions are supposed to be made and how people actually make them under pressure.
That gap is a change-management problem.
Agentic revenue models don’t just improve efficiency. They change who decides.
Who can approve pricing.
When exceptions are allowed.
How renewals are triggered.
Which actions happen without human involvement.
That’s not just a system change — it reshapes the organisation.
When leaders don’t make decision boundaries explicit, teams default to familiar behaviours. Not out of defiance, but because ambiguity feels risky in revenue-critical moments.
Most change programmes assume roles stay broadly the same, systems support people, and governance remains static.
Agentic revenue breaks all three assumptions.
Agents recommend, initiate, and enforce actions automatically. Without deliberate design, teams experience this shift as a loss of control rather than progress. People push back quietly by creating workarounds instead of confronting the change.
This is why revenue transformations most often collapse at the point of billing and execution — not strategy.
When organisations fail to manage change at the decision level, the same symptoms appear.
Sales teams create “one-off” exceptions that quickly become the norm.
Deal desks grow instead of shrinking.
A single unexplained AI decision undermines trust in the entire model.
Technology isn’t the problem. They signal that the organisation never adapted to the new way teams make decisions.
Successful organisations treat change management as a design discipline, not a communications exercise.
They make decision rights between humans and agents explicit. They introduce autonomy gradually, earning trust over time rather than demanding it at go-live.
And they focus on adoption as behaviour change, not feature usage.
Leaders cannot delegate change management.
When leaders remain ambiguous about agent-based revenue models, teams read that ambiguity as permission to revert. Visible executive sponsorship — of decision boundaries, accountability, and new ways of working — is what makes agentic revenue stick.
Revenue transformation fails when organisations automate execution without first designing how decisions are made. Effective transformation requires leaders to:
When behaviour, governance, and systems are designed together, transformation becomes durable.
When they are not, teams revert to workarounds — regardless of how advanced the technology is.
This is the design principle behind how Trigg helps organisations build governed, agent-ready revenue operating models — where change is engineered into the system, not left to chance.
Most revenue programmes look successful at go-live.
In a billing revenue transformation, that confidence often holds — until billing starts.
Quotes are faster.
Sales adoption is high.
Dashboards look impressive.
However, billing starts.
Invoices don’t match expectations.
Credits pile up.
Disputes consume Finance and Sales alike.
And quietly, confidence in the entire transformation erodes.
What looked like progress begins to feel fragile. Not because the vision was wrong — but because the hardest part of revenue was deferred.
From a finance perspective, most revenue transformations don’t fail because automation was a bad idea — they fail because billing is where risk finally becomes visible.
Upstream, everything looks healthy:
But once billing begins, Finance inherits decisions that are already locked:
At that point, invoices stop matching expectations.
Credits accumulate.
Disputes multiply.
What looked like momentum upstream becomes exposure downstream.
CFO scepticism isn’t resistance to change.
It’s resistance to uncontrolled, unrecoverable risk.
Finance isn’t reacting to automation — it’s reacting to the moment when upstream decisions become financially irreversible.
This pattern is explored in more depth in our CFO’s Guide to Agentic Revenue, which looks at how governed autonomy prevents these downstream failures before they reach billing.
Billing rarely gets attention early because:
These factors push billing downstream in programme design — even though it’s the first place customers and cash feel the impact.
Yet billing is where revenue intent becomes customer reality.
Every discrepancy is visible.
Each error damages trust.
Over time, disputes delay cash.
If revenue is an operating system, billing is its moment of truth.
When billing isn’t deliberately designed into revenue transformation, the consequences cascade:
As a result, none of these show up clearly in the original business case.
All of them show up in month-end close.
Worse, teams often blame these failures on “process” or “training” — rather than the architectural gaps that created them.
Traditional revenue models assume:
In practice, those assumptions no longer hold.
Modern revenue violates all three.
Subscriptions upgrade mid-term.
Usage fluctuates daily.
Entitlements change continuously.
Without a system that deliberately orchestrates these changes, billing chaos isn’t an exception — it’s the default.
Agentforce Revenue Management doesn’t always replace billing systems.
It makes them reliable.
ARM creates a governed layer between commercial intent and financial execution by governing what can be sold, tracking changes to entitlements, coordinating amendments and renewals, and explaining billing outcomes transparently.
As a result, ARM reduces invoice errors, credit volumes, and dispute cycles — while improving customer trust, cash predictability, and finance credibility.
Billing stops being reactive — and becomes explainable.
That explainability is what allows Finance to trust automation at scale.
Most billing failures don’t originate in billing.
They originate in upstream decisions that were optimised for speed rather than control.
Common root causes include unclear pricing logic, inconsistent amendment handling, and missing policy enforcement.
By contrast, fixing billing downstream is expensive.
Designing revenue correctly upstream is not.
The most dangerous assumption in revenue programmes is simple:
“We’ll fix billing later.”
By that point, trust has already been lost.
Leaders must co-design billing with pricing, contracts, and agents — or billing will expose every shortcut taken upstream.
You can automate quoting.
You can optimise contracts.
And you can deploy agents.
But if billing doesn’t work, none of it matters.
If billing feels fragile, it’s usually because revenue was designed for speed before it was designed for control.
The organisations that scale confidently treat billing as a design decision — not a downstream fix.
If this resonates and you’re reassessing how billing, pricing, contracts, and automation fit together, get in touch with the team at Trigg.
Most revenue transformations start in Sales.
The ones that succeed end with the CFO.
That’s not politics — it’s physics.
Agentforce Revenue Management is becoming essential as revenue models grow more dynamic, because the cost of getting revenue wrong shows up fast: margin leakage, billing disputes, and cash delays.
Those risks don’t sit with Sales.
They sit squarely in the CFO’s remit.
From a finance perspective, many “revenue transformation” programmes fail for the same structural reasons.
Too often, organisations bring Finance in after they have already encoded decisions into systems.
By that point, the financial consequences are already baked in:
CFO scepticism isn’t resistance to change.
It’s resistance to uncontrolled change.
In practice, strip away the jargon, and CFO expectations around revenue systems are remarkably consistent.
Margin Integrity
Margin protected by policy, not post-deal review.
Cash Predictability
Cash flows become deterministic, not reactive.
Control Without Paralysis
Autonomy governed by rules — not approvals.
As a result, this is where most legacy CPQ-centric approaches fall short.
CPQ systems optimise deal construction — not financial outcomes across the full revenue lifecycle.
Agent-orchestrated revenue systems shift the conversation from:
“Can Sales move faster?”
to:
“Can the business scale complexity without losing financial control?”
This is where Agentforce Revenue Management (ARM) becomes relevant — not as another CPQ iteration, but as a governed revenue control layer.
Agentforce Revenue Management builds on Salesforce’s broader Agentforce and Revenue Cloud capabilities, designed to bring governed automation into enterprise revenue operations — embedding finance policy directly into pricing, contracting, billing, and revenue execution.
When designed correctly, agentic revenue models:
Crucially, this only works when organisations embed finance policy directly into the revenue layer, rather than bolting it on later.
From what we see across enterprise organisations, CFO support for ARM initiatives depends on four non-negotiables.
1. Commercial Intent Has a Single Owner
Who decides pricing, under what conditions, and why must be explicit — not inferred from workflow.
2. Intent and Execution Are Seperated
Organisations should not bury revenue logic inside ERP customisations or sales processes. Policy must outlive tools, teams, and org changes.
3. Governed Autonomy
Agents can act — but only within clearly defined financial guardrails.
Autonomy without policy creates risk, not scale.
4. Measurable Financial Outcomes
CFOs expect to see:
Without this, Agentforce Revenue Management becomes just another technology programme.
In an agentic revenue model powered by Agentforce Revenue Management:
Importantly, this isn’t about giving Finance more work.
It’s about giving Finance structural leverage.
Without slowing down revenue or increasing approval overhead.
The future of revenue doesn’t belong to Sales or Finance alone.
Ultimately, it will only work at scale if CFOs trust the system more than they trust manual overrides.
Leaders must design that trust deliberately.
Agentforce Revenue Management is how that trust is operationalised at scale — through policy, not people.
Ready to design agentic revenue with financial control?
Agentic revenue only works when margin, cash, and policy are embedded into the system — not reviewed after the fact.
We work with CFOs and revenue leaders to design governed agentic revenue models using Agentforce Revenue Management — aligned to financial policy, auditability, and scale. Book a CFO-level strategy session
Autonomous revenue agents are changing how organisations think about AI across sales, finance, and operations.
AI has entered the revenue conversation loudly. New tools promise faster deals, smarter pricing, and fewer manual steps. But much of the conversation still misses the real issue.
The question isn’t whether agents can do more.
It’s which revenue decisions they should be trusted to make — and under what conditions.
Because the real impact of agents isn’t about automation volume or speed. It’s about decision authority.
Most organisations start with assistive AI. Agents summarise deals, draft contracts, recommend prices, and answer billing questions. These capabilities are low-risk and immediately useful, which is why adoption happens so quickly.
But assistive AI doesn’t change how revenue works. It helps people move faster inside the same operating model, with the same approvals, handoffs, and constraints.
Efficiency improves. Outcomes rarely do.
Autonomous revenue agents operate very differently. They don’t just advise — they act.
They initiate actions, make decisions, and resolve exceptions in real time, often across multiple systems. Operating continuously and at machine speed, they introduce a new dynamic into revenue operations.
This shift doesn’t simply increase productivity.
It reassigns who gets to decide.
And that’s where risk enters the picture.
Resistance to autonomous agents is often misread as fear of change. In reality, it’s a rational response to how revenue decisions actually work.
In revenue, flexibility isn’t a nice-to-have — it’s how deals get done. Sales teams worry about being overridden in moments where context matters more than rules. Finance worries about policies being applied inconsistently at scale, with no clear audit trail when something goes wrong. Legal worries about compliance and accountability when decisions are executed by systems rather than named individuals.
This isn’t a rejection of AI.
It’s a rejection of autonomy without boundaries.
The organisations succeeding with autonomous revenue agents aren’t trying to make agents as autonomous as possible. They’re designing autonomy deliberately.
They ask where autonomy creates value, and where it introduces unacceptable risk.
In practice, this leads to a staged model:
Assistive agents
that support human decision-making
Semi-autonomous agents
that act within clearly defined guardrails
Fully autonomous agents
operating in tightly bounded, well-understood domains
At every stage, autonomy is anchored to explicit policy, clear escalation paths, and complete auditability. Without these foundations, trust erodes quickly — and autonomy stalls.
Revenue is one of the most demanding environments for autonomy. Revenue decisions are financially material, customer-visible, and often legally binding.
Mistakes don’t stay internal. They surface in contracts, invoices, and renewal conversations.
That’s exactly why revenue is the right place to start.
If an organisation can govern autonomy across pricing, contracting, renewals, and billing, it can govern it anywhere. Revenue exposes every weakness in operating models, which is why point solutions and traditional CPQ systems break at scale.
Revenue isn’t a workflow problem.
It’s an operating system problem.
Even in an agentic future, some things remain constant:
Agents don’t replace leadership.
They execute leadership intent — consistently, continuously, and at scale.
The winners won’t be the companies with the most autonomous agents.
They’ll be the ones that design trustworthy autonomy, align it tightly to revenue policy, and scale it deliberately across the revenue lifecycle.
See autonomous revenue agents in action. Discover how Agentforce Revenue Management delivers governed autonomy across every deal, renewal, and billing event.
Book a strategy session to see what controlled, auditable revenue autonomy actually looks like in practice.
Agentforce Revenue Management (ARM) provides the revenue control plane enterprises need between CRM and ERP. Most enterprises already run two powerful systems:
CRM captures demand.
ERP records financial truth.
Yet revenue still leaks.
Deals stall.
Billing disputes rise.
Finance questions pipeline confidence.
The problem isn’t system capability.
Instead, neither platform was designed to orchestrate revenue end to end.
When revenue breaks, organisations swing between two extremes. One camp argues that sales should own it and push everything into CRM. Meanwhile, the other insists finance should take control and lock everything down in ERP.
Both approaches fail — and they fail for the same reason.
No single function owns revenue. Instead, revenue operates as a cross-functional system built on three elements: intent, decisioning, and execution.
CRM captures what customers want. However, ERP records what actually happened.
As a result, organisations lack real-time control.
What’s missing is a revenue control plane — a layer that governs what can happen before execution begins.
Between CRM and ERP sits the most fragile layer of revenue operations. Here, teams define pricing logic, govern discounts, manage contracts, handle renewals, apply usage changes, and hand off billing.
As a result, margin gets negotiated, risk increases, and exceptions multiply.
Historically, organisations stitched this layer together with CPQ rules, manual approvals, spreadsheets, and deal desks. At the time, this approach felt “good enough.”
However, it no longer scales.
Today, subscriptions, consumption pricing, global revenue models, and AI-driven decisions demand real-time control. Therefore, complexity has outgrown the tooling.
Modern enterprises don’t just need more automation. Instead, they need a revenue control plane.
This system coordinates decisions across Sales, Finance, Legal, and Operations. It enforces commercial policy dynamically and translates customer intent into execution.
This is exactly what Agentforce Revenue Management delivers.
ARM doesn’t replace CRM or ERP. Instead, it sits between them to orchestrate revenue with speed and governance.
As a result, leaders make the right decisions before execution — not after.
Agentforce Revenue Management (ARM) is Salesforce’s revenue orchestration layer. Its role is to own commercial intent, validate deals against policy and margin rules, and orchestrate execution into billing and finance systems.
ARM is not CPQ v2. It’s not a billing engine. And it’s not a reporting layer. It’s a control system.
In practice, CRM captures what the customer wants. ARM governs what the business allows. ERP records what gets booked and billed.
This structure removes friction, reduces risk, and dramatically improves forecast confidence.
As AI agents take on more responsibility — from creating quotes and managing renewals to resolving billing queries — the risk of unguided automation increases.
Without a revenue control plane, agents act on incomplete data, finance loses visibility, and trust starts to erode. Automation moves faster than governance, and that’s where things break.
Agentforce Revenue Management provides the guardrails that allow automation to scale safely. It ensures AI-driven actions are aligned with commercial policy, financial controls, and enterprise risk standards.
For a deeper view on modern revenue architecture, explore our guide to the Revenue Operating System.
If revenue still feels unpredictable, slow, or contested internally, it’s rarely a people problem. It’s almost always an architecture problem.
Until organisations design a revenue control plane between CRM and ERP, they will continue to leak value through friction, exceptions, and manual workarounds.
The future of revenue isn’t owned by Sales or Finance.
It is orchestrated — deliberately — through Agentforce Revenue Management.
Ready to take control of revenue?
See how Agentforce Revenue Management delivers real-time governance across every deal, renewal, and billing event. Book a strategy session to see ARM in action.
CPQ at scale rarely fails dramatically.
It doesn’t crash.
Nor does it get ripped out overnight.
And it rarely triggers a transformation programme on day one.
Instead, it degrades.
Quietly.
Not because CPQ is outdated — but because revenue has outgrown it.
As product portfolios expand, pricing models multiply, and revenue becomes more dynamic, CPQ shifts from enabler to constraint — not because the technology is poor, but because the role it’s been asked to play has fundamentally changed.
In practice, most organisations don’t wake up one morning and declare their CPQ broken. Instead, the signals emerge slowly:
🧾 Quotes still go out — but take longer than they used to
🧩 Exceptions increase — and quietly become “normal”
🔍 Finance validates after close — not before
🧑💼 Deal desks grow — instead of shrinking
📉 Margin erosion appears later — not in the moment
Individually, these look like operational issues.
Collectively, they signal something structural — revenue decisions are being forced through a system designed for a simpler world.
These are the early indicators of CPQ being stretched beyond its design limits.
Originally, CPQ was designed to answer a narrow set of questions:
Is this configuration valid?
Does the price follow the rules?
Can sales generate a quote quickly and consistently?
That worked when:
📦 Products were largely static
📊 Pricing models were predictable
🧭 Sales owned most decisions
🧾 Billing followed contracting with minimal deviation
In that environment, CPQ automated execution effectively.
But modern revenue no longer fits inside those assumptions.
Today’s reality includes subscriptions, usage, amendments, renewals, mid-term changes, regional overlays, and continuous optimisation — all happening simultaneously.
CPQ was never designed to orchestrate that level of dynamism.
As complexity rises, the same failure modes appear across industries when CPQ at scale becomes the de facto decision engine.
Logic becomes fragile
Pricing rules pile up. Bundles nest inside bundles. Small changes carry unexpected consequences.
Trust erodes
Sales, finance, and billing interpret the same deal differently — and stop relying on a single source of truth.
Speed declines
Approvals multiply. Manual intervention increases. Automation paradoxically slows things down.
AI adds risk instead of leverage
When AI is bolted onto an unstable decision model, confidence drops instead of rising. Governance becomes reactive.
The shift requires agent-based execution that operates inside clearly defined policy, pricing, and risk boundaries — not alongside them.
Real value only emerges when agents operate inside defined policy, pricing, and risk boundaries — not alongside them.
None of this is a tooling problem.
It’s an operating-model problem.
High-performing organisations aren’t “replacing CPQ”.
They’re demoting it.
They recognise that CPQ can’t sit at the centre of revenue decision-making. Instead, it needs to operate inside a broader revenue orchestration layer — one that:
🎛️ Governs pricing and policy centrally
🔄 Aligns sales intent with financial outcomes continuously
🤝 Defines where humans decide and where agents act
⚠️ Exposes risk before revenue is committed
In this model, CPQ executes — but it doesn’t decide.
Crucially, this isn’t CPQ v2.
It isn’t “CPQ plus AI”.
And it isn’t a better approval workflow.
It’s a recognition that revenue no longer behaves like a linear transaction flow.
It behaves like a system — adaptive, always on, and constantly recalculating.
Trying to manage that with tools designed for sequential handoffs guarantees friction, delay, and leakage.
Most CPQ programmes don’t fail at launch.
They fail over time — as complexity accumulates and confidence drains away.
The organisations pulling ahead are the ones willing to:
🚫 Stop treating revenue as a sales automation problem
🧠 Design decision-making, not just execution
🏛️ Embed finance, governance, and AI by design
🧩 Rethink the layer between CRM and ERP — where orchestration platforms like Agentforce Revenue Management increasingly sit — but where operating-model clarity is still missing
This is where we see transformation succeed — or stall.
Because revenue transformation is no longer a sales initiative.
It’s an enterprise design challenge.
CPQ at scale still matters. But it can no longer be the place where revenue decisions live.
The future belongs to organisations that design for complexity first — and let CPQ play the role it was always meant to play:
Execution, not orchestration.
Control, not complexity.
Insights
hello@triggdigital.com
© 2026 Trigg Digital Ltd. · All rights reserved · Company No. 12095839