COMPANY
Matter Motor Works
SCOPE
An ecosystem of Matter's Internal Operations (I covered Sales Module in this case study)
TIMELINE
8 to 9 months
TEAM
2 Designers, 1 engineer, 1 QA and 1 Manager
Project Details
Sales operations at Matter generate large volumes of data across multiple touchpoints—lead intake, lead quality, ETBR (conversion reports), dealership performance, sales metrics, and customer feedback.
This data needs to be monitored and acted upon by multiple stakeholders across dealerships and OEM levels, each requiring different levels of visibility and control.
To enable efficient decision-making, a unified and role-based dashboard system was required to consolidate data across channels and present it in a structured, actionable format.
Lead Generation to Lead Analyses
D-SUITE
Gather data from Sales Module of D-suite
MATTER ORBIT DASHBOARD
Outputs it in the form of meaningful analytics, shown via dashboards
Problem Statement
DOCUMENTATION CHALLENGED
The requirement for extensive documentation poses a barrier for rural customers who often face difficulties in gathering and submitting paperwork.
LIMITED INFORMATION
Many eligible customers lack access to comprehensive information about RPL, hindering their awareness and understanding of the loan offering.
ACCESSIBILITY CONCERNS
Rural customers often struggle to physically visit BFL branches, limiting their access to loan application assistance and creating a need for a more accessible solution.
The Beginning : Design Process
Business Goals - Marketing & Sales
MARKETING GOALS
​
1. Analyse lead/customer demographic data
2. Region/location from which most of the enquiries are being generated.
3. Source of enquiry generation
SALES GOALS
​
1. Lead drop-off point and reason
2. Dealership wise retail conversion rate
3. Test Ride conversion
4. Target completion analyses
5. Reviewing pending or over-due activities
Stakeholder Ecosystem
​Three unknowns, one launch. We were building a greenfield tool, no prior version to iterate on, no existing patterns to inherit. The users using it were selling a product (an EV) that most customers had never owned, using a tool they'd never used before, in a category where trust is the entire conversion mechanism. That's 3 simultaneous unknowns: the product (D-Suite), the category (EV) and the user's confidence. Most greenfield builds deal with one. We dealt with all 3 in parallel.

D-suite is the internal enterprise product suite which covers a Sales Module for lead management with features like lead scoring, nudge-based actions, a colour-coded urgency system, and an activity timeline, a Service module (used at EV service outlets) and a Provisioning Module to enable cloud services.
Wireframes : Built with Intention
Decisions
​Three unknowns, one launch. We were building a greenfield tool, no prior version to iterate on, no existing patterns to inherit. The users using it were selling a product (an EV) that most customers had never owned, using a tool they'd never used before, in a category where trust is the entire conversion mechanism. That's 3 simultaneous unknowns: the product (D-Suite), the category (EV) and the user's confidence. Most greenfield builds deal with one. We dealt with all 3 in parallel.

D-suite is the internal enterprise product suite which covers a Sales Module for lead management with features like lead scoring, nudge-based actions, a colour-coded urgency system, and an activity timeline, a Service module (used at EV service outlets) and a Provisioning Module to enable cloud services.
Outcome
Three unknowns, one launch. We were building a greenfield tool, no prior version to iterate on, no existing patterns to inherit. The users using it were selling a product (an EV) that most customers had never owned, using a
_gif.gif)
Three unknowns, one launch. We were building a greenfield tool, no prior version to iterate on, no existing patterns to inherit. The users using it were selling a product (an EV) that most customers had never owned, using a
Three unknowns, one launch. We were building a greenfield tool, no prior version to iterate on, no existing patterns to inherit. The users using it were selling a product (an EV) that most customers had never owned, using a
What I Learned as a Designer
In the end : When I finally look back
Designing Sales Module for D-Suite product has been both a professional leap and a personal milestone: teaching me to think system-wise, empathize ruthlessly, and collaborate fearlessly.
-
Designing for scale before reality — Building complex, multivariate loyalty rules from the start taught me how to manage exponential complexity while keeping the interface intuitive.
-
Collaboration as creation — Working with product, leadership, and engineering wasn’t just communication—it became co-creation.
-
Empathy in execution — Realizing Dyson’s need for custom-styled customer portals reminded me that design extends beyond UX patterns to emotional brand alignment.
Let's Work
Together
jayashreedhamija.com
jayashree676@gmail.com
Bangalore.
Home

About me

Contact
© 2026 by Jayashree Dhamija l Made with love