Nue
Usage-based and subscription CPQ with native billing, invoicing, and revenue recognition. Built for consumption pricing models (metered, tiered, hybrid) that Salesforce CPQ cannot handle cleanly. Sits outside Salesforce but syncs quotes, orders, and invoices back via API. The default choice when you need usage-based billing, automated invoicing, and do not want to stitch together CPQ, billing, and metering tools.
Why it ranks here
- Native usage-based pricing engine with tiered, volume, and hybrid models; Salesforce CPQ and Revenue Cloud require external metering or custom Apex.
- Automated invoicing and revenue recognition in one platform; eliminates the NetSuite or Stripe Billing middleware layer.
- API-first architecture makes it the cleanest replacement for teams migrating off Salesforce CPQ to consumption pricing without rebuilding their entire quote-to-cash stack.
Where it sits
- Salesforce Revenue Cloud is native to Salesforce but requires external metering and does not handle consumption billing as cleanly.
- Zuora and Chargebee offer similar billing automation but have weaker CPQ features and require more custom code for complex product catalogs.
- Stripe Billing is simpler and cheaper for pure consumption pricing but lacks the enterprise-grade quoting, approvals, and contract amendment features Nue provides.
How GTM Systems teams use it
- Deal desk configures product bundles, usage tiers, and pricing rules in Nue; sales reps generate quotes that flow back to Salesforce opportunities.
- Finance teams automate monthly invoicing for metered usage (API calls, seats, storage) and subscription components, then sync invoices to NetSuite or Stripe.
- RevOps architects build Nue-to-Salesforce sync flows (quotes, orders, invoices) via Workato or native API, monitor billing cycle time, and audit usage metering accuracy.
- Engineering teams integrate internal metering systems (DataDog, Prometheus, custom APIs) into Nue for real-time usage tracking and invoice generation.
In-depth notes
- Pricing combines annual platform fee with percentage of billed revenue; mid-market teams typically face low-five-figure base plus sub-1% revenue share.
- Nue requires Salesforce API integration for opportunity sync; teams must build and maintain the middleware or use a paid iPaaS connector.
- The product catalog lives in Nue, not Salesforce; this means product data exists in two systems and requires governance to keep in sync.
- Contract amendments and renewals are API-driven; teams must build automation to handle mid-term changes without manual re-quoting.
- Usage metering is external; Nue ingests usage data but does not collect it, so teams must integrate metering tools (Stripe Billing, Metronome, Amberflo) or build custom APIs.
Best for
B2B SaaS teams with consumption-based pricing (usage, tiered, hybrid) that need automated billing and want to replace Salesforce CPQ without rebuilding their entire quote-to-cash stack.
Avoid if
Your pricing is purely subscription-based with no usage components, you need a native Salesforce solution, or you do not have engineering resources to maintain API integrations.
The rest of CPQ & billing
Learning guide
Setup
Build product catalog with usage tiers, subscription bases, and hybrid bundles in Nue. Connect metering sources via API and configure Salesforce opportunity sync.
First thing to build
Quote a hybrid subscription (base seats plus usage overages) with tiered pricing, sync the order to Salesforce, ingest usage events, and generate the first automated invoice.
What actually matters
- Usage-based pricing models (tiered, volume, hybrid) and metering API integration
- Product catalog governance between Nue and Salesforce
- Automated invoicing schedules and billing cycle configuration
- Salesforce sync flows for quotes, orders, and invoices via API or iPaaS
Watch out
The product catalog lives outside Salesforce; teams that skip catalog governance end up with drift between systems and manual reconciliation work.