Skip to content

Faves

Faves is an app for saving and organizing the stuff you find on social media. I joined to work on the app, and today I also help the team figure out and build new products.

Role
Builder & designer
Period
Jun 2025 — now
Status
Ongoing
Built with
Figma, Claude Code, Notion
20+ideas written down and stress-tested
8killed in the first 46 days
7 weeksfrom prototype to people paying, our fastest so far
01

The app

I started by auditing the whole app, then redesigned the Pro plan, the onboarding and the paywalls, and gave it a more premium look.

On the paywall, people get a free week, we tell them clearly they won’t be charged today, and there’s an easy way to go with Plus or Free instead. The audit also flagged the forced trial, and it was removed. I designed it in Figma, and the team’s engineer built it.

Faves splash screen: All your saves, in one place
Splash screen
Faves onboarding screen explaining how to save with Share
Onboarding shows how to save from any app with Share
Faves onboarding screen showing folders and subfolders
Folders and subfolders
Faves Pro paywall with a free week and a clear way to other plans
Pro paywall, with a free week and the other plans
02

How we test ideas before building them

Faves also works as a small venture studio now. With AI, building got fast and cheap, so the hard part is knowing what’s worth building. I put together the process we use to check that with real people first. Every week we take one idea through it.

  1. MonWrite the idea downHalf a page, six questions. If it doesn’t fit, the idea isn’t clear enough yet.
  2. Tue — ThuTalk to people who have the problemCalls, messages, fake door tests, and a prototype when talking isn’t enough.
  3. FriDecide: go, wait or killWe write it down with the evidence, so everyone can see why.
HYPOTHESIS CARDH·XX
Who
One specific kind of customer
Hair-on-fire pain
What hurts badly enough to act on this week
Current way
How they cope today, and what it costs
New way
What we’d put in their hands instead
Why 10×
Why it’s not just a little better
Money
Who pays, how much, and why now
STRESS TEST0 — 100

Then we try hard to break it: the market, the angle, the risks, every reason it could die. It gets a score from 0 to 100, and under 55 we don’t build it.

One idea, as first pitched: 35Same idea, sharper angle: 56

That test also found a rule in a partner platform’s terms that would have broken the product as planned.

Every test gets a kill date on the calendar. If we don’t run it by then, the idea is dead.
Don’t ask people to confirm a problem that makes them look bad at their job. They won’t.

We’ve written down and stress-tested more than 20 ideas. In the first 46 days we killed 8 of them, and it was the first time the team killed an idea because of what customers told us instead of after building it. Before we had this process, our quickest build went from prototype to people paying in 7 weeks, and then had a hard time keeping them. That’s a big part of why we now test before we build.

NextTeachMe.To →I take care of conversion for a lessons marketplace in 250+ US cities, from the homepage search all the way to checkout. I design the experiments, build them and read the results.