Pulse
End-to-end design of an ERP software for solar energy projects
The Product
Pulse is the ERP system designed to support the Operations Department in its day-to-day activities at ecoligo GmbH by becoming its single source of truth.
It provides the core services required to record, manage, and archive information throughout the lifecycle of the company's solar energy projects, which are developed and operated by teams across 13 countries in Southeast Asia (SEA), Latin America (LATAM), and Sub-Saharan Africa (SSA).
By centralizing client and partner data, it provides configurable business workflows while maintaining operational flexibility, and ensures that processes are traceable and compliant with internal and regulatory requirements.
Here are some screens for quick browsing:
Project overview
| Company | ecoligo GmbH |
|---|---|
| Product | Enterprise Resource Planning (ERP) Web App |
| Team | Operations Department → Product Team |
| Roles | Senior Product Designer I; Product Lead |
| Scope | UX, UI, design system; product specifications |
| Tools | Figma, Figjam, Illustrator; Jira |
| Timeline | Sep 2024 - Dec 2025 |
I was in charge of rebuilding Ecoligo's ERP (Enterprise Resource Planning) software at the design and architecure levels, including areas such as:
• Onboarding experience (user sign up, authentication, log in, log out)
• Offboarding experience (remove user, deactivate user)
• Database pages to manage solar operations, including client registry, contract management, and tracking of solar energy measurements
• Client invoicing based on solar energy tracking
• EPC partner registry, in order to achieve internal user conversion (i.e. discourage external tools use).
The business goal I was targeting was to centralize all the operations' data in an in-house developed product to hinder any inaccuracy in financial calculations, construction specifications, etc.
Business impact
⏱️ 0.3s max API response time
From the initial scary time of aprox. 10s.
✅ 100% reliable data
By introducing a curated source of truth (aka backbone data) for every output needed at the company.
👥 96.85% adoption rate
From 10 users to 92 out of 95 (almost everyone in the company).
User impact
😌 Relief
Entering data that was repetitive was cancelled by having a centralized repository of that information.
👌🏻 Clear responsibilities
Who should update the backbone data points should not be the same person who is, for example, filling a contract.
🧑🏻💻 More focus on own tasks
Because re-entering backbone data implied desk research and lost time lost, or pasting information that might have not been updated.