Configure · Quote
Custom configuration with approval gates
Valid combinations, regional pricing, and approval thresholds, governed from first choice to signed quote.
Revenue Motions
Each tool was built for a step.
viax runs the whole motion.
Describe any revenue motion your business runs, and viax models it, governs it, and runs it from intent to cash, outside ERP.
The Revenue Motion
A revenue motion is the full path from intent to cash.
Who’s involved, what’s allowed, and what happens next, across quoting, ordering, fulfilling, renewing, and settling. Most businesses run their motions across several tools, each built for its own part. viax models the motion itself, so the whole path runs in one model.
-
Modeled around how the business operates.
Direct, partner, dealer, self-service, subscription, marketplace: any motion you can describe. The model fits the business, not a predefined template.
-
Pricing, approvals, eligibility, contracts, fulfillment, renewals.
Each one is an explicit rule in the model, not a code path. The model defines what is allowed.
-
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 sentence to a running motion.
Describe, Clarify, Plan, Build. You say what the business needs in plain language, viax models it, and you approve it before it goes live.
-
01 Describe
Say what the business needs.
A new pricing model, a dealer program, an approval path, in plain language and from any source. No ticket and no spec document.
“Build a product configuration model for our heavy equipment dealer network. Regional pricing tiers, fleet approval workflows over $250k, guided selling.”
-
02 Clarify
viax asks what the description left open.
Thresholds, exceptions, who approves what, and what happens when a rule doesn’t apply. The gaps get answered before anything is built.
-
03 Plan
See the model before it exists.
The interactions, rules, constraints, and participants the motion needs, laid out for review.
-
04 Build
Governed, approved, and running.
viax builds the governed model and the surfaces people act on it through. Nothing goes live until you approve it.
Execution defines what happens. Systems and interfaces define where it happens.
In Practice
Named for what the business does.
Each motion is described in the business’s own terms, modeled once, and run on any channel.
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.
Multi-entity
Multi-ERP order routing
One order, routed by the model to the ERP that records it, by entity, region, or product.
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.
Subscription
Auto-renewal with notice window
Renewals that run on contract terms, with notice periods and escalation by rule.
Contract
Mid-term contract amendment
Mid-term changes re-priced and re-approved inside the motion, outside ERP release cycles.
Channel · Incentive
Volume rebate accrual and payout
Rebates and incentives accrued per order and paid out by rule, without spreadsheet reconciliation.
These are examples. Any motion your business can describe can be modeled.
See what’s inside a motion ↓Inside a Motion
What a motion actually takes.
A checklist can say yes to approvals. A motion has to say how: by deal value, product line, segment, geography, and contract term, routed to wherever each approver works.
Sell complex things
Product configuration
Valid combinations governed by constraints, compatibility, and fitment, not a pick list. Each choice narrows the next.
Custom configuration with approval gatesBundled solution quoting
Guided selling
The valid choices at each step come from the model, so a dealer, a CSR, and an AI agent are offered the same options.
Kits, bundles, substitution
Bundles with substitution rules that still hold when a component is unavailable.
Bundled solution quotingSpare parts ordering with entitlement check
Show 3 more
Fitment and eligibility
Checked against serial number, installed base, and warranty state before an order is accepted.
Spare parts ordering with entitlement check
Entitlement
What an asset is covered for, resolved in the moment from warranty, contract, and service-level terms.
Spare parts ordering with entitlement checkService contract renewal with escalation
Service requests
Services handled as orders: requested, scoped, priced, scheduled, and billed in the same motion as products.
Price and promote
Contract and account pricing
Customer-specific prices, volume breaks, and regional lists resolved at order time, on any channel.
Margin floors
Quotes inside the floor execute. Exceptions route to the right approver with the reason attached.
Custom configuration with approval gatesQuote approval above margin floor
Rebates and incentives
Volume rebates, tiered incentives, and channel deal terms, accrued per order and paid out by rule.
Show 3 more
Promotions
Promotional structures that stack, exclude, and expire by rule, differently per channel.
Usage and consumption rating
Overage, tiered overage, pay-as-you-go, prepaid drawdown, and minimum commitment, rated per the declared charge model.
Usage-based billing and true-upConsumption commitment drawdown
Tender and bid pricing
A bid price built from cost, contract, and competitive rules, approved before it goes out.
Tender and bid pricing
Route and fulfill
Multi-ERP routing
The model decides which ERP records the outcome, by entity, region, or product.
Sourcing and DC routing
Orders sourced from the right location by rule: availability, cost, and service level.
Multi-party fulfillment
One order, several parties: warehouse, partner, and service provider, each leg on its own timeline and rules.
Partner-sourced deal fulfillment
Show 3 more
3PL hand-offs
Orders handed to third-party logistics with the right terms, then tracked back into the motion.
Allotments
Quantities allocated per account or program and enforced at order time, not reconciled afterward.
Credit holds
Orders held and released by rule, with the reorder picking up where it stopped.
Credit hold release and reorder
Change, renew, and pay
Quote-to-order
The hand-off is governed inside the layer, not integrated between two tools.
Amendments
Mid-term changes re-price and re-approve without touching the ERP.
Renewals
Auto-renewal with notice windows and escalation by rule.
Auto-renewal with notice windowService contract renewal with escalation
Show 3 more
Commissions
Credit split across sales roles, partners, and overlays, calculated on the order’s final outcome.
Currency, language, entity
A quote in the buyer’s currency and language, recorded in the right entity’s ERP.
Billing frequency and context
Billing set by frequency and trigger (sign-up, fulfillment, or activation) per the declared model.
Keep it governed
Approval routing
By deal value, product line, segment, geography, and contract term, routed where each approver works: Slack, email, or a partner portal.
Custom configuration with approval gatesQuote approval above margin floor
Parallel and sequential approvals
Declared in the model as constraints, not coded as workflows.
Channel conflict and territory
Territory, rebate, and conflict rules applied together, so one channel’s win isn’t another’s loss.
Show 3 more
Audit trail
Each decision traceable to the rule that governed it.
Agent actions
An AI agent acts inside the same rules as a person, and exceptions route to review.
Role-based views
What each participant sees differs. What executes underneath is identical.
These are examples. Any depth your business runs can be declared in the model.
See how a motion gets built ↑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.
Sales
Quotes from the same model as every other channel.
Customer
Self-service pricing that matches what a rep would quote.
CSR
The full state of the motion, with nothing to reconcile.
Partner · Dealer
Channel rules in the same model as direct. Changes apply at once.
Service
Fulfillment as an outcome of the motion, governed by the same rules.
AI agent
Acts inside the same rules as the people in the motion.
What each participant sees is resolved from context, not from separate systems.
- Participant
- Geography
- Agreement
- Product
- Segment
- Surface
- Time
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.