Tag: Revenue Operations

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.

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.

How Continuous Scales Without Slowing Down: A Q&A with Ruslan Saliei

Posted on January 27, 2026 by - Company News

Continuous Insights_ Quote-to-Cash conversation with Ruslan Saliei, Director of Program Management

Rachel Bruce

A Q&A for product, delivery, and operations leaders on how Continuous builds operating discipline, predictable delivery, and scalable execution as the company grows.

TL;DR

- Continuous is deliberately building internal delivery rails that keep product development and customer delivery work moving in sync.
- Strong program management improves visibility, prioritization, and time to production as complexity increases.
- Customers experience this as faster execution, clearer communication, and predictable delivery—even as Continuous scales.

____________________________________________________________________________

Scaling a company is not just about what you build. It’s about how you build it.

As Continuous grows, building strong operating rhythms behind the scenes becomes just as important as the products delivered to customers. That is where Ruslan Saliei, Continuous’ Director of Program Management, comes in.

Ruslan has built his career at the intersection of technical delivery, program management, and operational leadership. From leading scaled Agile teams in a high-growth e-commerce environment across Southeast Asia to running a revenue-driving delivery practice at a B2B commerce integration firm, he has repeatedly helped teams move faster with more clarity and less chaos.

At Continuous, Ruslan is focused on building the internal operating rails that help product and delivery move in sync, improve visibility and prioritization, and ultimately shorten the path from idea to production.

We sat down with Ruslan to talk about his background, what drew him to Continuous, and how strong program management translates into a better customer experience.

Tell us about your background. How did you build your career across program management, product, and technical delivery?

I’ve worked in IT management since graduating from university. I have a master’s degree in computer science, and early on I thought I would become a software engineer. I quickly realized that while I understand technology, my real strength is working with people and systems — building teams and improving how work gets done.

I started my career in ad agencies in Ukraine, delivering full-cycle work for large brands. That experience gave me a strong foundation in how businesses operate and how cross-functional teams collaborate. From there, I moved to Southeast Asia to join Lazada, part of Alibaba Group, which was building an Amazon-like platform for the region.

At Lazada, I led an engineering and QA organization of more than 100 people responsible for the web experience. Operating at that scale required strong delivery practices and operating models, especially with many dependent teams moving in parallel.

Later, I joined Zaelab, a B2B commerce integration firm, where I progressed from delivery management into portfolio leadership and eventually led the company’s largest revenue-driving practice. That experience reinforced a core belief of mine: high performance and predictable delivery don’t happen by accident — they’re built through intentional operating discipline.

What brought you to Continuous, and why was now the right time?

I’d previously worked with Jon Pora, now Vice President of Professional Services at Continuous, and as the company entered a new phase of growth, it was clear there was an opportunity for my background in scaled delivery and operating cadence to add value.

I was looking for a new challenge. I missed the energy of building in a startup environment, where you are inventing ways of operating, not just following an established playbook. Continuous has that energy. It is a growing company, a new domain for me, and the team quality really stood out.

People are a huge value metric for me. When the company is full of great people aiming for success, I want to be part of that.

What is your role as Director of Program Management, and what will you focus on first?

My main focus is improving time to production and strengthening the internal operational processes that help teams deliver consistently.

Continuous is moving fast, and my job is to make sure our operating cadence keeps pace so teams stay aligned and delivery stays predictable. That means creating clearer operating patterns and reusable flows, so teams have more alignment, less distraction, and clearer execution.

I will be working across product and customer projects, because much of what I do is internal operations, and improvements there benefit both. My role is not primarily client-facing. It is about being the glue internally so teams collaborate more effectively and delivery becomes more consistent.

I will also be working closely with the professional services organization to improve how product and delivery move together as we scale.

How does better program management translate into a better customer experience?

Improving visibility, traceability, and predictability across delivery translates directly into customer value.

When teams have a clearer view of requirements, priorities, and progress, customers experience more reliable timelines, clearer communication, and fewer surprises. Stronger operating rhythms allow us to plan, forecast, and manage change more effectively, which shortens the path from idea to production.

It also reduces the day-to-day burden on delivery teams by removing unnecessary manual work and ambiguity, allowing them to stay focused on execution. The result is a smoother delivery experience.

Where do you see the biggest opportunities to improve how Continuous scales product development and delivery at the same time?

One big opportunity is building clearer criteria and flows for how work created for a customer becomes part of the core product.

As we grow, we need a more transparent and scalable approach so decision-making stays consistent even as the volume of work increases.

Another priority is strengthening how we prioritize work across product investment and customer-driven initiatives so engineering has one clear operating cadence and teams spend less time context switching.

You’re based in Spain. How does that shape the way you support a global team?

Being based in Europe gives me a strong perspective on how global teams collaborate. I naturally sit between regions, which helps with continuity and communication across teams working in different time zones.

More importantly, it reinforces my focus on fundamentals. Regardless of geography, strong operating rhythms, clear processes, and good communication are what allow teams to move quickly and stay aligned.

What are you most excited about in this next chapter at Continuous?

I’m excited about growth and about learning a new domain. I have touched CPQ in previous work, and I see how important flexibility is becoming for companies. I also find modern billing models interesting, because so many companies want to be more flexible in how they package and price what they sell.

Most of all, I’m excited about the people. I’ve met strong individuals and personalities across the company, and that makes me want to commit fully and focus on making the team’s work easier and more effective.

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

I do motorcycle racing on superbikes. I’m also a certified rescue scuba diver. I do photography, play beach volleyball, and I’ve traveled to more than 50 countries. I spent several years living in Southeast Asia, including Thailand and Vietnam, and I still love that part of the world.

As Continuous grows, the difference between moving fast and scaling well is execution. Ruslan’s focus is on strengthening the operating discipline, cadence, and cross-team collaboration that allow product and delivery to keep pace with customer demand.

It’s the kind of intentional rigor that customers feel in the outcomes: faster time to production, clearer communication, and more predictable delivery, all built on a foundation that scales with the business.

Quote-to-Cash Conversations: Navigating CPQ EOS + What Comes Next

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

Salesforce CPQ and Continuous

Rachel Bruce

A recap for RevOps, Sales Ops, Finance, and Product leaders on CPQ end of sale, ARM readiness, and how to plan next steps without disrupting revenue.

TL;DR
- Salesforce CPQ end of sale does not require immediate migration, but it does require intentional planning. CPQ remains supported, giving teams a meaningful window to prepare.
- There is no direct upgrade path from CPQ to ARM. Revenue Cloud Advanced is a reimplementation with a different architecture, fewer guardrails, and greater operational responsibility.
- Most organizations succeed by modernizing in phases, extending CPQ where it makes sense while avoiding disruption to quoting, billing, and revenue workflows.
- Fragmenting quote-to-cash systems to “test” usage or consumption pricing often creates long-term reconciliation, reporting, and data integrity issues.
- Teams that plan now gain flexibility later, moving faster and with less risk when change becomes necessary.

In early 2025, Salesforce announced that CPQ would be end-of-sale. The news immediately raised questions across RevOps, Sales, and Product teams about what comes next.

As many companies approach the end of the fiscal year, that question still looms large. Budgets are being set. Roadmaps are being finalized. And for many teams, the refrain remains the same: What now?

To explore what CPQ EOS really means in practice, and how revenue teams should be thinking about next steps, John Banks, CEO and Founder of Continuous, sat down with John Garvens, Salesforce Revenue Cloud expert and Principal Architect at Garvens Consulting, for a live Quote-to-Cash Conversations discussion moderated by Rachel Bruce, VP of Marketing at Continuous.

Rather than fueling alarm, the conversation surfaced a more grounded reality. CPQ end-of-sale is not a cliff. It’s a runway. CPQ is still supported, the lights are not turning off tomorrow, and most teams have more time than they think. What has changed is the urgency to plan with intention.

Modern revenue models are putting new pressure on legacy quote-to-cash architectures. Hybrid pricing, credits, commitments, and usage-based monetization are no longer edge cases. They are rapidly becoming the default. If your business wants to experiment, launch, or scale those models, the real question is not simply what product comes next, but whether your quote-to-cash foundation is ready for where revenue is headed.

Quote to Cash Conversations with John Banks and John Garvens

▶ Watch the full recording

What follows is a curated recap of the most relevant insights from the conversation, focused on the choices revenue teams are weighing and what those choices mean in practice.

CPQ EOS is not a crisis, but it is a forcing function

End-of-sale does not mean end-of-life. CPQ is not disappearing overnight. The real risk is letting uncertainty turn into inertia, then finding yourself forced into a rushed decision later.

This period is best used as a planning window. It’s a chance to understand what actually lives inside your Salesforce org, how much of your revenue process relies on custom workarounds, and where friction has quietly turned into tech debt. Even teams that plan to stay on CPQ for several more years benefit from doing this work now, because preparation creates options.

Most companies are choosing one of three paths

While every environment is different, most teams navigating CPQ EOS tend to fall into one of three scenarios.

1. Stay on CPQ for now.
 Some teams will remain on CPQ for a period of time because budget, bandwidth, or organizational readiness make a near-term change unrealistic.

2. Start fresh in a contained scope.
 Others will implement newer tooling for a new product line, a new business unit, or a recent acquisition. This allows progress without disrupting the broader organization.

3. Take a phased bridge approach.
 Many teams will modernize incrementally, keeping the business running while gradually transitioning their quote-to-cash architecture.

The important distinction is that moving from CPQ to Revenue Cloud Advanced is not an upgrade. It’s a reimplementation with a different operating model, fewer guardrails, and a much higher premium on process clarity and architectural discipline. Treating it like a lift-and-shift is where teams tend to get into trouble.

Fragmentation is the fastest path to future pain

One of the strongest warnings that emerged from the conversation was around fragmentation. When teams try to test consumption or usage-based pricing by bolting on a separate billing system “just for a pilot,” the complexity rarely stays contained.

Over time, those experiments often create a second customer record, a second product catalog, and a second transaction engine. Reconciliation becomes manual. Reporting becomes unreliable. The quote-to-cash model slowly loses coherence.

If the goal is to introduce credits, commitments, usage, or hybrid pricing, the safer long-term approach is to extend what you already have without breaking the integrity of your architecture. That means protecting a single customer view, a single source of product truth, and clean lifecycle management even as monetization evolves.

The bridge matters because revenue cannot stop

A useful analogy surfaced during the discussion. Moving from CPQ to ARM requires a merge lane. Most companies cannot pause quoting, selling, amending, and invoicing while they rebuild their revenue stack. Continuity is not optional.

A phased transition allows teams to modernize transactionally, reduce risk, and avoid a single high-stakes cutover. When done well, migration becomes a controlled progression rather than a disruptive reset.

ARM success depends on people as much as product

While there is real excitement around ARM, the conversation was candid about where implementations can stall. The platform is evolving quickly, which creates opportunity but also risk for enterprise teams that need stability and governance.

Projects tend to struggle when teams build against the product’s intent, compensating with custom workarounds that become permanent. Over time, those decisions compound complexity instead of reducing it.

The implication for RevOps and Product leaders is clear. Domain expertise matters. Successful teams have experienced quote-to-cash practitioners in the room who understand not just what is possible, but what should be avoided. Being able to push back on requirements is often as important as delivering them.

A realistic planning window for CPQ EOS transitions

For many organizations, a six- to twelve-month preparation window is realistic, especially once remediation, catalog cleanup, process clarity, and cross-functional alignment are factored in. That time is not about delay. It’s about laying the groundwork that prevents expensive mistakes later.

Measured planning now leads to faster, more predictable outcomes when change does happen.

Final Thought

CPQ EOS does not demand immediate action, but it does reward intentional planning. Teams that use this period to clarify their processes, clean up their architecture, and modernize thoughtfully will have far more flexibility when the next decision arrives.

Want to go deeper?

  • Watch the full Quote-to-Cash Conversations recording to hear the complete discussion on CPQ EOS, ARM readiness, and modern revenue models, including real-world examples and audience Q&A.
  • Not sure what CPQ EOS means for your quote-to-cash architecture?
     Take the Salesforce CPQ EOS Assessment to understand your current state, evaluate your options, and identify the safest next steps based on your revenue model, quote-to-cash architecture, and timeline.

Whether you’re planning to extend CPQ, phase into Revenue Cloud Advanced, or explore alternatives, the right path starts with clarity.

▶ Watch the full recording
🧭 Take the CPQ EOS Assessment

CPQ EOS: Common Questions Revenue Leaders Are Asking

Do we need to replace Salesforce CPQ now that it’s end-of-sale?
No. End-of-sale means CPQ is no longer sold to new customers—not that it stops working. Existing customers will continue to receive support, giving teams time to plan instead of reacting under pressure.

Is moving from CPQ to ARM an upgrade?
No. ARM introduces a different operating model with fewer guardrails and greater architectural responsibility. Treating it as a lift-and-shift often leads to delays, rework, and avoidable complexity.

What happens if we wait too long to plan for CPQ EOS?
Teams that delay planning often face rushed decisions, fragmented architectures, and higher implementation risk once timelines compress. Early planning creates options—even if the decision is to stay on CPQ longer.

Can we experiment with usage or consumption pricing without breaking our architecture?
Yes—but only if experimentation happens within a unified quote-to-cash model. Adding separate billing or usage tools for pilots frequently leads to duplicate data, manual reconciliation, and reporting gaps.

How long should teams plan for a CPQ EOS transition?
For most organizations, six to twelve months of preparation is realistic. That time includes catalog cleanup, process alignment, cross-functional readiness, and architectural planning—not just implementation.

About Continuous

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 another system, portal, or integration layer.

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

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.