1
0 Comments

My Gmail reading app's biggest problem is getting anyone to trust it

Hey everyone

Founder here, building in public.

I shipped Subby today (it scans your Gmail (read only) and

finds the subscriptions you forgot you're paying for, with a "cost per use" for

each so you can see which ones actually waste money (that $15/mo thing you use

twice a year)).

I believe my biggest problem is getting people to trust it. It reads your email, I have no track record yet, and Google still shows the scary "unverified app" screen. That's a massive ask for a stranger.

My bet to get around it: lead with a fully interactive demo that needs no signup

or login. It runs on a sample inbox so people see the value before granting any

access: https://subby-eosin.vercel.app/#demo

What I'd love this community's take on:

  1. 1. Would you connect your Gmail to a brand-new app like this? If not, what wouldchange it; read only scope, local only parsing, open source?

  2. Does leading with a no signup demo actually lower the barrier, or do people bounce anyway?

  3. Is "cost per use" a frame that clicks, or a gimmick?

On privacy, since it matters: read only scope (can't send or edit anything), I

don't store emails, only the subscriptions found (name + price), never sold,

one click disconnect + delete.

Building this in the open. Happy to share what's worked and what hasn't.

posted toAvatar for product Subby
Subby