Resources

Perspectives on Revenue Execution

Clear thinking on how enterprises design, execute, and evolve revenue — without being constrained by systems of record.

Get the latest updates right to your inbox

Customer Patterns

How enterprises modernize revenue execution without rewriting their systems

View All

Customer Patterns

Don't wait for S/4HANA: How a Fortune 500 medical device manufacturer transformed order management during migration

Their growing & emerging markets region faced a classic dilemma — wait for S/4HANA, or build now and rebuild later. Neither option aligned with the business's pace or the expectations of distributors.

Doug Wessel

Head of Co-Innovation Engineering

Customer Patterns

Don't wait for S/4HANA: How a Fortune 500 medical device manufacturer transformed order management during migration

Doug Wessel

Head of Co-Innovation Engineering

Customer Patterns

Don't wait for S/4HANA: How a Fortune 500 medical device manufacturer transformed order management during migration

Doug Wessel

Head of Co-Innovation Engineering

Customer Patterns

Revenue Logic Is Now Fast to Change. Implementation Should Be Too.

Lucas Seidenfus

Customer Success Delivery Lead

Customer Patterns

How a healthcare device manufacturer extended legacy ERP investment while modernizing during divestiture

Andrew Martin

Chief Operating Officer

Customer Patterns

How a research publisher exited AS/400, preserved 30 years of bespoke logic, and simplified its path to S/4HANA.

Brian Diehl

VP of Industry Strategy & Partnerships

Revenue Logic Is Now Fast to Change. Implementation Should Be Too.

How a healthcare device manufacturer extended legacy ERP investment while modernizing during divestiture

How a research publisher exited AS/400, preserved 30 years of bespoke logic, and simplified its path to S/4HANA.

Customer Patterns

Revenue Logic Is Now Fast to Change. Implementation Should Be Too.

Lucas Seidenfus

Customer Success Delivery Lead

Customer Patterns

How a healthcare device manufacturer extended legacy ERP investment while modernizing during divestiture

Andrew Martin

Chief Operating Officer

Customer Patterns

How a research publisher exited AS/400, preserved 30 years of bespoke logic, and simplified its path to S/4HANA.

Brian Diehl

VP of Industry Strategy & Partnerships

Revenue Execution, Explained

What revenue execution really means—and why it breaks inside traditional systems

View All

Revenue Execution, Explained

Why enterprises need a revenue execution layer now

Growth, speed, and flexibility are no longer constrained by strategy. They’re constrained by how revenue is executed across systems that were never designed to change together.

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

Why enterprises need a revenue execution layer now

Growth, speed, and flexibility are no longer constrained by strategy. They’re constrained by how revenue is executed across systems that were never designed to change together.

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

Why enterprises need a revenue execution layer now

Growth, speed, and flexibility are no longer constrained by strategy. They’re constrained by how revenue is executed across systems that were never designed to change together.

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

From Tools-First to Motions-First: How AI Closes the Revenue Execution Gap

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

Revenue motions and the end of the strategy–execution gap

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

How a revenue execution layer creates value at every stage of the SAP journey

Larry Ramponi

Chief Product Officer

From Tools-First to Motions-First: How AI Closes the Revenue Execution Gap

Revenue motions and the end of the strategy–execution gap

How a revenue execution layer creates value at every stage of the SAP journey

Revenue Execution, Explained

From Tools-First to Motions-First: How AI Closes the Revenue Execution Gap

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

Revenue motions and the end of the strategy–execution gap

Larry Ramponi

Chief Product Officer

Revenue Execution, Explained

How a revenue execution layer creates value at every stage of the SAP journey

Larry Ramponi

Chief Product Officer

Inside the layer

How revenue execution actually works when it’s separated from systems of record

View All

Inside the layer

Model real-world revenue complexity — once, execute everywhere

How capturing real business complexity once prevents duplication across channels and systems

Larry Ramponi

Chief Product Officer

Inside the layer

Model real-world revenue complexity — once, execute everywhere

How capturing real business complexity once prevents duplication across channels and systems

Larry Ramponi

Chief Product Officer

Inside the layer

Model real-world revenue complexity — once, execute everywhere

How capturing real business complexity once prevents duplication across channels and systems

Larry Ramponi

Chief Product Officer

Inside the layer

Building revenue execution that evolves without constant restarts

Larry Ramponi

Chief Product Officer

Inside the layer

Gaining end-to-end visibility into how revenue actually executes

Larry Ramponi

Chief Product Officer

Inside the layer

Model revenue once and execute it consistently everywhere

Larry Ramponi

Chief Product Officer

Building revenue execution that evolves without constant restarts

Gaining end-to-end visibility into how revenue actually executes

Model revenue once and execute it consistently everywhere

Inside the layer

Building revenue execution that evolves without constant restarts

Larry Ramponi

Chief Product Officer

Inside the layer

Gaining end-to-end visibility into how revenue actually executes

Larry Ramponi

Chief Product Officer

Inside the layer

Model revenue once and execute it consistently everywhere

Larry Ramponi

Chief Product Officer

viax In Action

View All

viax In Action

Why CIOs Need to Prove Revenue Execution — Before Committing ERP Architecture

How execution-first proof reduces delivery risk, integration sprawl, and irreversible architectural decisions.

Larry Ramponi

Chief Product Officer

viax In Action

Why CIOs Need to Prove Revenue Execution — Before Committing ERP Architecture

How execution-first proof reduces delivery risk, integration sprawl, and irreversible architectural decisions.

Larry Ramponi

Chief Product Officer

viax In Action

Why CIOs Need to Prove Revenue Execution — Before Committing ERP Architecture

How execution-first proof reduces delivery risk, integration sprawl, and irreversible architectural decisions.

Larry Ramponi

Chief Product Officer

viax In Action

viax as a commerce backend and unified pricing engine

Andrew Martin

Chief Operating Officer

viax In Action

Simulating Revenue Outcomes Requires Deterministic Decisioning — Not Just Data

Dennis Golovaty

Head of Delivery

viax In Action

Why CFOs Should Demand Proof of Revenue Execution — Before ERP Commitments

Andrew Martin

Chief Operating Officer

viax as a commerce backend and unified pricing engine

Simulating Revenue Outcomes Requires Deterministic Decisioning — Not Just Data

Why CFOs Should Demand Proof of Revenue Execution — Before ERP Commitments

viax In Action

viax as a commerce backend and unified pricing engine

Andrew Martin

Chief Operating Officer

viax In Action

Simulating Revenue Outcomes Requires Deterministic Decisioning — Not Just Data

Dennis Golovaty

Head of Delivery

viax In Action

Why CFOs Should Demand Proof of Revenue Execution — Before ERP Commitments

Andrew Martin

Chief Operating Officer

Revenue Chaos Demystified

View All

Revenue Chaos Demystified

Revenue isn’t slow. Your architecture is.

Revenue doesn’t move slowly because businesses are complex. It moves slowly because decisions are trapped inside systems that were never designed to execute them.

Andrew Martin

Chief Operating Officer

Revenue Chaos Demystified

Revenue isn’t slow. Your architecture is.

Revenue doesn’t move slowly because businesses are complex. It moves slowly because decisions are trapped inside systems that were never designed to execute them.

Andrew Martin

Chief Operating Officer

Revenue Chaos Demystified

Revenue isn’t slow. Your architecture is.

Revenue doesn’t move slowly because businesses are complex. It moves slowly because decisions are trapped inside systems that were never designed to execute them.