Discovery
AuraScore 79/100

OTT Infrastructure Discovery Audit Checklist

Qualify technical streaming bottlenecks, CDN scaling limits, and ad insertion architecture before client solution scoping.

Use this checklist when preparing for discovery sessions with streaming platforms and digital broadcasters planning infrastructure migrations. It helps sales engineers systematically diagnose delivery latency, encoding workflows, and monetization integration points.

Template

Role: Principal Media & OTT Cloud Solutions Consultant specializing in high-throughput video streaming ecosystems.

Context

  • Target Streaming Brand: {{streaming_network_name}}
  • Incumbent Delivery Infrastructure: {{current_cdn_provider}}
  • Peak Audience Concurrency: {{concurrent_viewer_peak}}
  • Existing Monetization & Insertion Stack: {{ad_tech_stack}}
  • Primary Monetization Model: {{monetization_model}}
  • Target Cutover Window: {{migration_timeline}}

Task

Generate a rigorous, multi-stage sales discovery checklist tailored to evaluate {{streaming_network_name}}'s video delivery bottlenecks, origin shielding resilience, and commercial risks associated with moving away from {{current_cdn_provider}} before the {{migration_timeline}} deadline.

Method

  1. Analyze {{monetization_model}} requirements to frame discovery questions around ad insertion latency and subscriber quality-of-experience (QoE).
  2. Detail architectural verification items assessing how {{current_cdn_provider}} manages traffic spikes during {{concurrent_viewer_peak}} concurrent events.
  3. Formulate server-side versus client-side ad insertion inquiry items specific to {{ad_tech_stack}}.
  4. Draft multi-CDN switching and failover readiness diagnostic checkpoints.
  5. Establish DRM, watermarking, and regional content tokenization validation questions.
  6. Structure total cost of ownership (TCO) probing prompts covering egress fees, origin egress caching ratios, and mid-tier compute costs.
  7. Develop closing validation criteria to determine if {{streaming_network_name}} meets technical qualification thresholds for an architectural proof-of-concept.

Constraints

  • Every checklist item MUST include an explicit discovery objective and a red-flag warning trigger.
  • MUST NOT use generic IT infrastructure questions; phrasing must reference video streaming protocols (HLS, DASH, CMAF).
  • Include between 18 and 24 actionable checklist items organized across logical operational categories.
  • Keep technical terminology aligned with broadcast media engineering standards.

Output format

  • Executive Overview (3-4 sentences outlining account discovery strategy)
  • Phase 1: Video Ingest & Transcoding Architecture Checklist (5-6 items)
  • Phase 2: Edge Delivery & CDN Performance Checklist (5-6 items)
  • Phase 3: Monetization & Ad Insertion Telemetry Checklist (5-6 items)
  • Phase 4: Commercial & Contractual Migration Risk Checklist (3-4 items)
  • PoC Go/No-Go Decision Criteria Matrix (3 qualification gates)

Self-review

  • Verify all 6 context variables ({{streaming_network_name}}, {{current_cdn_provider}}, {{concurrent_viewer_peak}}, {{ad_tech_stack}}, {{monetization_model}}, {{migration_timeline}}) are embedded.
  • Confirm that every checklist item has an associated discovery objective and red-flag indicator.
  • Ensure no placeholder text or generic cloud IT terminology is present.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-discovery
media-entertainment
ott
streaming
cdn