Bulleted talking points, one block per slide. Deck runs ~12 to 14 minutes at this pace. The deck also carries these as presenter notes: press S in the deck to overlay them.
1
Title
The easy button.
One sentence, then pause: Continuous Control is the easy button for connecting Agentforce Revenue Management and NetSuite.
Let the picture talk: Salesforce, NetSuite, and the button between them.
If asked about trust: AppExchange certified, Built for NetSuite certified SuiteApp, SOC 1 / SOC 2.
2
The problem
NetSuite wasn’t built for lifecycle management.
Start on the LEFT, the positive: this is how customers sell today.
Ramp deals stepping up every year. The full subscription lifecycle: amend, renew, upsell, downsell. Usage-based models billing on consumption.
Agentforce Revenue Management supports all of it natively.
Then the right card: NetSuite alone is old school ERP, built for a linear world. Order it, ship it, invoice it, done.
Point at the X and land the line: it was not built for these lifecycle events. That gap is the problem.
3
The messy middle
Glue, code, and spreadsheets.
Ask the room: so how does this get solved today?
Option one: brittle middleware. Months of scoping, a systems integrator on the clock, and the bill keeps running after go-live.
Option two: point-to-point code. Undocumented, and it breaks every time either system changes.
Option three, the quiet one: the swivel chair. Spreadsheets and re-keying between two screens. Finance becomes the integration.
What the messy middle actually costs: missed revenue, amendments and usage that never reach billing. A slow close, weeks of reconciling two systems that disagree. Audit pain, because the trail lives in inboxes.
Transition: there is a better way, and it is one slide away.
4
What it is
The only purpose-built application, native in both systems.
Spoken opener: sell in Salesforce, account in NetSuite, Continuous connects them.
Left: every customer touchpoint happens in Agentforce Revenue Management: booking, billing, dunning, payments.
Right: finance keeps the books native in NetSuite: accounts receivable, revenue recognition, the General Ledger.
The middle is Continuous Control: one connection between two native apps, and the light on the line is the sync running.
Payoff line: full Agentforce Revenue Management adoption on Salesforce, while finance stays native in NetSuite.
5
How it works
Every sync, prebuilt.
Every bar on the left has a prebuilt mapping that ships with the product.
Customers, items, invoices, and payments land as native NetSuite records, and the transactions post to the General Ledger.
The contract, performance obligations, and billing schedules land in the Continuous SuiteApp, purpose-built for the lifecycle.
One connection, configured in clicks. No middleware, and no data stored outside the two systems you already own.
6
The data model
Under the hood: what lives where.
One level deeper, for the technical people in the room.
Left: the Agentforce Revenue Management graph, contract to cash, exactly as RCA and RCB produce it.
Right: mirrored into the Continuous SuiteApp: contract, orders, lines, grouped by product into Performance Obligations.
The POB is the unit of revenue. It rolls Booked, Billed, and Recognized.
Revenue branch: plans amortize each obligation into schedules, and recognition posts native journal entries to the General Ledger.
Billing branch: schedules drive native invoices, and every invoice line ties back through obligation details.
Everything is cross-linked both directions, and the POBs mirror back to the Contract in Salesforce.
7
Key features
Everything the easy button does.
The whole product on one slide, left to right.
Book in one click; invoices and payments post natively; revenue recognized with the same numbers in both systems.
The admin story: prebuilt mappings, Flow actions, full observability.
Tee up the tour: the next slides show each one on screen.
8
Tour
Book an order. That is it.
This is the sync card on the Order page. One click.
Watch the checklist: customer, contract, order, lines, billing schedules, all landing in NetSuite from one call.
No batch jobs, no middleware queue. The rep never leaves Salesforce.
9
Tour
A NetSuite side built for how you sell.
This is the ARM Contract inside NetSuite.
Ramps, amendments, and usage arrive intact, not flattened into a sales order.
Contract, orders, obligations, and billing schedules in one view, linked back to Salesforce.
10
Tour
Booked. Billed. Recognized.
Revenue posts to the General Ledger as native journal entries.
The inset is the actual NetSuite journal entry; the main screen is the same contract in Salesforce.
The point: your books tie out, same numbers in both systems.
11
Tour
Configured in clicks, not code.
The mapping editor: every sync ships prebuilt, and your admin tunes it here.
No consultants, no integration project, no middleware to babysit.
12
Tour
Drops into anything you build.
Branded Continuous actions inside Flow Builder, one per sync.
The inset is the Sync Runs dashboard: every run tracked, with links into both systems.
13
Outcomes
The messy middle, gone.
Call back to the three cost cards, now flipped green.
Revenue captured: every amendment and usage charge makes it to billing.
A faster close: the books tie out, both systems agree on every number.
Audit-ready: one click of lineage from the contract to the journal entry.
Land it: that is what the easy button buys you.
14
See it run
The whole flow in five minutes.
For the deep dive: the five-minute overview recording, quote to cash to revenue, both systems on screen.
The card is clickable in the deck; the same recording rides in the one-pager.
15
Close
How to find us.
Say the closing line out loud: Continuous Control is the easy button for connecting Agentforce Revenue Management and NetSuite.
Dreamforce: two sessions on Wednesday, come say hi.
Slack or email, we answer both: thane@continuoustech.com, jen.larco@continuoustech.com.
The one-pager travels with the deck, five-minute demo recording inside.