What CMP is
Devotel’s CMP is a cloud platform for the full eSIM lifecycle: create a plan, sell it, activate, top up, suspend or revoke, stay compliant, read the numbers. The pitch on their product page is specific: skip carrier negotiations, skip building telecom infrastructure, sell global data under your own brand. They quote a white-label storefront in 14 days, or API integration in under 30. The network behind it is 200+ carriers in 190+ countries, with multi-carrier pools and automatic fallback.
Who buys it is not one vertical. Devotel lists five: airlines, MVNOs and telcos, enterprise, tourism and travel, and digital platforms. An airline might attach a data pack to a confirmation email. An MVNO wants packages and a shop that look like them. A travel brand or a digital product wants the same rails without a telecom org chart. The design has to work for a business user (pricing, support, distributors), with API access if a technical team wants it deeper.
What I designed
The CMP surface, end to end, against that product. These loops are the same product recordings Devotel uses on the CMP page:
- Package builder — price, validity, carrier rules; different prices by region, season, or segment.
- White-label storefront — brand, language, mobile. Customers see the client, not Devotel.
- Lifecycle — provision, suspend, revoke, top-up, on those multi-carrier pools.
- One master account for internal staff (admin, support, read-only) and external resellers, each with their own portal and dashboard.
- Analytics — sales, activation rate, popular destinations, package conversion. Export, not a vanity chart.
- Billing that matches the product: usage, invoices, payout tracking, so finance is not reconciling by hand.
Carriers and the network were engineering. eSIMora is the consumer product on the same connectivity. I designed both. CMP is for the brand running the business. eSIMora is for the person buying a trip pack. They share status language. They do not share layout.
What I would not do
- Start the nav from routes and SIM profiles. The people who log in first are pricing and support. Carrier pools sit behind a package.
- Treat white-label as a logo toggle. Language and mobile storefront change per tenant. Install and activation do not, or support forks for every brand.
- One “team” list for staff and resellers. A distributor who can change price should not see another distributor’s payout.