Subtrack: a local-first subscription audit tool with a one-time unlock
A local-first web app that helps people audit and reduce recurring subscriptions.
Problem it solvesPeople want to reduce subscriptions without signing up for another monthly bill.
The solo developer behind Subtrack rebuilt it as a zero-login, local-first web app for people auditing subscriptions. The post says over 80% of new visitors jumped into the demo and roughly 10,000 views were tracked across recent posts.
How they grewRecent posts
Hot-Stranger644
u/Hot-Stranger644
Why I ditched auth and recurring subscriptions for a local-first utility (and what 10k views showed about paywalls) (Disclosure: I'm the solo developer behind Subtrack, sharing this as a build/metrics retrospective) When planning a simple utility SaaS, the common playbook is almost automated: spin up an auth provider (Supabase/Firebase), set up cloud database tables, block access behind a login screen, and charge $5/month. I originally went down that route, but the product fundamentals felt contradictory: people looking to audit and reduce recurring subscriptions are usually exhausted by the idea of adding yet another monthly bill. On top of that, forcing an account creation before delivering immediate utility creates a massive drop-off for simple tools. I decided to rebuild the project as a zero-login, local-first web app (localStorage only) backed by a flat lifetime unlock ($14.99) instead of monthly billing. After tracking roughly 10,000 views across recent posts and analyzing initial event data, here are the main technical and business takeaways: Removing mandatory logins completely transformed initial interaction. Over 80% of new visitors jumped straight into testing the pre-populated demo dashboard. However, zero-friction created a different product problem: users treated the demo as a static sandbox and did not naturally realize they could reset it to input their real data. I had to build an explicit "clear demo & start fresh" onboarding banner to bridge the gap between passive testing and actual active usage. - Zero server maintenance vs. Data risk: Storing user records client-side eliminated server maintenance, database scaling costs, and sensitive financial compliance concerns entirely. The trade-off is user retention: if a user clears their browser cache without exporting their CSV backup, their records are gone. The next logical step will be optional local file imports rather than centralizing data on an external server. - One-time fee resistance vs. Churn management: For micro-utilities, charging a one-time unlock ($14.99 after 5 free entries) eliminated the recurring churn problem completely. While it limits MRR predictability, initial conversion intent signals were noticeably higher than asking for an ongoing subscription. The project is live here for context on how the local flow works: https://getsubtrack.lovable.app For solo founders building utilities, how are you balancing local-first privacy architectures with long-term user retention? Do you see a sustainable resurgence in flat-fee utility pricing over recurring SaaS?
- Views
- 10K
- across recent posts
- Visitor demo starts
- 80%
- new visitors
