User Guide — Internal

Dashboard
User Guide

How to read, interpret, and use the Scramble Competitive Intelligence Dashboard in sales conversations and strategic planning. This guide covers every section, the methodology behind the analysis, and a glossary of all terms used.

Getting Started
What Is the Dashboard?
The Competitive Intelligence Dashboard synthesizes market analysis, competitor deep dives, GTM battlecards, and competitive advantages into a single interactive reference for the commercial team.
Who It's For
Sales & Commercial — for prospect conversations, objection handling, and competitive positioning.
Leadership — for strategic planning, fundraising narratives, and market context.
How to Navigate
The sticky nav bar at the top links to each section. Sections flow top-to-bottom from market context (macro) to sales tools (tactical). Hover over charts, dots, and cards for additional detail.
How to Use This Guide
Each dashboard section is explained below with what it shows, how to read it, and when to use it in conversations. The Glossary defines every term.
Dashboard Sections at a Glance
Market Context
Market Sizing
TAM / SAM / SOM
Competitive Intel
Landscape Quadrant
Threat Assessment
Capability Matrix
Funding
Sales Enablement
GTM Strategy
Pricing
Buyer Personas
Battlecards
Kill Phrases
Planning
Milestones
Gaps & Risks
Section-by-Section
Reading the Dashboard
What each section evaluates, how to interpret its visuals, and when to reference it.
●

Market Context

Macro-level market sizing and opportunity framing

01 Market Sizing

What It Shows
Four adjacent market segments Scramble operates at the intersection of: Platform Engineering, Cloud FinOps, IaC Management, and AI Agent Governance. Horizontal bar charts show 2025 sizes and 2030 projections with CAGR.
How to Read It
The solid bar is the 2025 market value. The faded extension behind it is the 2030 projection. The CAGR (compound annual growth rate) shows how fast each segment is growing. Cards below show combined totals and regional breakdowns.
Sales Use
Use when a prospect or investor asks "how big is this market?" Show that Scramble sits at the intersection of four growing segments rather than competing in one. The combined ~$24B (2025) number validates the opportunity.

02 TAM / SAM / SOM

What It Shows
The total addressable market (TAM), serviceable addressable market (SAM), and serviceable obtainable market (SOM) for Scramble. Displayed as funnels for 2025 and 2030, with a breakdown table by segment.
How to Read It
The funnel narrows from all possible revenue (TAM) to what Scramble can realistically serve (SAM) to what it can capture in Year 1/3 (SOM). The table breaks down how each market segment contributes to the TAM, with Scramble's estimated addressable percentage.
Sales Use
Use for investor conversations and internal planning. The SOM figures ($1.5–6M Year 1, $25–50M Year 3) are the revenue targets. Target deal size ($500K–$1.5M) and account count (200–400) frame sales capacity planning.
●

Competitive Intelligence

How Scramble compares to the competitive field

03 Positioning Quadrant

What It Shows
A 2D map plotting competitors on two axes: Governance Depth (vertical) and Developer Experience Breadth (horizontal). Scramble's gold dot sits in the upper-left: deep governance, narrow DX focus.
How to Read It
Hover over any dot to see the competitor name, funding, and positioning note. Dot colors indicate threat level (red = high, yellow = medium, blue = low-medium, green = low). Scramble's dot is larger and gold. The upper-right quadrant is intentionally empty — no competitor offers both deep governance and broad DX.
Sales Use
Use when a prospect is evaluating multiple tools. This chart visually demonstrates that Scramble is not competing with portals or CI/CD tools — it occupies a distinct position. Point to the empty upper-right: "Nobody does both well yet."

04 Threat Assessment

What It Shows
A table of 12 competitors ranked by threat level to Scramble. Includes category, total funding, estimated headcount, revenue, threat badge, and each competitor's key gap relative to Scramble.
How to Read It
Threat levels indicate how likely a competitor is to encroach on Scramble's positioning. HIGH means they have resources and some overlap. LOW means minimal overlap or insufficient resources. The "Key Gap" column is the most actionable — it's why they can't easily replicate what Scramble does.
Sales Use
Before a call, check if the prospect uses or is evaluating any competitor in this table. Read the Key Gap and use it to frame your positioning. For HIGH-threat competitors, prepare the full battlecard (see section 10).

05 Capability Matrix

What It Shows
A feature comparison table for Scramble's 5 structural advantages plus 2 gap areas, compared against 7 competitors. Each cell is color-coded green (native/strong), yellow (partial), or red (absent).
How to Read It
Native / Strong — built-in capability
Partial — limited or bolted-on
Absent — not available
Scramble's column is highlighted. The top 7 rows (taxonomy through agent governance) are Scramble's strengths. The bottom 2 rows (multi-cloud, self-hosted) are acknowledged gaps. Competitors may be strong there but weak on governance.
Sales Use
Use when a prospect asks "how do you compare to X?" Pull up the matrix, find their column, and walk through the rows. Lead with Scramble's green cells, acknowledge gaps honestly, then reframe: "They're strong on multi-cloud. We're strong on governance. Which is your bottleneck?"

06 Funding Landscape

What It Shows
Horizontal bar chart of total funding raised by each competitor, from Harness ($614M) down to Scramble (pre-funding). Cards below provide strategic context on M&A consolidation and Scramble's position.
How to Read It
Bars are proportional to funding amount. Valuation is shown alongside. The "Key Insight" card highlights that billions flow to portals and DevOps — but infrastructure governance is underfunded. This is the white space.
Sales Use
Use in investor conversations to show market validation (total capital deployed) while emphasizing Scramble's differentiated position (nobody is funded specifically for enterprise infrastructure governance). The M&A card (IBM+HashiCorp, Alphabet+Wiz) shows market consolidation creating opportunity.
●

Sales Enablement

Tactical tools for prospect conversations and deal execution

07 GTM Strategy

What It Shows
The four-phase go-to-market expansion plan: Beachhead (EU Financial Services) → Adjacent verticals → Expansion → Category Leadership. Includes the land-and-expand motion and channel/partner strategy.
How to Read It
The phase bar at the top shows the timeline (Year 0–6+) and ARR targets per phase. The land-and-expand diagram shows how a single X-Ray Discovery engagement grows into full-platform governance. The channel strategy cards show partner tiers.
Sales Use
Reference the beachhead table to validate why European Financial Services is the entry point (regulatory urgency, Azure prevalence, budget). Use the land-and-expand motion to plan account growth: start with X-Ray, expand to taxonomy, then policy, then cost attribution.

08 Pricing Strategy

What It Shows
Scramble's pricing model (flat-fee) compared to competitor pricing models (per-resource, per-execution, per-developer). Includes the price anchoring strategy — what alternatives cost the enterprise.
How to Read It
The top cards show Scramble's two price points: €13,800 for Alpha X-Ray Discovery and $500K–$1.5M ARR for the full platform. The competitor table shows their pricing gotchas (costs that scale with usage). Price anchoring cards show what not buying Scramble costs.
Sales Use
When a prospect asks about pricing, lead with the flat-fee advantage: "More usage equals more value at the same cost." Use the anchoring cards to reframe: "An in-house team costs $2–3M/yr. Backstage maintenance costs $500K+. One failed audit costs more than 3 years of Scramble."

09 Buyer Personas

What It Shows
Four enterprise buyer personas (CTO/CIO, VP Platform Engineering, CISO, CFO) with their specific pain points, a hook question to open the conversation, and a demo flow tailored to their concerns.
How to Read It
Each card has four parts: the role, the pain (what keeps them up at night), the hook (an opening question to use verbatim in conversation — shown in italics with a gold border), and the demo pitch (what to show and in what order).
Sales Use
Before any call, identify which persona you're meeting. Read their hook question and use it verbatim — it's designed to surface pain. Follow the demo flow to present Scramble in the order that resonates with that specific buyer.

10 Battlecards

What It Shows
Expandable competitor-specific battlecards for the 7 most relevant competitors. Each card includes their pitch, our counter-pitch, kill questions (to ask the prospect to ask the competitor), and walk-away signals.
How to Read It
Click any card header to expand it. Their Pitch is what the competitor says about themselves. Our Pitch is how to position Scramble against them. Kill Questions are questions to suggest the prospect asks the competitor — these expose their gaps. Walk Away signals tell you when this isn't our deal.
Sales Use
Prepare before any competitive deal. If a prospect mentions evaluating Harness, expand the Harness battlecard, read the kill questions, and coach the prospect: "When you demo with them, ask this..." The walk-away signals save time on deals we won't win.

11 Kill Phrases

What It Shows
Eight one-sentence reframing statements, each targeted at a specific competitive category or objection. Designed to be used verbatim in sales conversations.
How to Read It
The gold header identifies the competitive scenario (e.g., "vs Pipeline Tools" or "vs We'll Build It Ourselves"). The phrase below is the exact sentence to use. These are memorization-worthy — they compress complex positioning into one impactful line.
Sales Use
Memorize 2–3 that apply to your most common competitive scenarios. Use them as conversation pivots when a prospect brings up a competitor or raises a "build vs. buy" objection. They're designed to end one thread and open a better one.
●

Planning

Roadmap, traction targets, and honest risk assessment

12 Milestones

What It Shows
A timeline from current Alpha through Series A readiness (2028), with key milestones and dates. Alongside, cards highlight market tailwinds that create urgency (EU AI Act, IBM/HashiCorp, platform engineering adoption).
How to Read It
The timeline runs top-to-bottom chronologically. The active dot (filled) marks where we are now. Upcoming milestones show target dates and what "done" looks like. The tailwind cards on the right provide external context that validates timing.
Sales Use
Use the EU AI Act deadline (August 2026) to create urgency: "Governance becomes mandatory in [X] months. Better to implement now than scramble later." Use the milestone timeline to set customer expectations on product maturity and roadmap.

13 Gaps & Risks

What It Shows
An honest table of Scramble's current gaps (multi-cloud, self-hosted, AI agents, analyst recognition, etc.), who's ahead, when the gap closes, and how to frame it in conversations. Below, the 5 structural advantages card reinforces what no competitor has.
How to Read It
The "Framing" column is the most important — it's the exact wording to use when a prospect raises one of these gaps. Badges indicate severity. The structural advantages grid at the bottom is the counterbalance: even with gaps, these 5 advantages are architecturally impossible for competitors to replicate quickly.
Sales Use
Never hide gaps — prospects respect honesty. When a gap comes up, acknowledge it using the framing column, then pivot to the structural advantages: "We're Azure-only today because 70%+ of the beachhead is Azure-primary. And in exchange, we offer 5 capabilities no one else has at any price."
Methodology
How This Was Built
Understanding the data sources, rating systems, and analytical frameworks behind each section of the dashboard.
Data Sources
Market Sizing: Cervicorn Consulting, Precedence Research, MarketsandMarkets, Grand View Research, NextMSC
Competitor Funding: Crunchbase, press releases, SEC filings, verified investor announcements
Headcount & Revenue: LinkedIn data, published financial reports, industry estimates (marked with ~)
Capabilities: Product documentation, public demos, feature comparison pages, hands-on evaluation where possible
GTM & Pricing: Published pricing pages, sales conversations, analyst reports, partner intelligence
Update Cadence
Full refresh: Quarterly or upon major market event (funding round, acquisition, product launch)
Battlecards: Updated after every competitive encounter with new intel
Market sizing: Annual (based on analyst report cycle)
Pricing data: Checked quarterly against published pages
Last updated: February 19, 2026

Threat Level Criteria

LevelBadgeCriteriaExample
HIGH HIGH Significant funding (>$200M), large team, direct feature overlap with Scramble's core capabilities, active in the same buyer segment. Harness — $614M funding, AI-native DevSecOps, governance modules, overlapping enterprise buyers.
MED-HIGH MED-HIGH Strong funding ($50–200M), growing team, partial capability overlap, could pivot into governance. Spacelift — $73.6M funding, best OPA integration in IaC, could add discovery layer.
MEDIUM MEDIUM Moderate funding or strong market position, adjacent category, would require significant architecture change to compete. Pulumi, Env0, Port, Humanitec, Backstage — strong in their lane but would need fundamental redesign.
LOW-MED LOW-MED Limited funding or narrow focus, minimal overlap, unlikely to pivot into governance. Cortex, Kubiya — developer portals or AI agents without infrastructure governance context.
LOW LOW Small team, limited funding, experimental or niche, no enterprise traction in governance. OpsLevel, System Initiative, Massdriver — early-stage or too narrow to threaten.

Capability Matrix Rating System

Native / Strong (Green)
Built into the product architecture. Not a bolt-on, not a plugin, not a workaround. The capability is a core design decision and works out of the box.
Partial (Yellow)
Some version of the capability exists but is limited in scope, requires manual configuration, only covers a subset of the use case, or is a recent/early addition.
Absent (Red)
The capability does not exist in the product. It cannot be achieved through configuration, plugins, or workarounds. It would require building from scratch.

Market Sizing Methodology

Multi-source triangulation: Each market segment size comes from at least two independent analyst firms. Where estimates diverge, we use the midpoint or the more conservative figure.

Scramble's addressable %: For each segment, we estimate what percentage of the total market Scramble can address (e.g., 40% of Platform Engineering covers the governance layer, not the full IDP). These percentages are conservative.

SAM filtering: The SAM narrows from TAM by applying filters: 5,000+ employees, multi-country operations, IaC-mature (use Terraform/Pulumi/etc.), and active cloud spend. These filters match Scramble's ideal customer profile.

SOM estimation: Based on target deal size ($500K–$1.5M ARR), number of qualifying accounts in the beachhead (200–400), and realistic win rates for a new entrant (5–10% in Year 1). All figures are directional estimates, not guarantees.
Lexicon
Glossary of Terms
Every term, abbreviation, and concept used in the dashboard, organized by category.

Business & Financial

ARR
Annual Recurring Revenue. The yearly value of subscription contracts. A customer paying $100K/month has $1.2M ARR. The standard SaaS metric for measuring business scale.
CAGR
Compound Annual Growth Rate. The average yearly growth rate of a market or metric over a period. A market growing from $5B to $24B over 5 years has ~37% CAGR.
TAM
Total Addressable Market. The total revenue opportunity if Scramble captured 100% of every relevant market segment. It's the theoretical ceiling — useful for showing the size of the opportunity, not a realistic revenue target.
SAM
Serviceable Addressable Market. The portion of the TAM that Scramble can actually serve given its product focus (multi-country, IaC-mature, 5K+ employees). Smaller than TAM but more realistic.
SOM
Serviceable Obtainable Market. The portion of the SAM that Scramble can realistically capture in a specific timeframe. Based on sales capacity, win rates, and market penetration. This is the actual revenue target.
Beachhead
The first target market segment for initial market entry. Scramble's beachhead is European Financial Services — chosen because they have the strongest combination of regulatory pressure (EU AI Act, DORA, GDPR), multi-country operations, and Azure adoption.
Land-and-Expand
A sales motion where you enter ("land") an account with a small, low-risk engagement (X-Ray Discovery for €13,800) and then grow ("expand") into larger contracts as the customer sees value (taxonomy, policy, cost attribution — toward $500K–$1.5M ARR).
POC
Proof of Concept. A time-limited engagement (typically 30 days) where the product is deployed on a prospect's real infrastructure to prove value before a purchase decision.
TTV
Time to Value. How quickly a customer sees meaningful results after starting to use the product. For Scramble, X-Ray Discovery provides TTV in hours — first scan reveals unknown infrastructure immediately.
SI
Systems Integrator. Large consulting firms (Avanade, Accenture, Big 4) that implement technology solutions for enterprises. SIs are channel partners that can recommend and deploy Scramble within their client accounts.

Technical & Product

IaC
Infrastructure as Code. Managing cloud infrastructure (servers, networks, databases) through code files rather than manual UI clicks. Tools: Terraform, Pulumi, CloudFormation, OpenTofu. Scramble governs infrastructure whether or not it was created through IaC.
IDP
Internal Developer Platform. A self-service layer that lets developers provision and manage infrastructure without directly using IaC tools. Tools: Backstage, Port, Humanitec. Scramble provides the governance layer above IDPs.
OPA / Rego
Open Policy Agent / Rego language. An open-source policy engine and its query language for defining rules. "No public-facing databases in production" can be expressed as OPA policy. Scramble supports both OPA/Rego and JavaScript for policy, giving flexibility.
RBAC
Role-Based Access Control. Controlling who can do what based on their role (admin, developer, viewer). Scramble's RBAC is scoped to the 5-level taxonomy — e.g., "admin for the French payments division" is a single permission, not a manual mapping.
K8s
Kubernetes. A container orchestration platform for running applications in production. Some competitors (Humanitec) are K8s-centric. Scramble is infrastructure-agnostic — it governs VMs, serverless, and K8s resources alike.
OpenTofu
An open-source fork of Terraform created after HashiCorp changed Terraform's license. The IBM/HashiCorp acquisition ($6.4B) accelerated migration to OpenTofu. Scramble is IaC-engine-agnostic — it works regardless of which IaC tool is used.
OSS
Open-Source Software. Software with publicly available source code. Backstage has 89% OSS market share in developer portals. Scramble leverages OSS components ($35–70M equivalent R&D value) but is a commercial product.

Scramble Concepts

5-Level Taxonomy
Scramble's organizational model: Business Line > Country > Domain > Application > Service. Every resource, policy, cost, and event is scoped to this structure. Competitors typically have 0–3 levels. This is Scramble's most fundamental structural advantage.
X-Ray Discovery
Scramble's autonomous cloud scanning engine. Connects to cloud APIs (Azure today) and discovers all resources — including those not managed by any IaC tool ("shadow infrastructure"). This is the "land" in land-and-expand: first scan reveals what you didn't know you had.
Dual Policy Engine
Scramble supports both JavaScript and OPA/Rego for writing policy rules. JavaScript lowers the barrier (most teams know JS). OPA/Rego provides industry-standard rigor. Both evaluate against the full taxonomy context (country, business line, etc.).
Event Envelopes
Every write action in Scramble produces a typed, versioned, tenant-scoped event. This creates an automatic audit trail — who changed what, when, under which policy, in which jurisdiction. Competitors use webhooks (unstructured) or have no event architecture.
Agent Governance
A framework for governing AI agents that operate on infrastructure. Includes identity (who is this agent?), autonomy tiers (what can it do without approval?), kill switches (how to stop it), and taxonomy-scoped permissions (what resources can it touch?). Positioned for EU AI Act compliance.
Governance Runtime
Scramble's category term. A runtime is a continuously running system (vs. a tool you invoke). Scramble continuously discovers, classifies, governs, and accounts for infrastructure — it's "always on" governance, not a point-in-time scan.

Competitor Categories

IaC Orchestration
Tools that manage IaC execution pipelines — running Terraform plans, managing state, scheduling applies. Examples: Spacelift, Env0, Terraform Cloud. Key limitation: only govern infrastructure that flows through their pipeline.
Developer Portal
Tools that provide a self-service catalog for developers to discover and provision services. Examples: Backstage, Port, Cortex, OpsLevel. Key limitation: catalog, not governance — can't enforce policy or discover unknown infrastructure.
Platform Orchestrator
Tools that abstract infrastructure provisioning into developer-friendly workflows. Examples: Humanitec. Key limitation: typically K8s-centric, DX-first rather than governance-first.
DevSecOps Platform
Broad platforms covering CI/CD, security, testing, and deployment. Examples: Harness. Key limitation: governance is one module among many, typically pipeline-scoped with shallow organizational structure.

Regulatory & Compliance

EU AI Act
European Union regulation on artificial intelligence. High-risk AI system requirements become enforceable August 2026. Autonomous agents operating on infrastructure in regulated sectors will need governance frameworks. This creates a hard deadline for Scramble's agent governance positioning.
DORA
Digital Operational Resilience Act. EU regulation requiring financial institutions to ensure ICT resilience. Creates demand for infrastructure governance and audit trails — exactly what Scramble provides.
GDPR
General Data Protection Regulation. EU data privacy law. Relevant because infrastructure hosting personal data must be governed by jurisdiction. Scramble's taxonomy maps resources to countries, enabling jurisdiction-aware compliance.
GRC
Governance, Risk, and Compliance. The enterprise function responsible for ensuring regulatory compliance and managing risk. GRC platforms (ServiceNow GRC, OneTrust) are potential integration partners for Scramble.

Market & Analyst

MQ / Wave
Magic Quadrant (Gartner) / Wave (Forrester). Analyst frameworks that evaluate and rank vendors in a market category. Being included signals market maturity and vendor credibility. Scramble targets MQ/Wave participation at $25M+ ARR.
CNCF
Cloud Native Computing Foundation. Industry body governing cloud-native open-source projects (Kubernetes, Backstage, etc.). Their January 2026 "Four Pillars of Platform Control" report validates infrastructure governance as an emerging category.
FinOps
Cloud Financial Operations. The practice of managing and optimizing cloud spending. Scramble's cost attribution feature maps costs to the 5-level taxonomy, enabling FinOps at the business-structure level rather than just tag-based allocation.

Code30 • Dashboard User Guide • Confidential • February 2026
Companion document to the Competitive Intelligence Dashboard.