Other Work

Builder Cloud: Helping users stay on top of their cloud spend

Builder Cloud: Helping users stay on top of their cloud spend

Builder Cloud: Helping users stay on top of their cloud spend

A cleaner, smarter Builder Cloud dashboard that empowers users to track spend and with confidence.

A cleaner, smarter Builder Cloud dashboard that empowers users to track spend and with confidence.

Status

Shipped

Timeline

January 2025 - May 2025

Tools

Mixpanel • User Testing • Figma

Team

Solo • Product Manager

My Role

User Testing • Brainstorming • Competitor Analysis • Designing

Project Overview

Project Overview

Timeline

January 2025 - May 2025

Timeline

July 2024 - December 2024

Tools

Mixpanel • User Testing • Figma

Team

Solo • Product Manager

My Role

User Testing • Brainstorming • Competitor Analysis • Designing • Prototyping

About Builder Cloud

About Builder Cloud

Builder Cloud allows users to manage and pay for the cloud infrastructure powering their Builder.ai applications. It gives users visibility over their cloud spend, invoices, payments, and account settings, all through a prepaid wallet system that ensures their apps stay live and running.

The Problem

The Problem

The previous Builder Cloud dashboard made it hard for users to understand how much they were spending, what payments were due, or how costs were changing over time. This lack of clarity caused confusion and frustration—contributing to a 35% drop-off shortly after landing on the dashboard and 15% lower interaction rates than other parts of the platform.

Many users were also unaware that Auto-Recharge existed or didn’t realise it could prevent failed payments and service disruptions. Without a clear way to monitor cloud spend or enable key features, users struggled to stay in control, resulting in avoidable support tickets and missed payments.

Builder Now is seeing a significant drop-off rate of 92% when users reach the current platform. Users struggled to visualise their app ideas in a clear and simple way, making it harder for them to showcase their concept to investors, gain confidence in their vision, and fully understand their app idea before committing to a significant investment with Builder.ai.

The Solution

The Solution

We redesigned the dashboard to make spend data and key actions instantly clear at a glance. By simplifying the layout, surfacing Auto-Recharge, and prioritising clarity over complexity, the new design helps users stay on top of payments, avoid service disruptions, and confidently understand their cloud usage.

Builder Now is seeing a significant drop-off rate of 92% when users reach the current platform. Users struggled to visualise their app ideas in a clear and simple way, making it harder for them to showcase their concept to investors, gain confidence in their vision, and fully understand their app idea before committing to a significant investment with Builder.ai.

Results & Impact

Results & Impact

User Experience Improvement

User Experience Improvement

Post-launch metrics demonstrated significant improvements:

+ 85%

Increase in dashboard interaction rate compared to the previous version

+ 75%

of users discovered and enabled Auto-Recharge after the re-design.

- 50%

Drop in support tickets as more users enabled Auto-Recharge to avoid missed payments.

Business Goals Improvement

The platform delivered measurable business benefits:

+ 40%

Increase in user engagement, with more users actively interactign with the dashboard to monitor their cloud spend.

+ 38%

Boost in customer retention, as more users returned to view the breakdown of their spend.

+ 55%

Rise in Auto Recharge adoption, helping reduce failed payments and service interruptions.

Final Designs

Final Designs

Enjoyed the overview? Buckle up, its a long one for the curious minds

Extended case study on Notion.

Intro

Intro

The Builder Cloud dashboard had existed for years but hadn’t been updated since its initial build by engineers, with no product or design input. When the opportunity finally came to improve it, we had a short timeline and limited engineering capacity. We focused on gathering quick but meaningful user insights and prioritising the most critical issues, aiming to ship an MVP dashboard that delivered immediate clarity and value to users.

Current Builder Cloud Dashboard

Current Builder Cloud Dashboard

Discovery

Discovery

To understand why the dashboard was underperforming, we combined user interviews with an analysis of support tickets to uncover recurring pain points and areas of confusion.

What we knew already

What we knew already

Internal analytics showed the dashboard was underperforming compared to the rest of the product. When reviewing Mix panel, we found:

35% of users dropped off shortly after landing on the dashboard, suggesting it wasn’t clear or useful enough to keep them engaged.

The dashboard had only a 20% retention rate, meaning just 1 in 5 users returned to it after their initial visit.

From exisiting support tickets, we also learned:

  • Many users experienced unexpected service suspensions after forgetting to top up their wallet.

  • These incidents were often caused by poor visibility of the Auto-Recharge feature, which was buried in the UI and rarely discovered until it was too late.



But what else was stopping users from using the dashboard?

What we knew already

Internal analytics showed the dashboard was underperforming compared to the rest of the product.

When reviewing Mixpanel, we found:

  • 35% of users dropped off shortly after landing on the dashboard — suggesting it wasn’t clear or useful enough to keep them engaged.

  • It had only a 20% retention rate, meaning few users came back to use it again.

From support tickets, we also learned:

  • Many users experienced unexpected service suspensions after forgetting to top up their wallet.

  • These incidents were often caused by poor visibility of the Auto-Recharge feature, which was buried in the UI and rarely discovered until it was too late.

But what else was stopping users from using the dashboard?
To dig deeper, we conducted customer interviews.


Customer interviews

In-depth interviews were conducted with 5 existing Builder.ai customers who had previously used the "Cloud" platform to track their spend. These interviews focused on understanding their experiences, challenges, and expectations for using the current cloud dashboard. 


Customer interviews

What we knew already

Internal analytics showed the dashboard was underperforming compared to the rest of the product.

When reviewing Mixpanel, we found:

  • 35% of users dropped off shortly after landing on the dashboard — suggesting it wasn’t clear or useful enough to keep them engaged.

  • It had only a 20% retention rate, meaning few users came back to use it again.

From support tickets, we also learned:

  • Many users experienced unexpected service suspensions after forgetting to top up their wallet.

  • These incidents were often caused by poor visibility of the Auto-Recharge feature, which was buried in the UI and rarely discovered until it was too late.

But what else was stopping users from using the dashboard?
To dig deeper, we conducted customer interviews.


Customer interviews

In-depth interviews were conducted with 5 existing Builder.ai customers who had previously used the "Cloud" platform to track their spend. These interviews focused on understanding their experiences, challenges, and expectations for using the current cloud dashboard. 


In-depth interviews were conducted with 5 existing Builder.ai customers who had previously used the "Cloud" platform. These interviews focused on understanding their experiences, challenges, and expectations for using the current cloud dashboard. 

What we knew already

Internal analytics showed the dashboard was underperforming compared to the rest of the product.

When reviewing Mixpanel, we found:

  • 35% of users dropped off shortly after landing on the dashboard — suggesting it wasn’t clear or useful enough to keep them engaged.

  • It had only a 20% retention rate, meaning few users came back to use it again.

From support tickets, we also learned:

  • Many users experienced unexpected service suspensions after forgetting to top up their wallet.

  • These incidents were often caused by poor visibility of the Auto-Recharge feature, which was buried in the UI and rarely discovered until it was too late.

But what else was stopping users from using the dashboard?
To dig deeper, we conducted customer interviews.


Customer interviews

In-depth interviews were conducted with 5 existing Builder.ai customers who had previously used the "Cloud" platform to track their spend. These interviews focused on understanding their experiences, challenges, and expectations for using the current cloud dashboard. 


Lack of spend visibility

Users were unsure how much they were spending or how their costs were changing month over month.

Confusing discount graph

Users didn’t understand the 'discounted vs. non-discounted' view and didn’t find it helpful. They just wanted clear answers: How much have I spent? Is it going up or down? What will I owe this month?

Summary Over Charts

Users wanted a high level summary of their spend at a glance, instead of having to look at charts.

Unclear billing and next steps

Users didn’t understand figures like “unbilled amount” or “last payment.” It wasn’t clear if they needed to pay now or later, or whether the amount shown was overdue or upcoming, causing uncertainty and inaction.

Hidden Auto Recharge

90% of users said they’d prefer automatic top-ups, but most didn’t know the feature existed, leading to missed payments and service interruptions.

Mobile Experience

Mobile Experience

A review of analytics showed that over 40% of users accessed Builder Cloud from mobile devices. However, the existing dashboard was not responsive or optimised for smaller screens, leading to:


-> Difficult navigation and unreadable data.


-> Increased drop-off rates and frustration among mobile-first users.


-> Missed opportunities for users to take quick actions like topping up their wallet or enabling Auto-Recharge on the go.

The Problem

The Problem

Problem 1: Cloud Spend Visibility

The dashboard made it difficult for users to understand how much they were spending, what was due, or how costs were changing. This confusion led to a 35% drop-off rate shortly after landing on the dashboard. Users need a simple, clear way to track their cloud spend and stay on top of upcoming payments.

Problem 2: Auto-Recharge Awareness

When users ran out of credit, their services were suspended without warning. Many didn’t know that Auto-Recharge existed because it was hidden deep in the dashboard, resulting in high volumes of support tickets. Users need a clear, visible way to set up Auto-Recharge to prevent service disruptions and reduce reliance on manual top-ups.

The Goal

The Goal

Our goal was to redesign the dashboard to make spend tracking clearer, improve discoverability of Auto-Recharge, and reduce reliance on customer support—ultimately driving better engagement and retention.

The Goal

Our goal was to redesign the dashboard to make spend tracking clearer, improve discoverability of Auto-Recharge, and reduce reliance on customer support—ultimately driving better engagement and retention.

Ideation

Ideation

How might we make it easier for users to track and understand their cloud spend at a glance?

How might we make essential payment actions, like Auto-Recharge, more visible and accessible?

How might we simplify the dashboard so users can focus on what matters most?

Defining Dashboard Priorities

Defining Dashboard Priorities

To quickly validate layout clarity and information hierarchy, we skipped mid-fidelity wireframes and jumped straight into high-fidelity component design. Drawing from user pain points, competitive analysis of AWS, Google Cloud, and Microsoft Azure, and internal usage data, we identified the core information users needed most, then created modular components (like summary cards and spend trends) to test how easily users could digest key data at a glance.

Summary Cards

Early concept aimed to give users a quick glance, displaying key monthly spend figures, including current spend and change from the previous period.

Visualising spend trends

Presents a bar chart view of monthly spend over time. Each bar represents a different month, helping users track overall cloud expenditure patterns.

Spend by service

Visualises the breakdown of spending by service category. Each segment shows proportional allocation, with a legend listing specific values.

Breakdown spend by service

Highlights the Auto-Recharge feature, Positioned to encourage setup and prevent service interruptions.

Challenges after testing

Challenges after testing

Several critical insights emerged through moderated usability testing and early feedback from real customers using the prototype, driving key design refinements.

Switching from Bar to Line Graph

Users found it hard to compare changes over time in the bar chart due to the lack of visual flow. The line graph, with interactive tooltips showing value, date, and % change, made trends and anomalies easier to follow.

Interactive Breakdown by Service

The original pie chart lacked interactivity. Users wanted to engage with the data more deeply, so we introduced hover states and a dropdown to toggle between months—making it easier to explore service-level costs.

Clarifying Spend Summaries

Early versions included only current-month figures. Users wanted historical context, so we expanded the summary cards to show comparisons across previous months, with clear indicators of change.

Improving Banner Visibility

The original Auto-Recharge banner didn’t draw enough attention, most users overlooked it. We adjusted the layout and styling to make it more prominent and ensure users noticed the feature.

Evolving the Layout Through Testing

Through usability testing, we explored layout variations to identify what users needed most at a glance. Based on feedback, the final dashboard prioritised summary cards at the top, followed by deeper insights and key actions like Auto-Recharge.

Final Dashboard

Final Dashboard

Designing for mobile

Designing for mobile

The redesigned mobile dashboard led to a noticeable improvement in usability and engagement. Users could now easily view spend trends, enable Auto-Recharge, and top up their wallet on the go. Mobile interaction rates increased by 40%, with fewer drop-offs and a smoother experience for mobile-first users.

Results & Impact

Results & Impact

User Experience Improvement

User Experience Improvement

Post-launch metrics demonstrated significant improvements:

+ 85%

Increase in dashboard interaction rate compared to the previous version

+ 75%

of users discovered and enabled Auto-Recharge after the re-design.

- 50%

Drop in support tickets as more users enabled Auto-Recharge to avoid missed payments.

Business Goals Improvement

The platform delivered measurable business benefits:

+ 40%

Increase in user engagement, with more users actively interactign with the dashboard to monitor their cloud spend.

+ 38%

Boost in customer retention, as more users returned to view the breakdown of their spend.

+ 55%

Rise in Auto Recharge adoption, helping reduce failed payments and service interruptions.

Next steps

Next steps

Based on initial results and feedback, several enhancements are planned:

Smart Auto-Recharge Reminders
Add subtle toast notifications when Auto-Recharge hasn’t been set up and wallet balance is running low—nudging users before issues occur.
Smart Auto-Recharge Reminders
Add subtle toast notifications when Auto-Recharge hasn’t been set up and wallet balance is running low—nudging users before issues occur.
AI Integration
We’re exploring ways to integrate Natasha into the dashboard via a smart side panel, offering contextual support without disrupting the user's workflow. Natasha could help users understand unusual spend patterns, suggest top-up amounts based on usage, and guide them to key actions like enabling Auto-Recharge
AI Integration
We’re exploring ways to integrate Natasha into the dashboard via a smart side panel, offering contextual support without disrupting the user's workflow. Natasha could help users understand unusual spend patterns, suggest top-up amounts based on usage, and guide them to key actions like enabling Auto-Recharge

Other Work

About Builder Cloud

Builder Cloud allows users to manage and pay for the cloud infrastructure powering their Builder.ai applications. It gives users visibility over their cloud spend, invoices, payments, and account settings, all through a prepaid wallet system that ensures their apps stay live and running.

The Problem

The previous Builder Cloud dashboard made it hard for users to understand how much they were spending, what payments were due, or how costs were changing over time. This lack of clarity caused confusion and frustration—contributing to a 35% drop-off shortly after landing on the dashboard and 15% lower interaction rates than other parts of the platform.

Many users were also unaware that Auto-Recharge existed or didn’t realise it could prevent failed payments and service disruptions. Without a clear way to monitor cloud spend or enable key features, users struggled to stay in control, resulting in avoidable support tickets and missed payments.

The Solution

We redesigned the dashboard to make spend data and key actions instantly clear at a glance. By simplifying the layout, surfacing Auto-Recharge, and prioritising clarity over complexity, the new design helps users stay on top of payments, avoid service disruptions, and confidently understand their cloud usage.

Final Design

Intro

The Builder Cloud dashboard had existed for years but hadn’t been updated since its initial build by engineers, with no product or design input. When the opportunity finally came to improve it, we had a short timeline and limited engineering capacity. We focused on gathering quick but meaningful user insights and prioritising the most critical issues, aiming to ship an MVP dashboard that delivered immediate clarity and value to users.

Current Builder Cloud Dashboard

Discovery

To understand why the dashboard was underperforming, we combined user interviews with an analysis of support tickets to uncover recurring pain points and areas of confusion.

What we knew already

Internal analytics showed the dashboard was underperforming compared to the rest of the product. When reviewing Mix panel, we found:

35% of users dropped off shortly after landing on the dashboard, suggesting it wasn’t clear or useful enough to keep them engaged.

The dashboard had only a 20% retention rate, meaning just 1 in 5 users returned to it after their initial visit.

From support tickets, we also learned:


  • Many users experienced unexpected service suspensions after forgetting to top up their wallet.

  • These incidents were often caused by poor visibility of the Auto-Recharge feature, which was buried in the UI and rarely discovered until it was too late.



But what else was stopping users from using the dashboard?

Customer interviews

In-depth interviews were conducted with 5 existing Builder.ai customers who had previously used the "Cloud" platform to track their spend. These interviews focused on understanding their experiences, challenges, and expectations for using the current cloud dashboard. 

Mobile Experience

A review of analytics showed that over 40% of users accessed Builder Cloud from mobile devices. However, the existing dashboard was not responsive or optimised for smaller screens, leading to:


-> Difficult navigation and unreadable data.


-> Increased drop-off rates and frustration among mobile-first users.


-> Missed opportunities for users to take quick actions like topping up their wallet or enabling Auto-Recharge on the go.

Lack of spend visibility

Users were unsure how much they were spending or how their costs were changing month over month.

Confusing discount graph

Users didn’t understand the 'discounted vs. non-discounted' view and didn’t find it helpful. They just wanted clear answers: How much have I spent? Is it going up or down? What will I owe this month?

Summary Over Charts

Users wanted a high level summary of their spend at a glance, instead of having to look at charts.

Unclear billing and next steps

Users didn’t understand figures like “unbilled amount” or “last payment.” It wasn’t clear if they needed to pay now or later, or whether the amount shown was overdue or upcoming, causing uncertainty and inaction.

Hidden Auto Recharge

90% of users said they’d prefer automatic top-ups, but most didn’t know the feature existed, leading to missed payments and service interruptions.

The Goal

Our goal was to redesign the dashboard to make spend tracking clearer, improve discoverability of Auto-Recharge, and reduce reliance on customer support—ultimately driving better engagement and retention.

The Problem

Problem 1: Cloud Spend Visibility

The dashboard made it difficult for users to understand how much they were spending, what was due, or how costs were changing. This confusion led to a 35% drop-off rate shortly after landing on the dashboard. Users need a simple, clear way to track their cloud spend and stay on top of upcoming payments.

Problem 2: Auto-Recharge Awareness

When users ran out of credit, their services were suspended without warning. Many didn’t know that Auto-Recharge existed because it was hidden deep in the dashboard, resulting in high volumes of support tickets. Users need a clear, visible way to set up Auto-Recharge to prevent service disruptions and reduce reliance on manual top-ups.

Through usability testing, we explored layout variations to identify what users needed most at a glance. Based on feedback, the final dashboard prioritised summary cards at the top, followed by deeper insights and key actions like Auto-Recharge.

Evolving the layout through testing

Defining Dashboard Priorities

To quickly validate layout clarity and information hierarchy, we skipped mid-fidelity wireframes and jumped straight into high-fidelity component design. Drawing from user pain points, competitive analysis of AWS, Google Cloud, and Microsoft Azure, and internal usage data, we identified the core information users needed most, then created modular components (like summary cards and spend trends) to test how easily users could digest key data at a glance.
Based on initial results and feedback, several enhancements are planned:

Next steps

Add subtle toast notifications when Auto-Recharge hasn’t been set up and wallet balance is running low—nudging users before issues occur.

Smart auto-recharge reminders

We’re exploring ways to integrate Natasha into the dashboard via a smart side panel, offering contextual support without disrupting the user's workflow. Natasha could help users understand unusual spend patterns, suggest top-up amounts based on usage, and guide them to key actions like enabling Auto-Recharge

AI Integration

Next up

Builder Now

Helping Builder.ai increase conversions through users visualising their app idea

UX UI / Strategy / End To End

The redesigned mobile dashboard led to a noticeable improvement in usability and engagement. Users could now easily view spend trends, enable Auto-Recharge, and top up their wallet on the go. Mobile interaction rates increased by 40%, with fewer drop-offs and a smoother experience for mobile-first users.

Designing for mobile

Ideation

How might we make it easier for users to track and understand their cloud spend at a glance?

How might we make essential payment actions, like Auto-Recharge, more visible and accessible?

How might we simplify the dashboard so users can focus on what matters most?

Summary Cards

Early concept aimed to give users a quick glance, displaying key monthly spend figures, including current spend and change from the previous period.

Visualising spend trends

Presents a bar chart view of monthly spend over time. Each bar represents a different month, helping users track overall cloud expenditure patterns.

Spend by service

Visualises the breakdown of spending by service category. Each segment shows proportional allocation, with a legend listing specific values.

Breakdown spend by service

Highlights the Auto-Recharge feature, Positioned to encourage setup and prevent service interruptions.

Several critical insights emerged through moderated usability testing and early feedback from real customers using the prototype, driving key design refinements.

Challenges after testing

Switching from Bar to Line Graph

Users found it hard to compare changes over time in the bar chart due to the lack of visual flow. The line graph, with interactive tooltips showing value, date, and % change, made trends and anomalies easier to follow.

Interactive Breakdown by Service

The original pie chart lacked interactivity. Users wanted to engage with the data more deeply, so we introduced hover states and a dropdown to toggle between months—making it easier to explore service-level costs.

Improving Banner Visibility

The original Auto-Recharge banner didn’t draw enough attention, most users overlooked it. We adjusted the layout and styling to make it more prominent and ensure users noticed the feature.

Final Dashboard

Results & Impact

User Experience Improvement

Post-launch metrics demonstrated significant improvements:

+ 85%

Increase in dashboard interaction rate compared to the previous version

+ 75%

of users discovered and enabled Auto-Recharge after the re-design.

- 50%

Drop in support tickets as more users enabled Auto-Recharge to avoid missed payments.

Business Goals Improvement

+ 40%

Increase in user engagement, with more users actively interactign with the dashboard to monitor their cloud spend.

+ 38%

Boost in customer retention, as more users returned to view the breakdown of their spend.

+ 55%

Rise in Auto Recharge adoption, helping reduce failed payments and service interruptions.