Software deep dive
Anatomy of an Insight
This page shows the concrete output your reps and marketers consume: persona matrix, trigger-to-play mapping, and proof strips grounded in account-specific evidence.
One content model
One Content Model: Seller Knowledge & ABM Pages
Insight generates both internal seller knowledge and account-specific ABM landing experiences. Both pull from the same structured fields so the story matches, whether you are prepping a rep or inviting a buyer to read.
Seller Knowledge
Optimized for scan density (pivots, persona matrix, named plays).
Prioritize: Thesis · Diagram · Personas · Triggers · Proof
ABM Landing Page
Optimized for conversion (one thesis, minimal proof strip).
Prioritize: Thesis · Proof · Triggers
The Insight Output UI (Data Visualization)
Below is a representative sample of the structured, high-level insight Insight delivers per account: Architectural Pain Thesis, supporting proof, persona matrix, and signal-to-play hooks. In production, each field is grounded in your telemetry, connective research, and brand-approved narratives—this layout shows what reps and buyers can expect to see.
The Thesis
Grid modernization and telemetry load are forcing a move off legacy commercial databases; open data fabric maps to billing, assets, and compliance.
The Proof Strip
Egress / Transfer
85% reduction
Source: Comparable engagement summary
Early Warning
48h failure-warning window
Source: Pilot readout
Persona Matrix
| Role | Critical Pain | Value / Connective Tissue | Land the Meeting (The Hook) |
|---|---|---|---|
| VP Operations | Unplanned outages on remote assets cost production and safety exposure. | Edge-side models flag drift before trips. Vibration data shouldn't need a 1,000-mile round trip. | "15 minutes on how we run scoring locally and what hits your existing historian." |
| Head of Infra | Hybrid compliance and vendor exit pressure without breaking billing systems. | Reference architecture for Postgres/K8s fabric with support and migration lanes. | "Architecture review against your current RDBMS and AKS footprint." |
Trigger → Play
Signal: Spike in observability spend + latency complaints in job posts.
The Play (Egress-to-Edge): Contrast full-pipeline upload vs. insight-only upstream; tie to unit economics.
Signal: Active migration project to PostgreSQL / K8s for new services.
The Play (Greenfield First): Greenfield services are the wedge. Offer a bounded pilot on one service line with explicit success criteria.
Schema reference: lib/visionContentModel.ts