Turn a finished project into a referral

You just shipped. The client is happy, the invoice is paid, and you feel good. Then life moves on — for both of you. Three months later you need new work and that same client has half-forgotten what you built together.

The window between "project delivered" and "client mentally moves on" is short. It's also your single best chance to turn one good job into two. Here's how to do it intentionally, without being pushy or weird about it.

1. Send a proper close-out message within 48 hours

Most freelancers and small tech shops send a final file or a "let me know if you need anything" and disappear. Instead, send a short, warm close-out message that does three things:

• Restates what you built and the specific result it solves ("Your new onboarding flow is live and cuts sign-up steps from 7 to 3").
• Thanks them genuinely — one specific sentence about what made the project enjoyable.
• Opens the door: "If you know anyone else dealing with [the same problem], I'd love an intro."

That last line is easy to act on because it's specific. "Anyone dealing with clunky onboarding" is a real person your client can picture. "Anyone who needs tech work" is not.

2. Make the referral ask stupidly easy to forward

People don't refer you because they forget the right words. Give them a ready-made blurb they can copy-paste into a WhatsApp message or email. Something like:

"Hey — worked with [Your Name] on our onboarding rebuild. Came in on time, no drama. If you're dealing with something similar, worth a quick chat: [your link or email]."

Send this inside your close-out message or as a quick follow-up. When you remove the effort of composing a recommendation from scratch, the action rate goes up dramatically. Keep it under four sentences.

3. Follow up once at the 2-week mark

If you hear nothing, send one short follow-up. Not "just checking in" — that phrase does nothing. Instead, share a small relevant update or insight:

• A screenshot of a metric if you have access ("Saw your site hit a new traffic peak this week — congrats!")
• A quick tip related to what you built ("One thing worth checking once you've had a month of data is X.")
• A link to something genuinely useful in their space.

End with: "Also, if any referrals came to mind, even a casual intro works great for me." One ask per follow-up. Then stop — two touches is the limit before it becomes pressure.

4. Ask for a short testimonial at the same time

A referral and a testimonial are separate asks, but they work together. A written testimonial gives you social proof to show future clients; a referral gives you a warm lead. Ask for both in the same message so you're not pinging them twice:

"If you have two minutes, a quick sentence or two about your experience would mean a lot — and if anyone in your network comes to mind, an intro is always welcome."

Keep the testimonial ask frictionless. A Google review link, a LinkedIn recommendation request, or even just replying to your email — give them options so they can choose the path of least resistance.

5. Build a simple post-project rhythm so nothing slips

The real reason referrals don't happen is that follow-up falls off your plate when you're heads-down on the next project. Build a minimal system:

1. Day 0 — Deliver + send close-out message with referral blurb.
2. Day 14 — Send value-first follow-up with a soft referral ask.
3. Day 60 — Optional check-in to see how things are running. No ask needed; just staying present.

That's it. Three touchpoints, all short, all with a reason to exist beyond "please refer me." When you do this consistently across every finished project, referrals stop being a lucky surprise and start being a repeatable part of how you grow.

---

If keeping up with post-project follow-up sounds like one more thing you won't actually do, that's exactly the kind of task you can hand off. With Sidekyk, you can message your AI sidekick on WhatsApp right after a delivery — describe the project and the client — and it'll draft your close-out message, write the referral blurb, and schedule your follow-ups for you. You focus on the next build; your Sidekyk handles the relationship work that keeps new projects coming in.