Halvard is the dashboard that lets community solar cooperatives run on trust instead of spreadsheets: every member sees at a glance what their share produced and what they owe, every treasurer can close the month without a headache. This redesign takes Halvard from a working MVP serving three co-ops to a system ready to onboard twenty or more, without losing the clarity that made it trustworthy in the first place.
Overview & Goals
- Redesign the member view around the one number that matters: production, savings, or balance owed
- Give treasurers a settlement flow that exports cleanly into a format their accountant accepts
- Support the full member lifecycle: adding a member and transferring a share when someone moves away
- Make the dashboard something members actually open, even if they only visit four times a year
Budget & Timeline
Work starts with the member view, redesigned and shipped within six weeks. Treasurer flows follow, targeted for the end of the quarter, so the settlement and export pipeline is production ready well ahead of the January annual statements.
App & platforms
- Logo files
- Only PNG or JPEG
- Platforms
- Web app, Tablet
- Stage
- MVP exists
- Core flows
- The member view: what my share produced this month, what it saved me, what I owe or am owed. The treasurer view: the monthly settlement, exported in a form the accountant accepts. Adding a member and transferring a share when someone moves away. The annual statement every member gets in January.
- Constraints
- Accessibility requirement, Existing backend
- Handover
- Screens in Figma, Component library / design system
- Screens
- Around 15 views, most of them variations of the member overview.
- User roles
- Members see their own share and their monthly statement. The treasurer sees everything and sends statements. An admin sets up a new co-op.
Target Audience
Halvard serves people who are not full time energy professionals: volunteer treasurers managing co-op finances in their spare time, and members who check in occasionally to see how their share is doing.
Style
Typography
Chosen
- HalvardNeutral & functional · GrotesqueExample typeface: Inter. A starting point, not a requirement.
Colour
New color direction
Cool & trustworthy
The blues people associate with banks, software and being in safe hands.
Examples of the mood. The final colors are part of the job.
In the client's own words
Halvard is a dashboard for community solar cooperatives. A co-op owns a roof, forty members own a share of it, and every month somebody has to explain who produced what and who owes what. Today that is a spreadsheet emailed around by a volunteer treasurer. We have a working MVP with three co-ops on it, built by our own developer with no designer involved, and it shows: everything is a table, the numbers that matter are three clicks deep, and members log in once and never return. We want the redesign before we take on twenty more co-ops.
Scope & Deliverables
- Redesigned member overview, covering production, savings, and balance
- Treasurer settlement flow with accountant-ready export
- Member management: adding members and transferring shares
- Annual statement template for the January mailing
- Component library and design system for future co-ops
- Figma screens ready for developer handover
- Accessibility review across member and treasurer flows
Do's & Don'ts
Do
- Design the member view for someone who opens it four times a year and has forgotten everything since the last visit
- Settle on one chart style for production data and a separate one for money, and keep the two visually distinct
- Build the treasurer settlement flow to work on an old tablet, since that is what treasurers actually use
Don't
- Do not build a dashboard of twelve widgets, most members just want one number
- Do not require a new backend field without checking first, the developer is a one person team
- Do not let production charts and money charts share a visual language, they need to stay legible apart