Continuous

Competitive Battlecard · Internal & Partner Enablement

Continuous vs. Nue

Nue quotes natively in Salesforce, then bills and rates usage in its own cloud and pushes standard Sales Orders plus standalone invoices into NetSuite, handing ASC 606 to NetSuite ARM. Continuous lands the whole deal graph in NetSuite and recognizes revenue where the general ledger lives. Same RCA tent, opposite answers to one question: where should billing and revenue actually live?

Why this matters now

Nue is inside the RCA tent, and a threat to the whole Revenue Cloud stack

January 2025: $20M Series A.Led by Inovia Capital, roughly $40M raised to date. The founders come straight from Zuora, Salesforce CPQ, and Oracle CPQ.
Positioned as the replacement for Salesforce CPQ and Zuora.Their CEO calls Nue "the go-to alternative to Salesforce CPQ and Zuora." A Nue deal can displace Salesforce's own Revenue Cloud, so the Salesforce account team should want us in the room, not Nue.
January 2025 NetSuite push."Nue Enhances NetSuite Integration to Deliver RevOps Agility and Finance Rigor." Expect Nue pre-positioned as the modern quote-to-cash layer on NetSuite. The qualification battle is won on architecture, not features.

"A dual-platform system... fully native to Salesforce, and cloud-extended via AWS that powers self-service transactions, billing... and high-performance reporting."

nue.io/platform · the qualifier that reveals the off-platform billing engine

"Keep NetSuite as the trusted system of record... NetSuite remains the single source of truth for Finance."

nue.io/solutions/nue-for-netsuite · vendor claim

Know the competitor

Nue in five facts

A quote-to-revenue platform that quotes natively on Salesforce but bills and recognizes off it.

Category · verifiedQuote-to-revenue platformCPQ, billing, usage rating, and revenue analytics in one system. "One platform. Three layers." Pitched as the alternative to Salesforce CPQ and Zuora.

Delivery model · verifiedDual platform, not on-platformCPQ and Lifecycle Manager ship as a native Salesforce managed package (LWC, standard objects). Billing, usage rating, and revenue run in Nue's own AWS cloud.

NetSuite path · verifiedConnector sync into NetSuiteOrders flow in as standard Sales Orders. Invoices, credit memos, and payments post as native NetSuite documents, mapped to NetSuite ARM for 606.

Rev rec engine · verifiedThey do not have oneNue defers ASC 606 to NetSuite ARM, or to RightRev. Their revenue story is only as good as what ARM can consume.

Lifecycle · vendor claim"The minute you quote, you can bill"Swaps, upgrades, downgrades "without cancel-and-rebooks," mid-cycle proration, co-terms, ramp deals, all inside the Nue cloud.

Read the labels"Verified" = confirmed from Nue's own pages and press. "Vendor claim" = quoted from nue.io, not independently validated. The NetSuite sync mechanism (third parties list Tray) is unconfirmed, so we do not assert it.

Sources: nue.io (platform, how-nue-works, NetSuite solution, CPQ-native article), Series A press (Jan 2025), SiliconANGLE.

Market map

The question underneath every deal: where do billing and revenue actually live?

Camp 1

In the ERP, native

NetSuite SuiteBilling + ARM · Sage Intacct

Billing and revenue sit next to the GL, but the native tooling is rigid for modern subscriptions.

Camp 2

Standalone platform

Zuora · Maxio · Chargebee

A separate billing and revenue system off both the CRM and the ERP. Powerful, and a third system to reconcile.

Camp 3 · Nue

In the CRM plus a cloud

Nue

Quote in Salesforce, bill and rate in Nue's cloud, push documents to NetSuite, hand 606 to ARM. Two billing systems.

Camp 4 · Continuous

Unified books

Continuous

Salesforce runs the deal. The order graph lands in NetSuite as first-class records. Billing and revenue are one system of record where the GL lives.

The strategic point

Continuous is not a billing-feature competitor, it is an architecture competitor. Nue asks the CFO to run billing and revenue in a second cloud and reconcile it to NetSuite every close. We make NetSuite the single system of record and reconcile nothing.

Architecture head-to-head

Two flows of the same deal

Nue · billing runs in a second cloud

Salesforce

Nue CPQ, native

Quote · Order

Nue managed packagenative LWC quoting

→

Nue Cloud

Where the logic lives

Billing · usage ratingsubscription state, proration

Lifecycle engineswaps, downsells, ramps

→

NetSuite

Receives documents

Standard Sales Orders

Standalone invoicesARM tries to recognize

Billing logic lives in Nue's cloud. Every close reconciles that cloud against the NetSuite GL.

Continuous · billing and revenue at the GL

Salesforce

Owns the customer

RCA Orders · Amendments

Billing schedules · Invoices

→

NetSuite

Owns A/R, billing, revenue, books

Contract → Orders → Lines → POBsfull mirrored order graph

Native invoices · Obligation DetailsBooked / Billed / Recognized

Period JEs, drillable from the trial balance

The deal graph is transformed into native NetSuite records, not transported as summaries. One books model.

The core wedge

Nue’s lifecycle sophistication dies at the ERP boundary

Nue can model swaps, downsells, and ramps in its cloud. The moment they hand off to NetSuite as standard Sales Orders and standalone invoices, they hit primitives that cannot represent them.

Downsell / contractionNo negative Sales OrdersA NetSuite document total cannot go negative. A mid-term contraction cannot post as-is.

Multi-year rampNo obligation groupingNo native record groups ramp lines into one obligation, and standard billing cannot spread revenue evenly across the ramp.

Amendment lifecycleFrozen billing templatesNative billing schedules are unmodifiable reusable templates, with no renewal or amendment automation.

The tie-out killerARM Billed stays $0Native ARM only credits an element's Billed when the invoice is transformed FROM the Sales Order. Nue posts standalone invoices, so Billed reads $0 and Booked, Billed, Recognized never tie out.

What the customer inherits

A second billing system of record in Nue's cloud, and a monthly hand reconciliation between that cloud and the NetSuite general ledger. The sophistication was real, it just could not survive the handoff.

Use cases · subscription lifecycle into NetSuite

Does it land in NetSuite as tied-out native records?

Lifecycle event, as native NetSuite records	Continuous engine	Native ARM bridge	Nue into NetSuite
Multi-year ramp as one obligation	✓Liveramp segments collapse into one POB, one plan spans the ramp	◑Element per segment	◑Many SO lines, no grouping
Even-spread revenue over ramp term	✓LiveEven Spread flag, flat per month instead of stepped	✗No native counterpart	✗No native counterpart
Mid-term downsell / contraction	✓Livecredit memo + sign-aware ODs, day-weighted, prospective re-spread	◑Via negative delta line	✗No negative Sales Order
Swap in / swap out	◑Via amendment linesclassified from SF OrderAction	◑Element windows	✗Cancel-and-rebook in NS
Amendment, prospective (Type 2)	✓Liveposted periods freeze, remainder re-spreads, no restatement	✓Prospective merge	◑Only if SO lineage survives
Usage / consumption recognized as billed	✓Liveusage POBs recognize from Obligation Details	◑Billing-driven plans	◑Standalone invoice tie-out gap
% complete / delivery / fulfillment	✓Live% complete field, delivery and fulfillment anchoring	◑Project / event rules	◑Depends on ARM config
Booked / Billed / Recognized tie-out in NetSuite	✓Liverolled to POB and Contract, drillable	✓Native	✗Standalone invoices leave Billed at $0

✓ Lands tied-out ◑ Partial / conditional ✗ Does not survive the handoff Nue column measures what arrives in NetSuite as tied-out native records, not what Nue does inside its own cloud.

Where we win

Lead with the books and who owns them

One billing and revenue system of record.Invoices, Obligation Details, deferred balances, and period JEs are native NetSuite records. There is no second cloud to reconcile every close.
Your NetSuite admins own it.Continuous is a Built-for-NetSuite SuiteApp running inside NetSuite. Nue's billing engine is an off-platform vendor cloud your admins cannot open, tune, or audit.
Transformed, not transported.A downsell becomes a credit memo, a ramp becomes one POB with even-spread, so the deal posts and ties out. Nue hands NetSuite primitives that cannot hold the event.
No new system of audit.The auditor drills JE to POB to invoice line to SF order, all in NetSuite. Nue adds a cloud that becomes a second source of truth and a new place to audit.
We are an RCA ally.Every Continuous deal is an RCA deal. Nue displaces Salesforce's own Revenue Cloud and CPQ.

Proof point · the JE itself

+Line memo: "QB-API-MGMT · Jan 2026 · Straight-Line, month 1 of 36". Method, period, and position on every line. Evidence, not an import.

Proof point · the escape hatch

+Each POB is 1:1 with a native ARM Revenue Element. When revenue gets complex, the customer graduates to ARM without a rebuild.

Proof point · resilience

+Every record is idempotent on external IDs. Re-sync is safe and self-healing, and the result is queryable ERP truth.

The honest read

Where Nue is genuinely ahead

Front-end breadth · verified

−Nue is a full quote-to-cash front end: CPQ, catalog, billing, and usage rating in one platform. Continuous is not a CPQ or billing front end. It rides on Salesforce RCA and RCB.

Native quoting UX

−Genuinely native Salesforce quoting, LWC not iframe, "configuration not code," with fast deployment claims.

Usage rating maturity

−A mature usage and consumption catalog inside their own engine.

Funding and logos

−$20M Series A, named customers including OpenAI, Mews, and Procurify.

When we lose

The customer wants to replace Salesforce CPQ or Zuora with one modern quote-to-billing platform and does not care where the books live.

The counter

That is a Revenue Cloud displacement, so the Salesforce account team should be fighting it too. And even then, the revenue still has to land in NetSuite and tie out, which is exactly where Nue's handoff breaks.

The two questions that reframe any deal

Do you want one billing system of record or two? And what does reconciling Nue's cloud to the NetSuite GL cost you every month?

Objection handling

Landmines they’ll throw, and the counters

They say	We say
"Nue is native to Salesforce."	True for quoting. Billing, usage rating, and revenue run in Nue's AWS cloud, and the NetSuite side is a connector pushing standard Sales Orders. Native where you sell is not native where the books live.
"We map cleanly into NetSuite ARM for ASC 606."	Into standard Sales Orders and standalone invoices. Ask their SE to show a mid-term downsell and a three-year ramp tying out, Booked equals Billed equals Recognized, inside ARM. Standalone invoices leave element Billed at $0, and NetSuite will not accept a negative Sales Order.
"NetSuite is your single source of truth for Finance."	Only for the documents that arrive. The billing logic, usage rating, and subscription state live in Nue's cloud. That is a second billing system of record your controller reconciles every month.
"No brittle connectors."	The NetSuite integration is still a sync between two platforms, Nue's cloud and NetSuite. Continuous is one application running inside NetSuite. There is nothing to reconcile.
"We do the lifecycle events NetSuite can't."	In your cloud, yes. The problem is the handoff. Those same events have to become native NetSuite records to hit the GL, and standard Sales Orders cannot represent them. We transform them so they post and tie out.

Never disparage the Revenue Cloud platform itself. We are an RCA ally. The contrast is strictly about where billing and revenue belong.

Qualify the deal

One books, or a platform plus a cloud?

The shape of the choice

Continuous keeps the customer on Salesforce RCA and NetSuite, with no third cloud. Nue adds a platform and a billing cloud that becomes a second source of truth. The whole deal turns on whether finance wants one system of record or is willing to reconcile two.

Qualifying question 1One billing and revenue system of record, or billing in a second cloud you reconcile to NetSuite? If they want one, that is our ground.

Qualifying question 2Keeping Salesforce Revenue Cloud, or replacing it with Nue? If replacing, this is a platform fight the Salesforce account team should join.

If Nue is already inContinuous can still be the NetSuite books layer if revenue is recognized in NetSuite, but name the cost: two billing systems and a monthly reconciliation remain.

Where we plant the flagFinance wants revenue recognized and tied out in NetSuite, with the auditor working from the trial balance. That is the Continuous deal.

Co-sell implications

Run the play on architecture, and bring the Salesforce team with you

1 · Qualify on architectureOne books versus twoDo not fight on quoting features. Fight on where billing and revenue live and what the reconciliation costs.

2 · Arm the Salesforce teamNue shrinks Revenue CloudNue displaces their CPQ and RCA. Continuous grows the RCA footprint. That makes the account team an ally.

3 · Lead with the live rowsEven-spread, downsell, rampThese land tied-out in NetSuite for us and break on Nue's handoff. They are the demo.

4 · Prove it in the first demoWatch it tie outShow a downsell and a three-year ramp posting and tying out in NetSuite. The CFO watches it work, not a slide.

The one move that wins

Get the controller to ask Nue for a tied-out downsell and ramp inside NetSuite ARM. The answer is our whole pitch.

The one-liner

Nue bills in its own cloud and hopes NetSuite catches it. We put billing and revenue where the books live.

Nue competes with Salesforce Revenue Cloud and reconciles to the ERP. Continuous completes the ERP. The deal stays in Salesforce, the books stay in NetSuite, and the auditor never leaves the trial balance.

Qualify: one books or two?→ Lead with the tie-out demo→ Concede the front end, win the GL→ RCA ally, not RCA replacement

Nue facts sourced from nue.io and public press, July 2026. "Verified" claims confirmed from primary Nue pages; "vendor claim" quoted but not independently validated. NetSuite ARM behavior per Oracle NetSuite published documentation.