Solar installation management web app
Renewable energy
Desktop Application
UX Research
Product Owner Role
B2C
Design System
Product Design
UX Strategy
📈 45% faster sales creation
📉 35% less project management workload
📈 30% faster UI development time
Key results
* Unfortunately, since the project is confidential because of my employer's NDA contract, it isn't possible to share more details about the design deliverables. If you have any questions about the process or any particular aspect of the project, let me know.
Employer
About the project
I worked on an internal web application designed to streamline processes for employees involved in solar panel installations. The goal was to migrate an outdated system to a more centralized platform that would improve workflows across sales, project coordination, and installation.
One of the biggest challenges identified was the disorganization of client data, solar installation products, installation details, and planning processes. The scattered data made it difficult for the teams to access and update key information quickly, resulting in slow sales creation and inefficient project management.
After conducting UX research, including interviews with users and stakeholders and mapping the existing processes, it became clear that the company needed data centralization and process optimization.
The impact was significant:
-
A 45% reduction in the time it took to complete the sales creation process
-
A 35% reduction in the time spent on project management tasks
-
By automating repetitive tasks, the team was able to focus more on strategic activities and improve overall project delivery, reducing the money lost due to inefficiencies.
​
Role in the project
As the only UX/UI Designer in the team, I led the design of the new web application.
My responsibilities included:
​
-
UX Research: Conducting research to identify pain points in the old system and mapping out the current process.
-
Collaborating with stakeholders, product owners (PO), and users to define new user flows, functionality, and features.
-
Developing user personas based on interviews with end users to ensure the application met their specific needs.
-
Designing wireframes, flows, and navigation to improve the overall experience.
-
Regularly collaborating with development, QA, and stakeholder teams for feedback and iterative improvements.
-
Implementing metrics and research strategies to track user behavior and measure the impact of design changes (1 on 1 interviews, surveys and Hotjar reports).
Biggest challenges
-
The migration of an existing system to a new platform presented a significant challenge, especially in ensuring that it remained functional and user-friendly during the transition. Users were accustomed to the old system, so maintaining a smooth experience while introducing new features was key.
-
Another challenge was balancing the needs of multiple user groups, including sales, project coordination, and installation teams, each with their own distinct workflows. We had to find ways to unify these different processes while keeping the system intuitive for everyone.
-
Finally, the integration of a new design system (MUI) required careful planning to ensure it was scalable and adaptable, providing a consistent experience across the platform while being flexible enough for future growth.
Chosen solutions
To tackle the challenges, I adopted a user-centered design approach that not only addressed the pain points of the old system but also introduced new functionalities to improve the user experience.
Key actions included:
-
Comprehensive research through 1-on-1 user interviews, surveys, and Hotjar reports, as well as mapping the as-is processes to identify existing pain points and inefficiencies in the workflow.
-
Redefining user flows and processes based on feedback from users and stakeholders, ensuring the design was both intuitive and aligned with company goals.
-
Implementing a modular design system (MUI) to ensure the web application was scalable, consistent, and easy to maintain over time.
-
Collaborating closely with cross-functional teams (development, QA, stakeholders, PO) to create a solution that seamlessly integrated user needs with business requirements.
This approach helped create a more efficient and intuitive system, resulting in faster sales and project management processes.
Outcomes and lessons learned
The new internal web application is currently being implemented and used by the users and, aims to streamline workflows and improve efficiency for employees involved in solar panel installations.
​
Key lessons learned:
-
User collaboration is crucial: Engaging with end users and stakeholders regularly helped us make informed decisions that directly impacted the final product’s success.
-
Design systems ensure scalability: Adopting MUI for the design system helped us build a consistent user experience across the platform while making it easier to maintain and extend.
-
Balancing multiple needs: Designing for a diverse user base (sales, coordination, installation) required flexibility and a clear prioritization of features.
-
Iterative development: Regular feedback from development and QA teams ensured we were always aligned and able to address issues early in the process.
-
This project reinforced the importance of collaboration and user-centered design in delivering a high-quality solution.
Future work: Centralized Sales & Operations integration (HubSpot + internal tools)
The need for a centralized sales-to-installation workflow emerged directly from user research insights and stakeholder interviews conducted during the project.
​
Research foundation behind this next step
​
Through user interviews with sales representatives, coordinators, and installers, several recurring pain points surfaced:
-
Repeated manual data entry across multiple systems
-
Confusion caused by inconsistent customer information
-
Delays during handoffs between sales → contract → project teams
-
Lack of visibility into deal status and installation progress
In parallel, the stakeholder interviews (CFO, Marketing, Support, Operations Manager, Head of Sales, Commercial, Purchase, and Logistics) revealed broader organizational concerns about alignment, data accuracy, and system scalability.
​
I synthesized these conversations through stakeholder mapping, identifying influence, needs, and collaboration touchpoints. From there, I categorized insights into themes, data fragmentation, workflow inefficiency, and integration gaps, which became key drivers for prioritization.
This analysis made one thing painfully clear:
We needed a single, coherent source of truth for sales and project operations.
Why HubSpot integration?
​
Based on these findings, HubSpot became the logical next step to unify:
-
Customer creation and updates
-
Deal stages and sales pipeline
-
Automatic handoff to CPQ and Oneflow (for contract creation)
-
Automatic project creation in Blikk
-
Data continuity into Zendesk
The integration directly addresses user pain points and the strategic priorities identified in stakeholder mapping.
​
Scope of the next design phase
For the upcoming roadmap, I will define:
-
User flows between HubSpot and the internal sales tool
-
Interaction models and handoff logic for deals → contracts → projects
-
Error-handling patterns for data conflicts
-
Permissions and roles for 45+ sales users
-
UI updates to incorporate new HubSpot data structures
-
Unified information architecture integrating HSE + Project Inspection forms into the full lifecycle
Expected impact
-
Reduced manual steps
-
Clearer responsibilities across teams
-
Aligned data across sales, contract, project, and support tools
-
A scalable foundation for automation and analytics
This future work builds directly on research-driven insights and the strategic needs uncovered during stakeholder sessions.
Solar installation management web app - Scalable & User-friendly UI design
I designed the UI for an internal web application aimed at streamlining workflows for employees managing solar panel installations. The goal was to replace an outdated system with a centralized platform that would improve efficiency across sales, project coordination, and installation processes.
To create a scalable and consistent UI, I developed a design system using MUI (Material-UI), ensuring flexibility for future growth while maintaining a user-friendly experience. This system helped make the design both efficient and adaptable for the web platform.
I worked closely with the development team to ensure the designs were feasible and aligned with the technical requirements. I was involved in reviewing flows, interactions, and UI implementation, ensuring a seamless user experience from design to development.
The screens shown here are just a small sample of the many I created, and created considering scalability, usability, and cross-functional collaboration.
Expanded details: Current integrations
Current integrations (today’s ecosystem)
​
The internal system already supports several critical integrations, each covering a specific part of the sales → contract → installation → support pipeline:
​
Oneflow - Contract management
-
Used to automatically generate digital contracts directly from the CPQ tool.
-
Pulls customer and deal data from our internal system.
-
Sends signed contract information back to the system to trigger next steps.
-
Eliminates versioning issues and reduces manual edits from sales representatives.
Blikk - Project management
-
Creates installation projects immediately after contract signing.
-
Receives contract details, installation type, and customer data directly from the internal system.
-
Sends project updates and status changes back to internal users (sales, project coordination, installers).
-
Supports coordination tasks, scheduling, and assignment management.
Zendesk - Customer support
-
Connects customer information and project history with support tickets.
-
Ensures agents have visibility into installations, contracts, and customer details.
-
Reduces back-and-forth between sales, support, and coordination teams.
-
Provides historical continuity post-installation.
Together, these integrations cover contracts → projects → customer support, but the sales pipeline still lives outside the system, resulting in fragmented data and duplicated work.
Internal operational tools (already in use)
These tools aren’t external integrations, but they play a crucial role in the installation workflow and must remain aligned with the future ecosystem.
​
HSE plan (Health, Safety & Environment Form)
-
Required for every project before installation begins.
-
Captures site-specific safety conditions, risks, and compliance requirements.
-
Used by installers and project owners to ensure safe execution.
-
Stored within the system and connected to each project record.
Project Owner / Inspection form
-
Completed by the project owner or inspector during pre-installation site visits.
-
Includes technical checks, measurements, access restrictions, and installation feasibility details.
-
Feeds directly into project planning and procurement decisions.
-
Critical for material accuracy and scheduling logic.
-
Prevents project delays by surfacing issues early.
These two tools are essential to the installation lifecycle and represent operational steps that any future integrations must support.
Simplified system workflow (sale and project statuses)
Dashboard
Create new sale
Create new sale - Customer address step
Create new sale - Attachments tab
New system: Research-Driven design improvements
These screens represent the next iteration of the system, designed based on insights gathered from user interviews, stakeholder sessions, and cross-team workflow mapping. Throughout the research phase, users consistently highlighted gaps in clarity, data consistency, and handoff friction between sales, project coordination, and installation teams. Stakeholders reinforced these findings, emphasizing the need for a more integrated, scalable system aligned with upcoming CRM, contract, and project-management integrations.
​
The following designs reflect those insights in action. They focus on reducing cognitive load, improving data accuracy, aligning terminology across teams, and preparing the interface for future integrations such as HubSpot, Visma, and expanded project documentation flows. Each improvement is grounded in real user feedback and validated through stakeholder discussions to ensure the new system supports both operational needs and long-term business goals.
Stakeholder interviews, categories and themes
Stakeholders' mapping
New system
Dashboard view
View sale
Customer book
Callbacks & To Do's
Offers dashboard
