Define the service before comparing hosts
A proposal cannot be evaluated until the product requirements are concrete. Create one requirements sheet for every bidder so differences are commercial or technical—not artifacts of different assumptions.
- Customer segments, launch markets, critical routes, and indoor or rural requirements
- Voice, messaging, data, hotspot, fixed wireless, IoT, and international use cases
- Expected subscriber ramp, monthly usage distribution, seasonality, and peak concurrency
- Physical SIM, consumer eSIM, IoT eSIM, bring-your-own-device, and device-financing needs
- Required launch date, migration constraints, support hours, and compliance responsibilities
Score geography with customer-weighted evidence
National coverage percentages can obscure the places where customers actually live, work, and travel. Weight the evaluation by forecast subscribers or device count in each market and define minimum outcomes for critical locations.
| Requirement | Evidence to request | Pilot check |
|---|---|---|
| Launch-market footprint | Plan-specific map and technology layers | Outdoor and indoor tests at representative addresses |
| Domestic roaming | Included footprint, limits, and exclusions | Known roaming locations and handoff behavior |
| Capacity and performance | Available disclosures and escalation process | Peak-hour voice, upload, download, and latency |
| International service | Country, network, feature, and rate eligibility | Provisioning and usage controls in priority countries |
| Resilience | Incident communication and recovery process | Document notification contacts and fallback procedure |
Qualify devices and provisioning together
A strong footprint is not useful if the intended hardware cannot be activated reliably. Evaluate certification, device compatibility, SIM logistics, APIs, and exception handling as one operational flow.
- Build a device matrix with model, variant, radio bands, VoLTE, eSIM, and intended market.
- Test IMEI eligibility, physical SIM, eSIM download, activation, suspension, restoration, swap, and cancellation.
- Confirm API authentication, idempotency, rate limits, error codes, webhook delivery, sandbox fidelity, and production access.
- Measure manual steps and ownership when an automated order fails.
- For IoT, verify lifecycle, remote provisioning, private networking, telemetry, and long deployment horizons.
Model wholesale and usage economics
Use the actual confidential proposal and your own cohort assumptions. Do not substitute public retail prices or an online carrier ranking for wholesale economics. Normalize every bid into the same model and include one-time, recurring, usage, minimum, support, platform, SIM, shipping, tax, and compliance costs where applicable.
Run base, high-usage, low-growth, and roaming-heavy scenarios. Contribution margin should remain distinct from operating profit: staffing, marketing, software, bad debt, and other fixed costs still matter.
| Input | Normalize as | Question to resolve |
|---|---|---|
| Usage charges | Cost by voice, message, data, roaming, and feature unit | Are tiers pooled, committed, per-line, or account-wide? |
| Minimums and commitments | Monthly and term cash obligation | What happens before scale or after a forecast miss? |
| Platform and operations | One-time plus recurring cost | Which functions and support levels are included? |
| Overage and outliers | Cohort-weighted expected cost | How are fraud, abuse, and unusually heavy users treated? |
| Change mechanics | Scenario by effective date | Can rates, network rules, or pass-through charges change during term? |
Rehearse activation and number porting
Porting is a customer journey and an inter-provider process, not just an API endpoint. The FCC states that consumers can generally keep an existing number when switching providers in the same geographic area, but valid requests can still be delayed by mismatched account data, fraud controls, unsupported numbers, or unresolved exceptions.
- Test new-number assignment, port-in validation, submission, status, completion, cancellation, and port-out.
- Define ownership for rejections, stuck ports, partial failures, emergency escalation, and customer updates.
- Confirm local number availability in launch markets and any aging or inventory rules.
- Measure activation and port completion using a representative pilot, not a best-case demonstration.
Inspect support and escalation before launch
Request the operating model in writing and run a tabletop incident. The key question is not whether support exists, but whether your team can reach the right technical and commercial owner quickly with useful status information.
| Area | Document before signing | Test |
|---|---|---|
| Severity and response | Severity definitions, response targets, and service hours | Submit representative tickets at each severity |
| Network incident | Notification, status cadence, bridge access, and closure report | Run an outage tabletop with named contacts |
| Provisioning failure | Tier boundaries and engineering escalation | Trace one failed order end to end |
| Fraud and security | Controls, suspension authority, evidence, and notification | Simulate account takeover or SIM-swap response |
| Commercial dispute | Usage record, invoice, and credit process | Reconcile a sample wholesale invoice |
Contractual diligence checklist
Telecom counsel should review the final agreement and the allocation of regulatory duties. The business team should still maintain a plain-language issues list so operational promises are reflected in enforceable documents.
- Service description, eligible products, coverage references, and incorporated policies
- Term, renewal, termination, minimum commitments, deposits, credit support, and wind-down assistance
- Pricing units, taxes, pass-through charges, audit rights, dispute windows, and change notice
- Service levels, remedies, planned maintenance, incident notice, and force-majeure treatment
- Data rights, CPNI and privacy roles, security controls, breach notice, records, and subcontractors
- Numbering, porting, emergency services, lawful process, accessibility, and regulatory responsibility
- Brand, customer ownership, solicitation limits, confidentiality, publicity, and intellectual property
- Device acceptance, prohibited use, fraud allocation, insurance, indemnity, liability, and transition rights
Plan expansion before the first contract
Expansion can mean new plans, market segments, countries, network profiles, device classes, or an additional host. Ask what requires an amendment, a new integration, certification, minimum commitment, or migration.
- Can the platform support multiple network profiles and preserve a consistent customer experience?
- Who controls SIM profiles, phone numbers, customer data, and credentials during a migration?
- What are the lead times and acceptance criteria for new devices, features, and geographies?
- Can usage, provisioning, and support data be exported in documented formats?
- What transition services apply at expiration or termination?
Make a traceable decision
Use weighted criteria tied to approved requirements, attach evidence to each score, and record unresolved assumptions. A sensible gate order is: mandatory coverage and compliance, device and provisioning proof, operational readiness, normalized economics, then contract risk. A low headline rate should not offset a failed mandatory requirement.
Revisit the decision before launch and at renewal. The network, product, usage mix, and customer footprint can all change.