I Chose Retention Over Acquisition at Finvestfx. It Cost Us 6 Months of Growth.

The setup: we were growing, but nobody was staying

When I started managing Finvestfx's forex and treasury SaaS, we had about 15 enterprise clients. The sales team was pushing hard to get us to 30 by year-end. But here's what nobody was talking about: our existing clients were logging in maybe twice a month. Some hadn't touched the platform in weeks.

I had a choice. Double down on acquisition and hit that 30-client target, or pause new features, fix the core product, and make sure people actually wanted to use what we'd built.

I chose retention. I still think about whether that was right.

What building for retention actually looked like

Retention work is invisible. That's the first thing I learned.

When you're building for acquisition, you get to launch shiny new features. You get demo content. Sales loves you. Founders can tweet about it. But when you're fixing retention, you're often just making existing stuff less annoying.

At Finvestfx, I spent three months on stuff that didn't look like features at all. We rebuilt the onboarding flow because new treasury managers were getting lost after login. We added email digests so people remembered the platform existed. We fixed a bug where reconciliation reports would sometimes fail to generate, and users would just give up and use Excel instead.

None of this was exciting. But our DAU/MAU ratio went from 0.18 to 0.34 in four months. Clients who were about to churn started reaching out to ask about advanced features.

The problem? We didn't sign a single new client during that period. Sales kept asking when the new integrations would be ready. I kept saying "soon" and knowing it wasn't true.

Acquisition is a different game entirely

At Sonic Linker, I saw the opposite play out. We were a founding team building an AI SaaS platform from scratch. We had three months to ship a core product and get our first paying users. Retention didn't matter yet because we had nobody to retain.

Every decision was about speed and surface area. Can we ship this integration in a week? Will it look good in a demo? Does it solve a problem for at least five potential customers?

We cut corners everywhere. Our onboarding was basically a Loom video. Our dashboard had maybe four metrics. But we shipped in three months, got users in the door, and then started learning what they actually needed.

That's when I realized: acquisition and retention aren't just different strategies. They're different mental models.

Building for acquisition means you're optimizing for first impressions. You need hooks, clear value props, and something that looks credible in a sales call. You're trying to convince someone to take a chance on you.

Building for retention means you're optimizing for the tenth login. You need depth, reliability, and workflow integration. You're trying to make someone choose your product over the muscle memory of whatever they were using before.

The real question isn't which one to choose

Here's what I got wrong at Finvestfx: I treated retention and acquisition like a binary choice.

The actual question was: what's our biggest constraint right now?

If you have 50 clients and 10 of them are about to churn, fixing retention is existential. If you have 5 clients and they're all happy but you need 20 to hit your next funding milestone, acquisition is existential.

At Finvestfx, we had 20+ clients and decent retention when I started. The real constraint was that we'd plateaued. We needed new client segments, which meant new acquisition hooks. I should have split my time 70-30 instead of going all-in on retention.

At Sonic Linker, we had nobody. Spending a month perfecting onboarding before we had users would have been insane.

What I do now

I don't think in terms of retention vs acquisition anymore. I think in terms of what's leaking the most value right now.

If people are signing up but not activating, that's a retention problem disguised as an acquisition problem. If people love the product but nobody's hearing about it, that's an acquisition problem that retention can't fix.

At NJ Group, when I was coaching 60 insurance advisors and IFAs on product adoption, the biggest issue wasn't that the products were bad. It was that advisors would try them once, get confused, and go back to their old process. That's a classic retention problem, but it killed acquisition because nobody would refer new advisors to something they'd already given up on.

The fix wasn't more features. It was just making the first experience less overwhelming.

The takeaway

If I could go back to that moment at Finvestfx, I'd still focus on retention. But I'd carve out 30% of my time for small acquisition bets. Maybe one new integration. Maybe a better demo environment for sales.

Because here's the thing: retention and acquisition aren't opposing forces. They're two sides of the same loop. You need both. The only question is which one is your bottleneck today.