Stop silent churn before it drains your MRR

Know who's about to leave. Hear why when they cancel.

Most tools tell you churn happened. Flidget tells you it's coming, and captures the real reason when it does.

1Drift flags who's slipping, days before cancel
2Chat captures the real reason at cancel
3One dashboard shows both. Act from one place.
One npm install, then you're live in your app
npm install @flidget/web-sdk

Add your public key and call Flidget.init once. Drift signals and exit capture start from there.

14-day free trial · Live in 10 minutes · Works with your stack

Trusted by 16+ SaaS founders to stop silent churn · Works with any cancel flow · voice or text replies · no redirects

Retention Copilot

The moment they click cancel, you stop guessing.

One script tag on your cancel page. That's it. A short chat opens right there. No redirects, no forms. Users speak or type for 10 seconds. The real reason lands in your dashboard, tagged and ready to act on.

Drift detection

Know who's about to churn, before they've decided.

Not a score you have to decode. Plain-language signals tell your team exactly what's wrong and what to do before it's too late.

Healthy0 to 29% risk
22%Low churn risk

Sessions and milestones look healthy

Recent activity and your configured key features line up. Nothing urgent here—let your team focus on accounts that are actually cooling off.

last active 2 days ago · reached invite_teammate · session depth steady vs prior month
Risky30 to 60% risk
48%Churn risk rising

Engagement slipping—act before the next cycle

Patterns here often show up on accounts that churn next renewal if nobody intervenes. Still saveable: a timely nudge or rescue email usually lands better than waiting for cancel.

last active 5 days ago · fewer sessions vs prior month · good window for a personal touch
Drifting60%+ risk
74%Churn risk high

High churn risk—reach out today

Long idle without your milestone usually means they have already disengaged. If you wait, the next signal is often silence—or a cancel click with almost no context.

9+ days inactive · never reached invite_teammate · above the drifting cutoff you configured

Rescue email

Reach the right user before they've made up their mind.

When a user drifts, Flidget can trigger rescue email from your domain, in your voice, with templates you control.

  • Every user gets a drift score: Healthy, Risky, or Drifting
  • Email fires when risk crosses your configured threshold
  • Sent from your domain with templates you fully edit
  • Or send manually from the user profile in one click
Inbox previewDefault template

From: updates@yourdomain.com

Quick check-in from our team

Hi Alex, hope you are doing well. Quick check in from our side. If it helps, I can send a short walkthrough based on how your team uses the product. Best, your team

Sent automatically · Drift score 74%

Same starter copy as the dashboard default. Great fallback when no tighter rule wins.

Inbox previewPersonal outreach

From: updates@yourdomain.com

Can we help you get unstuck?

Hi Alex, our system flagged your account as higher risk this week. If something broke or priorities changed, reply with one honest line. A human reads every note. Say pause if we should stop.

Sent automatically · Drift score 48%

Map this template to offer_personal_outreach so auto email can send it for high risk outreach.

Inbox previewOnboarding follow-up

From: updates@yourdomain.com

Finish setup when you have five minutes

Hi Alex, onboarding still has a few open steps. This link picks up where you left off. Reply setup if you want a live walkthrough and we will book a short call.

Sent automatically · Drift score 22%

Map this template to send_onboarding_email so auto email can follow up after onboarding nudges.

After you sign in: Settings, Drift configuration, then Email and templates.

Customer story

A $49 desktop trial can die quietly. psyXe catches drift before day 14.

psyXe ProFlidget

macOS · Rust + Tauri · 14-day trial

psyXe Pro is a private macOS AI agent with no cloud analytics. Bart could not see who was still in the 14-day trial, who opened it once, or who was about to delete it. In v0.2.0, Flidget links first-launch email to three in-app events and scores every founding member Healthy, Risky, or Drifting before the $49 perpetual license decision.

Each rescued trial protects a $49 seat instead of a silent uninstall. Across the first 100 founding members, that is $4.9k of license value Bart can defend while the trial is still live.

“I want to catch drift before the trial ends — whether they barely use it or use it a lot and still do not buy.”

BJ

Bart Jenkins

Founder, psyXe Pro

100

founding trials tracked

$49

value per saved seat

$4.9k

cohort at stake

Tracked events

app_launchedquery_issuedsettings_configured
Start free for desktop apps
How it works

How the two modules work together

Add Flidget once, catch exits with the leaving widget, score users with drift detection, and see everything in a single dashboard.

  1. Add Flidget to your site

    Paste one script tag on your cancel or billing page for Retention Copilot. If you want Drift, send one event whenever a user does an important action.

  2. Retention Copilot catches users at the exit

    Anyone who clicks cancel, abandons checkout, or tries to close sees a short, friendly chat. They reply in text or voice. Your existing flow continues after.

  3. Drift engine scores users daily

    Behind the scenes, Flidget looks at sessions, last active date, and whether users reached your key feature. Each user gets a Healthy / Risky / Drifting label.

  4. Act with the full picture

    Retention Copilot reasons, drift scores, and user-level details all live in one dashboard. Filter, read, decide. No spreadsheets, no raw event logs.

Questions founders ask

Straight answers about the leaving widget, drift detection, and pricing.

What does Flidget actually do?

Two things. First, Retention Copilot. When someone tries to cancel or leave your site, a short chat appears and asks why. Second, drift detection. Flidget watches how users interact with your product and labels each one Healthy, Risky, or Drifting with clear reasons, so you know who needs attention before they reach the cancel page.

Is the leaving widget only for SaaS cancellations?

No. It works anywhere someone can leave: subscription cancel/downgrade, checkout abandonment, membership pause, trial exit, or just closing the page. Any frontend stack is supported.

How does drift detection work? Do I need to set up anything complex?

No. You choose which user actions matter (for example invite_teammate or complete_onboarding) in the dashboard, then send a short event from your app each time one happens. Flidget handles the scoring. The dashboard shows you who is Healthy, Risky, or Drifting with a clear reason, not just a number.

Will the leaving widget annoy my users?

It’s lightweight by design: short prompts, an optional skip, and it stays on your page without any redirects. You control where it appears, when it triggers, and how the copy is worded.

Do I need to email users after they leave?

Not necessarily. Flidget captures the reason at the exact moment someone decides to leave, when they are most willing to explain. That context is already in your dashboard. You can email if you want to, but you are not chasing replies to a survey sent hours later.

How long does it take to go live?

The leaving widget is a single script tag, so most teams are live in under an hour. Drift detection requires sending events from your app, which is one API call per action. Start on staging, verify the dashboard is receiving data, then ship.

Your next user is about to cancel without a word. Flidget changes that.

14-day free trial. Live in 10 minutes. No credit card. No complex setup.