Why 96% of Our Clients Come Back — And What That Says About How We Work

So a client asked us about it a few weeks ago, on a call, half-joking: "Is that number even real, or did someone round up?" Fair question. It's real. And once we actually sat down to figure out why it's true, the answer wasn't what we expected.

We assumed it was about the work. It's mostly not.

Our first guess was that people come back because the product turns out well. That's part of it, obviously — nobody refers an agency that shipped them something broken. But when we actually thought through our repeat clients, the pattern wasn't "the app worked great." It was closer to "they didn't disappear on me."

Idris came back for a second project after his first store launched, not because the store was flawless on day one — it wasn't, we fixed three things in the first month — but because when something broke, someone answered within the hour instead of making him open a support ticket and wait. Rebecca's team stuck with us through a dashboard build that got more complicated than anyone originally scoped, and what she's mentioned since isn't the dashboard itself, it's that she always knew where things stood.

That's the part that doesn't show up in a portfolio.

The thing we didn't expect to matter this much: we tell people no

A chunk of our return business exists because we've turned away work. Not often, but enough that it's a real pattern. If someone comes to us wanting a full e-commerce platform in three weeks with a two-person team on the other end who can't answer basic questions about their own product, we'll say so, and usually suggest they either slow down or bring someone in-house first.

That should, in theory, cost us business. Instead, most of those founders come back six months later once they actually are ready — and they bring someone else with them. We didn't plan for that to be a growth channel. It just is one.

Repeat clients don't ask us to re-earn trust every time

Here's something that only became obvious once we noticed it: our second, third, and fourth projects with a client take noticeably less time to get moving than the first one did. Not because the work is simpler. Because we've already been through the "can I actually trust these people" phase once, and it doesn't need repeating.

James's team, for example, didn't need a full requirements-gathering round for their second engagement. We already knew how they made decisions, who needed to sign off on what, roughly how fast they liked to move. That's not a technical efficiency. It's just — we'd already built the relationship, so we skipped straight to building the thing.

What this actually tells us about how we should operate

Honestly, it forced us to admit that "do good work" isn't a complete strategy on its own. Good work gets you the first project. What gets you the fifth is closer to: pick up the phone, tell the truth about timelines even when it's inconvenient, and don't pretend to be the right fit when you're not.

None of that is complicated. It's also not something you can fake for very long, which might be the actual point. A 96% repeat-and-referral rate isn't really a testament to our code quality. It's a testament to the fact that we haven't, so far, given people a reason to look elsewhere — and in an industry full of agencies that ghost clients mid-project, apparently that's rarer than it should be.

We'd like to keep that number where it is. Not by chasing it, just by continuing to answer the phone.

Curious whether we're the right fit for your project? Start a project or book a free 30-minute strategy call — we'll give you an honest answer either way.

Illustration by Rahmad Kurniawan

Illustration by Agung Prayoga