Continuous Control

Five-minute overview demo · script, talk track, and shot sheet
Runtime: 5:00 · title card + 13 beats Audience: Prospecting customer · Salesforce AE / SE Recorded on: the QuantumBit demo org · frames from Northgate Cloudworks, contract 00000247 Voice: scripted, recorded in post

How to use this sheet

One video, two jobs. A prospect watches it and understands what Continuous Control is without a meeting. A Salesforce AE or SE watches it once and can explain the product from memory afterwards.

Every beat carries four things: what is on screen, the voiceover word for word, a seller cue that never appears in the video, and capture notes for record day. The narration is customer-safe. The amber cue boxes are not; they are for the person presenting.

Everything on this page is editable. Click any block, change it, and use Save Edits to download your copy. Sentences with a dotted underline are the first ones to cut if a beat runs long. Word counts are shown against a 130 word per minute target, which is deliberate demo pace rather than conversational pace.

One shoot, two outputs

Capture each beat at the longer length in the middle column, then cut it twice: once for the stitched overview, once as a standalone clip. The standalone cuts fill the six [video link] slots that the product brief and the enablement hub already carry, so one recording session finishes both deliverables.

ClipCaptureOverview trimStandalone cut lands in
A · One catalog (Beat 2)30s15sOpens the Slot 2 clip, no slot of its own
B · Book the order (Beat 3)90s30sSlot 2, Book an order, one click
C · The books in NetSuite (Beats 4 and 5)120s64sSlot 4, The books, in NetSuite
D · The lifecycle (Beats 6 and 7)75s48sSlot 3, The lifecycle (was Amend a deal)
E · One view for every team (Beat 8)45s17sSlot 5, Revenue, back in Salesforce
F · Month end, reconciled (Beats 9 and 10)45s33sSlot 6, Month end, reconciled
G · The control room (Beats 11 and 12)60s35sSlot 1, The control room (the flow-actions section stays in this standalone admin clip; it is cut from the overview)
H · Graphics: title card, messy-middle animation, both closesn/a58sOverview only · animation at slides/messy-middle-animation.html
Total~7:45 captured5:00 cutOverview + six slots

Pre-flight, on record day

0

Title cardGraphic, no app surface

0:00 - 0:08 8s
ccContinuous Control

The easy button for connecting Agentforce Revenue Management and NetSuite.

Salesforce runs the customer · NetSuite closes the books
AppExchange certified · Built for NetSuite certified SuiteApp · SOC 1 / SOC 2 certified
On screen
The GTM deck's title slide treatment, not a generic card: navy canvas with the purple glow, the cc pill, the gradient "easy button" headline, the certification line. Export the deck's slide 1 (or rebuild it in the editor) at video resolution. Fade the tagline up one second after the headline.
Voiceover
Silent for the first four seconds. The Beat 1 voiceover starts over this card and carries into the first visual, so the video never opens on dead air.
Seller cue · not in the video
If you are playing this live, say nothing over the card. Let it land.
Capture
DONE: exported chrome-free from the GTM deck as 0-TitleCard-1080p.png (in CONTROL FINAL). The close has its own animated asset, slides/close-card-animation.html.
1

The messy middleGTM deck problem graphic, then the resolve

0:08 - 0:41 33s
Salesforce
System of customer engagement
OpportunitiesOrdersUsageBilling & InvoicingPayments & CreditsCollections
Messy middle
  • third-party billing/revenue solutions
  • neverending middleware & custom builds
  • manual spreadsheets & journal entries
NetSuite
Financial system of record
Accounts ReceivableRevenue RecognitionGeneral Ledger
The GTM deck's problem slide, animated. On the final narration line the three red items dissolve and the deck's solution-slide bridge replaces them: two arrows and one product, two native apps.
On screen
The GTM deck's problem slide, box for box: Salesforce on the left, NetSuite on the right, and the messy middle between them. Each of the three red items flicks in as the narration names it. On the last line the mess dissolves and the solution slide's bridge replaces it: transactions post right, ids and status flow back, one product, two native apps.
Voiceover 80 words · 145 wpm
Most companies run their customer experiences in Salesforce and close their books in NetSuite. Salesforce is the system of customer engagement. NetSuite is the financial system of record. And in between sits the messy middle: third-party billing and revenue solutions, never-ending middleware projects, manual spreadsheets and journal entries. All of it exists for one reason: to make sure every customer transaction is interpreted correctly into the right financial transaction. Continuous Control replaces the messy middle. One product, two native apps.
Seller cue · not in the video
This is the first-call framing, and it works without a screen. The messy middle is the moment every room nods, because they recognize at least two of the four items. Do not lead with the product. Lead with the mess.
Capture
No screen recording of the app: record the purpose-built animation instead. Open marketing/slides/messy-middle-animation.html full screen and capture it: click to play; the zones fade in, the three red items flick in at 15 / 17 / 19 seconds (timed to the narration naming them), and at 28.5 seconds the mess dissolves into the bridge. Press R to reset between takes.
2

One catalogSalesforce · Product page, Product Sync card

0:41 - 0:56 15s
Product page with the Continuous Product Sync card, synced to NetSuite
On screen
A Revenue Cloud product page with the Continuous Product Sync card. The card is the shot: Synced, 3 of 3 objects, the item created in NetSuite, and the config rows beneath it. Hover the rows as the narration runs, then the Open item in NetSuite link.
Voiceover 38 words · 152 wpm
Continuous Control works natively with Revenue Cloud's product catalog, and ensures your new offering is available in NetSuite with all of the necessary configurations. It is ready to book, bill, and recognize revenue, in Revenue Cloud and NetSuite.
Seller cue · not in the video
This beat answers the question every NetSuite admin asks first: do we have to rebuild our catalog on the other side? No. And the configuration detail is the differentiator: item type, subsidiary, and revenue rule land with the item, not as an afterthought someone fixes in NetSuite later.
Capture
Capture 30 seconds and trim to 18. The standalone cut opens the booking clip (Slot 2) rather than getting its own slot. Frame: the QB-COMPLETE product page with the Product Sync card showing Synced. GAP: the product page does not yet expose the NetSuite configuration itself (item type, subsidiary, revenue rule as editable setup on the product); that surface needs building or staging before this beat can show configuration, not just the synced result.
3

Book the order, one clickSalesforce · the order, the Book Order card

0:56 - 1:26 30s
The Book Order card, every object reporting in as it syncs
On screen
The activated Revenue Cloud order. Start at the top and point out the Contract lookup on the order: this is the contract the next beat opens in NetSuite. Then draw attention to the order line items: subscription, one-time, services, usage-based. Then click Book Order on the prebuilt card and let the LWC's animation carry the beat: each object lights up as it syncs. Cut the beat the moment the sync completes; the ARM Contract reveal belongs to the next beat.
Voiceover 75 words · 150 wpm
Here is an activated order from Revenue Cloud, tied to its contract, with subscription, one-time, services, and usage-based products. We can now book it to NetSuite with one click, and a single call. Continuous Control automatically mirrors the Revenue Cloud records into the Continuous SuiteApp: the customer, the contract, the order and its line items, and the billing schedules. It is prebuilt: no custom integration project or complex mappings, no nightly batches, no manual effort.
Seller cue · not in the video
The proof beat. One click, one unbroken shot. If they ask what is underneath it: a single authenticated call to a NetSuite endpoint, with the payload and the result stored on the run record. Ending on the completed sync sets up the ARM Contract reveal that opens the next beat.
Capture
Capture 90 seconds so this doubles as the standalone booking clip. Never cut away mid-call: the single unbroken shot is the proof. Speed-ramp the round trip to about two times if it runs long, and keep the narration continuous over the ramp so the viewer does not notice.
4

Performance obligationsNetSuite · ARM Contract lines → ARM POBs

1:26 - 2:00 34s
The ARM Contract's order lines: dates, amounts, discounts
The lines we just booked
ARM POBs sublist with revenue rules and amounts
Grouped into performance obligations
On screen
Start on the ARM Contract's order lines sublist: the lines from the order we just booked, with dates, amounts, and discounts readable. Then the ARM POBs subtab: every line grouped into a performance obligation, each row showing its revenue rule, total, billed, and recognized. Hold so the rules column is readable: Straight-Line, % Complete, Delivery, Event-Based.
Voiceover 69 words · 122 wpm
Our Salesforce transaction landed directly in NetSuite as the ARM Contract. We can see all of the line items from the order we just booked, with the financial details: dates, amounts, and discounts. The Continuous Control SuiteApp automatically groups order lines from Revenue Cloud into financial performance obligations that let you recognize revenue natively in NetSuite revenue schedules, or can be fed directly into NetSuite's Advanced Revenue Management module.
Seller cue · not in the video
The POB is the bridge concept: it is the 1-to-1 twin of a native ARM Revenue Element, which is why 'or feed it into ARM' is credible. If ARM is in the account, point at the Revenue Arrangement link on the record.
Capture
Capture 75 seconds; together with the next beat this is the standalone books clip (Slot 4). Run Update POBs once before recording so the sublist is fresh.
5

Inside a performance obligationNetSuite · one POB: revenue tab, then billing tab

2:00 - 2:30 30s
The POB's revenue schedule with its journal entries
Revenue tab: schedule + JEs
The POB's billing tab: synced schedules and native invoices
Billing tab: schedules + invoices
On screen
Click into one POB. Land on the Revenue Recognition tab: the schedule, period by period, recognized rows carrying their journal entry links. Then the Billing tab: the Revenue Cloud billing schedule group synced across, and the obligation detail rows pointing at real NetSuite invoices. End on the Booked / Billed / Recognized bars at the top.
Voiceover 70 words · 140 wpm
A performance obligation is the container for everything with the customer: every booking, every billing, and every dollar of revenue for that obligation. The revenue tab shows its schedule, period by period, with the journal entries automatically created in NetSuite, right to the general ledger. The billing tab shows our Revenue Cloud billing schedules, with the native NetSuite invoices synced from Revenue Cloud. One clear picture: booked, billed, and recognized.
Seller cue · not in the video
This deep-dive is where the recognize story now lives: the journal entries on the schedule ARE the proof revenue posts natively. The waterfall bars are the visual a CFO remembers.
Capture
Second half of the 120 second books capture (Slot 4). Run the engine once before recording so the schedule rows and journal entry links are populated.
6

Full asset lifecycle managementSalesforce · managed assets → upsell order → the asset

2:30 - 2:56 26s
The upsell order with its increased quantity, booked
The upsell order, booked
The Revenue Cloud asset: state periods and associated orders
The asset keeps the story
On screen
Start on the Salesforce contract: the managed assets under the contract. Click Amend on the Additional API asset, pick the date. Then the upsell order with its increased quantity, on the order screen with the Book Order card showing Booked (a quick shot, no live round trip). Then open the asset in Revenue Cloud: the Asset State Periods, the mid-term increases, each with its associated order. Beat 7 then cuts to the ARM Contract in NetSuite.
Voiceover 64 words · 148 wpm
Manage the full contract and asset lifecycle natively in Revenue Cloud. Here are the managed assets under the contract. When we amend one, the upsell books through the same one click, and the asset keeps the whole story: each state period, each mid-term increase, and the order behind it. Every lifecycle change syncs automatically with Continuous Control: mid-term add-ons, product swaps, uplifts, and renewals.
Seller cue · not in the video
Amendments are where competing tools break, so if a rival is in the deal, this is the beat to replay and slow down. The upsell order appears in its booked state; the live round trip stays in Beat 3.
Capture
First half of the 75 second lifecycle capture (Slot 3). Stage before recording: the contract page showing managed assets, and the upsell amendment already booked so the order screen shows the increased quantity with the card in its Booked state and the Asset State Periods show the mid-term increase with its associated order.
7

The lifecycle, in NetSuiteNetSuite · the upsell, rolled up to the POB

2:56 - 3:18 22s
The ARM Contract with the add-on order, type Upsell
The upsell order, aggregated
The performance obligation with the upsell line rolled up
Rolled up to the POB
On screen
The NetSuite ARM Contract's orders: the original order plus the add-on order with type Upsell. Then click into the performance obligation and land on its ARM Order Lines: the upsell line sitting beside the original, rolled up into the POB's totals and waterfall. Frames are provisional: capture once the upsell amendment is booked.
Voiceover 52 words · 142 wpm
And in NetSuite, the ARM Contract keeps up. The upsell arrives as its own add-on order. Click into the performance obligation, and the upsell order line is rolled right up to it, with revenue automatically recalculated. Any change through the lifecycle updates automatically in NetSuite, and it is all visible, right here.
Seller cue · not in the video
Prospective re-spread without restating posted periods is the phrase that matters to a controller. The roll-up story: one obligation, every order line behind it, the full lifecycle in the financial system of record.
Capture
Second half of the lifecycle capture (Slot 3). Needs the upsell amendment booked so the ARM Orders subtab shows the add-on order with type Upsell and the POB's ARM Order Lines show the upsell line beside the original.
8

One view for every teamSalesforce · the contract's obligation viewer

3:18 - 3:35 17s
Revenue summary card
Booked, billed, recognized
The obligation viewer: obligations from NetSuite
Obligation by obligation
On screen
Back on the Salesforce contract: the obligation viewer, showing the performance obligations straight from NetSuite with booked, billed, and recognized per obligation. Click Refresh from NetSuite and let the card re-render on camera.
Voiceover 37 words · 131 wpm
And back on the Salesforce contract, the obligation viewer shows the performance obligations straight from NetSuite. Finance manages revenue natively in NetSuite. Sales sees bookings, billings, and revenue, unified in Salesforce. One accurate picture, for every team.
Seller cue · not in the video
The alignment beat. It speaks to a revenue leader and a finance leader in the same breath, which is why it belongs in a first meeting where both are in the room.
Capture
Capture 45 seconds and trim to 17; the longer cut is the standalone Slot 5 clip. Verify before the take that booked is at or above billed on this contract, otherwise the card tells the wrong story on camera.
9

Native NetSuite transactionsSalesforce · the account's billing, synced on camera

3:35 - 3:54 19s
The posted invoice syncing, same rhythm as the booking
On screen
Start on the account record with its Revenue Cloud billing schedules and invoices related lists visible, then open an invoice that is already generated and posted (do not show the billing run itself). Click Sync and let the card report, the same rhythm as the order booking. Cut when the sync completes.
Voiceover 40 words · 126 wpm
When it is time to bill the customer, one click will sync the invoices generated from the Revenue Cloud billing schedules, the same way the order booked, and it lands as a native NetSuite transaction, alongside payments and credit memos.
Seller cue · not in the video
Decision baked in: the invoice is pre-generated and posted; the sync is the on-camera moment. The billing run itself is never shown.
Capture
First half of the 45 second month-end capture (Slot 6): account, posted invoice, sync on camera.
10

Accounting, native in NetSuiteNetSuite · the invoice and its GL Impact

3:54 - 4:08 14s
The native NetSuite invoice with its GL Impact subtab
On screen
The native NetSuite invoice, then its GL Impact subtab. Hold so the debits and credits are readable: receivables, deferred revenue, line by line.
Voiceover 31 words · 133 wpm
And in NetSuite, all of the accounting happens easily and natively. Every transaction posts real GL impact automatically: every debit and credit, on the ledger. The books close accurately, every time.
Seller cue · not in the video
The why-native beat. 'Automated GL postings' is the phrase that matters to an auditor and a controller: no second subledger to reconcile, no summary journal hiding the detail. If asked what posts, the GL Impact subtab on screen is the answer.
Capture
Second half of the month-end capture (Slot 6): the NetSuite invoice, ending held on GL Impact.
11

Prebuilt, and easily modifiableSalesforce · NetSuite Field Mappings

4:08 - 4:25 17s
Every object mapping, prebuilt and ready to go
Prebuilt, ready to go
The mapping editor: edit a row or add your own
Click in, edit or add
On screen
The NetSuite Field Mappings tab: every object listed, already filled in. Click into the Order mapping and show the editor: edit an existing row, then the add-mapping affordance, so 'easily modifiable' is seen, not claimed.
Voiceover 42 words · 148 wpm
Continuous Control ships with every object mapping prebuilt: products, orders, invoices, payments, all wired to the NetSuite application on day one. Nothing to design, nothing to build. And when you need something custom, any mapping is easily modified or extended, without code.
Seller cue · not in the video
The implementation-time answer: an application, not a build. Prebuilt is the speed story; modifiable is what keeps a solution architect from dismissing it as a toy.
Capture
First third of the 60 second control-room capture (Slot 1). Mappings list, click into Order, one edit, one add.
12

Full observability, no black boxSalesforce · Sync Runs

4:25 - 4:43 18s
The Sync Runs tab: every call into NetSuite, one screen
On screen
The Sync Runs tab, a full green window. Open one run so the stored payload and result are visible for a beat, then gesture at the notification setup, then back to the green list.
Voiceover 41 words · 137 wpm
And you can monitor every call Continuous Control makes into NetSuite, on one screen. No black box, no integration logs to dig through. Preconfigure notifications, and if anything ever needs attention you know immediately. Nothing slips, and no revenue is missed.
Seller cue · not in the video
The trust close for a technical evaluator, and the revenue-assurance line for a finance leader: nothing slips, no revenue missed. If an SE asks what a retry does, the answer is idempotent upserts by external id, safe to re-run against the same records.
Capture
Final third of the control-room capture. End on the green list; the overview cuts to the close from here.
13

Close: the easy buttonGraphic · the GTM deck's easy-button hero, two versions

4:43 - 5:00 17s
Salesforce
NetSuite
}
ccContinuous Control
Salesforce · the system of customer engagement Continuous Control · native to both · prebuilt application NetSuite · the financial system of record
On screen
The easy-button hero graphic from the GTM deck's title slide: the Salesforce and NetSuite tiles bracketed into the Continuous Control pill, with the three caption lines. Reuse the deck's slide 1 export; animate the closing lines over it, then hold the graphic alone. Record both closes in the same session and export two versions of the video.
Voiceover 32 words · 113 wpm
Salesforce runs the customer experiences. NetSuite closes the books. Continuous Control is the easy button that keeps them in lockstep. No integration project, no second billing tool. One product, two native apps.
Seller cue · not in the video
That is the customer close (the 'one product, two native apps' bookend echoes Beat 1; cut it if it feels like one line too many). The seller close is below, and it is the only ending that changes. Send the customer cut to a prospect; keep the seller cut for internal enablement.
Capture
Record slides/close-card-animation.html full screen: click to play; the five closing lines fade in timed to the narration (press 2 before playing for the seller-cut ending, 1 for customer). A static hold frame is exported as 14-CloseCard-hold-1080p.png. Record both voiceover endings back to back so the tone matches, then export twice.

Two closes, one shoot

Customer cut
Salesforce runs the customer experiences. NetSuite closes the books. Continuous Control is the easy button that keeps them in lockstep. No integration project, no second billing tool. One product, two native apps.
Seller cut
Salesforce runs the customer experiences. NetSuite closes the books. Continuous Control is the easy button that keeps them in lockstep. If there is a NetSuite account in your pipeline, bring us in early. We will demo it with your team.

Record both endings back to back so the tone matches, then export two versions of the same video. Everything before 4:43 is identical.

Timing guide

#TimecodeBeatSurface
00:00 - 0:08Title cardGraphic · the GTM deck's title slide
10:08 - 0:41The messy middleGraphic · GTM problem slide, then the bridge
20:41 - 0:56One catalogSalesforce · product page, Product Sync card
30:56 - 1:26Book the order, one clickSalesforce · the order, ends at sync complete
41:26 - 2:00Performance obligationsNetSuite · ARM Contract lines → ARM POBs
52:00 - 2:30Inside a performance obligationNetSuite · revenue tab, billing tab
62:30 - 2:56Full asset lifecycle managementSalesforce · managed assets, upsell, state periods
72:56 - 3:18The lifecycle, in NetSuiteNetSuite · the upsell, rolled up to the POB
83:18 - 3:35One view for every teamSalesforce · the contract's obligation viewer
93:35 - 3:54Native NetSuite transactionsSalesforce · the account's billing, synced
103:54 - 4:08Accounting, native in NetSuiteNetSuite · the invoice and its GL Impact
114:08 - 4:25Prebuilt, and easily modifiableSalesforce · NetSuite Field Mappings
124:25 - 4:43Full observability, no black boxSalesforce · Sync Runs
134:43 - 5:00Close: the easy buttonGraphic · the GTM deck's hero, two versions
5:00Beats 4 and 5 carry the finance proof; beats 6 to 8 carry the lifecycle; beats 9 and 10 carry billing to the ledger.

Lines worth keeping

Post-production

StepWhat to do
1. VoiceoverRecord the whole track in one pass, beat by beat, with a short pause between beats. One pass keeps the tone even. Re-take individual beats as needed rather than single sentences.
2. Cut to pictureLay the voiceover down first, then trim the screen capture to it. The narration sets the pace; the footage follows. Speed-ramp any wait longer than four seconds and keep the narration running over the ramp.
3. EmphasisZoom or highlight three moments only: the Book Order card going green, the revenue rules on the obligations, and the journal entry lines. More than three and none of them land.
4. CaptionsBurn in captions. Most of the first views are muted, in an inbox or a feed. The captions come straight from this script, so they cost nothing.
5. Export twiceCustomer cut and seller cut, identical up to 4:43. Name them so the difference is obvious.
6. PublishHost both, then fill the slots: the six standalone cuts go into the product brief and the enablement hub Watch section, and the overview becomes the hero card above them. The map of which file carries which slot is in marketing/VIDEO-LINKS.md.

Say it right

Post, never settle. Transactions post to NetSuite. Finance closes the books in NetSuite.
Name the roles. NetSuite is the financial system of record. Salesforce is the system of customer engagement.
Customer-facing naming. Say Agentforce Revenue Management. The platform stays Salesforce.
No pricing. Posture only, never a number, on anything a customer sees.
No compete in the narration. Rival handling lives in the field guide and the battlecards, not in this video.
One engine at a time. A customer picks the Continuous engine or NetSuite's own advanced revenue management. Never both on the same contract.

These are the library's locked rules. If a line in this script drifts from them in an edit, the script is wrong, not the rules.

Saved