Making telecom billing feel like it was built for humans.

Deep research, deliberate design, and a platform that shipped.

QuotingBill — customers page showing products selected for cancellation

The Challenge

Telecom billing is a mess. Carriers were stuck with slow, overly complex invoicing tools that couldn't keep up with metered usage, cancellations, and provisioning at scale. QuotingBill entered the market with an ambitious goal: make recurring billing feel genuinely simple for the people actually running it — not just the engineers who built it.

The Approach

Deep market research first — mapping what existing tools got wrong and where the actual pain was. From that foundation, the design process moved methodically: breadboarding the key flows, fat-marker sketching the interactions, and building an HTML/CSS/JS prototype before any pixel-perfect work happened. Each section was designed with the full system in mind, not in isolation.

01 — Process

Wired end-to-end before anything was designed.

Cancellations are where billing platforms earn or lose trust. One wrong step and the user loses confidence in the whole system. The flow was wired end-to-end from the very first concept — mapping what triggers a cancellation, how the activity log surfaces relevant context, and how multiple products can be cancelled cleanly in a single session. Breadboarding first, high-fidelity after.

QuotingBill user flow wireframe mapping the full cancellation process — QuotingBill — User flow diagram

Breadboard — steps for cancelling a subscription — Step 1 — Cancellation trigger

Breadboard — requests and activity log — Step 2 — Activity log surfaces context

Breadboard — handling multiple products and confirmations — Step 3 — Multi-product confirmation

02 — Interaction

Fat markers before pixels.

Fat-marker sketches kept the thinking high-level before anyone touched a screen. The bucket concept — where products could be collected and managed in batch — emerged from this phase. Once the interaction felt right on paper, the first prototype was built in HTML/CSS/JS to test timing, feel, and flow before committing to final designs. That prototype became the template for how every subsequent section was approached.

Fat marker sketch — the bucket concept — The bucket

Fat marker sketch — selection to bucket flow — Selection flow

First HTML/CSS/JS prototype of the bucket interface — First prototype

03 — Product

Every section designed as part of the whole.

The full platform covers invoicing, project management, user provisioning, and third-party service connections. Every section was designed with a consistent information hierarchy — so moving from one area to another never required relearning the interface. The end result: a platform that makes metered billing feel manageable, not overwhelming.

QuotingBill invoice page showing billing details and line items — Invoice page

QuotingBill projects page showing active telecom billing projects — Projects page

QuotingBill user provisioning interface for third-party services — User provisioning

QuotingBill provisioning front page — full product interface — QuotingBill — Provisioning front page

Billing software that doesn't fight you.

Billing software has a reputation for being dense and opaque — built for accountants, not operators. QuotingBill set out to do something different: make it feel like something you actually want to use. Two years of work across research, interaction design, and front-end development. The kind of project where the process mattered as much as the output — and where doing it right the first time saved significant time downstream.

The work.

Design

Market research
User flow mapping
Breadboarding
Fat-marker sketching
Interaction design
Interface design

Product

Invoicing
Project management
Cancellation flows
User provisioning
Third-party integrations

Development

HTML / CSS
Vue.js
Prototype development
Front-end implementation

Date: 2019–2021
Company: QuotingBill.com
Role: Principal designer + Front-end

Building something interesting?

Let's talk.

Start a project → ← Back to work