DrawdownSentinel — Set Your Drawdown Threshold Once, Sleep Without Watching Charts
You built a portfolio tracker in a weekend and 200 traders on r/automation are jealous. DrawdownSentinel is the hosted version — connect any broker via CSV or API, set a percentage threshold, and get an SMS or Telegram alert the moment your portfolio drops past it. No spreadsheets, no broker email lag, no panic-checking at 2am.
Difficulty
intermediate
Category
Finance
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
6/10
Validated by Real Pain
— sourced from real community discussions
Traders are manually building portfolio drawdown monitors because broker alerts are delayed and not threshold-customizable — they are willing to pay for an automated hosted version.
What is it?
Retail traders and crypto holders manually check their portfolios dozens of times per day because broker email alerts are delayed, generic, and impossible to customize. DrawdownSentinel lets users connect portfolio data via CSV upload or Alpaca/Coinbase API, define custom drawdown thresholds per asset class or total portfolio, and receive instant SMS via Twilio or Telegram alerts with a clear breakdown of what triggered the alert. The May 2026 market volatility wave means this pain is acute right now. Fully buildable with existing stable APIs: Alpaca for equities, Coinbase Advanced for crypto, Twilio for SMS, Telegram Bot API for messaging, and Supabase for user data and cron-based checks.
Why now?
May 2026 market volatility plus the explosion of retail self-directed trading means drawdown anxiety is at a peak, and Vercel Cron plus Alpaca's free API make a reliable polling-based alert system shippable in days not months.
- ▸CSV upload or Alpaca/Coinbase API connection for live portfolio value polling.
- ▸Custom threshold builder: set percentage drawdown per asset, asset class, or total portfolio.
- ▸Instant Telegram and SMS alert with breakdown of which positions triggered the threshold.
- ▸Alert history dashboard showing every trigger with timestamp and portfolio snapshot.
Target Audience
Self-directed retail investors and crypto traders managing $10k-$500k portfolios — an estimated 15 million active US retail brokerage accounts plus 5 million crypto-active users.
Example Use Case
Marcus has a $45k mixed equities and ETH portfolio, sets a 10% total drawdown alert and a 15% alert on his BTC position, and receives a Telegram message at 10:23am before he even opens his broker app — saving him from a panic-sell at the bottom.
User Stories
- ▸As a retail investor, I want to set a 10% portfolio drawdown alert, so that I get notified before a bad day turns into a catastrophic one.
- ▸As a crypto trader, I want separate thresholds for BTC and ETH, so that I can manage risk per asset without watching charts all day.
- ▸As a busy professional, I want alerts delivered to Telegram, so that I see them immediately without logging into my broker.
Done When
- ✓Portfolio connection: done when user uploads a CSV and sees their positions listed with current values on the dashboard within 30 seconds.
- ✓Alert setup: done when user sets a percentage threshold and saves it, and the rule appears in their alert list.
- ✓Alert firing: done when the cron job runs, detects a simulated breach, and the user receives a Telegram or SMS message within 5 minutes with the position breakdown named.
- ✓Alert history: done when user sees a timestamped log of every past alert trigger with the portfolio value snapshot on the dashboard.
Is it worth building?
$5/month x 400 users = $2,000 MRR. $19/month pro tier x 100 users = $1,900 MRR. Combined $3,900 MRR at month 4 is realistic given the r/investing and r/algotrading communities.
Unit Economics
CAC: $8 via r/algotrading organic posts. LTV: $108 (12 months at $9/month). Payback: 1 month. Gross margin: 90%.
Business Model
SaaS subscription
Monetization Path
Free: 1 portfolio, SMS alerts only, 10% threshold minimum. Pro $9/month: 5 portfolios, custom thresholds, Telegram plus SMS. Team $29/month: 20 portfolios, daily digest, CSV export.
Revenue Timeline
First dollar: week 2 via beta upgrade. $1k MRR: month 3. $5k MRR: month 7. $10k MRR: month 14.
Estimated Monthly Cost
Twilio SMS: $20, Vercel Cron: $20, Supabase: $25, Alpaca API: free, Stripe fees: $15. Total: ~$80/month at launch.
Profit Potential
$5k MRR viable within 6 months targeting r/algotrading and finance Twitter.
Scalability
High — add Robinhood, Interactive Brokers, and Fidelity CSV parsers, weekly digest emails, and a public leaderboard of anonymized alert patterns.
Success Metrics
Week 2: 100 signups from r/algotrading post. Month 1: 40 paid users. Month 3: 85% retention during a market volatility event.
Launch & Validation Plan
Post on r/algotrading and r/investing with a demo video of the alert firing in real time. Collect 50 email signups before writing any billing code. Ask directly: would you pay $5/month for this?
Customer Acquisition Strategy
First customer: reply to 20 r/automation threads where users describe manual portfolio monitoring and offer free beta access with a direct DM. Ongoing: r/algotrading weekly posts, finance Twitter/X, IndieHackers, ProductHunt.
What's the competition?
Competition Level
Low
Similar Products
Composer.trade for strategy automation (overkill, no simple alerts), broker native alerts (delayed, no custom thresholds), TradingView alerts (chart-based not portfolio-based). None offer multi-broker portfolio-level drawdown with Telegram.
Competitive Advantage
Cheaper than Bloomberg alerts, simpler than custom Python scripts, and actually works with both equities and crypto in one dashboard.
Regulatory Risks
Not providing financial advice — alert is informational only. Add disclaimer on all alert messages and landing page. Low regulatory risk if no trade execution is offered.
What's the roadmap?
Feature Roadmap
V1 (launch): CSV upload, Alpaca connect, threshold alerts, SMS and Telegram. V2 (month 2-3): Coinbase connect, alert digest email, multi-portfolio dashboard. V3 (month 4+): Slack alerts, anonymized community benchmarks, webhook output.
Milestone Plan
Phase 1 (Week 1-2): schema, auth, CSV parser, Alpaca fetch, cron job firing alerts locally. Phase 2 (Week 3-4): Telegram and SMS live, Stripe billing, dashboard deployed. Phase 3 (Month 2): 40 paying users, Coinbase integration, alert history UI.
How do you build it?
Tech Stack
Next.js, Alpaca API, Coinbase Advanced Trade API, Twilio SMS, Telegram Bot API, Supabase, Vercel Cron — build with Cursor for API logic, v0 for dashboard UI.
Suggested Frameworks
Supabase, Twilio, node-cron
Time to Ship
2 weeks
Required Skills
Broker API integration, Supabase cron jobs, Twilio SMS, basic Next.js.
Resources
Alpaca API docs, Coinbase Advanced Trade docs, Twilio SMS quickstart, Supabase Edge Functions docs.
MVP Scope
app/page.tsx (landing + hero), app/dashboard/page.tsx (portfolio and alert setup), app/api/connect/alpaca/route.ts (Alpaca OAuth), app/api/connect/csv/route.ts (CSV parser), app/api/cron/check-drawdown/route.ts (Vercel Cron polling job), lib/db/schema.ts (users, portfolios, positions, alerts, alert_history), lib/notify/telegram.ts (Telegram bot send), lib/notify/sms.ts (Twilio send), components/AlertBuilder.tsx (threshold UI), .env.example.
Core User Journey
Sign up -> connect Alpaca or upload CSV -> set threshold percentage -> receive first test alert in under 2 minutes -> upgrade to pro for Telegram.
Architecture Pattern
Vercel Cron fires every 5 minutes -> fetch portfolio values from Alpaca/Coinbase API or cached CSV -> compare to stored thresholds in Supabase -> if threshold breached, fire Twilio SMS and Telegram bot message -> log alert to alert_history table -> update dashboard.
Data Model
User has many Portfolios. Portfolio has many Positions. Portfolio has many AlertRules. AlertRule triggers many AlertHistory entries.
Integration Points
Alpaca API for equities data, Coinbase Advanced Trade API for crypto, Twilio for SMS, Telegram Bot API for messaging, Supabase for data and cron, Stripe for billing.
V1 Scope Boundaries
V1 excludes: trade execution, options tracking, tax lot analysis, mobile app, team sharing.
Success Definition
A paying stranger sets up a drawdown alert, the alert fires during a real market move, they DM the founder to say it saved them, and they renew the next month.
Challenges
Broker API coverage is the hard moat — Alpaca and Coinbase are easy, but Fidelity and Schwab have no public APIs, forcing CSV fallback for most users which is less real-time. Distribution reality: r/personalfinance mods ban self-promotion, so you need organic posts with value first.
Avoid These Pitfalls
Do not promise real-time sub-second alerts in v1 — 5-minute polling is honest and achievable. Do not add trade execution ever without legal review. Finding your first 10 paying customers takes longer than the build — spend week 3 on distribution, not features.
Security Requirements
Supabase Auth with Google OAuth, RLS on all user tables, encrypt broker API keys at rest in Supabase vault, rate limit cron endpoint, GDPR data deletion endpoint required for EU users.
Infrastructure Plan
Vercel for Next.js and Cron jobs, Supabase for Postgres and Auth, Cloudflare for CDN, Sentry for errors, Vercel Analytics for traffic — total under $80/month.
Performance Targets
200 DAU and 2,400 cron executions/day at launch. Cron check job under 3s per user batch. Dashboard page load under 2s. Cache position values in Supabase to avoid redundant API calls.
Go-Live Checklist
- ☐Security audit complete.
- ☐Stripe payment tested end-to-end.
- ☐Sentry error tracking live.
- ☐Vercel Cron monitoring active.
- ☐Custom domain with SSL set up.
- ☐Disclaimer and terms published.
- ☐5 beta traders signed off on alerts.
- ☐Rollback plan documented.
- ☐r/algotrading and X launch posts drafted.
First Run Experience
On first run: a demo portfolio named Sample Portfolio is pre-loaded with 5 positions and a 10% drawdown rule already set. User can immediately click Simulate Alert to trigger a fake breach and see the Telegram message format previewed on screen. No broker connection required to explore the demo.
How to build it, step by step
1. Define Supabase schema for users, portfolios, positions, alert_rules, alert_history with RLS. 2. Scaffold Next.js app with Supabase Auth Google OAuth. 3. Build CSV upload parser that maps columns to positions table. 4. Build Alpaca OAuth connection and position fetching route. 5. Build Vercel Cron job at /api/cron/check-drawdown that compares current value to stored baseline and threshold. 6. Build Twilio SMS send helper and Telegram bot send helper. 7. Build AlertBuilder component with threshold slider and asset selector using v0. 8. Build alert history dashboard showing past triggers with portfolio snapshots. 9. Add Stripe billing with free and pro tier gating on number of portfolios. 10. Deploy to Vercel, verify full journey: upload CSV, set threshold, manually trigger cron, confirm SMS and Telegram arrive.
Generated
May 27, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.