Role and scope

Role: Product design, end to end · Scope: Problem → working prototype · Platform: Web + mobile · Tools: Figma + Claude Design

Context

Valsoft runs useful on-site perks across its companies: car wash, barber, nail tech, and 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

I designed one portal where employees sign in with their work email, immediately see which perks they are eligible for, and book a slot or join a waitlist in a couple of clicks. Eligibility and waitlist position carry over between rounds so nobody has to track them manually.

The unglamorous half: the admin console

A perks portal is only as good as the people running it. Admins manage users and per-person access, schedule rounds, set vendor pricing, send notifications, and generate taxable-benefit reports. Getting that operational reporting right is what makes the program sustainable at company scale.

Onboarding that explains itself

Because most employees would open the product only once a month, the first visit had to teach itself. I built a short guided demo and demo accounts directly into the flow so anyone could try the portal without a manual or training session.

Built with Claude, on a real design system

I designed in Figma and built the working prototype with Claude on a small design system that keeps sign-in, dashboard, booking, and admin views consistent. The result replaces scattered spreadsheets with one place for eligibility, bookings, waitlists, and reporting, validated before committing engineering time.