Valeria Shulakova · Senior product designer
Under NDA · no product visuals by designUspio · B2B · 2025 — Present

From a costly third-party tool to an in-house messaging platform

I lead product design of a CPaaS platform built from scratch to replace a third-party solution and now in production. The work is under NDA, so this page covers the scope and my method, not the product itself.

1,000+
screens and states
In production · built from scratch
Role
Senior product designer, leading design end to end
Worked with
Product owner, analysts, engineers and the operations team
Timeline
June 2025 — present
Domain
CPaaS · SMS · internal B2B platform
Status
In production
Context

How a business SMS reaches your phone

Businesses send SMS — one-time passwords (OTP), notifications, marketing — through messaging platforms. A platform accepts traffic from many clients and delivers it through vendors and mobile operators. Around that sits a lot of operational work: client management, routing, pricing and balances, vendor connections.

The company ran it on a costly third-party solution and decided to replace it with its own platform.

Business clientsSend OTP codes, notifications and marketing
→
Messaging platformAccepts traffic from many clients and passes it on
→
Vendors and mobile operatorsDeliver messages to the network
→
RecipientsReceive the SMS on their phones
A generic CPaaS model based on public industry knowledge. It does not show Uspio's architecture or logic.
Scale

One platform, six domains

1,000+
screens and states
In production
built from scratch
01ClientsA multi-level structure with inherited settings
02RoutingCountry-based rules and fallback vendors
03Vendor monitoringStatuses, authentication failures, event logs
04BillingPlans, tariffs, payments, credit limits, balances
05Tables and importConfigurable tables with export; bulk changes reviewed before they go live
06Reports and analyticsLarge, complex reports built from platform data, kept readable
Four hard problems

Where the complexity lived

01

A multi-level client structure

Difficulty

Clients are managed in the system as a structure of several levels, and settings can be configured at every level or inherited from the one above.

Approach

I worked out the structure and the rules of inheritance with analysts before designing screens, and described every state in a behaviour specification.

Result

A flexible multi-level client structure with configurable and inherited settings at every level.

02

Routing that operations can configure

Difficulty

SMS routing is technical logic, yet the operations team is the one who configures it and diagnoses delivery.

Approach

I translated the routing logic into configuration flows and checked complex cases with analysts in AI-generated interactive prototypes before development.

Result

Configuration flows with country-based rules and fallback vendors, and real-time monitoring of vendor connections — statuses, authentication failures and event logs — that centralises delivery diagnostics for the operations team.

03

Billing for prepaid and postpaid clients

Difficulty

Billing combines cost and pricing plans, time-bound tariffs, payments, credit limits and balances. Every figure is money, so the interface has to be exact and easy to trust.

Approach

I applied the clarity and trust patterns that consumer checkouts rely on.

Result

The billing domain designed end to end, from plans to live balances.

04

An event data report people can use

Difficulty

The event data report is large and complex: many parameters, long periods and different needs for viewing and for download.

Approach

I designed viewing and downloading as one flow, with parameters grouped by purpose, periods managed in one place and templates that save a setup for reuse.

Result

An interface for viewing and downloading the event data report, with flexible parameters, period management and reusable templates.

Design system

A design system for data-heavy work

An internal platform is a working tool: people spend hours in it, not minutes. I shaped the design system around density, so screens hold more data and still read calmly.

Rule

One pattern, many places

A table, a form or a status behaves the same in every area, so learning one part of the platform teaches the rest.

Rule

Every state, not just the happy path

Each component is designed for empty, loading, error and restricted states from the start.

  • 01

    Configurable tables

    Columns, filters and search set up for the task at hand, with export.

  • 02

    Bulk import

    Large changes arrive in one file, and nothing goes live until it is reviewed.

  • 03

    Complex forms

    Long settings stay readable, with validation that explains what to fix.

  • 04

    Status and permission patterns

    The same signals for state and access everywhere, so nobody has to guess what they can change.

How I work

My process, not the product

Every feature goes through the same steps.

  1. 1

    Discovery

    with the operations team: how they work today and where it hurts

  2. 2

    Scoping

    with the product owner: what goes into the release and what waits

  3. 3

    Business logic

    with analysts: rules and edge cases agreed before any screens

  4. 4

    UX & UI design

    flows, screens and every state: validation, permissions, edge cases

  5. 5

    AI prototype

    complex logic validated before development

  6. 6

    Design support

    through development and release

Next case
Turning vocabulary practice into a plan for today
Palabring · Client project · Mini case
→