February, 2023 — 5 months

Wave — Increasing billing workflow efficiency in telecom

How we built the MVP of a B2B billing platform that made our client's billing workflow 600x faster and saved around 56 hours per analyst each month.

Context

Originally Nomo, a 100% digital mobile carrier, Wave was born to redefine customer experience in Brazil. Our journey evolved, leading us to turn into B2B model, where we partnered with large telecom companies, acting as a tech provider to drive internal impact.


This case study documents how we built a billing tool for the telecom market, starting from identifying opportunities within our client's billing pain points.

The opportunity

We first spotted some problem inside an active client's billing process.


To validate if these were industry-wide, we engaged with other companies through interviews and process reviews.


The pain points proved repetitive across all companies we interviewed, confirming a pattern.

1

Complex, outdated software

2

Poor performance

3

Limited tech support

4

Lack of data consistency
Recognizing the scope of the opportunity, we set out to build a focused billing solution that addresses these core pain points and can scale across telecom companies.

Discovery

We conducted a research with our client guided by crucial questions.

We conducted a research with our client guided by crucial questions.

We conducted a research with our client guided by crucial questions.

How the current billing workflow actually runs?

Who is responsible for each step?

What are the edge cases?

Why existing tools fail?

How the current billing workflow actually runs?

Who is responsible for each step?

What are the edge cases?

Why existing tools fail?

How the current billing workflow actually runs?

Who is responsible for each step?

What are the edge cases?

Why existing tools fail?

Part of our client's mapped billing workflow

Through stakeholder interviews, 7+ shadowing sessions with the billing team, and process mapping, we uncovered key insights about the entire billing workflow and its pain points.

Through stakeholder interviews, 7+ shadowing sessions with the billing team, and process mapping, we uncovered key insights about the entire billing workflow and its pain points.

Through stakeholder interviews, 7+ shadowing sessions with the billing team, and process mapping, we uncovered key insights about the entire billing workflow and its pain points.

1

The process was unnecessarily complex, with too many manual steps that increased the risk of human error.

2

The current billing software was slow and often took days to process all the required information.

3

Invoice disputes were frequent due to inconsistencies caused by the current billing system.

Design foundations

Error prevention

Mitigate known issues, and always provide a way for users to resolve problems themselves without support.

Mitigate known issues and provide ways for users to resolve problems without needing support

Simplicity

Break work into small, clear tasks to reduce cognitive load

Workflow‑oriented

Information architecture around how the billing teams actually works. Workflow drives navigation and decisions.

Align navigation and decisions to how the billing teams actually work

Align navigation and decisions to how the billing teams actually work

Workflow‑oriented

Align navigation and decisions to how the billing teams actually work

Open source components

We used the IBM Carbon Design System to build the solution, enabling us to generate value quickly and stay consistent without creating all components from scratch

Open source components

We used the IBM Carbon Design System to build the solution, enabling us to generate value quickly and stay consistent without creating all components from scratch

Open-source components

We used the IBM Carbon Design System to build the solution, enabling us to generate value quickly and stay consistent without creating all components from scratch

Solution

A single interface containing all information necessary for the billing team's workflow, eliminating the need to navigate multiple pages or external tools.

My role

I led the design of the invoicing workflow: iterating through information architecture options, creating wireframes, and validating them via user testing. The interface consolidates all critical information in a single environment, removing the need to switch between multiple pages or external tools.

+200k

Contracts and clients on the platform ~3 months after release

600x

600x

Faster billing workflow speed compared to the old workflow

Faster billing workflow speed compared to the old workflow

56h

Of work saved per analyst each month

56h

Of work saved per analyst each month

56h

Of work saved per analyst each month

+200k

Contracts and clients on the platform ~3 months after release

My role

I led the design of the invoicing workflow: iterating through information architecture options, creating wireframes, and validating them via user testing. The interface consolidates all critical information in a single environment, removing the need to switch between multiple pages or external tools.

Users can now view relevant invoice information like status, total value, and process errors. They're also able to navigate through tabs based on their workflow stage

With async invoice processing, users can manage other tasks while waiting, improving efficiency