Case study · AmpliPhi · 2024–25

AmpliPhi

AmpliPhi helps charities find the right donors without writing complex queries. I joined before there was even a repo, and shaped almost everything: the logo, the design system, the first versions of the app, and the first conversations with customers.

Role
Junior Designer, promoted to Product Designer. Brand, system, product, outreach
Timeline
2024 – 2025
Worked with
CEO, CTO, front-end and back-end developers
Tools
Figma, docs in ClickUp
The AmpliPhi mark

The brief

Fundraisers live in their donor database, but pulling the list for a single campaign segment usually means writing a complex query, or waiting for someone who can.

AmpliPhi connects to a charity's donor base. Instead of one complex query, you combine simple ones like building blocks, then export a separate donor list for every segment you're targeting.

From nothing to v1

MarkAmpliPhi means amplify philanthropy. The mark connects groups together, with an A and a P hidden in the negative space.
BrandColour, type and voice built out from the mark.
SystemThe full design system: foundations and components, ready for engineers.
App v1The first versions of the product, designed on that system.
In the fieldConferences, partnerships and the hunt for our first users.

The work

AmpliPhi segments tree with donor counts
Segments. Nest segments, with inclusions, exclusions and a catch-all, and see donor counts update.
AmpliPhi campaign table with lists per channel
Campaigns. Each segment gets a list per channel (email, mail, phone), with appeal codes.
AmpliPhi template gallery
Template gallery. Start from proven segmentation strategies and campaigns.
The AmpliPhi mark
The mark. I explored several directions; the CEO chose one in the family of his other company, SimpliPhi.

Beyond the screen

At a team this small, design didn't stop at Figma. I went to conferences to meet fundraisers, talk about the product and build the partnerships that would bring in our first users.

It paid off: stronger relationships, potential revenue-sharing partnerships, and three charities signed up for the beta after meeting us in person.

Outcome

0→1brand, design system and app, where there had been none
3beta users, met in person
1promotion, from junior designer to Product Designer

Plus stronger relationships in the sector, and partnership conversations that could become revenue sharing.

Looking back

I joined AmpliPhi as a junior designer. I'd designed plenty by then, but never a product like this, professionally, from zero. It was a huge learning experience.

At first I wasn't leading the UX. As I took on more, from the brand to the system to sitting across the table from customers, my influence grew, and I was promoted to Product Designer.

If I did it again, I'd spend much more time talking to potential users early on. I was new and learning by doing many things at once. But understanding their pains, what drives them and how they talk would have been incredibly valuable.