I Watched Churn Drop 40% When I Stopped Calling It a 'Retention Problem'

When I joined Finvestfx, the churn numbers looked brutal. We were losing 2-3 enterprise clients every quarter, and every exit interview said the same thing: "Great product, just not what we needed right now."

I did what any PM would do. I built retention features. We added better onboarding flows, sent engagement emails, built a reporting dashboard they could show their CFOs. Churn barely moved.

Then one day, our sales lead said something that broke my brain: "We're selling to anyone with a treasury department. Half these companies don't even do forex regularly."

That's when it clicked. We didn't have a retention problem. We had an acquisition problem that was killing retention.

The Real Difference Isn't Features, It's Who You Let In

Most PMs think retention is about what happens after signup. Better onboarding, more engagement loops, clearer value delivery. All true, but it misses the point.

Retention starts at acquisition. If you're letting the wrong users in, no amount of onboarding wizardry will save you.

At Finvestfx, we were acquiring companies that had maybe 5-10 forex transactions a year. Our product was built for companies doing 50+ transactions monthly. Of course they churned. They signed up because the sales pitch was good, but the product-market fit was never there.

I pushed hard to change our ICP (ideal customer profile). We stopped going after companies with small treasury teams. We started qualifying leads based on transaction volume, not just company size. Our acquisition rate dropped by 30%. But churn dropped by 40%.

That trade-off was worth it. Revenue stayed flat for two quarters, then started climbing because our retained clients were expanding usage.

Building for Retention Means Saying No Earlier

At Sonic Linker, we had the opposite problem. We were a founding team, and we wanted traction fast. So we said yes to almost every early customer request.

One agency wanted custom white-labeling. Another wanted API access before we even had stable endpoints. We built both. They stuck around for 3-4 months, then left because the core product still wasn't solving their base problem well enough.

I learned this the hard way: retention features only work if your core loop is solid. If someone is using your product weekly and getting consistent value, then yes, build the dashboard, add the Slack integration, improve the export flow. But if they're barely logging in, those features are just decorations on a house with no foundation.

Building for retention means doubling down on the core job-to-be-done before you optimize the peripherals. At Sonic Linker, we eventually cut two entire feature branches and focused entirely on link tracking accuracy and speed. Boring, but it's what users actually came back for.

Acquisition Features Look Impressive. Retention Features Look Boring.

Here's the uncomfortable truth: acquisition features get you demos. Retention features get you renewals.

Acquisition features are flashy. AI-powered insights. Beautiful dashboards. Integrations with every tool under the sun. They look great in a deck. They close deals.

Retention features are invisible. Faster load times. Better error handling. Small UX tweaks that remove friction. They don't win awards, but they're why people keep paying you.

At NJ Group, I coached 60+ insurance advisors and IFAs on adopting new product platforms. The platforms that had the best retention weren't the ones with the most features. They were the ones that made the daily workflow 10% faster. Bulk policy uploads instead of one-by-one entry. Auto-saved drafts so they never lost work. Small stuff that added up.

I see a lot of early-stage PMs (including past me) chase the shiny acquisition features because they want to feel like they're moving fast. But retention compounds. Acquisition is linear. You can't scale a leaky bucket.

What I Actually Do Differently Now

When I'm planning a quarter, I split my roadmap into two columns: "Gets people in the door" and "Keeps people coming back." I force myself to look at the ratio.

If I'm spending 80% of eng time on acquisition features, I know I'm setting up future churn. If I'm spending 80% on retention and growth has stalled, I know I need to rethink my top-of-funnel.

There's no perfect ratio, but I try to keep it 60-40 (retention to acquisition) once you have product-market fit. Before that, it's more like 80-20 toward retention because if your core loop doesn't work, nothing else matters.

The Real Unlock

The biggest shift for me was realizing that retention and acquisition aren't separate problems. They're the same problem with different time horizons.

Every acquisition decision is a retention bet. Every retention feature is a signal about who you're actually built for.

When churn dropped at Finvestfx, it wasn't because we built better retention features. It's because we stopped acquiring the wrong customers in the first place. That's the difference.