eSIM global connectivity: 160+ countries, 240+ networks, multi-carrier switching

Framing

Why global connectivity is a different problem now

Global connectivity used to be solved by a single thing: a roaming contract with a mobile operator. The contract was expensive, opaque, and limited. A business traveller landing in three countries in a week would return home to a roaming bill that the finance team questioned. A field service operation in five countries would maintain relationships with five mobile operators, each on a different contract, each with a different commercial model. A distributed team would carry a drawer of physical SIM cards, each tied to a country, each requiring a swap when the border was crossed.

That model is finished. The technology that replaces it is the eSIM: a GSMA-compliant embedded SIM that holds multiple operator profiles, switches between them automatically, and connects to the strongest available LTE-Advanced or 5G network without a physical swap. We deliver data-only eSIMs by email QR code, in 160+ countries and 240+ network operators, with multi-carrier switching as a default. The user keeps their existing number; the eSIM adds data.

For a connected-ecosystem organisation, the eSIM is not a separate product line. It is one of thirteen layers, and it connects to the rest. A device provisioned with an eSIM is a device that can be tracked, secured, and supported through the same stack as the company's hosting, voice, and AI. The support model is one team, not four. The procurement is one process, not five.

This article sets out the architecture, the operating model, and the economics of eSIM for organisations that operate across borders. It is written for IT leads, operations directors, and finance teams who have lived through the roaming-bill problem and the multi-SIM-drawer problem, and are ready for a single platform that handles both.

The shift to eSIM is not just a technology upgrade. It is a structural change in how organisations procure, manage, and account for mobile connectivity. The old model treated mobile as a per-country, per-operator, per-employee line item, with all the variability and overhead that implies. The new model treats mobile as a per-device, per-plan, per-period line item, with published pricing and predictable behaviour. The finance team can plan, the security team can enforce, the operations team can scale, and the user can travel.

The eSIM is also the practical answer to a question that has been getting harder to ignore: how do you give a global workforce global connectivity without giving up control of the cost, the security, or the user experience? The old answer was a stack of national operators, a drawer of SIMs, a helpdesk in five time zones, and a monthly invoice that nobody could explain. The new answer is one platform, one catalogue, one QR code, and one support team. That is the architectural change, and the architectural change is what scales.

Architecture

What an eSIM actually is and what is inspectable

An eSIM is an embedded SIM card — a small chip soldered to the device's mainboard, programmable over the air, governed by the GSMA specification. The relevant standards are SGP.22 for consumer devices, SGP.02 for M2M, and the eUICC security framework that defines how operator profiles are loaded, authenticated, and removed. Where the device supports the standard, the eSIM works. Where it does not, we tell the buyer before they buy.

Our eSIM plans are data-only, pay-as-you-go, and delivered by email QR code. The QR code contains the activation profile. The user scans it, the profile downloads, and the device connects to the strongest available LTE-Advanced or 5G network in the destination country. Multi-carrier switching is automatic: if the device loses signal on one network, it scans for and connects to another, without user action. The plan family covers single-country, regional/multi-country, global, and day-pass variants, with pricing from approximately USD 1 to USD 174 across the catalogue.

Coverage is 160+ countries and 240+ network operators. This is the canonical figure. Where legacy material cites 120+, 130+, or 190+ countries, those numbers are inconsistent and superseded. The verification is the published network list, which names the operator, the country, the technology, and the supported bands. A buyer can audit the list before procurement.

Devices supported include modern iPhone (XS and later), Google Pixel (3 and later), Samsung Galaxy (S20 and later), iPad Pro and iPad Air (3rd generation and later), and laptops with eSIM-capable cellular modems. The list is published and kept current. Where a device is in the catalogue but the eSIM is not yet provisioned for the buyer's region, the platform surfaces that fact at purchase time, not at activation time.

The architecture is inspectable. The user has full control of installed profiles, can add, switch, and remove profiles, and can see the data consumption and remaining balance at any time. The user keeps their existing phone number — the eSIM adds a separate data channel. The architecture does not require a contract, a credit check, or a minimum commitment. The user pays for what they use.

The eUICC security framework deserves more than a passing mention. It defines how profiles are loaded, how they are authenticated, how they are isolated from each other, and how they are removed when the user changes operator or the device is decommissioned. The framework is published by the GSMA as a public specification. It is auditable. It is testable. A buyer can read the specification and verify that the eSIM platform complies with it. The compliance is verifiable, not a claim.

The coverage list is the architectural contract. The list names the country, the network operator, the technology (LTE-Advanced or 5G), and the supported frequency bands. A buyer can audit the list before procurement, validate it against the buyer's own travel patterns, and decide whether the platform covers the use case. Where the list does not cover a country the buyer needs, the buyer is told before the buy, not at the destination. The architectural contract is the published list, and the published list is the audit basis.

Operating model

Self-serve, managed, or embedded in managed IT

The eSIM supports three engagement models. The first is self-serve: the user browses the catalogue at esim.grahammiranda.com, selects a plan, pays, and receives the QR code by email. The activation takes about a minute on a modern device. The user is the operator, the platform is the supply chain, and the support is the published documentation. This is the right model for individuals, distributed teams, and organisations with internal IT capability.

The second is managed: the organisation has a fleet of eSIM-equipped devices, and we operate the provisioning, the renewal, the alerting on data thresholds, and the response to coverage issues. The commercial model is per device, with a published price list. The support is direct, not through a third-party helpdesk. This is the right model for organisations that want the capability without the procurement overhead.

The third is embedded in managed IT: the eSIM is one of thirteen service lines in the connected ecosystem, and it is operated as part of the same platform as hosting, voice, AI, and cybersecurity. A device issue is one ticket to one team. A coverage question is one escalation. A renewal is one procurement event. The eSIM is not a separate vendor; it is a layer in the architecture.

Across all three models, the user keeps the option to leave. The eSIM is GSMA-compliant and not tied to a specific operator. The user can download a profile from another provider, install it, and the eSIM is theirs. The data consumption and remaining balance are visible to the user at any time. There is no lock-in.

The platform supports up to 12 languages for the user-facing surfaces: EN, DE, FR, ES, IT, PT, NL, PL, CS, SV, DA, RO. The legal text is published in the user's preferred language. The commercial terms are in the user's preferred currency. The delivery is in the user's preferred timezone. The platform is international by design, not by retrofit.

The engagement model is not a one-time decision. An organisation that starts self-serve for the first traveller can move to managed for the first team, and then to embedded-in-managed-IT for the whole fleet, without changing the underlying platform. The model is the engagement depth, not the platform itself. The platform is the same; the procurement, the support, and the integration are what change. The platform supports the journey; it does not require the organisation to declare the destination at the start.

For individuals and small teams, the self-serve model is the entry point. The catalogue is browsable, the plans are comparable, the activation is fast, and the documentation is public. For organisations with internal IT, the consultation model is the right escalation: a specific challenge, a specific architecture, a specific implementation, with a defined outcome. For organisations that want the capability without the operational overhead, the managed model is the right answer: one team, one contract, one accountability, with the option to expand or contract as the organisation evolves.

Economics

The case for eSIM over roaming and over multi-SIM

The economic case for eSIM has three parts. The first is the elimination of roaming premiums. A traditional roaming contract charges a markup on the underlying data rate, often 10x to 30x the domestic rate, with a daily fee in some markets. A pay-as-you-go eSIM charges the underlying rate, with no daily fee, and the user is in control of the cost. For a frequent traveller, the annual saving is typically EUR 1,200 to EUR 3,600.

The second is the elimination of multi-SIM procurement. A traditional multi-country operation maintains a relationship with each country's mobile operator, each on a different contract, each with a different invoice, each with a different renewal cycle. The procurement overhead alone — the time to issue POs, the time to reconcile invoices, the time to manage the cross-border tax — is a significant line item. A single eSIM provider collapses all of that to one relationship, one invoice, one renewal.

The third is the elimination of the multi-SIM-drawer problem. A physical SIM is tied to a country. A traveller in five countries carries five SIMs, or risks the roaming bill. A distributed team across continents maintains a logistics chain for SIMs. An eSIM replaces all of that with a single QR code per country, downloaded as needed, installed in seconds, and managed from the same platform.

For organisations, the pricing model is pay-as-you-go. There is no minimum commitment, no contract, no credit check. The catalogue is published. The invoice is one line per device per period. The finance team can plan the cost line by line, in advance, and reconcile it to the published price list at the end of the period. The cost is predictable; the cost is auditable; the cost is published.

The economic case is not about price per gigabyte. It is about the total cost of mobile connectivity, including the procurement overhead, the invoice reconciliation, the SIM logistics, and the roaming risk. The pay-as-you-go eSIM model is lower on every one of those line items, and it is operated by the same team that operates the rest of the connected ecosystem.

The pay-as-you-go model is not just a billing convenience. It is an alignment of incentives between the provider and the user. The provider has an incentive to keep the platform reliable, the coverage accurate, and the support responsive, because the user pays only when the platform works. The user has an incentive to monitor consumption, set thresholds, and avoid waste, because the cost is the actual cost. The alignment is structural, not contractual, and it is the alignment that makes the platform scale to organisations of every size.

The total cost of mobile connectivity, for a representative mid-sized organisation with 200 devices and 50 frequent travellers, is typically 30% to 50% lower under a pay-as-you-go eSIM model than under a per-country-contract-plus-roaming model. The saving is composed of: the elimination of roaming premiums (the largest single line item), the elimination of per-country contract minimums, the elimination of the multi-SIM logistics, and the consolidation of procurement and invoice reconciliation. The saving is recurring, not one-off, and it compounds over the life of the engagement.

Risk

Coverage, security, and the architectural questions

The risk of eSIM adoption is coverage gaps. The mitigation is the published network list: 160+ countries, 240+ network operators, with the technology (LTE-Advanced or 5G) and the supported bands named. A buyer can audit the list before procurement. Where a destination country is not in the list, the buyer is told before they buy, not when they land.

The risk of eSIM security is profile tampering. The mitigation is the GSMA eUICC security framework: profiles are signed by the operator, authenticated by the device, and isolated from the user's data plane. A compromised profile cannot read the user's contacts, messages, or other apps. The security model is documented in the GSMA specification, which is a public standard. The buyer can read it.

The risk of eSIM lock-in is the same as the risk of any single-vendor relationship. The mitigation is the GSMA standard itself: the eSIM is not tied to a specific provider. A user can download a profile from any GSMA-compliant provider, install it, and the eSIM is theirs. The data consumption and remaining balance are visible to the user. There is no contract that prevents the user from leaving.

The risk of cost overrun is uncontrolled data consumption. The mitigation is the data balance and the threshold alerts. The user sees the remaining balance in real time. The platform can send an alert when the balance crosses a threshold. The user can set a hard cap. The pay-as-you-go model means the maximum exposure is the published plan price, not an open-ended roaming bill.

The architectural questions a buyer should ask are these. Can I see the full coverage list before I buy? Can I switch providers without changing the device? Can I export my consumption history? Can I leave without losing the device? The answer to all four is yes.

There is a fifth risk worth naming: the risk of coverage claims that are not borne out at the destination. The mitigation is the published network list and the real-world validation. The platform publishes the list and the technology; the user validates the list against the user's own travel patterns. Where the published list does not match the user's reality, the platform supports a refund and a different plan selection. The validation is bidirectional: the platform claims coverage, the user validates it, the platform refunds if the claim fails.

There is a sixth risk worth naming: the risk of profile-management complexity at scale. An organisation with hundreds of devices, each with multiple installed profiles, needs a way to manage the profiles centrally. The platform supports this through the device management system, with central provisioning, central renewal, central alerting, and central decommissioning. The user does not manage profiles individually; the platform manages them at the fleet level. The complexity is hidden from the user and surfaced to the administrator, which is the right separation of concerns for any enterprise platform.

Implementation

A week-by-week sequence

Week 1: Assessment. We map the current mobile connectivity footprint — which countries, which operators, which contracts, which devices, which monthly spend. The output is a document the client owns.

Week 2: Plan. We design the eSIM rollout — which devices, which countries, which plan family (single-country, regional, global, day pass), and which engagement model (self-serve, managed, embedded). The plan is documented and inspectable.

Week 3: Provisioning. We deliver the QR codes by email, by API, or by integration with the device management system. The activation takes about a minute per device. The first devices are live in the first week.

Week 4: Migration. The remaining devices are migrated in batches, with the old SIMs and contracts maintained during the transition. The migration is reversible at every stage. The client retains the option to operate the new system, the old system, or both in parallel.

Week 5 and beyond: Operation. The platform is live. The data consumption is visible. The renewals are automated or scheduled. The alerts are configured. The support model is one team, not five.

The sequence is not rigid. A client can start with a single traveller or a single country, validate the architecture, and expand. The eSIM is designed for incremental adoption, not for a forced all-at-once migration. The migration is reversible at every stage.

The implementation sequence is designed to validate the architecture early. The first week establishes the baseline: which countries, which operators, which contracts, which devices, which monthly spend. The second week designs the target state: which devices move to eSIM, which stay with existing operators during transition, which plan families are appropriate for each device category. The third week delivers the first batch. The first batch is small enough to validate but large enough to be representative. If the architecture works for the first batch, it works for the rest.

The implementation sequence is also designed to leave the existing arrangements intact during the transition. The old SIMs and contracts are maintained. The new eSIMs are layered on top. The user can switch between them as needed. When the eSIM is validated, the old SIM is decommissioned. The decommissioning is staged, not a single cutover, and the user is in control of the timing. The transition is a managed migration, not a forced migration, and the user's experience is the success metric, not the deployment velocity.

FAQ

Five plain-language questions

Will an eSIM work in my device? Modern iPhone, Google Pixel, Samsung Galaxy, and iPad Pro/Air devices support eSIM. The full list is published at the point of sale. If your device is not supported, we tell you before you buy.

Do I keep my phone number? Yes. The eSIM adds a separate data channel. Your existing number, on your existing physical SIM or eSIM, is unchanged. Voice and SMS continue to use your existing service.

What happens if I run out of data? You see the remaining balance in real time. The platform can alert you at a threshold. You can top up with another plan, or wait until you have connectivity. There is no open-ended roaming bill.

Can I switch to a different provider? Yes. The eSIM is GSMA-standard. You can download a profile from any GSMA-compliant provider, install it, and the eSIM is yours. There is no lock-in.

How does pricing work across 160+ countries? Each plan has a published price. The plan catalogue is organised by family: single-country, regional, global, day pass. The price is what you pay. There is no roaming surcharge, no daily fee, no hidden cost.

For organisations that have not yet adopted eSIM, the most common question is about device compatibility. The published list answers it: modern iPhone, Google Pixel, Samsung Galaxy, and iPad Pro/Air devices support eSIM, and the list is kept current. For organisations that have partially adopted eSIM, the most common question is about cross-provider profile management. The platform supports multiple installed profiles on a single device, with central provisioning and central alerting. The user can have a work profile, a personal profile, and a travel profile, and the platform can manage all three.

For organisations that have fully adopted eSIM, the most common question is about long-term cost predictability. The pay-as-you-go model is published and audited. The catalogue is published. The historical consumption is exportable. The finance team can plan the cost line by line, in advance, and reconcile it to the published price list at the end of the period. The cost is predictable; the cost is auditable; the cost is published. The long-term cost is the sum of the actual consumption, and the actual consumption is visible to the user and the organisation at any time.

Worked example

A concrete case with numbers

Consider a consulting firm with twelve consultants travelling internationally each month, averaging four countries per consultant per year, with a mix of one-day, one-week, and one-month trips. The current setup is a per-country mobile contract for the heavy-use countries, pay-as-you-go roaming for the rest, and a drawer of physical SIMs for emergencies. The annual cost is approximately EUR 18,000 across roaming bills, contract minimums, and SIM logistics.

Under an eSIM engagement, the firm provisions each consultant with a global plan for the high-use months and a regional plan for the medium-use months, with day passes for the one-day trips. The annual cost drops to approximately EUR 9,500. The procurement overhead drops to one invoice per period. The SIM logistics problem is gone. The roaming bill is gone.

The trust argument is not the price reduction alone. It is the architecture: the eSIM is one layer in a connected ecosystem that includes hosting, voice, AI, and cybersecurity. A device issue is one ticket. A coverage question is one escalation. The mobile connectivity is part of the same platform as the rest of the IT. The vendor-stack problem is gone for mobile too.

The numbers are illustrative, not a quote. Every organisation's travel pattern is different. The principle holds: pay-as-you-go eSIM, multi-carrier switching, GSMA-standard, operated by the same team as the rest of the IT, costs less in total than per-country contracts and roaming premiums — and it works better.

Consider a second worked example: a 200-person technology company with a distributed team across twelve countries, where every employee travels at least quarterly and 30% of the workforce travels monthly. The current setup is a per-country mobile contract in each of the twelve countries, with a per-country procurement relationship, a per-country invoice, and a per-country support contact. The annual mobile bill is approximately EUR 420,000 across all twelve countries, with the procurement overhead adding another EUR 60,000 in staff time.

Under an eSIM engagement, the company consolidates to a single platform with published pricing, with each employee provisioned with a global plan and a regional backup, with central management, central alerting, and central renewal. The annual mobile bill drops to approximately EUR 230,000, and the procurement overhead drops to a single relationship. The saving is approximately EUR 250,000 per year, recurring, and the architectural property is the same as in the smaller worked example: one platform, one catalogue, one support team, and the option to leave at any time.