ChurnLens - NLP Support Ticket Churn Predictor for SaaS Teams

Your support inbox is screaming that a customer is about to cancel — you just can't hear it yet. ChurnLens runs NLP on incoming support tickets and tags accounts with churn probability scores before they hit the cancel button.

𝕏 Post Reddit HN

Difficulty

intermediate

What is it?

SaaS customer success teams lose accounts they could have saved because churn signals are buried in support tickets, Slack messages, and NPS responses. ChurnLens ingests support ticket text via Intercom or Zendesk webhook, runs a fine-tuned DistilBERT classifier trained on churn-correlated language patterns, and posts a risk score plus suggested retention action to the CS Slack channel. The model is pre-trained on SaaS churn language patterns and fine-tuned with each team's ticket history. Priced at $79/month per workspace. Why buildable now: HuggingFace Inference API makes fine-tuned DistilBERT deployable in hours, Intercom and Zendesk both have stable webhook APIs, and the April 2026 vibe-coding wave means a solo founder can ship the whole pipeline in under 3 weeks with Cursor.

Why now?

HuggingFace Inference API dropped fine-tuned model hosting costs by 80% in late 2025, making per-workspace NLP models economically viable for indie founders for the first time.

▸Zendesk and Intercom webhook ingestion with real-time ticket scoring.
▸Pre-trained DistilBERT churn classifier with per-workspace fine-tuning on ticket history.
▸Slack alert with risk score, ticket excerpts, and suggested CS action.
▸Account-level churn risk timeline dashboard showing trend over 30 days.

Target Audience

SaaS customer success teams at 10-100 person companies — roughly 50k CS teams globally using Zendesk or Intercom.

Example Use Case

A CS manager at a 40-person SaaS gets a Slack message flagging that account Acme Corp submitted 3 tickets in 7 days with frustration language, scores 87 percent churn risk, and suggested action is a proactive call — they call, save the account, and retain $2,400 ARR.

User Stories

▸As a CS manager, I want churn risk scores on support tickets in Slack, so that I can prioritize outreach before an account cancels.
▸As a CS rep, I want to see an account's risk trend over 30 days, so that I can spot deteriorating relationships early.
▸As a SaaS founder, I want churn signals from Intercom chats, so that I catch at-risk accounts before they reach the cancel flow.

Done When

✓Webhook ingestion: done when a Zendesk ticket fires and appears in the ChurnLens dashboard within 60 seconds
✓Slack alert: done when a ticket scores above 70 percent risk and a formatted Slack message appears in the configured CS channel
✓Dashboard: done when account risk timeline shows 30 days of scores without page errors
✓Stripe billing: done when workspace admin pays $79 and scoring activates for all team members.

Is it worth building?

$79/month x 60 workspaces = $4,740 MRR at month 5. Assumes 3% conversion from cold outreach to CS leads on LinkedIn at 200 touches/week.

Unit Economics

CAC: $30 via LinkedIn DM outreach. LTV: $948 (12 months at $79/month). Payback: under 1 month. Gross margin: 80%.

Business Model

$79/month per workspace. Annual plan at $699/year.

Monetization Path

14-day free trial on first 500 tickets, Stripe upgrade triggered when trial ends, Slack integration stickiness drives retention.

Revenue Timeline

First dollar: week 4 via first paying workspace. $1k MRR: month 3. $5k MRR: month 6.

Estimated Monthly Cost

HuggingFace Inference API: $50, Supabase: $25, Vercel: $20, Stripe fees: ~$30 at early MRR. Total: ~$125/month at launch.

Profit Potential

Full-time viable at $5k-$10k MRR with 65-130 workspace customers.

Scalability

High — can add email and NPS text ingestion, multi-language models, and CRM integrations.

Success Metrics

10 pilot workspaces in month 1. 75% precision on churn flags. 80% retention at month 3.

Launch & Validation Plan

DM 30 SaaS CS managers on LinkedIn offering a free 30-day pilot — validate precision on their real ticket data before charging.

Customer Acquisition Strategy

First customer: DM 30 CS managers at Series A SaaS companies on LinkedIn with a before/after churn signal story and offer a free 30-day pilot. Ongoing: ProductHunt launch, r/CustomerSuccess, SaaStr community posts.

What's the competition?

Competition Level

Medium

What's the roadmap?

Feature Roadmap

V1 (launch): Zendesk and Intercom ingestion, DistilBERT scoring, Slack alerts, risk dashboard. V2 (month 2-3): Email ingestion, NPS text analysis, per-account risk reports. V3 (month 4+): CRM sync (HubSpot), multi-language models, API access.

Milestone Plan

Phase 1 (Week 1-2): Webhook ingestion, scoring pipeline, and Slack alerts working end-to-end. Phase 2 (Week 3): Dashboard live, Stripe billing working, 3 pilot workspaces onboarded. Phase 3 (Month 2): 15 paying workspaces, precision above 75 percent validated.

How do you build it?

Tech Stack

FastAPI, HuggingFace Transformers (DistilBERT), Supabase, Slack API, Stripe, Vercel — build with Cursor for ML pipeline and API routes

Suggested Frameworks

HuggingFace Transformers, FastAPI, LangChain for prompt layer

Time to Ship

3 weeks

Required Skills

HuggingFace fine-tuning, FastAPI, Zendesk and Intercom webhooks, Slack API.

Resources

HuggingFace DistilBERT docs, Intercom webhook guide, Zendesk webhook guide, Slack Block Kit docs.

MVP Scope

api/webhooks/zendesk.py (Zendesk webhook handler), api/webhooks/intercom.py (Intercom webhook handler), ml/classifier.py (DistilBERT inference wrapper), ml/finetune.py (per-workspace fine-tune script), api/slack_notify.py (Slack Block Kit alert builder), app/dashboard/page.tsx (risk score timeline UI), lib/db/schema.ts (Drizzle schema for tickets and scores), .env.example (required env vars)

Core User Journey

Connect Zendesk webhook -> receive first scored ticket in Slack -> view account risk timeline -> save at-risk account -> upgrade to paid.

Architecture Pattern

Zendesk webhook -> FastAPI handler -> ticket text queued -> DistilBERT inference -> score stored in Supabase -> threshold breached -> Slack alert fired -> dashboard reads score history.

Data Model

Workspace has many Accounts. Account has many Tickets. Ticket has one ChurnScore. Workspace has one SlackConfig. ChurnScore has one RetentionSuggestion.

Integration Points

Zendesk Webhooks for ticket ingestion, Intercom Webhooks for chat ingestion, HuggingFace Inference API for DistilBERT scoring, Slack API for alerts, Stripe for billing, Supabase for data.

V1 Scope Boundaries

V1 excludes: email ingestion, NPS text analysis, CRM sync, multi-language support, mobile app.

Success Definition

A CS manager at a company the founder has never spoken to receives a churn alert, acts on it, saves an account, and renews ChurnLens for month two.

Challenges

False positive rates will erode CS team trust fast — the model must hit above 75% precision before teams act on alerts, which requires good training data from the customer.

Avoid These Pitfalls

Do not launch without a precision baseline — CS teams will ignore alerts after 3 false positives. Do not let fine-tuning require manual ML work from the customer. Finding the first 10 paying workspaces will take 3x longer than building — budget distribution time accordingly.

Security Requirements

Supabase Auth with Google OAuth, RLS on all workspace-scoped tables, Zendesk webhook HMAC validation, all ticket text encrypted at rest, GDPR data deletion endpoint required.

Infrastructure Plan

FastAPI on Fly.io for ML inference layer, Next.js on Vercel for dashboard, Supabase for Postgres and auth, HuggingFace Inference API for model hosting, Sentry for error tracking — total ~$125/month at launch.

Performance Targets

Ticket scoring under 2 seconds end-to-end, Slack alert under 5 seconds from webhook receipt, dashboard loads under 1.5s, handles 1,000 tickets/day at launch.

Go-Live Checklist

☐Security audit complete
☐Stripe billing tested end-to-end
☐Sentry error tracking live
☐Fly.io uptime monitoring configured
☐Custom domain with SSL set up
☐Privacy policy and DPA published
☐3 beta CS teams signed off
☐Rollback plan documented
☐LinkedIn outreach sequence and ProductHunt post drafted.

First Run Experience

On first run: 5 pre-seeded demo tickets from a fictional SaaS account with varying churn scores are visible in the dashboard. User can immediately see a Slack alert preview and the risk timeline without connecting Zendesk. No manual config required: demo mode runs on seeded data with no webhook setup needed.

How to build it, step by step

1. Define Supabase schema for Workspace, Account, Ticket, and ChurnScore tables. 2. Build Zendesk webhook handler in FastAPI that validates HMAC and stores raw ticket text. 3. Build DistilBERT inference wrapper using HuggingFace Inference API with churn probability output. 4. Build Slack Block Kit alert formatter with risk score, ticket excerpt, and suggested action. 5. Build per-workspace fine-tune script that batches historical tickets and pushes to HuggingFace. 6. Build Next.js dashboard showing 30-day churn risk timeline per account. 7. Add Stripe Checkout for $79/month workspace subscription with webhook to activate. 8. Build Intercom webhook handler mirroring Zendesk handler. 9. Write 14-day trial logic that gates scoring after 500 tickets without payment. 10. Verify: send a test Zendesk webhook with frustration-language ticket, confirm Slack alert fires with correct risk score and account name.

Generated

April 20, 2026

Model

claude-sonnet-4-6

← Previous

CodeRef - Live GitHub Snippet Sync Plugin for Obsidian

FrameCheck - Computer Vision UI Regression Detector for Frontend Teams

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.