Why most IoT provider decisions fail
Most RFPs focus on:
- coverage claims
- cost per MB
- SIM type
These are not the factors that fail at scale.
What happens when you scale
- devices deployed across multiple countries
- reliance on multiple networks
- long device lifecycles (5–15 years)
- increasing compliance requirements
Where decisions break
The wrong provider leads to:
- downtime from network instability
- inability to switch networks
- lack of visibility into device behaviour
- unpredictable costs
Most of these issues are not visible during evaluation.
How to use this checklist
Use this to:
- evaluate new providers
- benchmark your current provider
- structure RFP questions
- identify hidden risks
Scoring model
- Yes (fully supported): 2 points
- Partial / limited: 1 point
- No: 0 points
Weighting (critical vs non-critical)
- Questions 1–10 (connectivity + security): high impact
- Questions 11–15 (CMP): critical for scale
- Questions 16–20 (cost + compliance): commercial impact
Score interpretation
- 30–40: Enterprise-ready
- 20–29: Gaps that will impact scale
- 0–19: High risk for global deployments
Section 1: Global connectivity and reliability
1. Do you provide multi-network access per country (not just roaming)?
Why it matters:
Roaming-only models lead to degraded performance and downtime.
What good looks like:
- direct access to multiple networks per country
- not dependent on roaming agreements
Red flag:
- “global coverage” based purely on roaming
2. Does your SIM support multi-IMSI or equivalent switching?
Why it matters:
Improves resilience and reduces single-operator dependency.
What good looks like:
- multiple IMSIs or profiles
- dynamic switching
Red flag:
- fixed IMSI with limited fallback
3. Can devices automatically switch to the best available network?
Why it matters:
Prevents devices staying connected to weak networks.
What good looks like:
- signal and performance-based switching
Red flag:
- manual or static network selection
4. How do you handle cross-border connectivity?
Why it matters:
Performance changes significantly across borders.
What good looks like:
- seamless transition between networks
- no reliance on roaming priority
Red flag:
- degraded performance outside home region
5. What happens when a network fails?
Why it matters:
Fallback determines uptime.
What good looks like:
- automatic failover
- minimal downtime
Red flag:
- manual intervention required
Section 2: Security and network architecture
6. Is device traffic routed over the public internet?
Why it matters:
Public routing increases exposure.
What good looks like:
- private routing
- controlled network paths
Red flag:
- reliance on public internet + VPN
7. Do you offer private networking beyond APN?
Why it matters:
APNs do not provide full isolation or control.
What good looks like:
- isolated routing (e.g. SecureNet model)
- private IP addressing
Red flag:
- APN presented as full security solution
8. How is access controlled between devices and backend systems?
Why it matters:
Prevents lateral movement.
What good looks like:
- identity-based access control
- per-device or per-session rules
Red flag:
9. Do you support Zero Trust principles?
Why it matters:
Required for modern IoT security and compliance.
What good looks like:
- per-session validation
- continuous verification
Red flag:
10. Can you segment traffic by device, application, or region?
Why it matters:
Required for compliance and risk control.
What good looks like:
- granular segmentation
- policy enforcement
Red flag:
Section 3: Visibility and control (CMP)
11. Do you provide real-time SIM and device visibility?
Why it matters:
Without visibility, you cannot manage scale.
What good looks like:
- live status and usage data
Red flag:
- delayed or limited reporting
12. Can you detect and alert on anomalies?
Why it matters:
Improves response time.
What good looks like:
- automated alerts
- anomaly detection
Red flag:
13. Do you provide diagnostics and troubleshooting tools?
Why it matters:
Reduces downtime.
What good looks like:
- network diagnostics
- root cause insights
Red flag:
- limited support visibility
14. Can SIM lifecycle be managed centrally?
Why it matters:
Manual processes do not scale.
What good looks like:
- activation, suspension, updates via platform
Red flag:
- manual or fragmented processes
15. Do you provide API access?
Why it matters:
Enables automation and integration.
What good looks like:
Red flag:
Section 4: Cost structure and scalability
16. Do you offer data pooling?
Why it matters:
Reduces waste and improves efficiency.
What good looks like:
- shared usage across devices
Red flag:
17. How do you handle overages?
Why it matters:
Prevents cost spikes.
What good looks like:
- predictable pricing
- usage controls
Red flag:
18. Can pricing scale globally?
Why it matters:
Regional pricing can create cost variability.
What good looks like:
- consistent global pricing model
Red flag:
- fragmented regional pricing
Section 5: Compliance and enterprise readiness
19. How do you support compliance (e.g. NIS2)?
Why it matters:
Requires segmentation, monitoring, and control.
What good looks like:
- built-in support for compliance requirements
Red flag:
- reliance on external tools
20. Do you provide a single global platform?
Why it matters:
Fragmentation increases complexity.
What good looks like:
Red flag:
- multiple regional platforms
What your score actually means
30–40: Enterprise-ready
- strong reliability
- scalable operations
- compliant architecture
20–29: Scaling risk
- hidden gaps
- future operational issues
0–19: High risk
- not suitable for global deployments
- likely to fail at scale
What to do next based on your score
High score (30–40)
- validate performance in production
- optimise cost and usage
Medium score (20–29)
- identify critical gaps
- prioritise improvements
- consider alternative providers
Low score (0–19)
- high risk of failure
- reassess provider strategy
Where most providers fail (real-world patterns)
- reliance on roaming instead of multi-network access
- VPN-based security models
- lack of real-time visibility
- fragmented platforms
These issues are not visible in basic evaluations.
Why this checklist matters before RFP decisions
Switching providers later requires:
- device changes
- SIM replacement
- operational disruption
Getting this right upfront avoids:
- long-term cost
- downtime
- complexity
Why enterprises choose IXT
This checklist reflects what enterprise deployments require.
IXT is built around these principles:
Connectivity
- multi-network global access
- multi-IMSI architecture
Security
Zero Trust enforcement, including private networking and traffic isolation- Clientless remote access with no VPN clients required on devices
-
Control
- CMP with real-time visibility
- diagnostics and automation
Cost
- data pooling
- predictable pricing
Result
- higher uptime
- reduced risk
- scalable operations
FAQs
What should you look for in an IoT connectivity provider?
You should evaluate reliability, security architecture, lifecycle management, cost structure, and global scalability. Coverage alone is not enough.
What is the most important factor in IoT connectivity?
Reliability and control are more important than coverage or price at enterprise scale.
How do you evaluate an IoT provider?
Use structured criteria covering connectivity, security, visibility, and cost. Ask detailed questions and assess real capabilities.
What is a CMP?
A Connectivity Management Platform provides visibility, control, diagnostics, and automation for IoT connectivity.
Why is multi-network access important?
It improves reliability by allowing devices to switch networks and avoid failures.
What are the risks of choosing the wrong provider?
- downtime
- security exposure
- high cost
- limited scalability
How does IoT connectivity affect compliance?
Connectivity must support segmentation, monitoring, and control to meet regulatory requirements.
Is coverage enough when choosing a provider?
No. Reliability, control, and visibility are more important.
Final recommendation
Do not evaluate providers based on:
At enterprise scale, success depends on:
- reliability
- control
- visibility
- security
Use this checklist to identify gaps before they become failures.
Speak to an IoT connectivity specialist
Get a structured review of your current provider and evaluation criteria:
- identify gaps in reliability, security, and global coverage
- pressure-test your RFP against real enterprise requirements
- validate whether your current provider will scale
- map a more resilient, future-proof connectivity architecture
Make sure your next provider decision holds up at 1,000+ devices, across regions, and under real operational conditions.
