Beyond SaaS Metrics

An executive guide for PE operating partners, CEOs, CFOs, CROs, and board members

PE-backed information services businesses can look healthy while the underlying commercial picture is harder to read.

ARR may be growing, but product-level contraction may be hidden. NRR may look stable, but expansion may be masking weakened retention. A customer may cancel a legacy research product and buy a data platform. A parent group may consolidate contracts. A renewal may bridge for six months while a larger negotiation continues. A price increase may be accepted, but only after scope has been reduced.

That is the problem this guide addresses.

Most leadership teams do not lack reports. They have CRM dashboards, finance packs, customer success scorecards, product usage reports, and board decks. What they often lack is one trusted commercial operating view that explains what changed, why it changed, whether it matters, and what action is required.

A commercial intelligence system provides that view.

It is not another dashboard suite. It is the operating model that connects growth, retention, revenue quality, sales execution, customer risk, product performance, forecasting, and financial outcomes into one board-ready view of performance and action.

For PE-backed information services businesses, that distinction matters. Generic SaaS metrics are often too blunt for businesses where customer, product, contract, renewal, and pricing movements are layered. Commercial intelligence makes that complexity manageable, so leadership can protect revenue, improve growth quality, strengthen forecast confidence, and manage value creation with greater discipline.

The Core Problem: Commercial Performance Is Easy to Misread

As information services businesses scale, commercial reporting often fragments across functions.

Sales works from CRM pipeline, account plans, seller forecasts, and deal momentum. Finance works from revenue, billings, cash, margin, and budget assumptions. Customer Success works from renewal risk, usage, and account health. Product works from adoption, migration, and portfolio performance. RevOps works from process, quota, pipeline mechanics, and sales productivity. The board sees a summarised version of all of it.

Each view may be useful. None of them, on its own, is sufficient.

The same commercial movement can mean different things depending on which function is looking at it.

When the commercial logic is unclear, leadership spends too much time debating the numbers and too little time managing performance. The CRO may believe the pipeline is sufficient. The CFO may not believe the conversion assumptions. Customer Success may see renewal risk that is missing from the forecast. Product may see strategic migration progress that is invisible in ARR. The PE sponsor may see growth but not know whether it is durable.

That weakens value creation.

It also weakens exit readiness. A future buyer or investor will not only ask whether the business grew. They will ask what drove the growth, how durable it is, what revenue is at risk, how pricing power behaves, how retention works, and whether management can explain performance with confidence.

What a Commercial Intelligence System Is

A commercial intelligence system is the leadership operating model for understanding value creation.

It is not a CRM report, finance pack, product dashboard, customer success scorecard, or BI suite. Those tools may all contribute to the system, but they are not the system.

The system connects the commercial and financial logic of the business into one trusted view of performance, risk, and action.

It helps leadership answer seven questions:

1. What changed?
2. Why did it change?
3. Is the change good or bad?
4. Was it expected or unexpected?
5. What is the commercial and financial impact?
6. What decision is required?
7. Who owns the next action?

For the CRO, this means understanding whether the business will hit the number, where revenue is at risk, where account growth will come from, and whether the forecast can be trusted.

For the CFO, it means understanding whether ARR reconciles to revenue, billings, cash, margin, and plan assumptions.

For the CEO and PE sponsor, it means understanding whether the business is creating durable enterprise value, or simply reporting activity, growth, and pipeline that may not convert into value.

The Seven Layers of a Commercial Intelligence System

A commercial intelligence system has seven connected layers.

Each layer answers a different leadership question. Together, they create one commercial operating view: how the business grows, where revenue is at risk, how good that revenue is, which customers and products matter most, whether the forecast is credible, and whether commercial execution is aligned to the value creation plan.

The layers are not intended to create seven separate reporting packs. They are a way of organising the leadership conversation.

Layer 1: Value Creation Intelligence

A PE-backed business does not create value because it has more reports. It creates value when management can identify and improve the commercial levers that drive growth, retention, pricing power, revenue quality, margin, and predictability.

In an information services subscription business, value creation may come from several connected sources: improving gross revenue retention, expanding strategic accounts, creating qualified demand in priority segments, increasing price realisation, migrating customers from legacy products to strategic platforms, reducing discount leakage, improving sales productivity, reducing concentration risk, and making revenue performance more predictable.

These levers do not belong to one function.

Marketing may create qualified demand in priority segments. Sales may convert that demand into pipeline and ARR. Customer Success may protect and expand the base. Product may improve adoption, migration, and pricing power. Finance may assess whether the resulting revenue is durable, profitable, and predictable.

Value creation intelligence connects these actions into one operating view.

Without that connection, leadership can mistake activity for progress. The business may generate more leads, build more pipeline, close more deals, or launch more products without improving the quality, durability, or value of the revenue base.

Layer 2: Growth, Retention, and Renewal Intelligence

ARR movement is not always straightforward in information services businesses.

A customer may reduce coverage in one market while expanding in another. They may cancel a research product but buy a data platform. They may bridge temporarily while negotiating a larger renewal. They may consolidate contracts across a parent group.

A simple ARR bridge may show net growth, net contraction, churn, or expansion. But the management meaning depends on what actually happened.

Expansion may mask weakening product retention. Product migration may be treated as churn. Temporary bridges may be treated as secure renewals. Portfolio rationalisation may be interpreted as uncontrolled contraction.

Each scenario requires a different management response. True customer loss is not the same as product migration. A bridge renewal is not the same as a clean multi-year renewal. A price increase offset by scope reduction should not be treated as full pricing success.

Leadership needs to separate the movements that matter:

• True customer loss
• Product contraction
• Product migration
• Portfolio rationalisation
• Price increase
• Seat, user, coverage, or data package expansion
• Currency impact
• Timing effects
• Short-term or non-renewing deals
• Contract consolidation
• Parent account movement

The renewal book should also be forward-looking. Leadership needs to know what ARR is up for renewal, what has already renewed, what is likely to renew cleanly, what may contract, what is expected to bridge, what is exposed to churn, and which renewals require executive sponsorship.

This should be visible before the renewal date, not only after churn has occurred.

Layer 3: Revenue Quality Intelligence

ARR growth alone is not enough.

A business can report ARR growth while weakening revenue quality. Growth may be heavily discounted, short term, low margin, concentrated, difficult to collect, dependent on bespoke delivery, or misaligned with the strategic product direction.

Revenue quality helps investors and executives understand whether the company is creating durable enterprise value or chasing short-term revenue.

Sales performance may appear strong while the business creates revenue that is difficult to retain, expensive to serve, heavily discounted, weakly adopted, or strategically weak.

The business may also confuse revenue protection with revenue quality. A discount may be sensible if it protects a strategic account. But repeated discounting can also signal weak pricing power, poor product fit, or seller behaviour that undermines long-term value.

Bridge renewals create a similar issue. A bridge may be a useful commercial tool, but if it becomes a recurring pattern, it may be delaying churn rather than solving risk.

The system should connect commercial activity to financial quality:

• ARR to recognised revenue
• ARR to billings
• Billings to cash collection
• Revenue to gross margin
• Gross margin to EBITDA contribution
• Deferred revenue movement
• Payment terms and working capital
• FX impact
• Recurring vs non-recurring revenue

Pricing should also be treated as a core value creation lever. Leadership needs to know what price increase was targeted, what was proposed to customers, what was achieved, what was discounted away, where discounting protected retention, which segments accepted price, and which products resisted price.

Layer 4: Demand, Pipeline, Sales, and Quota Intelligence

A CRM pipeline report is not the same as commercial intelligence.

CRM tells you what sellers have entered. Marketing systems tell you what activity has been generated. Commercial intelligence tells you what leadership should believe.

That distinction matters because pipeline is often a blend of fact, process, judgement, seller optimism, stage discipline, and management pressure.

Leadership needs to know whether the pipeline is real, closeable, current, correctly staged, aligned to sales capacity, and likely to convert into durable recurring revenue.

A business can have a large pipeline that should not be believed. It may be stale, poorly qualified, overconcentrated in low-conversion segments, dependent on a small number of large deals, disconnected from renewal timing, or built on assumptions that do not match historical close behaviour.

A business can also have strong sales activity but weak demand quality. Leads and meetings are not enough if they do not convert into qualified opportunity, durable ARR, retained revenue, or strategic product growth.

Quota design can create further distortion. Sellers may be rewarded for short-term deals, temporary bridges, product swaps, or low-quality bookings that help the current period but weaken future revenue quality.

Pipeline intelligence should separate two questions.

Pipeline creation asks:

• Are we creating enough new opportunities?
• Is demand being generated in the right segments?
• Are campaigns, sellers, partners, events, and account plans creating qualified demand?
• Is pipeline creation keeping pace with the gap to plan?
• Are we creating pipeline early enough to convert within the required period?

Pipeline belief asks:

• Is the pipeline real?
• Is it current?
• Is it closeable?
• Is it correctly staged?
• Is it supported by historical conversion rates?
• Is it aligned to sales capacity?
• Is it likely to convert into high-quality recurring revenue?

This gives marketing a useful role in the executive operating model without turning the system into a marketing analytics framework. The executive question is not campaign optimisation. It is whether the business is creating enough right-fit demand to support future ARR growth, pipeline quality, acquisition quality, and forecast confidence.

The system should also show productive sales capacity, not just headcount or quota capacity. Too many ramping sellers, poor territory design, weak account coverage, or quota concentration in low-conversion segments can all create forecast risk.

Layer 5: Customer Value, Risk, and Account Growth Intelligence

Not all customers create the same value.

Some customers are large but low margin. Some are small but strategically important. Some have high expansion potential. Some are over-served relative to their contribution. Some appear stable but show weakening usage. Some are commercially quiet because they are deeply embedded. Others are quiet because they are disengaging.

Customer intelligence should help leadership allocate attention, resource, and executive sponsorship.

Without it, Customer Success may manage risk in one system, Sales may manage expansion in another, Finance may focus on revenue concentration, Product may focus on adoption, and the board may only see top customer movements after the fact.

This creates a reactive model. The business notices churn when it has happened, rather than identifying risk when there is still time to intervene.

It also creates poor resource allocation. High-value accounts may not get enough attention. Low-potential accounts may consume too much effort. Expansion opportunities may be missed because product usage, relationship strength, renewal timing, and whitespace are not connected.

Risk should not be treated as a black-box score.

Executives need to know which customers are at risk, why they are at risk, how much ARR is exposed, what action is planned, who owns the action, and whether the risk is improving or worsening.

Useful risk signals include late renewals, discount pressure, downgrade requests, falling usage, reduced stakeholder interaction, executive sponsor changes, low adoption, support issues, payment delays, procurement pressure, customer merger activity, cost-cutting, competitor displacement, and concentration risk.

The system should also direct account growth. It should show where to defend, where to expand, where to reprice, where to migrate, where to deepen executive relationships, where to improve adoption, where to accept rationalisation, and where to reduce effort.

Layer 6: Product and Portfolio Intelligence

Information services businesses often evolve through several product eras: legacy subscriptions, research packages, data feeds, platforms, add-on modules, enterprise bundles, bespoke arrangements, usage-based models, and strategic migrations.

Reported ARR may look stable while the underlying product mix is becoming stronger, weaker, more scalable, or more complex.

This matters because product mix affects retention, selling strategy, customer dependency, account planning, margin, pricing power, and investment priorities.

The business may protect ARR while leaving customers on weakening legacy products. It may celebrate growth in a product that is expensive to support. It may miss early signs that a strategic product is failing to convert demand into retained revenue.

Product-level contraction may be hidden by account-level expansion. Bundle renewals may obscure which products are truly valued. Strategic migrations may be understated if the system treats them only as churn and new business.

The system should help leadership answer which products are driving durable growth, which products are protecting retention, which products create cross-sell pathways, which products have weak renewal performance, which products are being discounted most heavily, which products are expensive to support, and which legacy products need migration, investment, simplification, or rationalisation.

Market demand signal can also be useful, but only at the right level. The executive question is not how every campaign performed. It is whether the products that matter to the future strategy are generating qualified commercial interest, converting into durable ARR, and supporting retention, expansion, pricing power, and margin.

Layer 7: Forecasting and Planning Intelligence

Forecasting should not be a spreadsheet argument.

It should be a structured view of how the number will be delivered, what assumptions need to hold, where risk sits, and what management action can improve the outcome.

In many businesses, the CRO forecast, CFO forecast, board plan, renewal forecast, and sales pipeline view are related but not fully reconciled. That creates tension at exactly the point where leadership needs confidence.

The CRO may focus on seller forecast and deal momentum. The CFO may focus on historical conversion, renewal risk, and plan credibility. The CEO may need one answer for the board. The PE sponsor may want to know whether the value creation plan is still on track.

A commercial intelligence system does not replace the CRO forecast or the CFO forecast. It reconciles them.

The question becomes less:

And more:

A good forecast operating model connects starting ARR, secured renewals, the renewal book still to close, at-risk renewals, expected churn, expected contraction, committed expansion, upside expansion, committed new business, upside new business, temporary bridges, price contribution, product migration impact, the gap to plan, required pipeline creation, downside case, upside case, and management actions.

The CRO, CFO, CEO, and PE sponsor should be able to work from one shared commercial forecast bridge that reconciles pipeline, renewals, expansion, churn, contraction, pricing, sales capacity, and plan assumptions.

The Foundations Underneath the System

The seven layers are the visible part of the system. The foundations underneath determine whether leadership trusts the numbers.

A commercial intelligence system requires governed definitions, trusted data, clear ownership, and an operating cadence that turns insight into action.

1. Metric governance

Leadership needs one commercial language.

That means clear definitions for ARR, ACV, NRR, GRR, churn, contraction, expansion, reactivation, renewal, bridge revenue, pipeline, bookings, quota attainment, price realisation, discounting, and revenue quality.

Without metric governance, every function creates its own version of the truth. Finance defines revenue one way. Sales defines bookings another way. Product defines adoption differently. Customer Success defines risk separately. The board receives a stitched-together narrative that may be directionally useful but analytically fragile.

2. Customer and product hierarchy

Information services customers often operate across parent groups, subsidiaries, regions, business units, and buying centres. Products may span families, platforms, modules, datasets, bundles, regions, and legacy structures.

Weak hierarchies distort account value, churn, expansion, concentration risk, product migration, quota credit, and portfolio performance.

Leadership needs to understand value, risk, growth, margin, usage, and expansion potential at the right level.

3. ARR movement logic

ARR movement logic defines how the business classifies new business, expansion, contraction, churn, price, volume, product migration, FX, bridge renewals, reactivation, and contract consolidation.

This is one of the most important foundations. If ARR movement logic is weak, the business cannot explain growth properly.

4. Renewal cohort logic

Renewal performance should be analysed against a clear renewal cohort.

Leadership should know what revenue was up for renewal, what renewed cleanly, what contracted, what expanded, what bridged, what churned, and what remains unresolved.

This is especially important where renewals slip, bridge, consolidate, or move across periods.

5. Revenue, pipeline, and forecast reconciliation

ARR must connect to revenue, billings, cash, and margin. Pipeline should be reconciled to targets, sales capacity, historical conversion, renewal timing, product mix, customer segment, and closed outcomes.

A forecast is only useful if leadership can understand the assumptions underneath it.

If these views do not reconcile, the business may have recurring revenue metrics that look healthy while financial performance, sales execution, or renewal risk tells a different story.

6. Data architecture, ownership, and cadence

The technical architecture should support trusted, repeatable, explainable commercial intelligence. It needs to connect CRM opportunities, contracts, subscriptions, products, customer hierarchies, parent accounts, revenue and billing data, finance actuals, usage, customer success signals, sales targets, forecasts, and plans.

For leadership, architecture matters because it determines whether the numbers are trusted, auditable, and board-ready.

Every major metric also needs a business owner and a data owner. The business owner defines what the metric means and how it should be used. The data owner ensures it is produced consistently, traceably, and accurately.

Finally, the system should be designed around the meetings and decisions it supports.

For each rhythm, the system should make clear what changed, why it changed, whether it matters, what is expected to happen next, which decision is required, which action has been agreed, who owns the action, and when it will be reviewed.

This is how intelligence becomes action.

Signs Your Business Needs a Commercial Intelligence System

The simplest test is not whether the business has dashboards. It is whether leadership can answer the following questions without manual reconciliation, functional debate, or last-minute explanation before the board pack is issued.

Executive diagnostic checklist

1. Can the CRO and CFO explain ARR movement the same way?
2. Can leadership separate true churn from product migration, portfolio rationalisation, or temporary bridges?
3. Can the board see whether expansion is masking contraction?
4. Can renewal risk be identified before the renewal date?
5. Can ARR be reconciled to revenue, billings, cash, and margin?
6. Can the business distinguish durable recurring revenue from temporary, discounted, low-margin, or non-recurring revenue?
7. Can pipeline be reconciled to historical conversion, sales capacity, renewal timing, and closed outcomes?
8. Can the forecast bridge renewal risk, expansion, churn, contraction, pricing, and new business in one view?
9. Can leadership identify which customers and products create the most value, risk, margin, and expansion potential?
10. Can the PE sponsor see which commercial levers are improving and which are underperforming?

The Next Stage of Maturity

For many PE-backed information services businesses, the next stage of maturity is not another dashboard suite.

It is a commercial intelligence system that helps leadership run the number, protect revenue, improve revenue quality, and manage value creation with greater confidence.

That system should help the CRO understand whether the business will hit the number. It should help the CFO understand whether commercial performance is credible and financially durable. It should help the CEO see where management action is required. It should help the PE sponsor understand whether the investment thesis is progressing.

Information services businesses are too complex to be managed properly from generic SaaS metrics alone. The customer relationships are more layered. The product movements are more nuanced. The revenue quality questions are more important than headline growth can show.

A good commercial intelligence system makes that complexity manageable.

It does not remove judgement. It improves the quality of judgement.

The aim is simple: to help leadership understand where value is being created, where revenue is at risk, and what action should be prioritised next.

About Ascendant Analytics

Ascendant Analytics helps B2B information services subscription businesses build trusted commercial intelligence systems.

We work with leadership teams to connect growth, retention, revenue quality, customer risk, product performance, sales execution, forecasting, and financial outcomes into one coherent operating view.

The goal is not more reporting. The goal is better commercial judgement, stronger management action, and clearer value creation.