Satellite Internet Procurement Checklist for Enterprises

Buying satellite internet for enterprise use is not the same as ordering a fiber circuit or an MPLS link. Terrestrial procurement follows a well-worn path — RFP, site survey, install, handoff. Satellite procurement introduces variables that most IT procurement teams have never encountered: orbital mechanics affecting latency, weather-dependent availability, shared spectrum with contention ratios, hardware that lives on your roof and costs tens of thousands of dollars, and contracts structured around committed versus burst bandwidth that bear no resemblance to terrestrial pricing models.

The stakes are high. A poorly specified satellite contract at a remote mine, offshore platform, or field hospital can leave a site with unusable connectivity for years — locked into a term agreement with bandwidth that does not match the application mix, availability that falls short of operational requirements, and support response times measured in weeks rather than hours. This guide provides a structured procurement framework for enterprises evaluating satellite internet services, covering technical requirements, commercial terms, vendor evaluation, and the questions you should ask before signing anything.

---

When Enterprises Should Consider Satellite Internet

Satellite is not a first-choice WAN technology for sites where fiber, fixed wireless, or cellular is available and adequate. It becomes the right choice — often the only choice — when specific conditions apply:

• No terrestrial options exist — the site is beyond the reach of fiber, cable, fixed wireless, and reliable cellular. This is common for mining operations, offshore platforms, pipelines, remote construction, and rural infrastructure.
• Backup WAN for business continuity — the site has terrestrial connectivity but requires a geographically diverse backup path that does not share infrastructure with the primary link. Satellite provides path diversity that no terrestrial backup can match.
• Temporary or project-based deployments — construction sites, exploration camps, disaster response operations, and seasonal facilities need connectivity for weeks to months. Satellite can be deployed in hours without waiting for infrastructure buildout.
• Mobile and field operations — vehicles, vessels, aircraft, and mobile command posts require connectivity that moves with the operation.
• Regulatory or geographic constraints — some jurisdictions or terrain conditions make terrestrial infrastructure construction impractical, prohibitively expensive, or subject to permitting timelines that exceed operational deadlines.

If your site fits one or more of these scenarios, satellite belongs in your procurement evaluation. For a broader overview, see the enterprise satellite internet guide.

---

Common Procurement Scenarios

The procurement approach depends heavily on the use case. Each scenario has different requirements for bandwidth, latency, availability, contract terms, and hardware.

Primary Remote Connectivity

The satellite link is the only WAN connection for the site. All enterprise applications — email, ERP, cloud services, VoIP, video conferencing — must traverse it. This scenario demands the highest bandwidth, the most robust SLA, and careful application-level planning. Bandwidth must be sized for peak concurrent usage, not average.

Backup WAN and Disaster Recovery

Satellite serves as a failover path when the primary terrestrial link goes down. Bandwidth requirements may be lower (only critical applications need to work during failover), but activation time, automatic failover capability, and SLA responsiveness matter. Some providers offer "cold standby" plans with lower monthly costs that activate on demand — understand what "activation" means and how long it takes.

Temporary and Project Sites

Deployable terminals for construction, events, or emergency response. Key procurement factors are lead time (how fast can the terminal arrive and be commissioned), contract flexibility (monthly terms, not multi-year), and portability (can the terminal be relocated). Hardware lease models are often more appropriate than purchase for temporary deployments.

Mobile and Field Operations

Satellite-on-the-move (SOTM) or satellite-on-the-pause (SOTP) for vehicles, vessels, or portable operations. This scenario introduces additional requirements: auto-pointing antennas, vibration resistance, power consumption, and coverage across the operational area. Maritime and aviation satellite services have specialized procurement considerations.

Industrial, Energy, and Mining

Remote industrial sites often combine general enterprise connectivity with operational technology requirements — SCADA, telemetry, remote monitoring. The procurement must account for both IT and OT traffic, QoS separation, and potentially different SLA tiers for different traffic classes. See satellite internet for mining and remote industrial sites for detailed guidance.

---

Technical Requirements to Define Before Talking to Vendors

Before issuing an RFP or engaging satellite providers, define your technical requirements precisely. Vague requirements lead to proposals that cannot be compared and contracts that do not match operational needs.

Coverage Footprint

Document every site location (coordinates) that requires satellite connectivity. Coverage varies by satellite operator, beam, and frequency band. A provider with excellent coverage over Southeast Asia may have no capacity over West Africa. If your sites span multiple regions, you may need multiple providers or a provider with global reach.

Bandwidth Profile

Define your bandwidth requirements in terms that satellite providers understand:

• CIR (Committed Information Rate) — the minimum bandwidth guaranteed at all times, regardless of network load. This is what you are paying for and what the SLA covers. See CIR vs MIR for detailed explanation.
• MIR (Maximum Information Rate) — the peak bandwidth available when other users on the same beam are not consuming their share. MIR is not guaranteed and should not be used for capacity planning.
• Symmetric vs asymmetric — satellite services are typically asymmetric (more download than upload). If your applications generate significant upstream traffic (video conferencing, cloud backup, SCADA telemetry), specify your upload requirements separately.
• Contention ratio — on shared services, understand how many subscribers share the same capacity pool. A contention ratio of 20:1 means very different peak-hour performance than 5:1.

Latency Tolerance

Different applications have different latency requirements. GEO satellite introduces ~600 ms round-trip delay; LEO offers ~20–60 ms. Map your application mix to latency requirements before evaluating providers. See satellite latency comparison for a detailed breakdown by orbit type and application.

Uptime and Availability Targets

Define your required availability as a percentage (e.g., 99.5%, 99.9%) and understand what that means in practice — 99.5% allows over 43 hours of downtime per year. Match your operational requirements to realistic satellite availability targets. Weather, equipment faults, and planned maintenance all affect availability. See satellite link availability and satellite SLA terms for guidance on what to specify and how to verify.

Application Mix

Document every application that will use the satellite link, including:

• VoIP and video conferencing (sensitive to latency and jitter)
• Cloud applications and SaaS (sensitive to latency for interactive use)
• SCADA and telemetry (low bandwidth but high priority)
• Email and web browsing (tolerant of latency)
• File transfer and backup (bandwidth-intensive, latency-tolerant)
• Video surveillance (high bandwidth, can be scheduled)

This application inventory drives bandwidth sizing, QoS policy design, and the need for QoS and traffic shaping capabilities in the satellite service.

Security and Compliance Requirements

Specify encryption requirements (VPN, IPsec), regulatory compliance (data sovereignty, industry regulations), and network segmentation needs (OT/IT separation). Some satellite services offer built-in encryption; others require customer-provided VPN equipment.

---

Commercial Factors

Satellite service pricing is structurally different from terrestrial WAN pricing. Understanding these factors prevents costly surprises.

---

Operational Factors

Technical and commercial terms matter, but operational realities determine whether the service actually works for your organization.

Deployment Lead Time

How long from contract signing to operational service? Satellite deployments involve equipment procurement, shipping (often to remote locations with limited logistics), site preparation, installation, and commissioning. Lead times of 4–12 weeks are common; rush deployments cost more.

Field Support and Spares

When hardware fails at a remote site, how quickly can it be replaced? Evaluate the provider's spare parts inventory, field service coverage area, and response time commitments. For critical sites, consider maintaining your own spare terminal equipment.

Monitoring and Reporting

What visibility do you get into link performance? Good providers offer real-time dashboards showing bandwidth utilization, latency, packet loss, and availability metrics. This data is essential for troubleshooting and SLA verification. See remote site network monitoring over satellite for what to monitor and how.

Escalation Process

When something goes wrong, who do you call and what happens? Map the provider's escalation path from first-line support through engineering to management. Understand response time commitments at each tier and whether your contract includes priority escalation.

Training and Documentation

Will the provider train your local IT staff on basic terminal troubleshooting? Is documentation available for the specific hardware and service configuration deployed at your sites? Self-service capability for common issues (terminal reboot, basic diagnostics) reduces dependency on provider support.

---

GEO vs LEO vs Hybrid: Buying Considerations

The choice between GEO and LEO satellite services is one of the most consequential procurement decisions. Each has distinct advantages and trade-offs. For an in-depth technical comparison, see the VSAT vs Starlink comparison.

Key buying insight: GEO VSAT remains the standard for enterprise deployments requiring guaranteed bandwidth (CIR), defined SLAs, and proven operational support. LEO is compelling for latency-sensitive applications and sites where GEO pricing is prohibitive, but enterprise-grade SLAs and support are still maturing. Hybrid architectures — using GEO for guaranteed capacity and LEO for burst or latency-sensitive traffic — are increasingly practical but add operational complexity.

---

Red Flags in Satellite Service Proposals

Watch for these warning signs when reviewing satellite provider proposals:

1. MIR quoted without CIR — a proposal that only states maximum bandwidth without specifying committed bandwidth is selling you shared capacity with no guarantee. Ask for the CIR explicitly.
2. Availability claims without methodology — "99.9% availability" means nothing without knowing how availability is measured, what counts as downtime, and what the remedy is for SLA breach.
3. No mention of contention ratio — if the provider will not disclose the contention ratio on shared services, assume it is high.
4. Hardware costs buried in fine print — some proposals show low monthly fees but require separate hardware purchase, installation fees, and commissioning charges that double the first-year cost.
5. No escalation path defined — if the provider cannot describe their support tiers and escalation process during the sales cycle, support will not improve after you sign.
6. Unrealistic lead times — a provider promising 2-week deployment to a remote site in a developing country is either not accounting for logistics or not planning to do a proper installation.
7. No site survey included — proper satellite installation requires a site survey to verify line-of-sight, identify interference sources, and plan mounting and cabling. Providers who skip this step are cutting corners.
8. Contract auto-renewal with short notice period — some contracts auto-renew for additional terms unless cancelled 60–90 days before expiry. Miss the window and you are locked in.
9. No performance reporting or dashboard access — if you cannot independently verify service performance, you cannot enforce the SLA.
10. Penalty-free exit only for provider — read termination clauses carefully. If the provider can terminate with 30 days notice but you face 12 months of remaining fees, the contract is one-sided.

---

Questions to Ask Satellite Providers

Technical Questions

• What is the CIR and MIR for the proposed service? What is the contention ratio?
• What satellite(s) and beam(s) will serve my site(s)? What is the beam loading?
• What is the measured latency (RTT) and jitter for the proposed service at my site coordinates?
• What frequency band (C, Ku, Ka) is used, and what is the rain fade margin at my site?
• Does the service support QoS? Can I define traffic classes and priorities?
• What happens to my service if the satellite reaches end of life or is repositioned during my contract?
• What is the terminal hardware specification (antenna size, modem model, BUC power)?

Commercial Questions

• What is the total first-year cost including hardware, installation, commissioning, and monthly service?
• Is hardware purchased or leased? Who owns it at contract end?
• What are the early termination fees at each year of the contract?
• How is bandwidth overage or burst usage priced?
• Is the SLA backed by service credits? What is the credit calculation methodology?
• Are there annual price escalation clauses?
• What is included in the support fee, and what costs extra (field visits, hardware replacement)?

Operational Questions

• What is the deployment lead time from contract signing to service activation?
• What is the NOC operating hours and escalation process?
• What is the mean time to repair (MTTR) for hardware failure at a remote site?
• Do you maintain spare equipment in-country or in-region?
• What monitoring tools and dashboards are available to the customer?
• What training is provided for on-site staff?
• How do you handle planned maintenance, and what is the notification lead time?

---

Sample Procurement Checklist

Use this checklist to ensure complete coverage during the procurement process:

Requirements Definition

1. Document all site locations with GPS coordinates
2. Define bandwidth requirements per site (CIR and MIR, upstream and downstream)
3. Identify latency-sensitive applications and their tolerance thresholds
4. Specify availability targets per site (e.g., 99.5%, 99.9%)
5. Document the application mix and estimate traffic profile per application
6. Define security requirements (encryption, compliance, network segmentation)
7. Identify any regulatory or licensing requirements for satellite use at each site

RFP and Vendor Engagement 8. Issue RFP to at least 3 qualified satellite providers 9. Require itemized pricing (hardware, installation, monthly service, support) 10. Request CIR, MIR, and contention ratio for each proposed service tier 11. Require SLA terms including availability definition, measurement method, and remedies 12. Request reference customers in similar industries or geographies 13. Require a site survey plan and timeline

Technical Evaluation 14. Verify satellite coverage at each site coordinate using provider's coverage maps 15. Evaluate terminal hardware specifications against site conditions (wind loading, temperature, power) 16. Confirm QoS capabilities match your traffic classification requirements 17. Assess monitoring and reporting capabilities 18. Verify compatibility with your existing network infrastructure (routers, firewalls, VPN) 19. Evaluate provider's network redundancy and disaster recovery capabilities

Commercial Evaluation 20. Compare total cost of ownership over the contract term (not just monthly fees) 21. Review termination clauses and penalties 22. Evaluate hardware ownership terms 23. Assess support model and field service coverage 24. Review auto-renewal terms and notice periods 25. Verify SLA credit methodology and exclusions

Pre-Deployment 26. Conduct site survey at each location 27. Verify line-of-sight to the satellite (no obstructions) 28. Confirm power availability and backup power at each site 29. Plan network integration (IP addressing, routing, VPN configuration) 30. Schedule installation with realistic lead times including logistics

Post-Deployment 31. Conduct acceptance testing against SLA parameters 32. Verify all applications function correctly over the satellite link 33. Establish baseline performance metrics for ongoing comparison 34. Confirm monitoring dashboards are accessible and accurate 35. Document escalation contacts and procedures

---

Vendor Evaluation Scorecard

Use this scorecard to compare satellite providers objectively. Adjust weights to reflect your organization's priorities.

Score each vendor 1–10 per category, multiply by weight, and sum for a weighted total. The scorecard forces structured comparison and reduces the influence of sales presentations on the decision.

---

How to Shortlist Without Overbuying

Enterprise satellite procurement often results in overbuying — more bandwidth, longer contracts, and more expensive hardware than the operational reality requires. This happens because procurement teams, unfamiliar with satellite, default to conservative specifications.

Right-size bandwidth using actual traffic data. If you have an existing connection at the site (even cellular), measure actual peak and average utilization. If the site is new, estimate based on user count, application mix, and usage patterns — then add 20–30% headroom, not 200%.

Start with CIR that matches your baseline, not your peak. Buy CIR for sustained traffic and rely on MIR or burst for peaks. A 5 Mbps CIR with 10 Mbps MIR costs significantly less than 10 Mbps CIR and handles most enterprise workloads.

Match contract length to site certainty. If the site has a defined operational life (e.g., a 2-year construction project), do not sign a 3-year satellite contract. Pay a modest premium for a shorter term rather than risk termination penalties.

Consider phased deployment. Start with a baseline service, measure actual usage for 2–3 months, then upgrade if needed. Most providers can increase bandwidth without hardware changes. Downgrades are harder — confirm downgrade terms before signing.

Evaluate GEO before defaulting to LEO. LEO services like Starlink offer compelling pricing and low latency, but enterprise support, SLAs, and guaranteed capacity are still maturing. For many enterprise use cases, GEO VSAT with proper QoS delivers better reliability at a predictable cost. Visit the satellite provider comparison and satellite service providers directory to evaluate options.

---

FAQ

What is the typical cost of enterprise satellite internet?

Enterprise satellite internet costs vary widely depending on bandwidth, coverage region, and service tier. GEO VSAT services typically range from $200–$2,000+ per month for 2–20 Mbps CIR, plus $3,000–$15,000 for terminal hardware and installation. LEO services may start lower ($100–$500/month) but often lack enterprise SLAs. Total first-year cost including hardware, installation, and service is the right comparison metric — not monthly fee alone.

How long does it take to deploy satellite internet at a remote site?

Typical deployment timelines range from 4–12 weeks from contract signing to operational service. This includes equipment procurement and shipping (2–6 weeks, depending on location), site preparation (1–2 weeks), and installation and commissioning (1–3 days on-site). Rush deployments are possible at additional cost. LEO terminals (e.g., Starlink) can be self-installed in hours if pre-ordered, but enterprise-grade installation with proper mounting, grounding, and network integration still requires professional services.

Should I buy or lease satellite terminal equipment?

Buy if the site is permanent and the contract term is 3+ years — ownership avoids recurring lease fees and gives you control over the hardware. Lease if the deployment is temporary, the technology may change, or you prefer predictable OPEX. Some providers bundle hardware into the monthly fee — verify whether this is a lease (hardware returned at contract end) or amortized purchase (hardware is yours).

What SLA should I expect for enterprise satellite internet?

Enterprise-grade GEO VSAT services typically offer 99.5%–99.7% link availability SLAs, with premium services reaching 99.9%. SLA availability is usually measured monthly and excludes planned maintenance and force majeure events. Ensure the SLA includes specific remedies (service credits) and that the measurement methodology is clearly defined. For guidance on evaluating SLA terms, see satellite SLA terms.

Can I use satellite internet for VoIP and video conferencing?

Yes, with caveats. GEO satellite introduces ~600 ms round-trip delay, which is noticeable in voice calls and creates conversation overlap in video meetings. VoIP works but requires jitter buffering and QoS prioritization. Video conferencing works for small meetings but high-participant calls may struggle with bandwidth and latency. LEO satellite services provide a significantly better experience for real-time communications due to lower latency. For all satellite VoIP deployments, ensure the service supports QoS and traffic shaping to prioritize voice traffic.

How do I compare satellite providers objectively?

Use a structured evaluation framework: define your requirements first, then score providers against those requirements using a weighted scorecard (see the scorecard template in this article). Compare total cost of ownership — not just monthly fees. Request and check reference customers. Conduct a pilot if possible. For a step-by-step evaluation methodology, see how to evaluate a satellite internet provider.

---

Conclusion

Satellite internet procurement for enterprises requires a structured approach that accounts for technical, commercial, and operational factors that do not exist in terrestrial WAN procurement. Define your requirements precisely before engaging vendors. Use the checklist and scorecard in this article to ensure complete coverage and objective comparison. Watch for red flags, ask the right questions, and resist the temptation to overbuy.

The best satellite procurement outcome is a service that matches your operational requirements at a predictable cost, backed by an SLA you can enforce, supported by a provider who can actually deliver at your site locations. Start with requirements, not proposals — and let the requirements drive the evaluation.

---

Related Articles

• How to Evaluate a Satellite Internet Provider — Step-by-step framework for assessing satellite providers covering technical capability, commercial terms, and operational readiness.
• Enterprise Satellite Internet Guide — End-to-end planning guide for enterprise satellite deployments covering architecture, provider evaluation, and operational management.
• Satellite SLA Explained — Engineering guide to satellite service level agreements covering availability commitments, performance metrics, and evaluation methodology.
• VSAT vs Starlink — Detailed comparison of traditional GEO VSAT and LEO Starlink for enterprise and remote site connectivity.
• CIR vs MIR Satellite Explained — Understanding committed vs maximum information rates in satellite bandwidth pricing and SLAs.
• Satellite Internet for Mining and Remote Industrial Sites — Comprehensive guide to deploying satellite connectivity for mining operations and industrial environments.