← All writing
Behind the build · Perks
One portal for perks that lived in spreadsheets.
How I replaced scattered sign-up sheets across Valsoft's companies with a single Perks portal, designed in Figma and built with Claude.
Valsoft runs genuinely nice on-site perks across its companies: car wash, barber, nail tech, corporate headshots, all half-price and on the clock. The problem was never the perks. It was finding them. Sign-ups lived in scattered spreadsheets and email threads, eligibility was tribal knowledge, and the best slots went to whoever knew who to ask.
Make eligibility obvious, make booking boring
A perks program is supposed to feel like a gift, and a spreadsheet ruins that. So I designed one portal where employees sign in with their work email, immediately see which perks they're eligible for, and book a slot, or join a waitlist when something's full, in a couple of clicks. Eligibility and waitlist position carry over from round to round, so nobody has to keep track by hand.
The unglamorous half: the admin console
A perks portal is only as good as the people running it, so half the work was the back office. Admins manage users and per-person access, schedule rounds, set vendor pricing, send notifications, and generate taxable-benefit reports (the requirement nobody puts on a mood board). Getting that reporting right is what makes a program like this survivable at a company's scale.
Onboarding that explains itself
Because most people would open this once a month at most, the first visit had to teach itself. I built onboarding directly into the flow: a short guided demo and demo accounts, so anyone can take the portal for a spin without a manual. If a tool needs a training session, the design has failed.
Built with Claude, on a real design system
I designed in Figma and built the working prototype with Claude, on top of a small design system that keeps the sign-in, dashboard, booking, and admin views consistent. The outcome replaces scattered spreadsheets with one place for eligibility, bookings, waitlists, and the reporting to run it all, validated as a clickable prototype before committing engineering time. Even "fun" internal tools carry real operational weight; designing the boring parts well is what lets the nice parts feel effortless.