Tag: NetSuite

What Your Portfolio Company’s ARR Isn’t Telling You

Posted on April 9, 2026 by - Private Equity

What Your Portfolio Company’s ARR Isn’t Telling You

How ramps, swaps and RPO are quietly distorting the revenue picture at your SaaS investments — and what it takes to fix it.

This article is for private equity operators and CFOs overseeing PE-backed SaaS companies running Salesforce and NetSuite. It explains how ramps and swaps distort ARR reporting, erode margin through miscalculated swap credits, and create audit and covenant risk — and what it takes to fix it without adding headcount.

TL;DR
  • Ramp and swap contracts are standard in B2B SaaS but create a structural gap between what’s booked in Salesforce and what’s recognized in NetSuite
  • seven records separate the two, and most PE-backed portfolio companies don’t know it exists.
  • Sales teams quoting swap credits from invoice math instead of post-allocation recognized revenue silently donate 1–3% of ARR annually
  • not from error, but from not having the right number available at the time of quoting.
  • ARR reporting built on Salesforce bookings is structurally disconnected from ASC 606-recognized revenue. The CRO and CFO are typically working from different numbers, and neither can cleanly explain the delta.
  • RPO is often understated at companies where ramp deals aren’t configured for even recognition in NetSuite
  • making forward revenue commitments unreliable for modeling or covenant purposes.
  • Continuous closes the Salesforce-NetSuite revenue gap automatically
  • surfacing the real recognized revenue position in Salesforce before credits are issued, and keeping bookings, billings, and recognition aligned without adding headcount.

Why Your Portfolio Company’s ARR Number Is Harder to Trust Than You Think

Every PE operator knows the feeling. The monthly report lands. ARR is up. The CRO is confident. And somewhere in the back of your mind a question forms that nobody in the room seems to be asking: is this number actually right?

Not wrong because of fraud. Not wrong because of bad intentions. Wrong because the systems that produce it weren’t built to keep pace with how modern SaaS companies actually sell — multi-year commitments, mid-contract changes, bundled pricing, expanding customers. The most common of these, and the most quietly damaging, are ramps and swaps.

The companies that have this problem rarely know the extent of it. Ask the CRO and CFO to explain the delta between bookings and recognized revenue and watch what happens. Ask how swap credits are calculated. Ask whether ramp deals are configured for even recognition in NetSuite. The answers to those three questions will tell you almost everything you need to know about whether this business is built to scale its revenue operations — or whether it’s one audit away from finding out it isn’t.  For PE operators, this isn’t an academic concern.  It’s exactly the kind of issue a buy-side QoE will surface late in a process–when the only options left are repricing the deal, adding protections, or watching the buyer walk away.

We’ve written separately about how this problem plays out at the operational level — between sales teams, finance teams, and the systems they rely on. This piece is about what it means when you’re looking at the business from the outside.

What Are Ramps and Swaps, and Why Do They Distort ARR?

Ramps and swaps are standard contract structures in B2B SaaS. A ramp is a multi-year deal with pre-negotiated price increases each year: a customer commits to $20,000 in year one, $25,000 in year two, $30,000 in year three. A swap is a mid-contract product exchange: a customer returns the unused portion of an existing product and applies the remaining credit toward something different.

Both are legitimate, common, and often a sign of a healthy sales motion. The problem isn’t the structures themselves. The problem is what happens to the numbers after the deal closes.

In Salesforce, the booking reflects what was sold on the day it was signed. Clean and simple. But in NetSuite, two things happen that change the financial picture entirely. First, revenue allocation: when a deal bundles a software license with professional services, NetSuite distributes value across each component based on standalone selling price, regardless of how the invoice was structured. A deal booked as $50,000 for software and zero for services might become $30,000 for software and $20,000 for services once allocation is applied.

Second, recognition timing: a ramp deal can’t be recognized as billed. The total contract value has to be spread evenly across the term under ASC 606, because the same product is being delivered each year. So you might book $75,000, bill $20,000 in year one, and recognize $25,000. Three different numbers from the same deal, none of them wrong, none of them equal. The portion not yet recognized is what’s known as Remaining Performance Obligation — the forward revenue commitment the business is obligated to deliver. For PE operators, RPO is one of the most important indicators of revenue health. If ramp deals aren’t configured correctly in NetSuite, RPO will be understated, and the forward revenue picture you’re relying on is wrong before anyone has made a mistake.

What’s visible in Salesforce and what finance is actually recognizing in NetSuite are separated by seven records. That’s where the ARR story starts to drift.

The distortion happens when those three numbers never reconcile in one place. ARR reporting at most mid-market SaaS companies is built on bookings, not recognized revenue. That can work for internal dashboards, but it breaks the moment someone underwrites the business on the durability and quality of its revenue streams.  Which means the number you’re using to value the business, model retention, and project growth may be structurally disconnected from what the company has actually earned. What’s visible in Salesforce and what finance is actually recognizing in NetSuite are separated by seven records — and that gap is where the ARR story starts to drift.  In practical terms, it’s how you end up marketing a business at 10x ARR only to discover in diligence that 20 to 40 percent of that “ARR” doesn’t behave like recurring revenue at all.

Where Does the Margin Go When Swaps Go Wrong?

The most immediate financial consequence is margin leakage, and it’s more pervasive than most portfolio companies realize.

When a customer requests a swap, the account manager calculates the credit based on what they can see: the original invoiced amount, prorated for the remaining term. If a customer paid $50,000 for a one-year license and wants to swap at the six-month mark, the sales rep quotes $25,000 in credit. Straightforward.

Except after allocation, the actual remaining recognized value might be $15,000. The $50,000 booking was split by NetSuite into $30,000 for software and $20,000 for professional services. Six months in, only $15,000 of the software value remains. The sales rep doesn’t know this because the post-allocation position never made it back to Salesforce. They quote $25,000. The company issues $25,000. And $10,000 of margin quietly disappears. The rep isn’t cutting corners — they’re working with the only number available to them. When systems aren’t architected to surface the real revenue position, over-crediting isn’t a process failure. It’s the predictable outcome of asking people to make financial decisions without financial data.

Across PE-backed SaaS companies, it’s common to see 1 to 3 percent of ARR effectively donated each year — purely because swap credits are based on invoice math instead of recognized revenue.

Multiply that across a sales team doing dozens of swaps a quarter and you have a material drag on margins that doesn’t show up as a line item anywhere. It’s not just an ARR problem; it’s an EBITDA quality problem.  Those quiet credits compress gross margin and introduce noise into the EBITDA you’re counting on at exit, without ever announcing themselves as an explicit cost.  Across PE-backed SaaS companies, it’s common to see 1 to 3 percent of ARR effectively donated this way each year — purely because swap credits are based on invoice math instead of recognized revenue. It just shows up as ARR that’s slightly lower than it should be, retention that looks a little softer than expected, and a finance team that’s perpetually reconciling deals they had no part in structuring.

Why Don’t Portfolio Companies Catch This Earlier?

Because the signal is diffuse and delayed. There’s no moment where the system throws an error or flags a discrepancy. The swap closes. The invoice goes out. The deal gets logged as an expansion or a renewal. Finance processes it weeks later, notices the numbers don’t reconcile, makes a journal entry adjustment, and moves on. By the time it surfaces in a board report, it’s ancient history.

The organizational dynamic makes it worse. Sales and finance at most mid-market SaaS companies operate in separate systems with separate priorities. Sales owns Salesforce. Finance owns NetSuite. The revenue position that matters for swap credits, ramp reconciliation, and accurate ARR reporting lives in NetSuite. The people who need it are in Salesforce. Bridging that gap requires a manual handoff: the account manager calls the revenue team, who is buried in month-end close, who pulls the number manually, who relays it back. By which point the deal has sat long enough that the proration has changed.

The signal is diffuse and delayed. There’s no moment where the system throws an error or flags a discrepancy. By the time it surfaces in a board report, it’s ancient history.

Most portfolio companies have one revenue accountant who genuinely understands how allocation and recognition interact. That person is doing seven other things. They hired the second one two years after they needed to. The processes that depend on their knowledge don’t scale, which means the problem gets worse as the business grows, not better.

And it compounds. Ramps and swaps are already painful for simple subscription models. As more companies move to usage-based and hybrid pricing, mid-contract changes stop being edge cases and become everyday occurrences. The seven-record gap between Salesforce and NetSuite doesn’t shrink as the business scales — it widens. Reconciliation spreadsheets get bigger. Audit prep becomes a recurring nightmare. And for PE operators, those spreadsheets are a signal. Investors ask to see them. They ask what the audit cost and what it focused on. A valuation built on numbers that can’t be traced cleanly from bookings to billings to revenue is a valuation waiting to be challenged.  Viewed across a portfolio, it shows up as a pattern: NRR and GRR that are consistently a few points off expectations, forecasts that miss in the same direction quarter after quarter, audit fees that run higher than they should for the company’s scale, and finance teams that are bigger and more manually oriented than the investment thesis assumed.

What Should PE Operators Be Asking Their Portfolio Companies?

The ramps and swaps problem doesn’t always announce itself. It tends to hide in the gap between what the CRO reports and what the CFO reconciles. Below are a few questions that surface it quickly — think of this as a 30-minute revenue-quality sanity check you can run on any SaaS asset:

Can your account managers see the remaining recognized revenue position for a product before they build a swap quote? If the answer is no, they’re quoting from invoice math. Credits are likely being over-issued and margin is leaking.

Do your bookings, billings, and recognized revenue figures reconcile in a single system? If your CRO and CFO are working from different ARR numbers and neither can explain the delta cleanly, the gap is structural, not a reporting error.

How are mid-contract changes processed? If the answer involves someone calling finance, waiting for a manual pull, and re-running the quote, that’s not a process. That’s a workaround. It won’t scale past the headcount that currently maintains it.

How are ramp deals structured in NetSuite? If multi-year step-up pricing isn’t configured to recognize evenly across the contract term, you may have an ASC 606 compliance exposure and RPO that’s been understated from day one.

Across the portfolio, how many companies require finance involvement every time a customer wants to change a contract mid-term?  If the honest answer is “most of them,” assume you have a systemic revenue-operations risk that will show up in QoE, not just an isolated process gap.

If more than one of these questions doesn’t have a clean answer, the problem is systemic. These aren’t exotic edge cases. They are the standard mechanics of how SaaS companies grow from existing customers. If the systems can’t support them cleanly, the business isn’t built to scale.

A valuation built on numbers that can’t be traced cleanly from bookings to billings to revenue is a valuation waiting to be challenged.

How Does Continuous Fix the Revenue Operations Gap?

Most quote-to-cash stacks stop caring about revenue the moment the invoice goes out. Everything after that gets handed to finance and forgotten. Continuous is built differently. It operates at the architectural boundary between Salesforce and NetSuite, embedded in both systems’ transaction and revenue layers, tracking the full lifecycle of a deal from opportunity through allocation, recognition, and journal entry — keeping the revenue position accurate in real time across both systems.

For swaps, that means the account manager sees the actual remaining recognized value before they build the quote. Not invoice math. Not a CPQ estimate. The number pulled directly from post-allocation accounting. Credits reflect financial reality, finance doesn’t get a phone call, and margin doesn’t quietly erode.

More importantly, the system enforces alignment. Revenue logic is embedded directly in the quoting flow, so sales cannot issue credits that exceed what has actually been earned. The gap between bookings and recognized value closes before it ever becomes a reporting problem.

For ramps, Continuous structures recognition correctly from the start and recalculates automatically when a contract changes. Allocation, deferred revenue, and billing schedules stay aligned without manual intervention. No surprises when a ramp year turns over, no reconciliation required when a customer modifies mid-term.

The same infrastructure governs amendments, credits, true-ups, and hybrid pricing models, absorbing commercial flexibility into system design rather than leaving finance to reconcile it after the fact.

On the reporting side, bookings, billings, and revenue reconcile structurally. The CRO and CFO operate from the same source of truth. ARR reflects recognized reality. Mid-contract changes surface in forecasts immediately, not six weeks later.

For PE operators, the result is a portfolio company whose revenue reporting can be trusted. Not because someone is manually checking it, but because the system is built to close the seven-record gap automatically — and produce accurate numbers by default.

The alternative is to keep throwing senior revenue accountants at the problem — one or two extra hires per company, per portfolio — just to keep the spreadsheets under control. Continuous replaces that with repeatable infrastructure: the seven-record gap closes in the system, once, and scales across every Salesforce-and-NetSuite-based asset you own.

Ready to see how Continuous ensures your revenue position is always accurate, in both systems, in real time? Schedule a Demo.

Also in this series:

Ramps and Swaps 101: Why the Math Is Easy, the Execution Isn’t, and They’re Costing SaaS Companies More Than They Realize

Frequently Asked Questions

ARR reporting at most mid-market SaaS companies is based on bookings recorded in Salesforce at the time a deal closes. But bookings don’t account for post-close revenue allocation, recognition timing under ASC 606, or the impact of mid-contract changes like swaps and amendments. The result is an ARR figure that reflects commercial activity rather than financial reality, and a gap between what the CRO reports and what the CFO can reconcile.

The most direct impact is margin leakage from swap credits that are calculated from invoice amounts rather than post-allocation recognized value. Across PE-backed SaaS companies, it’s common to see 1 to 3 percent of ARR effectively donated this way each year. Beyond that, manual processes create reporting delays, ARR inaccuracies, and a finance team that spends significant time reconciling commercial decisions made without access to the right data. For PE-backed companies, the downstream effects include unreliable forecasting, covenant risk, and audit exposure.

Under ASC 606, a ramp deal where the price increases each year must be recognized evenly across the full contract term, because the same product is being delivered throughout. A three-year deal at $20,000, $25,000, and $30,000 generates $75,000 in total contract value, which must be recognized at $25,000 per year regardless of what is billed. In year one, billing $20,000 while recognizing $25,000 creates an unbilled receivable. The unrecognized portion is recorded as Remaining Performance Obligation — and if ramp deals aren’t configured correctly in NetSuite, both recognized revenue and RPO will be misstated.

Key indicators of a revenue operations gap include: a CRO and CFO who report different ARR figures without a clean explanation; account managers who require finance involvement to quote mid-contract changes; ramp deals that aren’t configured for even recognition in NetSuite; and swap credits calculated from invoice amounts rather than recognized revenue positions. Ask to see the reconciliation spreadsheets. Ask what the audit cost and what it focused on. Any of these suggest the business is not built to scale its revenue operations without adding headcount.

When a deal bundles multiple products or services, ASC 606 requires the total contract value to be allocated across each component based on standalone selling price. This means the recognized value of any individual product may be significantly different from what appears on the invoice. When a customer swaps that product mid-contract, the credit owed is based on the remaining recognized value, not the invoiced amount. Sales teams working from Salesforce data don’t have access to the post-allocation position, which means they routinely over-issue credits without knowing it.

Continuous closes the seven-record gap between Salesforce and NetSuite by tracking the full deal lifecycle from opportunity through revenue recognition and feeding the current revenue position back into Salesforce automatically. This means swap credits are calculated from financial truth, ramp recognition is structured correctly from inception, and bookings, billings, and revenue reconcile in one place. For PE operators, the result is a portfolio company whose ARR reporting reflects recognized reality rather than commercial activity — without adding headcount to maintain it.

Get a demo

Ramps and Swaps 101: Easy Math, Hard Execution, Real Cost

Posted on March 3, 2026 by - Quote-to-Cash

Continuous Insights_Ramps & Swaps 101

Owen Karlsson

Why the Math Is Easy, the Execution Isn’t, and Both Are Costing SaaS Companies More Than They Realize

For CFOs, CROs, and RevOps leaders at mid-market SaaS companies: learn why ramps and swaps cause bookings, billings, and revenue to diverge in Salesforce and NetSuite — creating margin leakage, RPO reporting gaps, and a finance team reconciling numbers that should never have drifted.

TL;DR
- Ramps (multi-year step-up deals) and swaps (mid-contract product exchanges) are standard in B2B SaaS — but they create a structural gap between what Salesforce records as booked and what NetSuite recognizes as earned under ASC 606.

- Post-allocation, the financial value of a product sits seven records deep in NetSuite and never flows back to Salesforce. When account managers quote swap credits from invoice math instead of recognized revenue, companies silently donate 1–3% of ARR annually.

- The reporting consequences compound: ARR reflects bookings rather than recognized revenue, RPO is understated when ramp deals aren't configured correctly, and the CRO and CFO are reconciling different numbers with no clean explanation for the delta.

- Fixing this requires being native to both Salesforce and NetSuite — not integrated through middleware or synced on a schedule, but embedded in the transaction and revenue layers of both systems simultaneously. That's what Continuous is built to do.

Ramps and swaps are two of the most common contract structures in B2B SaaS — but two of the most reliably painful to execute. A ramp is a multi-year deal where the price increases each year: for example, a customer commits to $20,000 in year one, $25,000 in year two, $30,000 in year three. A swap is a mid-contract product exchange: a customer returns the unused portion of what they bought and applies the credit toward something different. Both are standard. Both are expected. And both have a way of breaking things that shouldn’t break.

Consider this scenario. A customer calls their account manager. They’ve been on Product A for six months and want to upgrade to Product B. They expect a credit for what’s left on their current contract. It seems straightforward. The account manager agrees. They go to build the quote.

However, in most mid-market SaaS companies, what actually happens is more complicated than a three-day delay. The account manager calls finance, who is buried in month-end close. But even when the number comes back, it may not be what anyone expected. The implementation, training, or support services bundled into the original deal — discounted or included at no cost — were still allocated a portion of the contract revenue at the time of booking. The account manager never knew. They see what the customer paid, estimate the remaining value, and build the quote on a number that was never accurate to begin with. Add in the days that have elapsed since the swap request came in, and the proration has shifted too. The number is wrong twice over. The customer is frustrated. The deal is delayed. And everyone involved is doing work that, in a properly architected system, no human should have to do at all.

This is the ramps and swaps problem. Not a math problem. Not a people problem. A systems problem — one that most companies quietly absorb by building a RevOps team whose real job, underneath the title, is cleaning up the accounting side effects of deals the systems were never designed to handle.  What sales sees on an opportunity and what finance is actually recognizing in NetSuite are separated by seven records. That’s not a gap. That’s where margin goes to die.

Why Do Ramps and Swaps Leave Sales Flying Blind and Finance Cleaning Up the Mess?

To understand why this breaks, you have to understand what happens to a deal after it closes.

When an opportunity closes in Salesforce, the booking reflects what was sold: the price on the quote, the products on the order. That’s the number sales owns. It’s clean, it’s simple, and it’s already out of date by the time the deal reaches NetSuite.

In NetSuite, two things happen that Salesforce will never see. The first is allocation. When a deal includes a software license and a professional services engagement — even if the implementation was “free” — the revenue has to be distributed across both components based on their standalone value, not what the invoice says. A deal booked as $50,000 for software and zero for services might become $30,000 for software and $20,000 for services once NetSuite applies allocation. The invoice wasn’t wrong. The revenue treatment just reflects the economic reality of what was delivered.

The second is recognition timing. A ramp deal — $20,000 in year one, $25,000 in year two, $30,000 in year three for the same product — can’t be recognized as billed. The total contract value has to be spread evenly, because you’re delivering the same thing each year. So you recognize $25,000 annually regardless of what the invoice says. Year one generates an unbilled receivable. Year three generates deferred revenue. None of this is visible in Salesforce.

The portion of that total contract value not yet recognized is what’s known as Remaining Performance Obligation, or RPO. For a three-year ramp deal, RPO represents the revenue the business is committed to deliver but hasn’t yet earned. It’s a number that matters enormously to investors and auditors, and one that’s almost impossible to report accurately when ramp deals aren’t configured correctly in NetSuite from the start.

“The post-allocation financial picture that lives in NetSuite never makes its way back to Salesforce. In 99% of cases, only the most sophisticated organizations manage to close that gap — and they’ve had to build it themselves.”

So when the account manager goes to quote a swap, they’re working from the Salesforce number — what was originally booked. The actual remaining recognized value is a different number, sitting in NetSuite, accessible only to someone who knows where to look and has time to pull it. The gap between those two numbers is where margin goes to disappear. Sales closes the deal with the wrong credit. Finance inherits the mess: reconciling recognition patterns the sales rep never knew existed, after a deal that can no longer be unwound.

What Does It Really Cost When Ramps and Swaps Go Wrong?

The most immediate cost is margin leakage — and it’s more common than most finance teams realize. When a customer wants to swap products and the account manager calculates their credit as $25,000 because that’s what six months of a $50,000 contract looks like on paper, but the actual remaining recognized value is $15,000 because of how allocation was applied, the business has two choices. Get finance involved, slow the deal down, and try to explain to the customer why they’re getting less credit than expected. Or just give them the $25,000, close the deal, and eat the $10,000 difference. And it’s worth being clear about what’s actually happening here. The rep isn’t cutting corners — they’re working with the only number available to them. When systems aren’t architected to surface the real revenue position, over-crediting isn’t a training problem or a process failure. It’s the predictable outcome of asking people to make financial decisions without financial data. The rep trades margin for a fast quote. The customer gets their answer. The business absorbs a loss it didn’t know it was taking.

Most companies, most of the time, take the path of least resistance. They don’t have a process that makes the right answer easily available, so they default to the wrong one. Across PE-backed SaaS companies, it’s common to see 1 to 3 percent of ARR effectively donated this way each year — purely because swap credits are based on invoice math instead of recognized revenue. That’s not a rounding error.

“When a swap credit should be $15,000 but the sales rep can only see the invoiced number, companies are often cornered into issuing $25,000 and eating the $10,000 difference. It happens constantly. It’s not an edge case. It’s the hidden cost of two systems that don’t talk to each other.”

Beyond the immediate margin hit, the reporting consequences compound over time. When a customer’s recognized revenue drops mid-contract because a swap was executed at the wrong value, it shows up in the CFO’s monthly report as an unexplained ARR decrease. Weeks after the fact. Long after anyone could have done anything about it. Revenue forecasts drift. ARR reporting reflects bookings rather than recognized revenue. The gap between what the CRO thinks the business is doing and what the CFO knows it’s doing widens with every quarter.

For PE-backed companies, the stakes are higher still. Covenant compliance, investor reporting, and the credibility of the management team all depend on financial numbers that reconcile, including RPO, which investors increasingly scrutinize as a forward indicator of revenue health. When they don’t, the conversation shifts long before the board asks a question. Executives are defending numbers instead of discussing growth. The CRO and CFO are reconciling versions of reality instead of aligning on what’s next. By the time someone asks why bookings, billings, and revenue don’t line up, the credibility cost has already been paid.

Why Can’t Your Systems Handle Ramps and Swaps Automatically?

Because the revenue position that matters sits seven records deep in a system the sales team never touches. A deal moves through a chain: opportunity in Salesforce, order line in Salesforce, sales order in NetSuite, sales order line in NetSuite, revenue element, recognition plan, journal entries over time. By the time allocation has been applied and recognition has begun, the number that’s relevant for a swap or a ramp reconciliation is buried at the end of that chain. No existing tool has been built to traverse it automatically and send the answer back.

To get that number back to the person quoting the deal, someone has to manually bridge the gap. Call finance. Run a report. Export a spreadsheet. In organizations that have tried to build this themselves, it typically means a sales ops person who has a standing relationship with someone on the revenue team and knows to call before month-end when the queue is manageable. That’s not a process. That’s a workaround with a name badge.

The reason no one has solved this systematically is that it requires being native to both systems simultaneously — not integrated with them or synced to them on a schedule, but genuinely embedded in the data layer of both Salesforce and NetSuite. Most tools live on one side of that boundary. The revenue data lives on the other.

“Most quote-to-cash stacks stop caring about revenue the moment the invoice goes out. Everything after that gets handed to finance and forgotten. To take the final answer on that revenue element and tie it seven records back to the opportunity in Salesforce — and have a system send that answer back automatically — No one had built that yet. Until now. That’s what Continuous solved.”

How Does Continuous Solve the Ramps and Swaps Problem?

Continuous operates at the architectural boundary between Salesforce and NetSuite, embedded in both systems’ transaction and revenue layers, not bolted on through middleware or nightly syncs. It tracks the full lifecycle of a deal from opportunity through allocation, recognition, and journal entry, keeping the revenue position accurate in real time across both systems.

For swaps, that means the account manager sees the actual remaining recognized value before they build the quote. Not invoice math. Not a CPQ estimate. The number pulled directly from post-allocation accounting. Credits reflect financial reality, finance doesn’t get a phone call, and margin doesn’t quietly erode.

More importantly, the system enforces alignment. Revenue logic is embedded directly in the quoting flow, so sales cannot issue credits that exceed what has actually been earned. The gap between bookings and recognized value closes before it ever becomes a reporting problem.

For ramps, Continuous structures recognition correctly from the start and recalculates automatically when a contract changes. Allocation, deferred revenue, and billing schedules stay aligned without manual intervention. No surprises when a ramp year turns over, no reconciliation required when a customer modifies mid-term.

The same infrastructure governs amendments, credits, true-ups, and hybrid pricing models, absorbing commercial flexibility into system design rather than leaving finance to reconcile it after the fact.

On the reporting side, bookings, billings, and revenue reconcile structurally. The CRO and CFO operate from the same source of truth. ARR reflects recognized reality. Mid-contract changes surface in forecasts immediately, not six weeks later.

Continuous isn’t another billing tool. It’s embedded revenue infrastructure built to close the seven-record gap automatically — so ramps and swaps execute cleanly, accurately, and without hidden margin loss

Ready to learn more? See how Continuous ensures your revenue position is always accurate, in both systems, in real time.

Schedule a Demo

Frequently Asked Questions (for FAQ section)

What are ramps and swaps in SaaS contracts?

A ramp is a multi-year contract structure where the price increases by a pre-negotiated amount each year. For example, a customer might pay $20,000 in year one, $25,000 in year two, and $30,000 in year three for the same product. A swap is a mid-contract product exchange where a customer returns the unused portion of an existing product and applies the remaining credit toward a different one. Both are common in B2B SaaS and both create significant complexity when it comes to revenue recognition and billing.

Why do ramps and swaps cause problems in NetSuite?

NetSuite applies revenue allocation and recognition rules that change the financial value of a product after a deal closes. A ramp deal that bills at different amounts each year must be recognized evenly across the contract term under ASC 606. A bundled deal with a free implementation must allocate value across each component based on standalone selling price. These adjustments happen entirely in NetSuite and are never reflected back in Salesforce, creating a disconnect between what sales knows and what finance knows.

What is the difference between bookings, billings, and revenue recognition?

Bookings are the total value of deals closed, typically recorded in your CRM on the day the contract is signed. Billings are the amounts actually invoiced to customers, which may follow a different schedule. Revenue recognition is the amount recorded as earned revenue under ASC 606, which depends on when and how value is delivered. For a ramp deal, all three numbers can be different in the same year: you might book $75,000, bill $20,000, and recognize $25,000. Understanding the difference is critical for accurate ARR reporting and financial forecasting.

How does revenue allocation affect swap credits?

When a deal includes multiple products or services, NetSuite allocates revenue across each component based on standalone selling price, regardless of how the invoice was structured. This means the recognized value of a product can be materially different from what appears on the quote. When a customer goes to swap that product, the credit they are owed should be based on the remaining recognized value, not the invoiced amount. If sales quotes the swap using the invoiced figure, the company may issue a larger credit than it has actually earned, resulting in direct margin leakage.

Why does ARR drop when a customer swaps products?

ARR can drop after a swap when the new ARR secured in the replacement product is less than the recognized ARR being retired from the original product. This often happens because the account manager is quoting based on the Salesforce booking value rather than the actual remaining recognized revenue position in NetSuite. The difference between those two numbers can be significant, and without visibility into the real revenue position, sales teams routinely offer more credit than the business has earned.

How can software companies automate ramps and swaps?

Automating ramps and swaps requires closing the data loop between your CRM and your ERP. The recognized revenue position for each product needs to flow back into Salesforce automatically so account managers have the right number before they quote. This means being native to both systems, tracking the full chain from opportunity through revenue element and recognition plan, and updating the revenue position in Salesforce as it changes over time. Continuous is built to do exactly this, eliminating the manual handoffs between sales and finance that slow deals down and introduce errors.

What is Remaining Performance Obligation and how do ramps affect it?

Remaining Performance Obligation, or RPO, is the total contract revenue a company is obligated to recognize in the future but has not yet earned. Under ASC 606, it represents the value of work still to be delivered on existing contracts. For ramp deals, RPO can be significant: a three-year ramp with $75,000 in total contract value has $50,000 in RPO at the end of year one. If ramp deals aren’t configured correctly in NetSuite — with even recognition across the full contract term — RPO will be understated, misrepresenting the company’s forward revenue position to investors, auditors, and the board.

Continuous Launches Continuous Control to Solve the Biggest Quote-to-Cash Challenge

Posted on February 25, 2026 by - Announcements

Continuous Control Revenue Intelligence Dashboard

The industry’s first certified product that seamlessly aligns CRM to ERP for complex hybrid subscription and advanced consumption revenue models.

MOUNTAIN VIEW, Calif., Feb. 25, 2026 /PRNewswire/ — Continuous Technologies, a leading provider of Quote-to-Cash applications, today launched Continuous Control, the industry’s first certified product delivering a unified Quote-to-Cash lifecycle for companies using Salesforce Agentforce Revenue Management (ARM) and NetSuite Financials and Advanced Revenue Management.

Modern SaaS and consumption monetization models, including AI, continuously change. Contracts are amended mid-term, consumption visibility makes every day a selling opportunity, customers upgrade, expand, or top-up. Yet as these lifecycle events move from CRM to ERP, financial context is lost. What should be seamless traceability between bookings, billings, and revenue instead breaks down in “the messy middle”—the operational gap between what was sold in CRM and what is invoiced and recognized in ERP.

“Finance still needs clean invoices, accurate revenue, and predictable closes.” said John Banks, Founder and CEO of Continuous. “Too often, ERP systems are an afterthought. Not because teams don’t care about Finance, but because Sales needs to remain agile to meet customer’s evolving needs. With Continuous Control, the ERP is unified with the CRM from the beginning, eliminating that operational pain and improving operational efficiency.”

This new offering is pre-built to eliminate implementation pain and pre-configured with use cases enabling teams to test and launch new revenue models in days. Continuous Control reduces time-consuming CRM-ERP integration costs along with ongoing maintenance and monitoring costs. Continuous Control is already operating in production with several enterprise customers who have reported a seven-figure reduction in operational costs.

“With Continuous, finance stopped looking backward and became a true thought partner in driving growth,” said Steve Finley, Chief Financial Officer of ACI Learning. “Keeping NetSuite at the center was critical. Continuous allowed us to preserve financial integrity while increasing commercial flexibility.”

 Continuous Control enables:

  • Traceability for bookings, billings, and revenue so Finance can confidently close the books
  • Out of the box support for selling models from Salesforce Agentforce Revenue Management and Salesforce CPQ
  • Invoicing and revenue recognition to work as designed in ERP from the Sales Order, out of box
  • Lifecycle changes to execute correctly without manual rework and complex customizations in ERP
  • Future-proofed to test and launch new AI revenue models with clicks, not code
  • Reduced audit risk with detailed linkage across all sales transactions for all customer lifecycle changes over time.

Continuous Control is live with customers and available today in Essentials, Enhanced, and Enterprise editions — designed to scale from simple subscriptions to complex, usage- and consumption-based models.  Access Continuous Control via continuoustech.com, in the Salesforce AppExchange, or on the NetSuite SuiteApp.

Learn more:

Request a Demo
Download the Datasheet

About Continuous Technologies
Continuous helps companies modernize and future-proof their Quote-to-Cash process directly inside Salesforce and NetSuite. By embedding pricing, usage, and credit models into the platforms teams already use, Continuous eliminates the need for a standalone billing system or complex custom integration logic and helps companies innovate faster with reduced operational costs.

With Continuous, Sales can quote any selling model, Finance gains confidence in forecasts and compliance, and Product can launch new pricing and packaging strategies without bottlenecks.

Founded in 2021 and built by veterans of Salesforce, Zuora, and Conga, Continuous makes modern pricing models simple to operationalize. Trusted by companies that span industries, Avalara, Dynatrace, Aurora Solar, Dwolla, Global Switch, Concord Technologies, and many more rely on Continuous for Quote-to-Cash success.

Link to the original release.

Making NetSuite Work for Modern Finance Teams: A Q&A with Caitlin Swofford

Posted on February 2, 2026 by - Company News

Continuous Insights_ Quote-to-Cash conversation with Caitlin Swofford, VP of Solution Delivery

Rachel Bruce

A Q&A for finance and RevOps leaders on delivery, embedded revenue infrastructure, and how to fix quote-to-cash in NetSuite without adding risk or new systems.

TL;DR
- Quote-to-cash breaks when finance teams are forced to manage complexity across disconnected systems.
- Adding another billing or monetization platform increases delivery risk instead of reducing it.
- Embedded revenue infrastructure keeps Salesforce and NetSuite aligned without spreadsheets or manual handoffs.
- Continuous helps finance teams support modern pricing models while maintaining control, auditability, and trust in the numbers.

Continuous is scaling its NetSuite presence and strengthening delivery to match. Caitlin Swofford, VP of Solution Delivery at Continuous, brings deep experience spanning NetSuite administration, Salesforce, enterprise applications, consulting, and engineering leadership.

Her focus is simple. Help finance teams make quote-to-cash work as pricing models grow more complex, without adding more systems, risk, or spreadsheet-driven workarounds.

We sat down with Caitlin to talk about what drew her to Continuous, how she approaches delivery as a strategic lever, and what it really takes to make NetSuite work for modern finance teams.

You’ve had a unique path into NetSuite. What led you here?

I didn’t start in finance or ERP. I started in marketing operations and marketing technologies, working with tools like Marketo, Eloqua, and even Siebel CRM early on. My first exposure to NetSuite came in a high-growth environment, and the more I saw it, the more intrigued I became. It was powerful, configurable, and deeply connected to how the business actually runs.

When an opportunity opened up to step into a NetSuite administrator role, I jumped at it. From there, I expanded into owning broader enterprise applications, including NetSuite and Salesforce, with a strong focus on compliance, change management, SDLC, and segregation of duties. Later, I shifted into consulting and services, partnering directly with customers to implement and optimize NetSuite in real-world environments.

That mix of being both a system owner and a services partner really shapes how I think about delivery today.

What made Continuous the right next step?

Two things stood out to me. The people and the product.

Culture matters a lot to me, especially as a remote worker. I want to feel like I’m part of a team moving in the same direction and building something meaningful. Continuous gave me that feeling from day one.

The product mission was equally compelling. I’ve seen how often quote-to-cash becomes a bottleneck as pricing models evolve. What stood out is that Continuous is not about adding another system. It is about improving how the systems finance teams already rely on work together.

How do you explain Continuous Revenue Fabric to finance leaders dealing with complexity across Salesforce and NetSuite?

I think of Revenue Fabric as something that embeds into your existing tools and helps them work together the way they were meant to.

If sales is quoting in Salesforce and finance is managing orders, billing, and revenue in NetSuite, those systems often don’t speak the same language, especially with usage-based or hybrid pricing. Continuous Revenue Fabric enables that flow end to end so sales can stay in Salesforce, finance can stay in NetSuite, and the handoffs actually work without forcing teams into a third standalone system.

Why does embedded revenue infrastructure matter from a delivery perspective?

From a delivery standpoint, the biggest risk I see is introducing more complexity in the name of solving complexity.

Standalone billing platforms often introduce a separate operating layer with their own logic, workflows, and reconciliation processes. Even when data syncs back to Salesforce or NetSuite, teams still end up managing pricing rules, billing behavior, and exceptions outside the systems they rely on day to day. That fragmentation is where delivery risk shows up.

Embedded infrastructure keeps the flow where it belongs, between the systems finance and sales already trust. That leads to cleaner implementations, fewer points of failure, and more confidence in the numbers downstream.

Where do you most often see misalignment between sales and finance?

Sales and finance are working on the same deal, but with very different objectives. Sales needs speed and flexibility to support the customer and close the deal. Finance needs clean, auditable data they can rely on to bill, recognize revenue, and close the books.

Misalignment shows up when processes force extra work. Fields that exist just because, manual handoffs, or one-off steps that don’t reflect how the business actually sells. The fix is treating quote-to-cash as one continuous motion so both teams get what they need without unnecessary workarounds.

As VP of Solution Delivery, what are you focused on building right now?

My focus is on helping customers be successful with Continuous, not just at go-live, but over the long term.

That means partnering closely with customers to understand how they actually use NetSuite and Salesforce, making sure implementations reduce risk instead of adding it, and helping teams build a foundation they can scale as their business evolves. Success looks like trust in the system and confidence in the data.

What excites you most about the opportunity ahead for Continuous?

There are so many companies running on NetSuite and Salesforce that still struggle to make quote-to-cash work smoothly, and that complexity is only increasing.

Continuous has a real opportunity to help finance teams simplify that reality through cleaner handoffs, less manual work, and a more connected view of revenue. Helping customers build that foundation and grow on top of it is what excites me most.

Finally, outside of work, what’s something people would be surprised to learn about you?

I recently became certified as a Maine Master Naturalist, a ten-month program focused on nature education. I volunteer with a wildlife rehabilitation center, and my areas of focus are birds and mammal tracking. It’s what I spend a lot of my nights and weekends doing.

As Continuous continues to grow in the NetSuite ecosystem, Caitlin is helping shape how the company shows up for finance teams that need more than another system. Her focus is clear. Make NetSuite work the way modern finance teams need it to work. Reduce risk in delivery. Simplify quote-to-cash. And build a foundation that supports scale as revenue models evolve.

It’s a delivery-first approach grounded in real-world experience, and one that reflects Continuous’ broader commitment to helping finance teams move from managing complexity to driving confidence and growth.

Connect with Caitlin on LinkedIn.

Scaling Smarter: A Q&A with Owen Karlsson on Joining Continuous

Posted on January 12, 2026 by - Company News

Continuous Insights_Quote-to-Cash Conversation with Owen Karlsson, SVP NetSuite Solution Management

Rachel Bruce

A Q&A for finance, RevOps, and systems leaders on Owen Karlsson joining Continuous, scaling NetSuite revenue operations, and fixing quote-to-cash across Salesforce and NetSuite.

TL;DR
Owen Karlsson joins Continuous as SVP of NetSuite Solution Management.
- He brings deep NetSuite and ARM expertise, including leading ASC 606 conversions.
- His focus is scaling revenue operations and connecting Salesforce and NetSuite.
- Continuous aims to close the gap between sales creativity and finance execution.

____________________________________________________________________________

Owen Karlsson, Senior Vice President of NetSuite Solution Management, joins Continuous with more than a decade in the NetSuite ecosystem, spanning operations, professional services leadership, and hands-on revenue management. He was the first person globally certified on NetSuite Advanced Revenue Management (ARM) and has led dozens of revenue conversion and optimization projects for software companies.

At Continuous, he will help advance the company’s mission to fix quote-to-cash in Salesforce and NetSuite, bridging two of the most critical systems in modern revenue operations.

What does your new role at Continuous entail, and where will you focus first?

The title is Senior Vice President, NetSuite Solution Management. In the short term, I’m bringing a group of NetSuite customers I’ve supported for years into the Continuous family and making their transition smooth: same responsiveness, same results.

From there, I’ll focus on three things. First, building strong NetSuite relationships, navigating Oracle’s partner ecosystem and keeping efforts aligned. Second, supporting sales and credibility by joining customer conversations where deep finance knowledge helps move things forward. And third, shaping product direction, especially around revenue management. 

We’re solving business-critical problems today and expanding the number we can solve tomorrow, and that’s how you scale impact.

Give us the quick version of your path into NetSuite.

I first got to know NetSuite at Rapid7 in 2012, where it ran both CRM and ERP in a complex, heavily customized setup. I started as a user, moved into an admin role, and was there when the company went public. Later I joined Zone & Co as one of the first hires. We grew from a small services firm into a product-led company after customers asked us to tackle usage and variable billing. I led professional services, operations, and later built out the knowledge and training side of the business. That experience taught me that the best users are the ones who can self-educate, and if you don’t build for that, you’ll never have power users.

Most recently I founded OK Consulting, and through ongoing work with Avalara, I met John Banks and the Continuous team.

Fun fact: I was the first person globally certified on NetSuite Advanced Revenue Management (ARM) and led around 50 ASC 606 revenue conversion projects, mostly for software companies.

How does your experience scaling operations and leading professional services inform how you’ll approach this new role?

At Zone, I helped grow the services organization and then built a team to implement a new billing product while keeping traditional NetSuite projects healthy. Later, as Chief Knowledge Officer, I focused on customer enablement, building a public knowledge base and training program so people could solve problems faster.

That mix of delivery discipline, enablement, and scalable processes is how I’ll operate here. The goal is always the same: build solutions that scale as fast as the business does.

What attracted you to Continuous and this next chapter in your career?

Honestly, it was John Banks and the team. I wasn’t looking to make a move, but the way John talked about the company, the culture, and the opportunity really stood out.

Continuous brings together deep Salesforce and NetSuite expertise. It felt like a natural fit, a team that thinks big, moves fast, and loves building. Salesforce and NetSuite are the two giants of the cloud, and Continuous sits right between them. Fixing quote-to-cash across those systems isn’t just the goal, it’s the mission.

Continuous’ mission is to fix quote-to-cash in Salesforce and NetSuite. Why is this challenge so important right now, and what makes Continuous uniquely positioned to solve it?

Sales creativity always outpaces systems. Every few years, there’s a new sales motion like subscriptions, usage, credits, or consumption, and sales can start selling it long before finance can operationalize it. That gap is where the friction lives. The companies that win are the ones whose systems evolve just as fast as their go-to-market.

Continuous was built to close that gap, to fix quote-to-cash in Salesforce and NetSuite so companies can sell however they want without breaking the back office. We already handle prepaid and credit models really well, and we’re expanding into more complex revenue motions without adding unnecessary complexity. The more flexible we make quote-to-cash, the more confidently our customers can grow.

You’ve worked across every phase of the NetSuite lifecycle. What are the biggest opportunities for improvement you see in how companies manage finance and revenue today?

Most companies still have too many disconnected processes between sales and finance. Every manual step, rekeying data, duplicating orders, or reconciling invoices, adds friction and limits scale. The big opportunity is to build connected, auditable systems that keep up with how the business actually sells. When that happens, revenue operations stop reacting and start driving growth.

AI is reshaping every step of quote-to-cash, from forecasting and pricing to billing and revenue recognition. Where do you see the biggest potential for automation and intelligence to create real business value?

The biggest shift will come from AI-driven consumption models, where credits or usage for AI features become billable SKUs. That changes how companies price, forecast, and even pay commissions.  I’m optimistic about AI as a productivity multiplier, but cautious about unchecked automation in finance. The key is systems that support new pricing models safely, accelerating innovation without sacrificing accuracy.

Finally, when you’re not thinking about finance and optimization, how do you like to spend your time?

Sports, golf, family, and my dog. I’m a lifelong New York sports fan, Yankees, Giants, Knicks, Rangers, and a proud uncle to five nieces and nephews. That’s my favorite title, honestly.

Owen’s deep NetSuite experience, operational discipline, and product vision strengthen Continuous’ mission to fix quote-to-cash in Salesforce and NetSuite, helping companies scale revenue operations with confidence.

As he puts it, sales creativity always outpaces systems, and Continuous exists to close that gap.

The Year Companies Finally Fix Quote-to-Cash: 9 Predictions for 2026

Posted on January 6, 2026 by - Quote-to-Cash

Embedded Revenue Infrastructure

John Banks

Nine predictions for finance, RevOps, and systems leaders on how quote-to-cash becomes core infrastructure as hybrid revenue models redefine operations in 2026.

TL;DR
- In 2026, quote-to-cash becomes core business infrastructure, not a system you rebuild every year.
- Hybrid revenue models expose the cracks between Salesforce and NetSuite faster than teams can patch them.
- Embedded revenue logic replaces stacked tools, fragile integrations, and constant reimplementation.
- Companies that connect revenue end-to-end will price faster, bill cleaner, and scale with confidence.

The next year will redefine how companies manage quote-to-cash across Sales, Finance, Product, and Pricing. With hybrid and consumption-based models now the standard, it’s clear that most organizations weren’t built to support them. 2026 is about closing that gap.

The focus will shift to making these models operational, whether by modernizing legacy systems or building new architectures designed for what’s next. And success will depend on keeping everything connected through a single source of truth. That means keeping Sales in Salesforce, Finance in NetSuite, and revenue data perfectly aligned between them.

When that alignment doesn’t exist, the cracks show up fast. Usage, credits, commitments, and multi-year deals expose the gaps between CRM and ERP, forcing teams into custom code, spreadsheets, or one-off billing pilots just to keep deals moving and invoices accurate.

Continuous exists to solve that problem. We run directly inside Salesforce and NetSuite, providing a shared revenue layer that keeps pricing, lifecycle changes, usage, and financial impact connected end to end, whether a company is extending what it has today or preparing for what comes next. Here’s what we see coming in 2026.

1. Quote-to-Cash Becomes Essential Business Infrastructure

In 2026, companies will stop treating quote-to-cash as a project and start treating it as mission-critical infrastructure. The 12 to 18 month rebuild cycle can’t keep up with how fast pricing and go to market strategies evolve, and teams are tired of redoing the same work every year.

This is the year revenue logic moves inside the systems that already run the business, Salesforce and NetSuite, instead of relying on disconnected tools and fragile integrations. When pricing, product, and revenue logic live inside the core systems, companies can evolve how they sell and bill without breaking downstream finance every time monetization changes.

The most resilient companies will take this approach, eliminating the middleware tax that has slowed transformation for years.

2. Companies Stop Adding Revenue Systems and Embed Revenue Logic Instead

In 2026, companies will stop trying to solve quote-to-cash complexity by adding more systems. Years of layering CPQ, billing, usage tools, and reporting platforms have created duplication everywhere. Change one thing in pricing or packaging, and suddenly CRM, billing, revenue recognition, and reporting all need to be updated separately.

That approach won’t hold. Leading teams will focus on aligning how Salesforce and NetSuite handle pricing, usage, entitlements, and lifecycle events instead of expanding the stack. This alignment becomes critical as businesses introduce more hybrid, consumption, and commitment-based models.

This shift gives rise to embedded revenue infrastructure. Rather than introducing another standalone billing or monetization platform, companies will embed revenue logic directly into the systems they already run. The result is a shared revenue foundation that supports complex quote-to-cash without duplication, constant rework, or fragile integrations.

3. Hybrid Revenue Models Become Table Stakes

In 2026, hybrid revenue models will no longer be a competitive advantage. They will be the baseline. Subscriptions, usage, credits, commitments, and overages will coexist inside the same customer relationship, and companies will be expected to support all of them at once.

The difference will be execution. Leading companies will design their quote-to-cash architecture to handle multiple revenue motions simultaneously instead of optimizing for a single model. Teams that can operationalize this complexity will forecast more accurately, bill with fewer exceptions, and give customers clear visibility into what they’ve bought and consumed.

Companies that can’t will feel the impact quickly, not in pricing strategy debates, but in broken billing, unreliable forecasts, and frustrated customers.

4. Entitlements Become the Glue Between Sales, Product, and Finance

In 2026, entitlements become the new source of truth. Companies will be forced to reconcile what customers actually bought with what they actually have. Entitlements evolve into the connective tissue linking quoting, provisioning, billing, and renewals.

If your entitlement data is wrong, every downstream motion is wrong. The most effective teams will treat entitlements as infrastructure, not afterthoughts, keeping sales, product, and finance in sync and every renewal accurate. Clean entitlements mean clean revenue.

5. Finance Moves Upstream and Sets the Guardrails for Quote-to-Cash Design and Architecture

As revenue models become more complex, informal rules and downstream cleanup no longer scale. Pricing logic, usage handling, entitlements, and lifecycle changes carry immediate billing and revenue recognition implications. When those rules live in spreadsheets, custom code, or disconnected systems, finance is left reacting after problems appear.

In 2026, companies respond by formalizing quote-to-cash rules inside the systems that run the business. Pricing, usage, entitlements, and lifecycle constraints are embedded and enforceable, applied consistently from deal design through financial reporting. This shift makes governance possible upstream instead of downstream.

As a result, finance is no longer brought in after deals are designed. It is involved upfront, setting the constraints that quote-to-cash solutions must meet. Sales and RevOps still design deals, but they do so within guardrails that ensure billing, revenue recognition, and audit requirements are met by default.

6. Cleanup Beats Quote-to-Cash Reimplementation

Salesforce CPQ’s end-of-sale will tempt teams to blow everything up. In 2026, the smartest companies will resist that urge. Instead of launching massive quote-to-cash reimplementation projects, they will improve what they already have.

These teams will modernize in steps: clean the catalog, return to out-of-the-box where possible, embed the right logic, and move to Revenue Cloud Advanced when they are ready. Companies that attempt giant, multi-year reimplementations will spend 2026 managing risk and overruns instead of delivering business value.

Cleanup beats reimplementation every time.

7. The 60-Second Rule: Data Transparency Defines the Next Market Leaders

In 2026, data trust becomes the ultimate differentiator. Boards, investors, and executives will expect revenue answers on demand, not after days of reconciliation. The companies that can trace every deal from quote to contract to invoice to revenue in under 60 seconds will earn the confidence of their boards, investors, and markets alike.

Clean revenue lineage evolves from operational hygiene to strategic foresight. Teams will stop treating traceability as a reporting exercise and start designing for it upfront. With connected data architectures uniting bookings, billings, and revenue, finance shifts from proving what happened to driving what comes next, anchored in truth rather than assumptions.

8. The Rise of the Revenue Architect

A new role is emerging inside scaling organizations: the Revenue Architect. Equal parts business analyst, systems thinker, and finance translator, these leaders will bridge the gap between CRM and ERP, guiding architecture decisions that last. In 2026, companies that empower this role will build cleaner systems and scale faster than those that do not.

9. Companies That Rapidly Innovate Pricing Will Dominate and Grow

In 2026, pricing agility becomes the new growth lever. The fastest teams will stop treating pricing changes like mini transformations and start shipping new models continuously: commits, credits, outcomes, and more, all without breaking quoting or billing.

Companies that can do this will outpace competitors and compound growth. If you can’t change pricing fast, you won’t compete with companies that can.

What This Means for 2026

In 2026, companies that treat quote-to-cash as connective infrastructure will move faster, price more creatively, and operate with confidence across sales and finance. Those that continue to rely on fragmented systems, manual workarounds, and downstream cleanup will struggle to keep up.

Continuous helps leading organizations operationalize complex revenue models by embedding the revenue infrastructure that connects Salesforce and NetSuite, so change is possible without breaking billing, revenue, or trust.

____________________________________________________________________________

About Continuous

Continuous helps B2B companies modernize and future-proof quote-to-cash directly inside Salesforce and NetSuite. By embedding pricing, usage, and credit models into the core systems of record, Continuous creates a single, shared source of truth across sales and finance.

With Continuous, companies can support complex revenue models without adding new systems, breaking downstream finance, or re-implementing quote-to-cash every time the business changes. The result is faster monetization, cleaner revenue, and confidence that what sales sells can actually be billed, recognized, and reported accurately.