The weird moment we realized our client’s churn problem had almost nothing to do with the product
A couple years ago at Yellowchalk (UI/UX design studio), we were working with a SaaS team that genuinely had a good product.
Like… actually good.
People who understood it loved it. Retention after onboarding was solid. The founders were smart. Support was responsive. Pricing wasn’t crazy. On paper, everything looked fine.
But trial users kept disappearing.
Not dramatically. Just quietly.
Every week looked the same. New signups, decent activation numbers, then a slow leak nobody could fully explain. The founders thought competitors were undercutting them. Then they thought maybe the pricing page was weak. Then they blamed the market for a while, which honestly feels like a SaaS rite of passage at this point.
So we started sitting with real users while they used the product.
And wow.
One flow in particular was absolute carnage.
People kept clicking the same thing twice because the interface feedback was so subtle they thought nothing happened. One button looked disabled when it wasn’t. The onboarding checklist technically made sense, but mentally exhausted people by step three.
Nobody mentioned any of this in churn surveys, by the way.
They just said stuff like:
“Didn’t fully fit our workflow.”
“Trying another option.”
“Will revisit later.”
Classic polite breakup language.
The wild part is the fixes weren’t even huge. We didn’t rebuild the whole platform. We simplified navigation, changed hierarchy, rewrote microcopy, made states clearer, cleaned up onboarding.
Three weeks later, support tickets dropped hard.
That project permanently changed how I think about churn.
Sometimes users are not leaving because your product is bad.
They’re leaving because using it feels slightly harder than it should… over and over again until their brain quietly goes, nope.