Billing software does not have one standard pricing model
Two billing platforms may appear to solve a similar problem but charge in completely different ways.
The price may depend on:
- revenue processed;
- usage events received;
- active customers or contracts;
- invoices generated;
- platform features;
- implementation and support;
- completed billing workflows.
1. Percentage of billing volume
Some platforms charge a percentage of the revenue processed through their billing system.
For example, Stripe Billing's pay-as-you-go plan currently charges 0.7% of billing volume, including recurring billing transactions processed both on and off Stripe. Stripe also offers annual subscription tiers for companies that want more predictable costs.
Under a percentage model, cost follows billing volume directly.
Advantages:
- low upfront commitment;
- easy to begin;
- cost follows billing volume;
- suitable for uncertain or early-stage demand.
The software cost rises with revenue even when:
- the number of contracts stays similar;
- the billing workflow does not become more complex;
- the platform performs the same calculation each month.
Percentage pricing can therefore become expensive for companies with high contract values but relatively few billing workflows.
2. Usage-event pricing
Metering platforms may charge according to the number of raw events they process.
An event could represent:
- an API call;
- an AI-token record;
- a transaction;
- a compute action;
- a message;
- a completed workflow.
This model aligns price with the technical load placed on the metering infrastructure. Metronome's current Starter plan includes $100,000 in billing volume and 10 million usage events. Above those allowances, its published rates are 0.8% of additional billing volume and $0.04 per 1,000 additional events.
Advantages:
- appropriate for high-volume real-time metering;
- cost reflects event-processing demand;
- supports granular product analytics and usage visibility.
Event counts can grow much faster than revenue. A product may generate thousands of technical events to calculate one customer invoice. Before choosing event-based pricing, companies should estimate:
- events generated per customer;
- events generated per product action;
- expected growth in activity;
- duplicate and retry events;
- retention and reprocessing requirements.
3. Platform subscription
Some providers charge a fixed monthly or annual platform fee, usually linked to feature tiers or company size.
Tabs currently lists its Launch plan at $2,000 per month for companies with up to $5 million in annual revenue and up to 100 active contracts. Higher tiers use custom pricing, and implementation is priced separately according to the selected plan.
Advantages:
- more predictable than revenue-percentage pricing;
- easier to budget;
- may include several finance functions in one package;
- cost does not change with every invoice.
Limitations include a high starting price for smaller companies, bundled features not all organisations need, additional implementation costs, and the possibility of paying for unused capacity.
A platform subscription makes more sense when the business needs a broad revenue-operations system rather than one specific workflow.
4. Contract- or customer-based pricing
Another model charges according to:
- active contracts;
- active subscriptions;
- billed customers;
- legal entities;
- connected accounts.
This can align well with contract-to-cash platforms because each customer agreement creates operational work. However, companies should clarify how the provider defines an “active” contract. Questions include:
- Is a contract counted every month?
- Are amendments counted separately?
- Are expired agreements included?
- Does one master agreement with several order forms count once or several times?
- Are partner agreements charged in the same way as customer agreements?
5. Workflow-based pricing
Workflow pricing charges when the platform completes a defined business process.
For example:
- one customer billing cycle generated from an agreement and usage data;
- one partner invoice reconciled against its agreement;
- one approved billing schedule sent to an invoicing system.
This differs from charging for every raw event or taking a percentage of the resulting invoice.
Advantages:
- cost is connected to a completed operational outcome;
- high-value contracts do not automatically cost more;
- raw product-event growth does not necessarily increase the fee;
- suitable for periodic agreement-led workflows.
The provider must clearly define what counts as one workflow, including agreement interpretation, usage retrieval, calculation, review and approval, downstream integration, and reprocessing after corrections.
Do not compare price without comparing scope
A lower price does not always mean a lower total cost. Different platforms may include different capabilities.
A full billing platform may cost more because it replaces several existing systems. An agreement-operations platform may cost less because it works with systems the company already has.
The comparison should therefore begin with: which part of the workflow are we paying this platform to own?
Remember the implementation cost
The licence fee is only one part of the total cost. Implementation may require:
- product instrumentation;
- event-pipeline development;
- historic data migration;
- customer and contract migration;
- CRM and ERP integrations;
- testing parallel invoices;
- Finance training;
- ongoing engineering support.
A platform with a low published price may still be costly if it requires a major billing migration. A higher-cost platform may be justified when it removes several internal systems and substantial manual work.
Questions to ask every vendor
Before selecting a pricing model, ask:
- What is the primary chargeable unit?
- Does price increase with revenue, events, contracts or customers?
- What is included in the base fee?
- Are implementation and integrations charged separately?
- Is there a minimum annual commitment?
- Are test, duplicate or failed events billable?
- What happens when usage grows tenfold?
- Can the company retain its existing billing and payment systems?
- How are amendments, recalculations and historical corrections priced?
- Are customer billing and partner reconciliation included?
Where Verdix fits
Verdix is designed around completed agreement workflows rather than taking a percentage of customer revenue or charging for every raw product event.
A workflow can represent:
- a customer billing cycle generated from the agreement and relevant operational data; or
- a partner invoice reconciled against its agreement and supporting activity.
Verdix retrieves only the information required from customer-defined endpoints and sends approved billing instructions to the company's chosen billing or invoicing platform. The existing finance stack remains in place.
The takeaway
Billing-software pricing reflects the architecture and scope of the product.
- Revenue-percentage pricing is easy to start but scales with billing volume.
- Event pricing suits real-time metering but can grow with technical activity.
- Platform subscriptions provide predictability but may have a high entry point.
- Contract pricing follows the number of commercial relationships.
- Workflow pricing connects cost to completed billing or reconciliation work.
The right model is the one that reflects the capability your company actually needs—not simply the amount of revenue it earns or the number of events its product generates.