Designing Clevero's no-code widget builder
A self-serve dashboard builder that gave customers the flexibility to create dashboards from live platform data while reducing customization requests to engineering by 75%.
PROJECT DETAILS
ROLE
I was the First in-house Senior Product Designer, working closely with one Product Manager and the engineering team.
CONTEXT
Clevero, a low-code business management platform for service businesses.
PROJECT
Self-serve Dashboard Builder
DURATION
8 weeks (2026)
TEAM
Riya (me!)
TOOLS
Claude Code, Supabase, Vercel, Figma
OVERVIEW
What is the Widget Builder?
A visual builder that lets non-technical users create their own dashboards from live platform data. 16+ widget types, one shared configuration framework, zero code.
Issue reported for:
Content
Dev
Others
08
15
22
29
01
May
250
200
150
100
50
0
Data Visualization
User Research
Iteration
Others (0.3%)
BACKGROUND & PROBLEM
EXPLORATION
Every dashboard request became an engineering ticket.
Clevero is built around the idea that customers should be able to configure the platform themselves. From workflows to forms and automations, almost everything could be customized without writing code.
Dashboards were the exception.
Whenever a client wanted a new chart, KPI, or table, it became an engineering request. Even small changes competed with roadmap work, slowing customers down and pulling engineers away from building the product.
Building another dashboard wasn't the challenge.
Designing a system that let anyone build their own was.
Digital Space
Your Space
CHALLENGE
Balancing flexibility with simplicity
Every business wanted different dashboards.
Some wanted sales metrics. Others tracked appointments, invoices, enrollments, or support requests. The builder needed to support completely different use cases without exposing the complexity behind the data.
The question became:
Digital Space
Your Space
HMW
How might we give users the flexibility to build dashboards around their business without asking them to think like developers?
CHALLENGE
Finding the Right Abstraction
Every business wanted different dashboards.
Some wanted sales metrics. Others tracked appointments, invoices, enrollments, or support requests. The builder needed to support completely different use cases without exposing the complexity behind the data.
The question became: