Quick Intro: A Snapshot of Your Team and Mission

• Tell us your organization name, the team we'll be collaborating with, and the best contact role for technical discovery (e.g., Network Architect, IT Director).
• Which vertical best describes your primary use case for satellite connectivity? Options: Maritime / Fleet, Oil & Gas / Remote site, Aviation / Aeronautical, Enterprise remote branch, Government / Defense, Humanitarian / Disaster response, Other
• Roughly how many remote sites, vessels, or aircraft will be in scope for the first phase (pilot) and the potential full rollout? Options: 1–5, 6–25, 26–100, 101–500, 500+
• What currently keeps you awake at night about connectivity for these sites? (A brief statement of your top worry.)
• How soon are you looking to start a pilot or initial deployment? Options: Immediately (0–4 weeks), Short term (1–3 months), Medium (3–6 months), Planning horizon (6–12 months), No timeline / exploratory

Are You Still Settling for 'Good Enough' Connectivity?

• When you think about your current connectivity experience, what assumptions have you quietly accepted as ‘good enough’ that might actually be costing you?
• How often do connectivity issues interrupt critical operations at a remote site or on a vessel/aircraft? Options: Daily, Weekly, Monthly, Rarely, Never
• When an interruption occurs, which of these consequences do you experience? (Select all that apply.) Options: Operational downtime, Safety risk, Lost revenue, Delayed decision-making, Regulatory exposure, Customer experience impact, Other
• Can you share a recent example where connectivity failure led to measurable loss or near-miss? What happened and who was impacted?
• What would need to change for you to stop tolerating the current level of service and pursue a different approach?

When Latency or Outages Start to Hurt — The Real Impact

• Which applications are most mission-critical over these links (rank top 3)? Options: VoIP / Voice comms, Video conferencing / situational awareness, SCADA / OT telemetry, File sync / backups, Crew/customer internet, Real-time control / UAVs, Other
• Do you have specific throughput or latency targets for those applications? If so, list targets by application (e.g., VoIP < 150 ms RTT).
• How do you currently measure service quality and how accessible are those metrics when troubleshooting? Options: Real-time dashboard with alerts, Periodic reports, Manual testing only, No formal measurement, Other
• Which failure modes concern you most: sustained outage, frequent brief drops, slow degraded performance, or unpredictable latency spikes? Options: Sustained outage, Frequent brief drops, Degraded throughput, Latency spikes, Intermittent packet loss, Other
• When performance degrades, what compensating actions do you take today (automation, manual reroute, mobile backup, delay tasks)? Options: Failover to cellular, Reduce bandwidth-hungry apps, Manual restart/triage, Activate backup satellite capacity, Accept degradation, Other

Who's Responsible When Things Go Dark?

• Who owns availability and incident response for these sites within your organization? Options: Network / Infrastructure team, Operations / Site lead, IT Security, Third-party service provider, Executive sponsor, Other
• Describe your escalation path for a connectivity incident that impacts mission-critical operations—who gets notified and when?
• Which internal stakeholders must sign off on changes to connectivity architecture or vendor agreements? Options: Network engineering, Security / Compliance, Operations, Procurement/Finance, Legal, Executive leadership, Other
• How do procurement and contracting timelines typically look for network services (select closest match)? Options: 6–12 months, Weeks (rapid procurement), 1–3 months, 3–6 months, Longer / politically constrained
• What internal pressures (budget cycles, regulatory deadlines, seasonal operations) create hard deadlines for this project?

The Unseen Constraints: Physical, Regulatory, and Environmental Limits

• What physical constraints exist at your sites that affect terminal selection or installation (roof access, mast height, power availability, space), and where are those constraints most severe?
• Which regulatory, export control, or spectrum compliance rules apply to your operations (select all that apply)? Options: Data sovereignty / localization, Encryption export controls, Maritime/Coast Guard regs, Civil aviation (FAA/EASA), Defense-specific approvals, None/Not sure, Other
• Tell us about environmental stresses we must design for: extreme temps, salt spray, icing, high vibration, frequent storms, EMP risk, or others.
• Are there physical or operational windows when on-site work is impossible or highly restricted (e.g., operations must remain live, no dry-docking, runway constraints)? Options: Yes—frequent restrictions, Occasional restrictions, Rare or none, Not sure
• Do you anticipate requirements for on-the-ground third-party installers, government-cleared personnel, or special certifications for field teams? Options: Yes—cleared personnel required, Yes—vendor-specified installers, No special requirements, Not sure

If Everything Worked Perfectly for Your Mission

• Imagine a pilot that exceeds your expectations—what three measurable signals would prove success to you?
• What are non-negotiable acceptance criteria for a site to be considered operational (throughput, latency, uptime %, monitoring access)?
• Beyond raw numbers, what qualitative changes would indicate success (reduced operator stress, faster incident resolution, simplified management)?
• How would a successful pilot change your willingness to adopt satellite-first designs across more sites? Options: Immediate rollout, Phased rollout, Further validation needed, Pilot-only interest
• Which stakeholders would need to see pilot results to greenlight expansion, and what format of evidence convinces them (dashboard, test log, executive summary)? Options: Technical dashboard, Test reports / logs, Executive summary, Site visits, Vendor demo

What Would It Take to Commit? Budget, Terms, and Timeline

• What budget range have you allocated or expect to allocate for the pilot and for a 12‑month operational phase? Options: <$10k, $10k–$50k, $50k–$250k, $250k–$1M, >$1M, Undecided
• What commercial structures do you prefer for satellite services? Options: Dedicated capacity (fixed Mbps), Shared contention plans, Burstable pooled capacity, Pay-as-you-go / consumption, Hybrid
• Which SLA elements matter most when comparing providers (select top 3)? Options: Availability %, Latency / jitter guarantees, Time to provision new sites, MTTR for outages, Financial penalties, Support hours & escalation
• How flexible must provisioning timelines be—are you comfortable with standard lead times or do you need rapid on-demand activation? Options: Need rapid activation (days), Accept standard lead times (weeks), Comfortable with months for hardware, Depends on region
• Would you consider a short-term commercial pilot with limited term and defined exit criteria to de-risk the full commitment? Options: Yes, ideal, Maybe with conditions, Prefer full contract, Not interested

Early Signals & Readiness — What We Need to Start Fast

• Which readiness items are already available to begin a pilot (choose all that apply)? Options: Site survey reports, Power and mounting diagrams, List of on-site contacts, Regulatory approvals in place, Network diagrams & IP plan, None of the above
• Are there preferred terminal classes or vendor hardware you must use or avoid? Options: Preferred list available, Must use specified vendor, Open to recommendations, Avoid certain vendors
• What lead-time constraints matter most for you: hardware procurement, field crew availability, or regulatory approvals? Options: Hardware procurement, Field crew availability, Regulatory approvals, All equally important
• What would be an acceptable pilot duration to validate both technical and operational assumptions? Options: 2–4 weeks, 1–3 months, 3–6 months, 6+ months
• What risks, if unaddressed, would cause you to pause or cancel the pilot? Please be specific so we can mitigate them.

Decision Rhythm & Next Steps — Who Signs and How Quickly?

• Who is the ultimate decision-maker for selecting a satellite connectivity partner, and who influences that person?
• What information or deliverables would shorten your procurement timeline (technical design, PoC, pricing bands, compliance proof)? Options: Technical design+diagram, Pilot pricing & terms, Compliance & certifications, Reference sites / case studies, All of the above
• What internal approvals or committee reviews typically slow decisions, and how can we help satisfy those gates?
• If we could remove one obstacle today to move you toward a pilot, what would that be?
• Would you like us to propose a concrete next step package (site survey + pilot scope + commercial term sheet) within a specific window? Options: Yes—deliver in 1 week, Yes—deliver in 2–3 weeks, Yes—deliver in a month, Not yet / need more discovery

• Solution Experience Kickoff — Current State & Consequence
• Scenario-Based Performance Validation
• Failure Modes & Resilience Workshop
• Terminal Selection, Field Fit & Installation Responsibilities
• Pilot Objectives, Acceptance Criteria & Go/No-Go

• Ops to provide terminal cut sheets, mounting diagrams, and power/backhaul requirements for each selected SKU.
• Introductions & Objectives
• Catalog the top failure modes and attach quantified consequences for each.
• Agree on mitigation architecture and the SLA/operational commitments needed to meet the future state.
• Define resilience acceptance criteria and tests to be executed in the pilot.
• Identify any compliance or regulatory constraints that change mitigation design.
• Create a failure-mode matrix showing RTO/RPO, business impact, mitigation, and responsible party.
• Schedule a failover simulation during the pilot with owners and success metrics defined.
• NOC to provide sample alerting and escalation playbooks tied to each failure mode.
• Site Environmental & Access Constraints
• Select terminal class per pilot site with clear justification tied to scenario KPIs.
• Agree installation responsibilities and produce a pre-deployment checklist for each site.
• Identify procurement lead times, mounting/permit risks, and any environmental mitigations required.
• Achieve a crystal-clear one-sentence current state statement from the customer.
• Customer to confirm site access windows, permits, and any local vendor constraints.
• Procurement to return lead-time estimates and place pilot device orders or reservations.
• Restate Future State & Pilot Purpose
• Agree a concise set of measurable pilot objectives aligned to the future state.
• Establish detailed acceptance tests with numeric pass/fail thresholds and owners.
• Set monitoring access, reporting cadence, and the go/no-go decision framework.
• Schedule pilot kick-off conditional on hardware availability and site readiness.
• Create and circulate the pilot test plan with responsibilities, timelines, and data templates.
• Ops to provision monitoring dashboards and grant customer access prior to pilot start.
• Confirm pilot kick-off date once hardware lead times and site access are verified.
• Surface and quantify the operational and financial consequences of the current state.
• Agree a one-sentence future state (target operational outcome) that the experience must prove.
• Confirm all required data and telemetry will be delivered for scenario validation.
• Customer to provide site list, traffic profiles, recent outage logs, and performance baselines (due in 48h).
• Seller to prepare coverage maps overlayed on customer sites and initial beam-capacity estimates.
• Schedule the Scenario-Based Performance Validation session and share prework requirements.
• Reconfirm Priority Scenarios & KPIs
• Map every prioritized scenario to a specific constellation, beam, and terminal class with clear assumptions.
• Demonstrate expected KPI performance through modeling or measured data for each scenario.
• Obtain explicit customer validation (thumbs-up / list of gaps) for at least one high-priority scenario to proceed to pilot design.
• Capture any modeling assumptions that require further testing or field validation.
• Seller to deliver per-scenario performance report with input assumptions, margin analysis, and recommended terminal SKU list.
• Customer to confirm and prioritize scenarios for the pilot (top 2–3), including success thresholds.
• Ops team to prepare any live tests or telemetry hooks required for pilot validation.
• Inventory Likely Failure Modes
• Consequence Mapping per Failure Mode
• Define Acceptance Tests & Pass/Fail Thresholds
• Customer Readback — One-sentence Current State
• Terminal Class Capabilities & Trade-offs
• Coverage & Beam Mapping (Diagnosis->Proof)
• Test Schedule, Responsibilities & Data Collection
• Consequence Quantification
• Mitigation Architecture & Trade-offs
• Terminal Class Mapping & Trade-offs
• Integration & Backhaul Considerations
• Proof of Mitigation — Timelines & Degraded Performance
• Performance Modeling / Simulation Proof
• Future State — One-sentence Target Outcome
• Monitoring Access & Reporting Cadence
• Installation Responsibilities & Pre-deploy Checklist
• Acceptance Criteria for Resilience Tests
• Pilot Device List & Validation
• Go/No-Go Decision Criteria and Next Steps
• Data & Prework Confirmation
• Validation Check — Customer Confirmation
• Clarify Assumptions & Next Deliverables

• Provision Dedicated Satellite Bandwidth Circuit
• Activate Shared Contention Service Plan
• Install and Commission VSAT Terminal and Antenna
• Mount and Align Stabilized Maritime Antenna System
• Install Aeronautical Broadband Terminal and Certification
• Configure Managed AES-256 Encrypted VPN Service
• Provision IP Addressing and BGP Peering
• Configure QoS and VoIP Prioritization Profiles
• Deploy Redundant Failover Routing (Terrestrial/Satellite)
• Provide 24/7 Network Operations Center Monitoring
• Deliver Customer Portal with Real-Time Usage Controls
• Perform Remote Terminal Management and OTA Updates
• Supply and Provision Spare Terminal Kits for Field

Provision Dedicated Satellite Bandwidth Circuit

• What committed bandwidth (CIR) do you require per site or circuit? Options: <5 Mbps, 5-25 Mbps, 25-100 Mbps, 100-500 Mbps, 500+ Mbps, Specify in free text
• What peak/burst bandwidth should be available above the committed rate (if any)? Options: No burst, 10% above CIR, 25% above CIR, On-demand burst (metered), Specify in free text
• Do you have a preferred satellite layer for the dedicated circuit? Options: GEO, MEO, LEO, No preference
• What SLA availability target do you require for the circuit? Options: 99.5%, 99.9%, 99.95%, Custom (specify)
• Which billing or commercial model do you prefer for dedicated capacity? Options: Committed monthly CIR, Usage-based (GB), Hybrid (commit + usage), Short-term trial/monthly, Other (specify)
• Are there regulatory or export controls, encryption restrictions, or geographic limitations that affect provisioning? Options: Yes, No

Activate Shared Contention Service Plan

• What is the expected average throughput per site under the shared plan? Options: <1 Mbps, 1-5 Mbps, 5-20 Mbps, 20-50 Mbps, 50+ Mbps, Specify in free text
• What peak-to-average contention tolerance is acceptable during congestion? Options: 1:1 (no contention), 2:1, 5:1, 10:1, Unsure - recommend sizing
• Do you require guaranteed minimum bandwidth during contention windows? Options: Yes - specify minimum in next field, No
• If guaranteed minimum required, specify minimum bandwidth per critical site (Mbps).
• Do you need traffic isolation (VLANs, private subnets) within the shared plan? Options: Yes, No
• Is tolerance for occasional throughput reduction during extreme events acceptable (e.g., weather, beam saturation)? Options: Yes, No

Install and Commission VSAT Terminal and Antenna

• What is the installation environment for the terminal and antenna? Options: Fixed site (ground mount), Rooftop, Pole mount, Maritime deck, Mobile trailer, Other (specify)
• What power sources are available at the installation site? Options: AC mains, Generator, Solar/Battery, 24/48V DC, Unknown - site survey required
• Which antenna size/class is preferred or required for this site? Options: Small (<=1m), Medium (1.2–1.8m), Large (>1.8m), No preference - recommend
• Will civil works, roof penetrations, or concrete pads be required for the mount? Options: Customer provides, Seller to provide, Shared/coordinate, Unknown - site survey required
• Who is responsible for cabling (RF, power, ethernet) and conduit installation? Options: Customer, Seller/Contractor, Third-party subcontractor, Shared
• What are the acceptance test criteria for commissioning (throughput, latency, jitter, packet loss)? Please specify numeric targets.

Mount and Align Stabilized Maritime Antenna System

• What type of vessel or platform will host the stabilized antenna? Options: Commercial vessel (cargo/tanker), Passenger vessel, Fishing vessel, Offshore platform, Pleasure craft, Other (specify)
• What level of stabilization/performance is required (able to operate at high vessel motion)? Options: High (operational at high sea state), Medium, Low (calm waters)
• Will the antenna be permanently mounted or require portable/roll-on capability? Options: Permanent mount, Portable/temporary, Trailerized, Unknown - advise
• Do operations require connectivity while underway at specific speeds? If yes, specify typical max speed (knots).
• What onboard power options exist for the stabilized system (voltage and redundancy)? Options: 24V DC, 48V DC, AC mains, Generator backup, Other (specify)
• Do you require spares or inline redundancy for stabilization components (e.g., spare gyros, spare modem)? Options: Yes, No

Install Aeronautical Broadband Terminal and Certification

• What aircraft platform will host the terminal? Options: Commercial airliner, Regional turboprop, Business jet, Rotorcraft/helicopter, Unmanned aerial vehicle, Other (specify)
• Which certification authorities or standards must be met (select all that apply)? Options: FAA, EASA, Local CAAs, DO-160 environmental, DO-178/DO-254 software/hardware, None/Not required
• Are there weight, drag, or installation envelope constraints that affect the terminal/pod selection? Options: Yes - provide limits in next field, No, Unknown - provide aircraft model for assessment
• If 'Yes', please specify weight, drag, or envelope limits (free text).
• Is in-flight acceptance testing, telemetry capture, or datalink certification part of the scope? Options: Yes, No
• Who will manage airworthiness paperwork and certification artifacts (customer, vendor, or third party)? Options: Customer, Seller/vendor, Third-party certifier, Shared

Configure Managed AES-256 Encrypted VPN Service

• How many VPN endpoints (sites or terminals) will participate in the managed VPN? Options: 1-5, 6-20, 21-100, 100+
• Which authentication method do you prefer for VPN endpoints? Options: PSK (pre-shared key), Certificate-based (PKI), Mutual TLS, OTP/2FA, HSM-based key storage
• Do you require customer-supplied encryption keys or vendor-managed keys (or HSM integration)? Options: Customer-supplied keys/HSM, Vendor-managed keys, Hybrid
• Are there compliance requirements for encryption (e.g., FIPS 140-2/3, government-only cryptography)? Options: Yes - specify in next field, No
• If 'Yes', please list required compliance frameworks or cryptographic constraints.
• Do you prefer full-tunnel (all traffic via VPN) or split-tunnel (select prefixes) VPN modes? Options: Full-tunnel, Split-tunnel, Hybrid

Provision IP Addressing and BGP Peering

• Do you require public IP addresses and direct BGP peering? Options: Yes - we have ASN, Yes - need ASN assigned, No - NAT/private addressing only
• Which IP protocol families are required? Options: IPv4, IPv6, Both IPv4 and IPv6
• Will each terminal/site need a static IP or will NAT be acceptable? Options: Static public IP per terminal, Static private IP with NAT, Dynamic IP acceptable
• Describe desired routing policy: advertise all prefixes, specific prefixes, or default route only. Options: Default route only, Advertise specific prefixes, Advertise all customer prefixes, Hybrid
• Estimate number of prefixes and expected prefix change frequency (daily/weekly/monthly).
• Do you require route filtering, RPKI validation, or prefix-limit protection? Options: Route filtering, RPKI validation, Prefix limits, None

Configure QoS and VoIP Prioritization Profiles

• Which latency-sensitive applications must be prioritized (select all that apply)? Options: VoIP/SIP, Video conferencing, Real-time telemetry/SCADA, Remote desktop/VDI, Other (specify)
• How many QoS classes do you want (e.g., gold/silver/bronze)? Options: 1-2, 3-4, 5+
• Do you require DSCP marking and end-to-end DSCP preservation for prioritized flows? Options: Yes, No, Unsure - recommend
• What numeric targets define acceptable voice quality (e.g., latency < X ms, jitter < Y ms, packet loss < Z%)? Provide values.
• Should QoS be applied per-site, per-terminal class, or globally across the fleet? Options: Per-site, Per-terminal class, Global, Hybrid
• Do you need SBC (Session Border Controller) or SIP normalization integrated as part of VoIP prioritization? Options: Yes, No

Deploy Redundant Failover Routing (Terrestrial/Satellite)

• Which terrestrial backup links are available or planned (select all that apply)? Options: Cellular (4G/5G), MPLS, DSL/Copper, L-Band backup, None/Not available
• What failover behavior do you want when primary path fails? Options: Automatic failover, Manual failover, Hybrid (manual for critical)
• Do you require active-active multi-path routing or active-passive priority-based failover? Options: Active-Active, Active-Passive, Depends on site
• What RTO/RPO or service continuity targets must be met during failover?
• Which health-check mechanisms should trigger failover (BGP, IP SLA, ping, HTTP/HTTPS)? Options: BGP, IP SLA, Ping/ICMP, HTTP/HTTPS, Other (specify)
• Do you require link-cost-based routing, weighted policies, or manual priority lists for path selection? Options: Link-cost-based (automated), Weighted policies, Manual priority list

Provide 24/7 Network Operations Center Monitoring

• Which monitoring categories should be included (select all that apply)? Options: Availability/Uptime, Performance (throughput/latency/jitter), Security/IDS, Hardware health (temperature/power), Configuration drift
• Which alerting channels do you require for incidents? Options: Email, SMS, Phone call/voice, Ticketing system/API, Chat ops (Slack/MS Teams)
• What incident response SLA do you need for critical (P1) events? Options: 15 minutes, 30 minutes, 1 hour, 4 hours, Custom
• Do you require direct escalation to satellite operations and engineering teams? Options: Yes, No
• What reporting cadence and detail do you want (real-time dashboards, daily summary, weekly/ monthly analytics)? Options: Real-time dashboard, Daily summary, Weekly report, Monthly executive report, Custom
• Do you want proactive maintenance windows and scheduled notification of known degradations? Options: Yes, No

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• SLA Penalties & Credits
• Commercial Terms & Pricing
• Payment & Invoicing Schedule
• Provisioning & Activation Schedule
• Installation & Responsibilities Matrix
• Pilot Acceptance & Handover Criteria
• Change Order & Scope Management
• Data Processing & Security Addendum (DPA)
• Compliance & Export Controls
• Escalation & Support Commitments
• Termination, Renewal & Exit Terms

• Pilot Operational Review
• Pilot Lessons & Root-Cause Workshop
• Backlog Prioritization & Roadmap Alignment
• Operational Handover & Monitoring Ownership
• Executive Review & Customer Sign-off

• Provision monitoring dashboard access and appropriate data feeds to ops and customer teams.
• Plan and schedule validation tests for each remediation with metrics to prove success.
• Document consequence calculations used during the workshop for exec summary.
• Backlog Overview
• Agree on a prioritized backlog with committed owners and delivery windows.
• Identify and document any contract or procurement actions needed to implement top items.
• Establish release waves and a communication plan for stakeholders.
• Publish the prioritized backlog with owners, estimates, and target milestones.
• Raise contract amendment requests or purchase orders for items requiring commercial change.
• Schedule follow-up sprint planning sessions for the first release wave.
• Assign a product/ops owner to maintain backlog health and status updates.
• Handover Checklist Review
• Ensure operations team has access, tools, and documentation to own steady-state support.
• Define clear alerting thresholds and escalation procedures mapped to SLA obligations.
• Establish training and review cadence to maintain performance and continuous improvement.
• Introductions & Objectives
• Publish and store runbooks in the shared knowledge repository with version control.
• Finalize on-call rota and distribute escalation contact matrix.
• Schedule initial training sessions and a tabletop incident exercise within 30 days.
• Executive Summary & Key Metrics
• Obtain executive-level acceptance or conditional sign-off to proceed to the agreed rollout phase.
• Ensure commercial and operational commitments (capacity, timelines, SLAs) are mutually agreed.
• Confirm remediation timelines for any residual high-risk items before broad rollout.
• Capture formal sign-off document or conditional acceptance and circulate to stakeholders.
• Finalize and sign any required SOW or contract amendments to support rollout.
• Publish an executive one-page summary with milestones, owners, and dates for the rollout.
• Schedule the official rollout kickoff and distribution of stakeholder communications.
• Confirm whether the pilot met each documented success signal with evidence.
• Identify and assign owners for any SLA breaches or high-impact incidents.
• Agree immediate remediation steps and a 72-hour action plan.
• Establish cadence for deeper investigation and follow-up sessions.
• Publish a consolidated pilot metrics report with annotated evidence for each success signal.
• Open RCA tickets for each SLA breach with assigned owners and target completion dates.
• Schedule 72-hour checkpoint meeting to validate temporary mitigations.
• Share raw telemetry and test scripts with customer engineering team for independent verification.
• Recap of Pilot Outcomes
• Produce RCA-backed corrective actions for the top failure modes.
• Define measurable acceptance criteria for each remediation so fixes can be validated.
• Capture reusable lessons and any updates needed to deployment runbooks.
• Identify quick wins that can reduce near-term SLA risk.
• Create prioritized remediation tickets with owners, estimated effort, and acceptance tests.
• Update deployment runbook and commissioning checklist to incorporate lessons learned.
• Pre-work & Data Validation
• Monitoring & Dashboard Walkthrough
• Prioritization Criteria Review
• Consequence Mapping
• Business Impact & Consequence Summary
• Prioritization Workshop
• Root-Cause Breakouts
• Metric-by-Metric Review
• Outstanding Risks and Remediations
• Alerting & Escalation Paths
• Runbooks & Playbooks
• Mitigation Options & Trade-offs
• Resource & Timeline Alignment
• SLA / Acceptance Criteria Status
• Commercial Commitments & Rollout Plan
• Commercial & Contract Implications
• Sign-off & Next Milestones
• Operational Impact Discussion