easy

The easy button for connecting Agentforce Revenue Management and NetSuite.

AppExchange certified · Built for NetSuite certified SuiteApp · SOC 1 / SOC 2 certified

Your presenters

From Continuous.

JL

Jen Larco

Senior Product Manager, Continuous.

jen.larco@continuoustech.com

TT

Thane Tagg

Head of Solution Engineering, Continuous.

thane@continuoustech.com

Who we work with

Some of our customers.

The problem

NetSuite wasn't built to handle lifecycle management.

How customers sell today.

Ramp deals

annual step-ups

Subscription lifecycle

amend
renew
upsell
downsell

Usage-based models

metered consumption

Agentforce Revenue Management supports

Built for linear order and invoicing.

Order

→

Ship

→

Invoice

Lifecycle events not supported

Old school ERP · 20+ years old

The solution

The only purpose-built application, native in both systems.

System of customer engagement

Continuous native app

Accounts & Contacts Opportunity Management Order Management Usage & Consumption Billing & Invoicing Payments & Credits Dunning & Collections

Financial system of record

Continuous native app

Accounts Receivable Revenue Recognition General Ledger

AppExchange certified · Built for NetSuite certified SuiteApp · SOC 1 / SOC 2 certified

When to think of Continuous

Anytime the customer has NetSuite.

See it working, first call.

We demo Agentforce Revenue Management and NetSuite working together, live.

We speak both platforms.

Salesforce and NetSuite experience in the room, ready to go deep on either side.

easy

The plays

How Continuous helps in Revenue Cloud deals.

Displacewin the compete

Beat the platform vendors

Nue, DealHub, Zuora hand NetSuite a summary. RCB posts the real transactions to the books.

Beat NetSuite-side billing

SuiteBilling, ZoneBilling, 360 Subscription Billing win because finance wants billing near the ledger. That reason disappears.

Complement & co-sell RCB

We help explain that the native sales order can't handle lifecycle changes: amendments, ramps, usage, credits. RCB can.

Replace third-party vendors

Zuora, Chargebee, and other third-party billing. The renewal is the opening; the line item becomes RCB consumption.

Unblockmove the cycle

Turn the finance veto into a sponsor

Every document posts as a native NetSuite transaction, tied out to the penny.

Keep NetSuite ARM

Obligations map straight into the revenue engine their auditors already trust.

Simplify the integration to NetSuite

Prebuilt on both sides: derisk the implementation, faster time to value.

Land RCB in phase 1

Billing stays in the initial project. If it slips, we stay in and hand you the RCB moment.

Talk track · ~2.5 min

Two plays, and both are about your number. Displace is the compete column: the platform vendors keep the subledger in their cloud and hand NetSuite a summary, which finance will not sign; the NetSuite-side billing tools win on one instinct, billing near the ledger, and we remove it; the standard sales order cannot receive a lifecycle; and an installed Zuora or Chargebee is a renewal-time displacement where the third-party line item becomes RCB consumption. Unblock is the stuck-deal column: the finance veto becomes a sponsor because everything posts native and ties out, NetSuite ARM stays, the NetSuite integration simplifies to a package install, derisking the implementation and pulling time to value forward, and billing lands in phase 1 instead of a phase that never comes. Close on the line at the bottom, said without hedging: Continuous Control requires Agentforce Revenue Management, it does not work with legacy CPQ, so every deal we touch is one of yours.

Which accounts

Where Continuous Control is the best fit.

The best fit

✓Any account that wants to keep revenue in NetSuite

✓NetSuite is the financial system of record, and staying

✓SuiteBilling, ZoneBilling, or any other third-party billing solution installed or in the eval

Not the fit

✗RCA / RCB is not selected, and no move is planned

✗NetSuite is not the General Ledger or ERP system

✗The customer wants to migrate off NetSuite

Compatibility

Continuous Control RCA/B compatibility.

RCA + RCB · preferred

The full picture

Billing and the customer lifecycle stay on Salesforce, and every invoice, credit memo, and payment posts to NetSuite as a native transaction.

This is the configuration everything in this deck shows.

RCA alone

Compatible

RCA billing schedules integrate directly: invoices and credit memos sync to NetSuite automatically. Works for subscription and one-time products.

Requires RCB for:

usage & consumption billing
payment processing: credit cards & ACH
dunning & collections

RCA + NetSuite-side billing

Not compatible

SuiteBilling or ZoneBilling is not a supported path: both systems want to do proration, and both want to own the customer lifecycle.

The customer lifecycle should live on Salesforce.

Start on RCA alone today and the tracks for RCB are already laid: the application is installed, and adding RCB functionality is as simple as turning on the synchronization.

Talk track · ~2 min

This slide answers the question every seller asks sooner or later: does this need RCB, or does RCA alone work? First card is the preferred picture and the one the demo shows. The middle card is also a green check, and say it supportively: RCA alone works, the RCA billing schedules integrate directly and invoices and credit memos sync to NetSuite automatically, great for subscription and one-time products. What the customer does not get without RCB: usage and consumption billing, payment gateway processing like credit cards and ACH, and dunning and collections; that is the natural upgrade conversation, not a limitation lecture. Red on the right is the line to hold: a NetSuite-side billing tool instead of RCB is not a supported path, because two systems end up fighting over proration and the customer lifecycle, and the lifecycle belongs on Salesforce. Then the bottom line, which is the sales move: starting on the standard Sales Order is not a dead end, because the application is already installed, and when RCB lands the upgrade is turning on the synchronization. RCA-alone deals are still Continuous deals, and they become RCB deals.

Live demo

One deal, end to end, live.

1 · Salesforce ARM

Quote → Book → Invoice → Payment

2 · NetSuite

ARM Contract → Recognize Revenue → Native Accounting

3 · Salesforce ARM

Booked · Billed · Recognized → Full Asset Lifecycle

Plus the admin behind it: field mappings · Flow actions · observability · configured in clicks, not code

The questions we actually get

Six questions, answered.

"Do you do implementations?"

Yes. Continuous implements Continuous: a fixed-scope package included with the license. The RCA and RCB implementation stays with an SI partner.

"How do you price?"

A flat annual license per Salesforce and NetSuite org pair, implementation included. A product license, not a services contract.

"Who do you implement with?"

Continuous or a certified partner. If an SI is already in the account, they keep the RCA and RCB configuration and the integration line leaves their scope.

"Are any customers live?"

Yes. Continuous Control has multiple referencable live customers, posting real transactions and closing books on time.

"How do we engage with you?"

Reach us at Slack thane@continuoustech.com or Slack jen.larco@continuoustech.com, and we demo with your SE.

"Are you competitive with m3ter?"

No, complementary: Continuous Control integrates event-based billing to NetSuite for revenue and accounting, posting revenue and GL impact.

Talk track

These are the six that come up in every room, so answer them fast and move on. Implementations: yes, and it is a fixed scope that ships with the license, not a time-and-materials arm; we have no services business to grow. Cost: give the posture, never a number in the room. Flat annual license per connected org pair, implementation included, product license not a services contract, and it is not carved out of the customer's RCA or RCB budget line. If they push for a figure, take it offline. The SI question is the one that buys you trust with delivery partners: Continuous implements Continuous, the SI keeps the RCA and RCB work, and the only thing that leaves their scope is the integration line, which they did not want to own anyway. Customers live: name only the logos on the customers slide, do not improvise numbers. Engagement: the two addresses are live, Thane and Jen directly. m3ter: this answer is locked, say it exactly as written; we are complementary, we integrate its event-based billing to NetSuite for revenue and accounting. Customers live: multiple, referencable, and the logos are one slide back.

Connect with Continuous

How to find us.

Say hi at Dreamforce

2 sessions · Wednesday

Slack or email

thane@continuoustech.com
jen.larco@continuoustech.com

The one-pager

Sent after this session · 5-minute demo recording inside

easy