Crossing $1B in verified value: why realized outcomes are the new enterprise success model

Cognite announced on October 28, 2026 that companies using its Industrial AI and Data Platform have unlocked more than $1 billion in verified, realized value. The milestone matters well beyond industrial AI: it is a public, auditable example of enterprise software being judged by customer outcomes instead of seats, licenses, or consumption.

Verified customer value is the business impact a customer has actually achieved, measured against a baseline both sides agreed on and signed off by the customer. It is not a forecast, an ROI calculator output, or a slide-deck model. When a vendor makes verified value its success metric, the business case stops being a pre-sale artifact and becomes an operating system that runs from first meeting to renewal.

What did Cognite announce?

Cognite announced that customers using its platform have unlocked more than $1 billion in verified, realized value in the 12 months since it launched its Moonshot, a 10-year commitment to deliver $100 billion in quantifiable value to customers by 2035.

According to the press release, Cognite works with each customer to identify the operational KPIs that matter most to that customer, and a dedicated value team connects KPI improvements to business impact. Over the year, Cognite and its customers identified billions in potential value and verified $1 billion of it.

"Documenting $1 billion in verified value in just twelve months is a testament to the deep collaboration among our customers, partners, and the internal teams at Cognite that support them," said Girish Rishi, CEO of Cognite.

The distinction between identified and verified value is the whole point. Potential value is what most vendors report. Verified value is what survives contact with the customer's own data and sign-off.

Why are seats and licenses no longer the right success metric?

Seats, licenses, and consumption measure what the vendor sold. They do not measure what the customer achieved. That gap is why renewals turn into price negotiations and why economic buyers increasingly ask for proof before they expand.

In their blog post, Girish Rishi and Justin Hester, Cognite's VP of Customer Value, describe the legacy model plainly: B2B tech has evaluated success with supplier-focused metrics such as licenses sold, seat adoption, consumption rates, and endless proof-of-concept pilots. The press release frames the Moonshot as a shift away from those metrics "towards a transparent model of measured, bottom-line business impact."

For a CFO, the logic is simple. A seat count tells them how much they are spending. Verified value tells them what they got for it. Only one of those numbers defends a budget line in a planning cycle.

What does "verified value" actually mean?

Verified value is business impact that has been measured against an agreed baseline and confirmed by the customer, not estimated by the vendor.

Cognite puts it directly: in enterprise tech, value is too often treated as a theoretical forecast or a slide-deck model, and for them "it's real business impact; verified in partnership with, and signed off by, our customers."

Three conditions separate verified value from a claim:

• An agreed baseline. Both sides define pre-deployment performance using a specific historical window and data set.
• Shared measurement. The customer opens operational data so improvements can be measured, not assumed.
• Customer sign-off. The number is co-validated with the people who own the operation and the budget.

How does Cognite verify customer value?

Cognite verifies value through a four-part operating model: multi-stakeholder alignment, upfront baselining, a structured review cadence, and shared accountability. The steps below summarize the methodology published in Cognite's blog.

1. Treat go-live as the starting line

In the traditional model, the vendor considers the job largely done at go-live, and the customer is left to justify the investment and calculate ROI after the sales team has moved on. Cognite rejects that model and describes going live as "merely the starting point." Value tracking is positioned as a shared strategic operating system, not an administrative afterthought.

2. Align five stakeholder groups from day one

Value cannot be validated from a single vantage point. Tracking only through IT or project managers captures deployment milestones, not operational impact. Cognite aligns five groups:

• Frontline end users, who confirm whether daily workflows are genuinely faster, safer, and more effective
• Project leaders, who aggregate system data and establish baseline metrics
• Executive champions, who make sure use-case KPIs map to corporate strategy
• Operational leadership, who verify that efficiency gains translate into real plant improvements
• Economic buyers, who review business impact to assess ROI and approve scaling

3. Baseline before you expand

Before any production deployment expands, Cognite runs Value Alignment sessions with operational leaders to agree on the pre-deployment baseline and on two types of indicators: leading signals (for example, alert adoption or workflow steps eliminated) and lagging returns (for example, avoided downtime or reduced energy consumption). Cognite does not charge for these sessions and describes them as a required investment in customer success.

4. Run a review cadence, not an annual retrospective

Cognite's verification rhythm runs on four cycles:

Within this cadence, Cognite tracks both hard savings (direct cash impact and downtime prevention) and soft savings (recovered engineering capacity). Keeping the two separate is what lets a CFO trust the total.

Where does the $1B in verified value come from?

According to Cognite, the verified value splits across four operational categories:

The pattern is instructive for any category. The largest share comes from metrics the customer already reports on: downtime, cost, throughput, and productivity. None of them is a product metric. Verified value is easiest to defend when it lands in a KPI the customer's leadership already reviews.

What does this mean for RevOps, CS, and value teams?

The Cognite model is industrial, but the operating principles transfer to any B2B company that sells on a business case.

• The business case is a contract, not a pitch. If the drivers and baseline are not captured at close, there is nothing to verify later.
• Customer success owns outcomes, not logins. Adoption is a leading indicator. Realized value is the lagging proof.
• Value reviews belong in the operating rhythm. A QBR that opens with realized value against baseline changes the renewal conversation before it starts.
• Economic buyers need hard and soft savings separated. Blended numbers invite skepticism. Labeled numbers get approved.
• Internal alignment matters as much as customer alignment. Cognite notes that product, customer value, and sales all had to operate around measurable customer ROI rather than seat counts.

As Justin Hester put it in the announcement: "Crossing $1 billion isn't just a victory for Cognite, it's a testament to the vision, discipline, and industrial industry leadership of our customers."

How should a revenue or value team get started?

Start small and make it repeatable. A practical sequence:

1. Pick three to five outcome metrics per segment that your buyers already report to their leadership, such as cost, time, risk, or revenue.
2. Capture the baseline and business case at deal close in a system of record, not a sales deck that gets filed away.
3. Name the stakeholders on the customer side who will confirm usability, own the baseline, and sign off on impact. Include the economic buyer from the start.
4. Define leading and lagging indicators so you can see progress in weeks, not only at renewal.
5. Set a review cadence that matches your motion, for example monthly operational check-ins and quarterly business impact reviews.
6. Label hard and soft savings separately in every value summary.
7. Feed verified outcomes back into new business cases so each renewal makes the next pre-sale case more credible.

Frequently asked questions

What is the difference between potential value and verified value?

Potential value is what a vendor or customer projects could be achieved. Verified value is what has been measured against an agreed baseline and confirmed by the customer. Cognite reports identifying billions in potential value and verifying $1 billion.

Why does go-live matter for value realization?

Go-live is when value starts, not when it is proven. Teams that stop engaging at go-live leave the customer to justify the purchase alone, which is where renewal risk begins.

What is the difference between hard and soft savings?

Hard savings have a direct cash impact, such as prevented downtime or reduced costs. Soft savings are real but indirect, such as recovered engineering capacity. Reporting them separately makes the total more credible to finance.

How often should customer value be reviewed?

Cognite uses a biweekly, monthly, quarterly, and annual rhythm. Most B2B teams can start with monthly operational reviews and quarterly business impact reviews, then add frequency where adoption risk is highest.

Minoa is the value intelligence layer that puts a consistent, defensible business case on every deal and proves the value through renewal and expansion.

Ready to make verified value your success model? Book a demo to see Minoa in action.

Last updated: Oct 28, 2026