Work/1/5/Case study

GALVANY Operating System. One flow from lead to installed heat pump.

The seller’s leads board in the Sales Portal: no appointment, appointment, offer, detailed planning and order

A lead’s drawer over the seller’s board: call and e-mail, the offer, the next steps, the key facts and the appointments

Leads in GALVANY OS as a board: new, contacted, waitlist, scheduled — The teams’ leads

Refining a view in GALVANY OS: a chat on the left, the view’s preview on the right, a dashboard and the orders behind it — A view, refined with AI

Company: GALVANY
Role: Lead Product Designer
Year: 2026

Brief

GALVANY sells heat pumps through sales partners. GALVANY OS is meant to replace Airtable for its own teams. Its Sales Portal is the part the partners work in, and every customer passes from one side to the other and back. I design all of it.

Outcome

GALVANY’s production design system is our developer’s version of mine. It took its brand colours from my OS prototype, and I made the ten design calls that were still open. The OS prototype itself is meant to become the spec the backend is built from.

My part

I lead product design at GALVANY, and its design system started with me. I own the prototypes, the Sales Portal included: what each team and each seller sees, and how a project moves between teams. On the teams’ side, I also own the interviews. I design in code with Claude Code: clickable prototypes on fictional, seeded data.

Built with

Next.js, React, TypeScript, Tailwind, Claude Code

Decisions

Key decisions.

1/3

A rejection names the page

Back on the teams’ side, order review sits beside the signed offer: a seven-point checklist, each point with its page. It ends in a release, or a rejection with a reason. The seller sees it in the Sales Portal, so whoever fixes it doesn’t have to guess.

Order review: the signed offer on the left, the seven-point checklist with its page numbers on the right

2/3

Gates before anyone installs

Nothing gets installed until its four gates are clear: subsidy, detailed planning, financing and the electrics. Every pipeline card shows them as check circles (the electrics joined later), so what’s blocking is visible at a glance.

Three of the gates (subsidy, detailed planning and financing), each with its open, done and not-applicable count

3/3

A view starts with a sentence

In the OS, people describe the view they need in their own words: region, amount, period, team. It becomes a list or a dashboard on the live data, saved with their other views. To change it, they tell the AI what should change, or edit each part of the view directly.

Views in GALVANY OS: “Which view do you need?” above a box to describe it in your own words

More screens

The seller’s week: on-site appointments, product demos and calls — The seller’s week

Offers in GALVANY OS as a board: sent, opened, expiring, signed — The teams’ offers

Every person, customer and record on these screens is fictional: the prototypes run on seeded mock data. Only the product names are GALVANY’s own.

Next / 2/5 Juno