The problem SubZero solves
The Problem It Solves
People and companies today lose significant money to:
- Forgotten subscriptions
- Unused tools
- Silent price hikes
- Auto-renewing free trials
Most existing solutions only list subscriptions.
They do not highlight what is actually wasting money or needs urgent action.
As a result, users remain unaware of hidden financial leaks.
How Sub-Zero Solves It
Sub-Zero transforms raw subscription data into Waste Intelligence.
Instead of just showing what users are subscribed to, it clearly reveals:
- How much money is being wasted annually
- Which subscriptions have increased prices without notice
- Which free trials are about to charge
- Which tools overlap in functionality
- Which subscriptions are likely no longer being used
This makes financial waste visible, emotional, and actionable.
Real-World Impact
For individuals, Sub-Zero helps:
- Avoid surprise charges
- Cancel unused services
- Regain control over spending
For businesses, Sub-Zero enables:
- Detection of redundant SaaS tools
- Identification of unused licenses
- Control over rising subscription costs
It turns subscription chaos into clear spend control.
Why It Matters
Sub-Zero doesn’t just track spending.
It exposes waste and drives better financial decisions.
Challenges we ran into
Challenges I Ran Into
1. Slow Gmail Email Sync
Fetching hundreds of emails using the Gmail API was initially very slow because requests were processed sequentially. Syncing around 500 emails took over 75 seconds, which was not practical for real users or live demos.
How I solved it:
I implemented parallel processing using a controlled thread pool with safe batch sizes. This reduced sync time by 5 to 10 times while avoiding Gmail API rate limits.
2. Detecting Real Subscriptions vs Noise
Many emails contained promotions, newsletters, or unrelated receipts. Accurately identifying actual recurring subscriptions without false positives was a challenge.
How I solved it:
I used:
- Keyword-based filtering
- Metadata scoring
- Vendor normalization
- Amount and frequency checks
This ensured only true subscription-related emails were processed.
3. Handling Silent Price Increases
Subscriptions often change prices without clear notifications. Tracking these changes across historical receipts required consistent amount parsing and proper storage.
How I solved it:
I created a price history table to store past charges and compared them over time to detect percentage increases automatically.
4. Free Trial Detection
Free trials appear in many formats and are not always labeled clearly. Some emails do not mention the trial duration.
How I solved it:
I combined:
- Amount-based detection (0 dollar charges)
- Keyword matching (free, trial)
- Fallback duration logic
This ensured reliable trial ending alerts.
5. Performance vs Accuracy Balance
Aggressive API calls caused timeouts and rate-limit errors, while conservative calls slowed the system.
How I solved it:
I tuned:
- Batch sizes
- Worker limits
- Retry logic with exponential backoff
This achieved a stable balance between speed and reliability.
What I Learned
Building Sub-Zero required solving real-world problems related to API limits, data accuracy, performance optimization, and user trust. These challenges helped shape a more robust, scalable, and reliable system.
Tracks Applied (1)
Open Innovation
Technologies used