Launch an MVNO with Spenza in 7 Days: What It Takes

Last verified 30 October 2026.

Can you launch an MVNO with Spenza in seven days? Spenza says yes for a defined scope: its TelecomHub page states “Go live in under 7 days” and adds “We handle integrations and billing setup. Your team needs basic REST API knowledge.” That is a published target, not a promise that every business finishes in a week. Network access, commercial approval, device support and testing decide your real date.

This guide explains what the seven-day claim covers, what Spenza handles and what you bring, a day-by-day plan with an exit artifact for each day, how a Shopify storefront fits in, and how to prove a customer can go from checkout to a working line before you open sales. If you are still choosing a model, start with what an MVNO is, then return with a defined offer.

What Spenza says about launching in 7 days

Spenza makes the seven-day statement on several of its product pages. Read it as written. The wording is narrow, and it is worth knowing exactly what each page does and does not say.

So the honest summary is this: seven days is Spenza’s stated launch target for a scoped deployment, backed by one customer case. It is not a guarantee, and no page defines the starting line. When someone quotes you a launch date, ask three questions. What is in scope? When does day one begin? What evidence marks day seven as done?

Longer launches are normal. If you need a market-specific view, the US launch guide covers the compliance and carrier steps that sit outside any platform timeline, and the guide to how MVNEs speed up a launch explains which parts of the work a platform can shorten.

What Spenza handles and what you provide

An MVNO sells mobile service under its own brand without owning the radio network. An MVNE-style platform supplies the technology and operations behind that brand. Spenza describes three hubs on one data model, one API and one invoice: UXHub for the branded customer experience, ControlHub for plans, pricing and reseller billing, and TelecomHub for carrier connectivity and SIM and eSIM management. The split below follows those pages.

The right-hand column is the one that decides your date. A platform can be ready on day one and the launch still slip because the offer was never settled.

What must be ready before day one

A short implementation window needs usable inputs on the first morning. Write down the first release in plain terms: who can buy, where service is available, which devices are supported, what each plan includes and how customers get help. A constrained release is easier to test than an open promise of service everywhere.

• Offer. Plans, allowances, validity, retail prices and renewal terms, approved by whoever signs them off.
• Network and markets. Which countries and which networks, whether you use Spenza’s supplier offers or your own agreement, and what voice, text and data you need.
• Devices and SIM type. Physical SIM, eSIM or both, and the exact phone models you will support.
• Brand. Logo, colors, approved copy and the domain or store the customer will see.
• Store access. If you sell on Shopify, admin access and a test store or environment.
• Owners. One named person each for product, finance, support, engineering and the go or no-go decision.

Obligations that apply to your service, such as licensing, customer identification, number porting or emergency calling, depend on the market and the offer. Platform setup does not settle them. Get specialist advice for the markets you target, and keep the result in the launch record. The MVNO launch cost guide and the MVNO calculator help you put numbers on these inputs, with the calculator’s own caveat that its pricing is indicative.

A seven-day launch plan, day by day

The plan below is a working sequence, not a record of any customer’s week. Each day ends with an artifact the next day uses, and day seven ends with a decision rather than an assumption. Parallel work does not remove dependencies, so extend it whenever an essential test or approval is still open.

A go or no-go review can correctly end in a later date. That is a better outcome than opening sales on an untested path. Integrations that already exist reduce configuration, but they do not prove every dependency is done. A new operator integration, an unusual account hierarchy, unusual billing rules, physical SIM logistics or a new market each add work, so ask the delivery team what is included, scheduled separately or excluded.

Selling plans on a Shopify storefront

Spenza’s UXHub page says merchants can “offer mobile plans, eSIMs, and devices through Shopify” while Spenza handles activation, subscriptions and billing, and that Spenza “automatically creates subscriptions, provisions eSIMs, and tracks device assignments after checkout.” That makes Shopify a practical storefront for brands that already sell products online and want to add connectivity, for example a device maker bundling a plan.

Shopify handles the storefront, checkout and payment. Spenza handles the mobile service behind it. A Shopify product does not create network access by itself, so every plan you list must map to a real supplier offer. Spenza’s guide to reselling data plans on Shopify covers the order, fulfillment and exception handling in depth. The sequence below is the shape of an integration, based on Spenza’s earlier published walkthrough.

1. Connect the Spenza business account to the Shopify store, and record which store and account are linked so test and live environments cannot be confused.
2. Install the Spenza app from the Shopify admin and sign in to the business account.
3. Choose plans from the Spenza marketplace and add them to the Shopify catalog.
4. Organize the imported products into collections and make them available to the online store channel.
5. Review each product page for description, eligibility, price and renewal terms, on mobile and desktop.
6. Place a test order, then follow it into the Phone Lines and Subscriptions views in Spenza.

Go-live acceptance: from checkout to a working line

A confirmation screen proves that a customer paid. It does not prove that they can make a call or use data. Before you open sales, show that each purchase reaches the correct subscription record and that the service works on a supported device. Record evidence at three boundaries.

Use Shopify’s test order procedure to check the storefront and payment setup, which Shopify says does not charge you. Agree separately how test orders reach the Spenza environment and whether any network activity or charge can occur, because store testing and carrier testing may have different controls.

Test duplicate and interrupted events too. Shopify notes that an app can receive the same webhook more than once and recommends making processing idempotent or storing each webhook ID so a repeat delivery is skipped. Ask the implementation team how the integration spots repeated work, and make sure a timeout never produces a second subscription for one order.

For eSIM offers, separate three events: the profile is delivered, the profile is installed, and the network service works. Apple’s eSIM setup guidance says the method depends on the carrier’s eSIM support, so test the phone models you will actually accept. A successful install on one team member’s phone does not cover your whole device list.

Include a cancellation, a failed payment, a plan change and a support escalation. Finance should be able to explain every resulting charge, and support should see enough history to name the next responsible team. The MVNO billing platform guide sets out the rating, invoicing and payment boundaries to test. Finally, name the person who can pause new activations, the team that investigates failures and the owner of customer messages, before the first customer buys.

MVNO in a box, and how it differs from a custom build

“MVNO in a box” describes a packaged platform: subscriber and SIM management, billing, a customer portal and APIs delivered together, so a brand configures a service instead of building one. It suits digital-first businesses such as device makers, software platforms and retailers that want to add branded connectivity without a telecom team. The white label MVNO guide compares what the brand controls under this model.

The phrase has no standard scope. One provider may include a customer app and billing and leave network access to you, while another bundles the lot. Published comparisons of launch time and cost between a box and a traditional build vary widely, and none is reliable enough to plan from. Ask each provider for a written list of what is included, what you operate, and what the quote assumes. Then compare launch time against your own scope, not against a general figure.

What can stretch the timeline

• A new operator integration. A network not already connected adds technical setup and validation.
• Custom account structures. Parent-child billing, multiple reseller tiers or unusual invoice rules need extra configuration and testing.
• Physical SIM logistics. Manufacturing, shipping and inventory sit outside a software schedule.
• A new market. Local rules, device support and coverage have to be checked for each country.
• Late scope changes. A new device class or channel after day four resets testing.
• Approvals. Legal, finance and network sign-off often take longer than configuration.

Many of these appear on lists of common MVNO launch mistakes, and most are avoidable by fixing the first release early.

What Spenza’s published cases show

Spenza’s Butlr case study reports a reduction in regional launch time from 60 days to 7 days, which is where the seven-day figure on the product pages gets its customer evidence. It concerns launching connectivity in new regions for one customer, and it does not say how the 60-day baseline was measured. It supports the idea that a fast launch is possible, not that yours will take seven days.

The RocketPhone case study shows what an implementation can include beyond a storefront. Spenza describes supplying carrier integration, eSIM provisioning, rating, billing, subscriber management and multi-tier reseller control, plus SIP routing for enterprise voice workflows. The case gives no go-live dates and no quantified results, so it informs scope questions rather than a schedule. Both cases are written by Spenza.

Use them to ask sharper questions. Which communication path must work for your product? Which account tiers need administration? What do finance and support need to see? Turn each answer into a test.

Conclusion

You can plan an MVNO launch with Spenza around a seven-day sequence, and Spenza’s own pages state a go-live target of under seven days. Treat that as a target for a defined scope, not a guarantee. The work that sets your date sits mostly on the brand side: a settled offer, network and device scope, approvals and tested order-to-service paths. Fix those first, run the seven-day plan against them, and let the day-seven review decide whether to launch or to revise the date. Bring the written scope, the dependency list and your acceptance tests to a conversation with Spenza so the timeline is confirmed for your launch rather than assumed.

FAQs about launching an MVNO with Spenza