Skip to contentjump to list
Back to Field Guide

How we discover customers about to churn

Brian Lovin

Brian Lovin

Co-founder

We’re always trying to make Campsite better for teams, but we know it won’t stick for everyone. When that happens and a customer churns, we need to understand what happened — are there major workflow issues we need to fix? Was there an annoying bug we didn’t know about? Did they switch to a different tool for a specific task or feature?

But it’s better to catch people before they completely churn, not after. If we notice someone who was recently-active, but hasn’t used Campsite for a few days, we do our best to reach out early to get fresh feedback, answer questions, and hopefully solve problems that might keep them around.

I also believe it’s important that everyone on our team knows when customers are about to churn. Developing shared context helps us to spot trends, make more informed product decisions, and keep the health of our business top-of-mind.

We’ve built a simple system using Retool, Zapier, and Campsite posts to alert us when customers are about to churn and create visibility for everyone on our team.

Here’s how it works:

  1. Every morning at 8, we run a check that looks for teams:
  • With more than one member
  • Where the admin uses a work email (not Gmail, iCloud, or Outlook)
  • Who have used Campsite in the last month
  • But haven’t created anything (post, doc, call, or chat) in the last four days (to account for long weekends)

We include both paying customers and new teams who are still on their 30-day trial. Combined, this criteria keeps our alerts high-signal by only showing organizations that we have a good chance of learning from.

A screenshot of a Retool workflow showing how we find organizations that are about to churn

If a team meets all these criteria, we move to the next step.

  1. For each of these teams, we create a post in a “Churning orgs” channel with:
  • The admin’s email and job title (if they shared it during onboarding)
  • How big their company is and how many are using Campsite
  • What plan they’re on, and how many seats they’re paying for
  • A link to our Retool dashboard to see usage over the last month

This post gives us enough insight into how they’ve used Campsite in the past so we can decide if it's appropriate to send them an email.

A screenshot of a sample posts in Campsite showing orgs about to churn

Triagining these about-to-churn organizations is now part of my morning ritual.

And because these posts live on Campsite, I can have an async conversation with my team to ask questions, gather context on previous interactions with the customer, and report back with the customer’s feedback. These conversations are easy to search for later as we look for patterns and prioritize our roadmap.

We’ll keep iterating on this workflow over time as we learn — if you have ideas or feedback, I’d love to hear from you.

You can create a workflow like this for yourself with our Zapier integration.

Published August 20, 2024

More writing

How we made a Ruby method 200x faster

Nov 12, 2024

How we prototype API integrations with Val Town

Oct 30, 2024

Class methods are Ruby’s useEffect

Oct 17, 2024

Realizing the dream of good workplace software

Oct 10, 2024

How we use channels to keep our conversations organized

Sep 3, 2024

Desktop App Icon

Teamwork, meet deep work.

Try Campsite today with a free 14-day trial. No credit card required.