Pricing
Priced to your revenue, not your seat count
Every plan includes the AI agents. You move up a tier when your revenue does.
Choose a plan
Tiers are banded on annual revenue and active contract count.
What is included
The core platform is identical on every plan. Volume and complexity change.
| Feature | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Billing & collections | ||||
| Billing and invoicing | ✓ | ✓ | ✓ | ✓ |
| Automated billing & invoicing | ✓ | ✓ | ✓ | ✓ |
| Payment gateway integration | ✓ | ✓ | ✓ | ✓ |
| Contract processing | – | ✓ | ✓ | ✓ |
| Collections & cash application | – | ✓ | ✓ | ✓ |
| Complex usage billing | – | ✓ | ✓ | ✓ |
| Revenue & reporting | ||||
| Reporting | ✓ | ✓ | ✓ | ✓ |
| ASC 606 RevRec | – | ✓ | ✓ | ✓ |
| Advanced RevRec for complex usage | – | ✓ | ✓ | ✓ |
| Predictive analytics | ||||
| Expansion opportunity identification | – | – | ✓ | ✓ |
| Downgrade risk detection | – | – | ✓ | ✓ |
| Churn risk scoring | – | – | ✓ | ✓ |
| Cash flow forecasting | – | – | ✓ | ✓ |
| Collection forecasting | – | – | ✓ | ✓ |
| Renewal forecasting | – | – | ✓ | ✓ |
| Payment integrations | ||||
| Stripe | ✓ | ✓ | ✓ | ✓ |
| PayPal | – | ✓ | ✓ | ✓ |
| Bill.com | – | ✓ | ✓ | ✓ |
| CRM integrations | ||||
| Salesforce | – | ✓ | ✓ | ✓ |
| HubSpot | – | ✓ | ✓ | ✓ |
| Accounting integrations | ||||
| QuickBooks Online | ✓ | ✓ | ✓ | ✓ |
| Intuit Enterprise Suite | – | ✓ | ✓ | ✓ |
| Rillet | – | ✓ | ✓ | ✓ |
| NetSuite | – | with limitations | ✓ | ✓ |
| Sage Intacct | – | – | ✓ | ✓ |
| Custom integrations | – | – | ✓ | ✓ |
Optional add-ons
Custom reporting
Available on any plan
Multi-entity support
Growth tier and above
Custom workflows
Growth tier and above
AI agents that work like an extension of your finance team
Built into the platform, working around the clock on billing, collections, and cash.
Contract agent
Reads each contract and extracts every obligation with a citation.
Invoice agent
Composes each invoice from the graph and holds it for your approval.
Collections agent
Chases overdue invoices and escalates only what needs a human.
Revenue agent
Builds ASC 606 schedules and the journal entries behind them.
Questions
The total you invoice through Verlix over a rolling twelve months. Credit notes come off that total, so a corrected invoice never counts twice. Internal and test invoices are excluded, and so is anything you void before it sends. We recalculate on the first of each month and show the figure on your account page, so you can check it against your own books whenever you want.
We flag it on your account the day the rolling total crosses, and the new rate applies from your next billing period. It is never retroactive and it never lands mid-close. The notice carries the figure that triggered it, so you can check the arithmetic before it takes effect. If the crossing was a one-off, tell us and we hold the old rate for another period.
No. Pricing follows billed revenue and contract volume, not event count, so metering more of your product never raises the bill. Send 4 million events a month or 40 million and the price is the same. This is deliberate. A meter that costs you money is a meter you will under-use, and every invoice built on a thin meter is wrong. Ingest everything and rate it properly.
No. Your ledger stays where it is. Verlix syncs both ways with NetSuite, QuickBooks and Sage, posting journal entries into your system and reconciling against what is already there. Nobody re-keys a line and there is no cutover weekend. If you move systems later, the schedules and the audit trail come with you, because they live on the contract rather than in the ledger.
It is a real plan, not a countdown. Bill under $1M a year and you can stay on it as long as you like, with no card required and nothing switched off to push you into upgrading. You get the full contract graph, the invoicing engine and the revenue schedules. Your data stays yours: export it whenever you want, in a format your accountant can open.
Roles are set per person and per entity, so someone who works one subsidiary sees that subsidiary and not the rest. Growth adds approval limits, which means an invoice over a threshold you set needs a named approver before it sends. Every view and every change is logged with the person and the timestamp, so an auditor asking who approved something gets an answer.