Building a non-SaaS product in a SaaS dominated market taught me difficult lessons
Over the past year I’ve been building a finance product, and one of the biggest strategic decisions I made early on was choosing not to make it SaaS.
Which, in today’s environment, sounds counterintuitive.
Most finance and productivity tools rely on:
- Cloud sync
- Subscription revenue
- User analytics
- Engagement tracking
I went the opposite direction and built the product fully offline.
No accounts.
No cloud storage.
No subscriptions.
No telemetry.
From a user trust perspective, this aligned strongly, especially for financial data.
But from a business and growth perspective, it introduced real challenges:
1. No recurring revenue
Without subscriptions, monetization becomes unclear. You’re either relying on one-time purchases, donations, or goodwill.
2. No behavioral analytics
No funnel tracking, no churn metrics, no engagement dashboards. Product iteration becomes feedback-driven rather than data-driven.
3. Harder retention loops
No email capture, no lifecycle messaging, no re-engagement automation.
4. Distribution disadvantage
SaaS products benefit from network effects and integrations. Offline tools grow slower and rely more on community discovery.
Despite this, the trust and alignment benefits have been significant.
Users are increasingly privacy conscious, especially around finance data.
Curious how other founders here think about:
- Non-SaaS monetization models
- Privacy vs analytics tradeoffs
- Offline first product viability
For context, the product I’m referring to:
Android
https://play.google.com/store/apps/details?id=com.anotherwhy.zero
iOS
https://apps.apple.com/us/app/zero-offline-expense-tracker/id6759560225
Open source repo
https://github.com/indranilbhuin/zero
Posted Feb 26, 2026, 2:05 PM UTC