Configure · Price · Quote · Governed Execution
CPQ is not a category
viax competes in.
It is a motion viax runs.
CPQ logic modeled once, governed, and executed end-to-end — across every channel, every participant, every downstream system. Without a CPQ platform. Without touching ERP.
The Architectural Problem
The CPQ platform solved the
sales rep's problem.
It created an architectural one.
CPQ platforms were built for one participant and one surface — the sales rep in a sales interface. They worked in that context. The problem is what happens when the business grows around them.
Every new channel, every new participant, every new go-to-market model requires the CPQ platform to be extended — or bridged to something else. The result is familiar: CPQ logic that diverges from what the commerce portal shows. Partner pricing running on different rules than direct sales. A pricing change that takes months because the rules are buried in configuration code nobody fully understands, connected to ERP by an integration that breaks when either side changes.
How viax Is Different
Three architectural differences.
Not three more features.
In a CPQ platform, product configuration logic, pricing rules, and approval workflows are buried in platform configuration — often in proprietary scripting, tables, and integration code. Changing them requires platform expertise, release cycles, and testing across connected systems.
In viax, that same logic is declared as an explicit, inspectable model. Pricing rules are visible. Approval thresholds are declared constraints, not hardcoded conditions. Product configurations are governed models — not platform-specific setups. Changing the model is a business operation, not an engineering project.
CPQ was built for the sales rep. The self-service portal was built for the customer. The dealer portal was built for the channel partner. Each has its own rules, its own pricing logic, its own version of what's valid.
When the CPQ motion runs in viax, every participant — sales, customer, CSR, partner, dealer, AI agent — draws from the same governed execution model. The surface changes. The rules do not.
A CPQ implementation typically requires a front-end build: screens designed, workflows mapped, approval flows coded. In viax, the execution model generates the experience — guided selling, approval flows, quote-to-order handoffs — directly from the rules.
No front-end spec. No separate build. The model is the product.
The Full Motion
Configure. Price. Quote & Approve. Order.
Modeled end-to-end — not handed off.
Any configure-price-quote motion a business can describe, viax can model and execute.
- Product and component configuration with constraint enforcement
- Guided selling — valid choices governed by the model
- Fitment, eligibility, and installed-base validation
- Kit and bundle logic with substitution rules
- Account-specific and contract pricing
- Regional tiers, volume breaks, fleet thresholds
- Channel and dealer pricing — all from one governed model
- Rebate and incentive logic attached to the motion
- Quote generation with full governance trail
- Threshold-based approval routing — amount, margin, tier
- Parallel and sequential approval paths as declared constraints
- Amendment and revision handling without ERP involvement
- Order capture and lifecycle state in the execution layer
- Multi-ERP routing — the model determines which ERP records the outcome
- ERP stays system of record; viax owns execution up to that point
- No integration to maintain. No custom code.
viax doesn't replace the ERP program — it de-risks it.
Common Contexts
CPQ complexity does the most damage
in programs that can't afford it.
The Execution Layer
Every layer has an owner.
viax owns the one CPQ was supposed to fill.
CPQ logic embedded in ERP or tightly integrated platforms is exactly the complexity that makes ERP migrations stall, channel conflict persist, and M&A synergies delay.
viax models the configure-price-quote motion end-to-end in a governed execution layer. The ERP receives what it needs to record. The storefront receives what it needs to sell. No CPQ platform required.