2024 – now · BIGOH TECHThe system behind 14 products.Design SystemsProduct DesignComponent Architecture14 products, 130 releases3 designers, 20+ developers use it25 components, 160+ tokensView case studyAIRTEL DIGITEL • 2026 · 3 min read
Every number existed. Finding one took hours.
Treasury, in one place

As the only designer on Airtel Digitel's treasury app, from March to September 2026, I faced one problem: the numbers sat in Excel, Murex, Bloomberg and Crystal, and each director's question took hours. I designed an app that consolidates every source, down to the trade. Reporting went from 1–2 hours to under 10 minutes, and the yearly L1 report is one click.
Figma link
Digitel App · view only
OVERVIEW
<10 min
Reporting, from 1–2 hours
1
Designer, working solo
1 click
Annual L1 report
For directors and stakeholders, every year.
1 app
For every source
Excel, Murex, Bloomberg, Crystal and the rest.
THE SITUATION
The answer was always somewhere. Never in one place.
- The Group Treasurer runs Debt, Liquidity and FX, and answers the directors.
- A director's question went to a team lead, who consolidated reports by hand. It took hours.
- Every figure existed, across Excel, Murex, Bloomberg and Crystal.
The core challenge:
Answer a director while they wait — and keep every figure traceable to its source.

THE USERS
A treasury, top to bottom.
- Group Treasurer (GT)
Runs Debt, Liquidity and FX, and answers the directors. - Treasury Controller (TC)
Works under the GT, senior to the team leads, and owns compliance. - Debt, Liquidity and FX teams
Hold the numbers, and until now, consolidated them by hand.
PAIN POINTS
Everything scattered, everything by hand.
- Scattered sources
Excel, Murex, Bloomberg, Crystal and more — no single place to look. - Hours per question
Every director's question went to a team lead, who built the answer by hand. - Compliance by hand
The Treasury Controller must be sure every compliance holds. Checking each one was very hard. - Spikes without reasons
When a number spiked, tracing why took a long time. Early detection was close to impossible.
WHY IT HAPPENED
The data existed. The access didn't.
- Nothing was missing; it was spread across files, systems and teams.
- Every question cost hours, and every compliance check carried risk.

DESIGN GOALS
Design goals
- One place for every number
- Answer while they wait
- Catch compliance early
- Trust every figure
SOLUTION
Core solution modules
- Consolidated view
Slice and dice across teams and sources in a few taps. - Detail and trade views
From a total to the full detail, down to individual trades. - Send to self
Any view becomes a report in your inbox. - One-click L1 report
The report shared with directors and stakeholders every year, in one click. - Compliance tracking
Compliance in one place for the Treasury Controller, with spikes surfaced early. - Bank contact directory
The dedicated person at every bank, one tap from a call.

PROCESS
From discovery to handoff
01 · PRODUCT
Consolidated, detail and trade views · Illustration

Consolidated, detail and trade views · Illustration 02 · DIRECTORY
Bank contact directory

Bank contact directory 03 · PROTOTYPE
Send to self, and the L1 report

Send to self, and the L1 report
DECISIONS & TRADE-OFFS
Key decisions and trade-offs
- Backed by the source
Every figure is backed by its own Excel or Murex file, so any number in the app can be checked against the source it came from. - Reports as a button
The annual L1 report and ad-hoc reports became actions — one click, or send to self — instead of a team lead's afternoon. - Bottom sheets, not cards up top
Stakeholders asked for cards at the top of the screen and a popover for filters. I showed them mobile-first alternatives built around the thumb zone, and filters and deep dives moved into bottom sheets.Trade-off: Rejected: cards up top and a popover. The top of a phone is the hardest place to reach; a bottom sheet opens at the thumb (Fitts's Law).
OUTCOMES
From hours to minutes
1–2 hrs → <10 min
REPORTING TIME
THE TEAM
The team
The only designer on it. Engineering built it.

Adesh Singh
Product Designer
REFLECTION
What it taught me
In a treasury, speed only matters if the number is trusted. Every view had to trace back to the file behind it before a faster answer was worth anything.
SELECTED WORK
Morecasestudies
2024 – now · BIGOH TECHThe system behind 14 products.Design SystemsProduct DesignComponent Architecture14 products, 130 releases3 designers, 20+ developers use it25 components, 160+ tokensView case study
