Pricing
Priced on what you run, not on how many people log in.
Three components: a Foundation subscription that every module runs on, a fee for each functional module you switch on, and a one-time implementation fixed to the scope. Seat count is not the driver — the scale and complexity of the programmes is, because that is what actually produces the work.
How pricing works
Three components, in this order
Two run annually, one is paid once. None of them means much on its own, which is why there is no price list on this page.
-
01
Foundation subscription
Required — no module runs without it. It carries the engine, the ledger, the audit trail, access control and the integration layer, and it comes in three tiers. The tier sets your guardrails (users, agreements, transaction volume, storage, endpoints) and how much governance you get: AI policies and segregation of duties from Premium, an isolated private cloud at Sovereign. A number of functional modules is included in the tier.
-
02
Then, per functional module
Each additional module — rebates, ship & debit, trade promotions, contracts, pricing, billing — carries its own annual fee. That fee is revenue-banded: it scales with the revenue flowing through the programmes the module governs, so a lower-market distributor and a multi-billion manufacturer do not pay the same for the same switch.
-
03
One-time implementation
Paid once, at the start, as a fixed budget — not time and materials. The figure is set from the scope: which programmes go live first, how many source systems and feeds have to be mapped, how much history is migrated, and how complex your agreement terms and approval paths are. Agreed before work begins, so the number you approve is the number you pay. How we deliver it →
The result is that a business running one programme starts small and a business running twenty pays in proportion to what it is actually governing — rather than to how many people happen to have a login. Implementation is bounded and paid once; the subscription and module fees are what recur.
Foundation tiers
Three tiers, by how much governance you need
Every tier runs the same engine. What changes is the guardrails, the controls, and where your data lives.
Core
The standard platform, with product guardrails.
- Two functional modules included
- Agreements, vendor and customer rebates on the standard engine
- Automated accrual, settlement, period close and GL reconciliation
- Role-based and attribute-based access control
- Standard integration endpoints and support
- Usage guardrails on users, agreements, transaction volume and storage
Premium
Adds governed AI and the advanced controls.
- Three functional modules included
- Everything in Core, plus:
- Governed AI agents, policies and automated flagging
- Segregation of duties, data masking and access reviews
- Substantially higher guardrails across users, agreements, volume and storage
- Priority SLA and dedicated resourcing
Sovereign
Private cloudYour own isolated cloud.
- Three functional modules included
- Everything in Premium, plus:
- Dedicated single-tenant private cloud with data residency
- No limits beyond the standard product guardrails
- Custom AI policies written to your controls environment
- Dedicated SLA, white-glove onboarding and compliance reviews
Module fees
Banded by the revenue you run through them
The same module costs differently depending on the scale it is governing. Three bands, and we will tell you which one you are in on the first call.
Lower market
A single region or a focused programme portfolio. Enough scale to matter, small enough that one module usually proves the case before the second is switched on.
Mid-market
Multiple programmes across several partners or regions, where the reconciliation work has already outgrown the spreadsheet that used to hold it.
Large market
Multi-billion channel revenue, many programme types running at once, and a close calendar that cannot move. Usually the full platform rather than a module at a time.
Why there is no price list here
A figure for the Foundation tier without the modules, or a module fee without the band, is a number that will be quoted back at us out of context. Tell us which programmes you run and at what scale, and you will get the actual annual figure — both components, in writing, on the first call. No pipeline games, and no obligation to sit through a demo to hear it.
Book a call for pricingDelivery
Fixed budget. Agile delivery. Zero surprises.
We implement on a fixed budget with sprint-based delivery — value shipped in increments, working software early, and no change-order games or scope creep. You get predictable cost, rapid time-to-value, and a partner accountable to the outcome rather than to the hours.
Start with one programme
The one with the most leakage or the most manual effort. Get it live, prove the number, then extend.
The second is configuration
Because everything runs on one configurable engine, programme two is not a new project.
We do not replace your ERP
RevUpra owns the incentive, contract and settlement layer. Transactions come in, settlements go back, the GL stays authoritative.
Commercial FAQ
How buying works
How is RevUpra priced?
Three editions — Core, Premium and Sovereign — sized by the modules you run and the scale you run them at, with implementation on a fixed budget. Pricing is quoted after a scoping conversation because programme complexity, not user count, is what drives effort. See the editions page for what each one includes.
What happens in a demo?
Thirty minutes, tailored to your programmes. We walk an agreement through modelling, contracting, accrual, claim and settlement using examples close to your own, show the integration path from your ERP, and model an indicative ROI against your channel volumes. No obligation.
Can we start with one programme?
Yes, and we usually recommend it. Pick the programme with the most leakage or the most manual effort, get it live, prove the number, then extend. Because everything runs on one configurable engine, the second programme is configuration rather than a new project.
Do you replace our ERP?
No. RevUpra sits alongside the ERP and owns the incentive, contract and settlement layer that ERPs handle poorly. Transactions come in, settlements go back, and the GL stays authoritative.
Get your number.
Pricing follows a scoping conversation because programme complexity, channel depth and data quality are what drive effort — not user count. Thirty minutes usually gets us there.