Valid combinations governed by constraints, compatibility, and fitment, not a pick list. Each choice narrows the next.
Revenue Motions
Any revenue motion.
Governed and executable,
end to end.
Any motion your business runs. No point solution required.
The Revenue Motion
A revenue motion is
the full path from intent to cash.
Who’s involved, what’s allowed, and what happens next.
-
Modeled around how the business operates.
Direct, partner, dealer, self-service, subscription, marketplace: any motion you can describe. Pricing, approvals and eligibility become explicit rules in the model, not code paths.
-
One model, every surface.
Sales app, customer and partner portals, marketplace, AI agents: each runs on the same rules, so no channel prices or approves differently.
-
Change the motion, not the systems.
New channels, new pricing structures, and new go-to-market models arrive in the same model. The motion updates. ERP keeps recording.
How a Motion Gets Built
From a description to a running motion.
The Revenue Motion Agent takes it from description to execution: Describe, Clarify, Model, Execute.
Got it. That's the Describe step.
We'll walk you through how viax would model it. Pick a time, or we'll reach out within one business day.
Book a time →In Practice
Spoken in the language of the business. Not translated into software categories.
Each motion is described in the business’s own terms, modeled once, and run on any channel.
| The motion · Business ask | Translated into software categories | Modeled in viax |
|---|---|---|
| Configure · Quote Custom configuration with approval gates |
| Valid combinations, regional pricing, and approval thresholds, governed from first choice to signed quote. |
| B2B · Self-service Account-specific self-service ordering |
| Each account buys from its own catalog, at its contract prices and credit terms, through its own approval chain, on the same model the sales team quotes from. |
| Dealer · Partner Dealer ordering at contracted prices |
| Each dealer orders at its own terms, through a portal generated from the same model as direct sales. |
| M&A Price harmonization across acquired entities |
| One pricing model across acquired businesses, without waiting on ERP consolidation. |
| Usage · Subscription Usage-based billing and true-up |
| Metered usage, thresholds, and overage rated by the declared model each cycle. |
| Channel · Incentive Volume rebate accrual and payout |
| Rebates and incentives accrued per order and paid out by rule, without spreadsheet reconciliation. |
Six examples of motions modeled in viax, not a catalogue. viax has no fixed list of supported motions — any motion your business can describe can be modeled.
Inside a Motion
Any capability, in any motion.
viax is one platform. Pricing, approvals, configuration, fulfillment, and more are available to any motion you model, to the depth it needs.
Sell complex things
The valid choices at each step come from the model, so a dealer, a CSR, and an AI agent are offered the same options.
Bundles with substitution rules that still hold when a component is unavailable.
Checked against serial number, installed base, and warranty state before an order is accepted.
What an asset is covered for, resolved in the moment from warranty, contract, and service-level terms.
Services handled as orders: requested, scoped, priced, scheduled, and billed in the same motion as products.
Price and promote
Customer-specific prices, volume breaks, and regional lists resolved at order time, on any channel.
Quotes inside the floor execute. Exceptions route to the right approver with the reason attached.
Volume rebates, tiered incentives, and channel deal terms, accrued per order and paid out by rule.
Promotional structures that stack, exclude, and expire by rule, differently per channel.
Overage, tiered overage, pay-as-you-go, prepaid drawdown, and minimum commitment, rated per the declared charge model.
A bid price built from cost, contract, and competitive rules, approved before it goes out.
Route and fulfill
The model decides which ERP records the outcome, by entity, region, or product.
Orders sourced from the right location by rule: availability, cost, and service level.
One order, several parties: warehouse, partner, and service provider, each leg on its own timeline and rules.
Orders handed to third-party logistics with the right terms, then tracked back into the motion.
Quantities allocated per account or program and enforced at order time, not reconciled afterward.
Orders held and released by rule, with the reorder picking up where it stopped.
Change, renew, and pay
The hand-off is governed inside the layer, not integrated between two tools.
Mid-term changes re-price and re-approve without touching the ERP.
Auto-renewal with notice windows and escalation by rule.
Credit split across sales roles, partners, and overlays, calculated on the order’s final outcome.
A quote in the buyer’s currency and language, recorded in the right entity’s ERP.
Billing set by frequency and trigger (sign-up, fulfillment, or activation) per the declared model.
Keep it governed
By deal value, product line, segment, geography, and contract term, routed where each approver works: Slack, email, or a partner portal.
Declared in the model as constraints, not coded as workflows.
Territory, rebate, and conflict rules applied together, so one channel’s win isn’t another’s loss.
Each decision traceable to the rule that governed it.
An AI agent acts inside the same rules as a person, and exceptions route to review.
What each participant sees differs. What executes underneath is identical.
Every capability here runs today, and this isn’t the whole list. How deep each one goes is yours to declare, motion by motion.
Any Participant
The surface changes. The rules don’t.
The rep, the customer, the partner, the CSR, and the AI agent all act on the same model. Context decides what each one sees. The rules stay the same.
One model. Any participant. Any surface.
Start With One Motion
Start with one motion. Keep what already works.
Most teams begin with a new initiative while their current tools keep running. Each motion after that runs on the layer the first one built.
-
First
A new initiative, running in viax.
Pick the motion the business needs next, often one the current stack can’t take on without a project. Prove it in a proof-of-value before any commitment.
-
Next
The next motion starts on the same layer.
Rules, participants, and surfaces from the first motion are already modeled. Each new motion builds on them instead of starting over.
-
Over time
Existing tools hand off when it makes sense.
At a renewal, a migration, or the next change that would have been a project, that part of the work moves into the motion. Nothing is ripped out to get started.