Every scorecard on a tool profile is scored against a category rubric — the 5 rubrics below define the critical requirements that decide purchases in each market, with written anchors for what a 0, 1, and 2 mean. Scores cite their evidence; anything we can't verify from public material stays unscored. Rubrics are versioned, anchor changes ship as new versions, and assessments record the version they were scored under — the same governance as our KISS pricing framework.
Updated July 2026 · 36 tools assessed
Scored so far: Amberflo , BillingPlatform , Chargebee , Lago , m3ter , Maxio , Metronome , OpenMeter , Orb , Paddle , Recurly , Stripe , Togai , Zenskar , Zuora
| Requirement | 2 · Strong | 1 · Adequate | 0 · Weak |
|---|---|---|---|
| Real-time balances & drawdown Can a customer (and your product) see an accurate credit or spend balance mid-period? | Live balance API with prepaid credits, drawdown, expiry rules, and hard-cap enforcement at request time. | Balances exist but update on a batch cadence, or credits lack expiry/priority rules. | Balances are derivable only from invoices after the period closes. |
| Correction & re-rating When a meter was wrong, can you fix history without hand-editing invoices? | Event-sourced pipeline: void/backfill events, replay periods, and re-rate under corrected prices with an audit trail. | Manual adjustments and credit notes cover corrections; no true replay. | Corrections require support tickets or database surgery. |
| Commits, credits & custom rate cards Can it express how enterprise AI deals are actually signed? | First-class commitments with drawdown, ramps, true-ups, per-customer rate cards, and overage terms. | Discounts and prepayments approximate commits; rate cards need per-customer plan clones. | Plans are global; negotiated deals live in spreadsheets. |
| Billable-metric flexibility Can finance define a new meter without re-instrumenting the product? | Metrics defined declaratively (SQL or expression language) over raw events; new metrics rate historical data. | Fixed aggregation types (sum/count/max) over pre-shaped events. | Each metric is a code change in the ingestion pipeline. |
| Invoice & proration correctness Do mid-cycle changes, consolidation, and multi-currency come out right? | Proration engine handles amendments/pauses; consolidated and hierarchy-aware invoicing; multi-currency rating. | Standard proration on upgrades/downgrades; consolidation or FX needs workarounds. | Mid-cycle changes produce manual credit notes. |
| Rev-rec & ERP handoff Can the numbers survive an audit once they leave the billing system? | Rev-rec-ready reporting (or native ASC 606) plus maintained GL/ERP connectors with drill-down from journal to event. | Summary exports finance re-shapes for the ERP. | CSV exports only; the ledger mapping is your problem. |
| Ingestion scale & integrity Does the meter stay correct at production event volumes? | Streaming + API ingestion with idempotency keys, dedup, late-event policy, and documented high-volume operation. | API ingestion with idempotency; bulk/streaming paths are limited. | Trust-me ingestion: duplicates and stragglers surface as disputes. |
| Price-change velocity How fast can you ship a pricing change safely? | Versioned catalog, dry-run/simulation against live data, and grandfathering controls — pricing changes ship like code. | Plans are editable with effective dates but testing happens in production. | Pricing changes are migration projects. |
Scored so far: Conga , DealHub , MonetizeNow , Nue , Oracle CPQ , Salesforce , Subskribe
| Requirement | 2 · Strong | 1 · Adequate | 0 · Weak |
|---|---|---|---|
| Configuration & bundling depth Can it enforce what may be sold together, at scale of catalog? | Rules-driven configurator: compatibility, nested bundles, guided selling; invalid quotes are impossible to build. | Product picklists with basic dependency rules. | Free-form line items; validity is the rep's job. |
| Usage & commit quoting Can a rep quote consumption deals — commits, ramps, drawdown — natively? | Commits, ramps, tiered/volume usage rates, and custom rate cards are quotable objects that flow to billing unchanged. | Usage terms quotable as text or custom fields; billing re-keys them. | Seat-and-term only. |
| Approvals & pricing governance Do discount floors and deal policies enforce themselves? | Conditional/parallel approval chains driven by policy rules; exceptions route to deal desk with full context. | Linear approval chains on discount thresholds. | Approvals happen in email. |
| Contract hierarchy & amendments Can it model the paper enterprises actually sign — and change it mid-term? | Parent-child agreements, co-terming, and mid-term amendments as first-class operations with correct downstream proration. | Amendments supported via replacement quotes; hierarchy is manual. | Every change is a new contract. |
| Quote-to-order handoff Does a signed quote become a billable order without re-keying? | Bidirectional CRM sync plus structured order output that provisioning and billing consume directly. | CRM sync is solid; billing handoff is an export. | Closed-won kicks off manual order entry. |
| Documents & close How much friction sits between approved quote and signature? | Branded proposal generation, terms library, and native or deeply integrated e-signature with a tracked buyer flow. | Document generation plus a bolt-on signature integration. | Reps assemble PDFs by hand. |
| Catalog & admin velocity How fast can ops change products, prices, and rules? | Versioned catalog changes by admins with effective dating and sandbox testing; no consultant dependency. | Admin-editable but changes are risky enough to batch quarterly. | Changes require implementation partners. |
Scored so far: ChurnZero , Gainsight , Planhat , Totango , Vitally
| Requirement | 2 · Strong | 1 · Adequate | 0 · Weak |
|---|---|---|---|
| Health-model depth Can health scores blend usage, support, billing, and engagement — per segment? | Configurable multi-signal scorecards with per-segment models and weight transparency. | One global score over a fixed signal set. | Health is a CSM-set traffic light. |
| Playbook automation Do risk and lifecycle events trigger work automatically? | Score and lifecycle triggers fire multi-step plays with tasks, sends, and CRM writeback. | Manual playbooks with reminders. | Process lives in spreadsheets and memory. |
| Product-usage ingestion Does real product telemetry drive the platform, not just CRM fields? | Native event ingestion and/or warehouse sync with adoption analytics at feature grain. | Periodic imports of usage aggregates. | Usage data is whatever the CSM pastes in. |
| Renewal management & forecasting Is the renewal a managed pipeline with risk-adjusted forecasting? | Renewal objects with dates, stages, forecast categories, and risk-adjusted ARR roll-ups. | Renewal dates and reminders on the account record. | Renewals surface when the contract expires. |
| Onboarding & time-to-value Can it run structured onboarding with milestone tracking? | Project templates, customer-visible milestones, and time-to-value measurement feeding health. | Task lists per account without milestone analytics. | Onboarding lives in a separate PM tool with no data flow back. |
| Expansion signal routing Do whitespace and usage signals become qualified expansion pipeline? | Expansion scoring with whitespace analysis routed into CRM as opportunities. | Upsell flags CSMs review manually. | Expansion is discovered at renewal. |
| Voice-of-customer integration Are NPS/CSAT programs native and tied to health and playbooks? | Native surveys with responses feeding health models and triggering recovery plays. | Survey-tool integrations land scores on the account. | Sentiment is anecdotal. |
Scored so far: Leapfin , NetSuite , RightRev , Sage Intacct
| Requirement | 2 · Strong | 1 · Adequate | 0 · Weak |
|---|---|---|---|
| ASC 606 engine Are performance obligations, SSP allocation, and modifications first-class? | Full five-step model: obligation identification, SSP allocation, contract-modification accounting. | Schedule-based recognition covering standard subscription cases. | Recognition is a spreadsheet beside the ledger. |
| Usage & variable consideration Can it recognize consumption revenue at transaction granularity? | Event/transaction-level recognition for usage, credits, and commits with true-up handling. | Monthly usage summaries recognized as billed. | Usage revenue is manually reclassed. |
| Deferred revenue waterfall Is the deferred balance auditable as a roll-forward, not a plug? | Automated schedules with balance roll-forward reporting by contract and period. | Schedules exist; roll-forward assembled at close. | Deferred revenue is a quarterly true-up entry. |
| Multi-entity & multi-book Can it hold entities, currencies, and parallel books (GAAP/IFRS) together? | Multi-entity, multi-currency, multi-book recognition with intercompany awareness. | Multi-currency within a single book and entity. | One entity, one book. |
| Close & journal automation Do recognized numbers land in the GL and the close checklist automatically? | Automated journal creation with period controls integrated into the close workflow. | Journal exports finance posts manually. | Rekeying into the ERP each period. |
| Audit drill-down Can an auditor walk from a journal line back to the source transaction? | Line-level lineage from journal to contract to source event, with SOX-grade controls. | Contract-level support schedules on request. | The trail is tribal knowledge. |
| Source-system connectivity Does billing/CRM/payment data arrive without custom pipelines? | Maintained connectors for the major billing, CRM, and payment sources with reconciliation checks. | File-based imports on a schedule. | Every source is a custom integration project. |
Scored so far: Billtrust , HighRadius , Tesorio , Upflow , Versapay
| Requirement | 2 · Strong | 1 · Adequate | 0 · Weak |
|---|---|---|---|
| Dunning orchestration Are follow-ups sequenced, segmented, and multi-channel? | Segment-aware sequences across email, portal, and phone tasks with governed templates. | Fixed reminder schedule per invoice. | Collectors work from an aging report. |
| Cash application automation What share of payments auto-match without a human? | Remittance capture plus ML matching across formats; exceptions-only workflow. | Rule-based matching on clean references. | Manual matching in the ERP. |
| Collector workflow Do collectors get prioritized worklists with promises and disputes tracked? | Risk-prioritized queues, payment promises with auto-resume, and dispute state on the invoice. | Shared task lists over the aging. | Inbox archaeology. |
| Buyer payment portal Can customers see, dispute, and pay invoices self-serve? | Branded portal with invoice history, structured disputes, and multiple payment rails. | Pay-this-invoice links. | Payment instructions in a PDF footer. |
| AR analytics & cash forecasting Does the platform predict cash, not just report aging? | Payment-behavior models driving collection forecasts and DSO analytics. | Aging and DSO dashboards. | The aging report is the analytics. |
| ERP & bank connectivity Do invoices, payments, and bank data sync both ways without projects? | Maintained bidirectional ERP connectors plus bank/lockbox feeds. | One-way ERP import with manual bank files. | CSV round-trips. |
| Involuntary-churn recovery For card-based revenue, are failed payments recovered automatically? | Smart retries, account-updater services, and grace-period orchestration. | Fixed retry schedule. | Failed cards become churn. |
Each category has a versioned rubric of critical requirements — the capabilities that actually decide purchases in that market. Every requirement has written anchors for 0 (weak), 1 (adequate), and 2 (strong), and every score cites its evidence. 36 tools are assessed across 5 rubrics so far.
It stays unscored and renders as 'Not assessed' — scores are never guessed from marketing copy. The same governance as our KISS pricing framework: evidence-gated anchors, versioned rubrics, and changes shipped as new versions.
No. Assessments are editorially independent, based on public documentation, product behavior, and the usage evidence in UsagePricing's company corpus. Vendors can flag factual errors, which we correct with a dated note.