JAF Logo
Holafly Business Center
← Back
2024·B2BSaaSEnterprise

Holafly Business Center

Corporate eSIM management platform built from zero, from stakeholder workshops to 3,000+ enterprise clients.

View in Figma

End-to-end UX and UI design

Mobile + Web

5 constraints

Design and build Holafly Business Center, a corporate connectivity management platform, from scratch, with Iberia, Volvo, and BBVA as the first enterprise clients

There was no existing product to iterate from. The buyer (IT manager) is not the user (the traveling employee). This was a zero-to-one design challenge with a fundamentally different product logic from B2C.

01

The admin is not the employee, every design decision had to be made from the IT manager's perspective. The employee's eSIM installation experience is handled by the Holafly consumer app, not by HBC.

02

Bulk assignment was the primary workflow, individual assignment is the exception at enterprise scale. The UI had to lead with bulk (Excel upload) and make individual assignment a secondary option.

03

Centralized billing was table stakes, IT managers couldn't expense 50 individual receipts. Single invoice view across all purchases was a hard requirement.

Wireframes

Designed the Dashboard as the primary surface: full eSIM inventory overview with state-based filtering, inline status chips, and contextual action buttons per row. Parallel design of the plan architecture (Always On, Unlimited, Enterprise) with clear tier trade-off visibility.

User Flows

Three primary admin workflows: bulk assignment (Excel upload → auto-notification to employees), individual assignment (manual entry), and subscription management (cancel, reassign, reactivate per employee). Each workflow resolved at the dashboard level, no separate management screens required.

Iterations

Naming workshop was a prerequisite, couldn't design state-based UI until the state names were locked. The three-state model (Active / Pending / Unassigned) was finalized before any UI was built, ensuring consistency across the product, the API documentation, and client-facing communications.

A dashboard-first platform: full eSIM inventory with Active / Pending / Unassigned status chips, contextual action buttons per row, bulk assignment via Excel upload, and centralized invoice view. Plan architecture (Always On, Unlimited, Enterprise) designed to support decision-making without requiring a sales call for most choices.

Full eSIM inventory dashboard with inline status chips and contextual actions

Excel-based bulk assignment, employees receive install instructions via email and WhatsApp automatically

Per-employee subscription management

cancel, reassign, reactivate from dashboard

Centralized billing

single invoice view across all purchases and entities

Outcomes

from zero

Enterprise Clients

initial launch cohort

First Clients

global eSIM management

Destinations Covered

Holafly Business Center launched and onboarded its first enterprise clients, Iberia, Volvo, and BBVA, within the initial release cycle.

What worked

The naming workshop before any UI design was one of the highest-leverage decisions of the project, locking state terminology upfront prevented inconsistency across the product, the API, and client communications.

Excel-based bulk assignment required zero onboarding for IT managers, they already had their employee data in spreadsheets. The upload-to-notify flow handled everything from there.

What I'd improve

In-platform analytics showing which employees are actively using their eSIMs vs. which have pending plans, IT managers want to see utilization, not just assignment status

Role-based permissions within the platform, larger organizations need to delegate assignment to department admins without giving full billing access

Let's talk