# Built differently > Pricing, quoting, contracts and incentives became separate software categories because each application carried its own commercial model. Revomo puts the model underneath and composes applications above it. Source: https://revomo.ai/built-differently/ --- Built differently ## Commercial software, rebuilt from first principles for the AI-native era. Commercial software evolved as separate applications, each carrying its own model of customers, products, economics, policies and decisions. **Revomo places shared commercial context and governed decisioning underneath, then composes applications, workflows and agents above it.** 01 · The first principle ### Every commercial system turns context into governed action. Understand what is happening. Model what could happen. Decide what should happen. Execute within policy. Learn from the outcome. Pricing, quoting, planning, contracts and incentives are different manifestations of this same underlying system. - 01 **Context** What is true? - 02 **Understand** What is happening? - 03 **Model** What is likely to happen? - 04 **Objective** What are we trying to improve? - 05 **Policy** What are we allowed to do? - 06 **Decision** What should we do? - 07 **Action** Publish, quote, approve, accrue, settle. - 08 **Outcome** What actually happened? - 09 **Learning** What should change next time? Learning returns to context. The cycle is the system. 02 · The old model ### Many categories. Many copies of the truth. Commercial technology fragmented into analytics, planning, pricing, optimization, quoting, contracts, incentives and portals. Each application carried its own customer and product context, economics, logic, policy, workflow, integrations and audit history. The hardest integration problem was not moving data. It was reconciling what the data meant. Analytics Planning Pricing Optimization Quoting Contracts Incentives Portals 7 × 8 rebuilt layers - Data / context - Business logic - Rules / policy - Workflow - Integrations - Audit - AI context Seven foundational layers, implemented once per application, then reconciled forever. The application on top was rarely the expensive part. 03 · Why now ### AI does not fix fragmentation. It multiplies it. Fragmentation was expensive when humans reconciled it in spreadsheets, and slow enough that someone noticed before a number left the building. It becomes structurally dangerous the moment models and agents can reason and act on their own. Ask three applications what margin a deal earns and you get three numbers, each defensible inside its own system and none named precisely enough to be reconciled with the others. Same commercial event · three unnamed interpretations **Analytics returns “margin”**on a basis it does not state 18.4% **Quoting returns “margin”**on a different one 22.1% **Incentives returns “margin”**on a third 15.7% None of them is wrong. None of them carries a definition a neighbouring system or an agent could check it against, so the three cannot be related, only argued over. One governed semantic model **Gross margin**invoice price less standard cost 18.4% **Quoted margin**after on-invoice discount 22.1% **Pocket margin**after accrued incentives 15.7% All three are real and all three survive. Each is defined once, related to the others through the same waterfall, and available under that name to every application, model and agent. One truth does not mean one metric. It means every metric has one governed meaning. Shared commercial context, semantics, policy, actions and governance are prerequisites for trustworthy agentic decisioning. Figures are illustrative, on the worked example used across this site. 04 · The commercial spine ### Model it once. Planning Pricing Optimization Quoting Contracts Incentives Portals ONE COMMERCIAL SPINE One governed model of the commercial world, shared across the platform. Applications do not each recreate commercial context. They operate on the same governed foundation. **Customer** Who you sell to, at every level of the hierarchy. **Product** What you sell, and how it rolls up. **Cost** Standard, landed and actual, as of a date. **Transaction** What was actually invoiced. **Price** Every price that applies, and why it applies. **Term** What was agreed, and for how long. **Commitment** What is owed as a result. **Decision** What was chosen, by whom, against which policy. These are the shared objects every commercial application needs, not the whole of the Revomo model. 05 · The horizontal platform ### Everything a modern platform should give you. These capabilities make Revomo a complete modern analytical and application platform. The differentiation begins when that platform becomes commercial-native. #### Data & Analytics - Sources - Models - Relationships - Metrics - Calculations - Queries - Tables - Charts - Writeback - Scenarios #### Application & Experience - Pages - Grids - Forms - Inputs - State - Functions - Events - Actions - Documents - Portals #### Workflow & Automation - Rules - Workflow - Approvals - Notifications - APIs - Integrations - Jobs - Events #### AI & Agents - Models - Tools - Actions - Context - Agent workflows - Human-in-the-loop #### Governance - Identity - Permissions - Policy - Audit - Versions - Lineage - Effective periods 06 · Commercial semantics ### And then it knows what a price is. A horizontal platform gives you the machinery. You still have to encode what prices, commitments, rebates, corridors and commercial decisions mean. Revomo begins with this commercial language and logic already available. #### A horizontal platform provides Table Chart Form Query Function State Rule Workflow API Agent #### Commercial language · Commercial context Customer Product Cost Transaction #### Commercial language · Pricing and economics Price Price List Waterfall Price Component Adjustment Guidance Corridor Rule Precedence #### Commercial language · Intelligence and decisioning Metric Assumption Scenario Forecast Prediction Objective Constraint Recommendation Decision #### Commercial language · Commercial execution Quote Agreement Term Commitment Rebate Incentive Eligibility Accrual Claim Chargeback Approval Exception 07 · The decision and execution system ### From commercial context to governed action. The Commercial Spine defines what the business knows. Revomo uses that shared context to understand, model, decide, govern, execute and learn. That is what makes the phrase Commercial Decision & Execution Platform concrete. **Humans** Pricing, sales, finance and operations, in the applications they already use. **Applications** Composed experiences reading and writing the same governed context. **Agents** Bound by the same policy, acting through the same governed actions. Peers at the experience layer. All three operate through the system below. - 06 **Outcomes and learning** What happened, and what should improve Realized price · Won and lost · Claims settled · Behaviour - 05 **Workflow and execution** What the business does Publish · Quote · Approve · Activate · Accrue · Settle - 04 **Policy and constraints** What the business may do Corridors · Precedence · Authority · Commitments · Exceptions - 03 **Objectives and decisions** What the business should do Objectives · Constraints · Optimization · Recommendations - 02 **Intelligence and models** What the business understands and predicts Metrics · Scenarios · Forecasts · Elasticity · Win probability - 01 **Commercial Spine** What the business knows Customer · Product · Cost · Transaction · Price · Term · Commitment · Decision Read from the base upward: the spine is 01. Decisioning is not the whole product. Revomo also holds analytical, transactional, workflow and experience systems. This is the operating cycle that connects them. 08 · Composition ### Applications, composed. Revomo applications combine shared commercial primitives, commercial capabilities, platform services and governed actions. They are not separately engineered products that merely share a login, and today's applications are not the architectural ceiling. Select an application to see what composes it, or select a primitive to see what it could compose into. Clear selection Primitives Commercial context Customer Product Cost Transaction Pricing and economics Price Price List Waterfall Price Component Adjustment Guidance Corridor Rule Precedence Intelligence and decisioning Metric Assumption Scenario Forecast Prediction Objective Constraint Recommendation Decision Commercial execution Quote Agreement Term Commitment Rebate Incentive Eligibility Accrual Claim Chargeback Approval Exception Platform services Model Feature Version Workflow Effective period Identity Document Portal Commercial capabilities Margin analysis Price realization Opportunity detection What-if analysis Driver-based planning Scenario modelling Forecasting Variance analysis Feature preparation Training and scoring Elasticity and win probability Model monitoring Objective modelling Constraint management Optimization Recommendation explainability Price governance Mass repricing Publishing Exception management Deal guidance Customer-specific pricing Exception control Approval orchestration Agreement administration Term governance Contracted pricing Compliance and renewal Program administration Eligibility Accrual calculation Claim adjudication Settlement Review queue Guidance override Margin impact Approval routing Partner price access Claim submission Agreement visibility Contracted price lookup Quote request Document access Commitment tracking Term adherence Leakage detection Promotion design Eligibility rules Uplift measurement Funding control Tiered programs Partner accruals Performance measurement Cost change capture Recovery claims Pass-through tracking Cross-functional planning Assumption management Consolidated targets Applications Margin Intelligence Planning & Forecasting Predictive Modeling Decision Optimization Price Management Quote Management Contract Management Incentives Management What composes next Deal Desk Distributor Portal Customer Pricing Portal Contract Compliance Promotion Management Channel Incentives Supplier Cost Recovery Commercial Planning Workspace Illustrative compositions of the same primitives, shown to make the point that the shipped set is not the ceiling. Not available products. Margin Intelligence Planning & Forecasting Predictive Modeling Decision Optimization Price Management Quote Management Contract Management Incentives Management Deal Desk Distributor Portal Customer Pricing Portal Contract Compliance Promotion Management Channel Incentives Supplier Cost Recovery Commercial Planning Workspace Primitives ↓ Commercial capabilities ↓ Application An illustrative composition, not an available product. 09 · AI-native by design ### Agents need somewhere to stand. AI is not a chatbot attached to each application. Humans, applications, workflows, models and agents participate in the same commercial system. They read the same definitions, operate through the same governed models, policies and actions, and leave the same audit history. 01 READS **The same context** - Customer - Product - Cost - Agreement - Prior prices - Guidance 02 INVOKES **The same models and policy** - Predictive model - Optimization - Rule - Corridor - Precedence 03 ACTS **Through the same actions** - Recommendation - Price change - Quote - Approval 04 LEAVES **The same evidence** - Audit history - Transaction - Lineage - Learning loop **Agents do not get a privileged path around commercial policy.** They act through the same governed models, policies and actions as everyone else. There can be more than one valid route to a decision; what is not optional is that every route reads the same commercial meaning and respects the same authority. 10 · One continuous loop ### Understand. Plan. Decide. Execute. Govern. Learn. Most commercial software stops at the recommendation, because the system that recommends and the system that executes are different products. Here execution writes back to the same model the analysis reads. Governance is not a stage that follows execution. It bounds what may be decided and done, and audits what happened. **Understand** Where margin actually goes. **Plan** Targets and scenarios against drivers. **Decide** Guidance, optimization, recommendation. **Execute** Prices published, quotes sent, claims settled. **Learn** Outcomes become the next input. Governance spans deciding and doing. Policy and authority constrain what can be recommended, approved and executed; audit records what actually was. 11 · Start anywhere ### Start with one. Add the next without starting over. Solve one valuable problem first. As you expand, the next application reuses the commercial context, permissions, integrations, policies, workflows, AI context and audit model already established instead of rebuilding that foundation. **Margin Intelligence** **Price Management** **Decision Optimization** **Quote Management** **Incentives Management** One possible path, not a required sequence. Start where the money is. - One commercial context - One identity and permission model - One policy framework - One workflow model - One AI context - One integration fabric - One audit history - One application framework **Faster time to value** The foundation is already there for the second application. **Less repeated integration** One integration fabric, not one per application. **Less duplicated logic** Commercial meaning is defined once and reused. **Consistent policy** The same corridors and authority wherever a decision is made. **Better collaboration** Finance, sales and pricing work from the same numbers. **Continuous feedback** Outcomes return as evidence for the next decision. **Lower cost per use case** Each addition reuses context, permissions and workflow. **Greater adaptability** The model changes when the business does. ### See it on your own commercial data. Bring one problem. We will show you the model underneath it, and what composes next. [See Revomo in action](https://revomo.ai/contact/)[Explore the platform](https://revomo.ai/platform/)