ValueOS

Measurement: Truth. Transparency. Trust.

What this does

A strategic value model that treats outages as inevitable—and focuses on reducing the time-to-know and time-to-fix, while quantifying cost protection across customers, networks, workforce, and infrastructure.

Catchpoint | Global Internet Performance Monitoring

Establish Assessment Context

Use the legal entity or brand name; this appears in the PDF export.

Controls how strongly improvements and cost assumptions are applied—use Conservative for CFO discussions.

How to get it: last annual report, investor deck, or internal finance estimate.

Baseline incident risk

Outages will happen. This step defines the baseline: how often, how long, and how expensive. You can use benchmarks now, then refine later with customer data.

How to get it: incident postmortems, PagerDuty/ServiceNow “P1/P2” count, SRE weekly report.

How to get it: “time open” for incidents. Use median, not the worst case.

How to get it: time from user impact to “we know what is broken.”

Benchmarks available in Sources panel. Prefer customer-specific if finance provides it.

How to get it: ecommerce %, online channel %, subscription online share, app purchase share.

Conservative default: 20–35%. Use higher if it’s a single critical funnel.

RUM Impact Model

How to get it: GA4, Adobe, internal analytics, CDN logs, or estimated MAU × visits.

CX Improvement Assumption

This represents faster detection/mitigation reducing impact window. Start with 10–25%.

Use when presenting “enterprise-wide resilience uplift”.

NetX (Network Experience) time reduction

How to get it: average duration of “bridge time” before you isolate ISP/CDN/DNS vs internal.

3rd Party Dependencies (Internet Sonar)

If they have credits/penalties tied to uptime/latency commitments, enter expected annual exposure.

If the customer already has a finance-approved “cost per minute,” use it here.

Workforce (WX) ticket model

How to get it: ServiceNow/Jira ticket volume; isolate tickets caused by network/connectivity/app performance/remote work (often 50–80% depending on org).

Pricing / Investment

Select a pricing model appropriate for the conversation. For prospects, use a tiered estimate. For customers, use Points + CPM and/or usage SKUs.

Use if prospect hasn’t discussed spend yet; later replace with actual quote/points.

Estimated annual investment

Customers: pull from contract / usage allocation.

Use contracted CPM.

How to get it: analytics “page_view” events or RUM PV estimate.

Set to your list/target for the deal.

Use for Internet Sonar or bundles sold as a fixed rate.

Annual investment

Total annual investment

Ready

Review the headline outcomes. You can change assumptions anytime from the pillar tabs. Use the PDF export once you’ve aligned the baseline assumptions with the customer.

Annual Value Identified

Combined value across CX, NetX, WX, CDN, RUM, and dependency.

Annual Investment

Based on your selected pricing model.

ROI Efficiency

ROI = (Value - Investment) / Investment.

Payback Window

Investment recovered based on annual value rate.

Executive Scorecard

Outages are inevitable. Value is created by reducing uncertainty, response time, and business impact.

Annual Value Identified

Loss Avoidance + Efficiency

Annual Investment

Pricing mode:

ROI Efficiency

Yield on spend

Payback Window

Days to breakeven

Strategic Value Pyramid

Qualitative account alignment connecting corporate goals to Catchpoint capabilities.

OBJECTIVES
STRATEGIES
INITIATIVES
CHALLENGES
REQUIRED CAPABILITIES /
HOW CATCHPOINT SOLVES

Persona Narrative

can reduce expected loss by closing visibility gaps across the Internet Stack (DNS, BGP, ISP/CDN routing, last-mile) and accelerating incident response. Under assumptions, this analysis identifies in annual value protection, with a payback of .

Operational Velocity

Reclaim engineering hours lost to war rooms & vendor ambiguity.

hrs/year reclaimed (WX).

Internet-Stack Assurance

Validate reachability and isolate 3rd-party issues faster.

/year protected (dependency).

Value vs Investment

Value Composition

Quick Controls

Use Low/Mid/High buttons on onboarding to align with benchmarks.

Recommendation

Start conservative, then refine with customer-specific incident data. The goal is credibility, not perfection.

Customer Experience (CX) Protection

Quantifies digital revenue risk protected by reducing the incident impact window.

Finance / analytics estimate. For SaaS, use % of revenue dependent on online app availability.

If only checkout is broken, use 20–40%. If auth is broken, use 60–90%.

Represents faster detection, isolation, and mitigation reducing the window of user impact.

Annual value protected (CX)

Based on digital revenue, incident minutes, and impact reduction.

Guidance

  • Ask: “During an incident, what % of customer journeys are impacted (browse, login, checkout, playback)?”
  • Use a conservative number first; align with the business owner, then refine.

NetX (Network Experience) Resilience

Models MTTI/MTTR reduction + war-room shrinkage from faster blame isolation across ISP/CDN/DNS/BGP paths.

How to get it: average duration of “bridge time” for vendor/provider validation.

Default 120/hr. Use fully loaded if available.

This adds a small risk bucket tied to revenue; adjust in Baseline Risk if needed.

Annual value protected (NetX)

Direct incident minute reduction + reduced war-room time + optional reputation component.

Workforce Experience (WX) Optimization

Excel-parity model: reduce ticket volume (proactive) + reduce resolution time (reactive).

How to get these numbers

  • Tickets/month: ServiceNow → Reports → “Incidents created per month”.
  • Relevant %: filter by categories like network, connectivity, app performance, remote work.
  • Resolution mins: mean/median time to resolve for those categories.

Annual savings (WX)

engineering hours reclaimed per year.

Workforce Experience analysis is currently disabled. Toggle it back on above to include helpdesk/engineering efficiency in the business case.

CDN / Origin Offload Analyzer

Quantifies egress deflection from hit-rate improvement.

How to get it: CDN logs, analytics, or RUM pageview events.

Guidance

  • Hit rate: pull from CDN analytics dashboard (Akamai, Cloudflare, Fastly, etc.).
  • Origin egress: cloud billing line item (AWS/GCP/Azure) or CDN origin transfer cost.

Projected annual savings (CDN)

Egress deflected: GB/year

RUM Value Engine

Optional: model conversion impact from performance improvement.

Guidance

  • Sessions: GA4 “sessions” or unique visits; Pageviews also works as a proxy.
  • Perf improvement: use p75/p90 LCP/TTFB improvement targets.
  • Conversion lift: keep conservative unless they have internal elasticity studies.

Annual value (RUM)

If disabled, RUM can still be priced without counting value.

Enable RUM if you want to include conversion/performance value, or keep it off if the conversation is purely about monitoring coverage/pricing.

3rd Party Dependencies (Internet Sonar)

Models faster isolation and mitigation of external incidents (ISP/CDN/DNS/BGP/cloud).

Guidance

  • Ask: “How often are incidents caused by external providers or Internet routing/DNS/CDN issues?”
  • Minutes saved: time to prove it’s external + time to mitigate via reroute/failover.

Annual value (Dependency)

Direct minutes saved × cost/minute + SLA exposure reduction.

Pricing Engine

Switch pricing mode without changing value assumptions (prospect → customer-friendly flow).

Annual investment

Annual investment

Total annual investment

Commercial outcome

Value

Investment

ROI

Benchmarks & Sources (2025–2026)

Defaults are editable. Use customer-specific finance numbers when available.

Outage cost (high-impact)

New Relic reporting cites median high-impact outage cost around $2M/hour (~$33k/min).

References: New Relic Observability Forecast press materials and coverage.

Downtime cost distribution

ITIC survey: >90% report >$300k/hour, and 41% report $1M–$5M+/hour.

Use “Low/Mid/High” quick buttons to align assumptions.

Incident cost per minute + average duration

PagerDuty figure: $4,537/min, average incident 175 minutes, implying ~$794k/incident in that example framing.

Outage analysis framing

Uptime Institute’s Annual Outage Analysis emphasizes external risks, complexity, and third-party dependencies—useful when discussing inevitability of outages and need for faster isolation.

WX Scenario Grid

% ticket reduction (rows) × % MTTR reduction (columns)

Monthly savings ($)

Ticket ↓ / MTTR →

Annual savings ($)

Ticket ↓ / MTTR →