When a project ends, your reputation begins—here's how to end on purpose.
Most people lose repeat work because they end projects passively.
If you want the next project to come from the last one, the last 2 weeks matter most.
When a project ends, most people treat it like the end.
You deliver the work.
Finish the calls.
Send the invoice.
Move on.
Then a few weeks later you’re asking:
“Where is the next one coming from?”
I was on a call with a researcher who had a strong year.
She hit her number.
Did better than last year.
Felt proud of the work.
And then she said something I hear all the time:
“I pulled it off. But I don’t know if I could do it again.”
Not because she doubts her ability.
Because every project felt like a sprint.
Finish one. Recover. Start over.
So we didn’t talk about confidence or motivation.
We talked about what happens after a project ends.
At one point she said:
“The most concrete thing I can do this week is ask for referrals or talk about what comes next.”
That was the real issue.
The last few weeks of a project matter more than people think.
The work has landed.
The outcome is visible.
You’re still top of mind.
Once a project ends, attention shifts fast. New priorities, new fires, new people.
So the move isn’t to sell harder later.
It’s to end the project on purpose.
Here are five moves that turn a good project into more work without feeling weird about it.
The best time to ask is when the result is visible and you’re still top of mind.
Most people avoid this because it feels awkward. That’s not the real problem.
The real problem is timing.
People rarely refer once a project is over because they’ve already moved on.
So ask while the result is still concrete.
Be direct and specific.
Try one of these:
“Who else on your team is dealing with the same thing?”
“Do you know anyone at another company running into this?”
“If someone asked what I helped with, how would you explain it?”
If they hesitate, it’s usually because they’re searching for language.
So help them.
Offer to draft the testimonial.
Offer to write the intro email.
Send a few options and tell them to change anything.
You’re not pushing. You’re removing friction at the moment trust is highest.
After a project, most clients default to an all or nothing choice.
Either keep going at the same pace or stop completely.
That’s a false choice.
Instead, name a softer landing.
“We don’t need the same pace anymore. But it makes sense to stay connected while you hire or things settle.”
Lower cadence.
Smaller scope.
Clear boundaries.
A small monthly retainer does one thing well. It keeps trust active.
Be explicit about what it covers, what it doesn’t, and when it should end.
Growth doesn’t have to mean doing it all or becoming an agency.
There’s a middle ground:
“I’ll stay involved on direction and decisions. I’ll bring in someone I trust for execution. You still work with me. I’m responsible for the result.”
They don’t want to manage another person. They want things to work.
This lets you protect your role without carrying every task.
Slides came up in this conversation.
Two full days building decks for a workshop. She hated it.
That’s usually a signal.
If you’re being hired for judgment, thinking, and facilitation, a lot of polish work shows up to make you feel like you’re earning your keep.
Same with overbuilt proposals.
Same with endless custom touches.
A simple check helps:
If it clearly helps the client or saves time, do it.
If it mostly helps you feel safer, stop.
Resentment usually means the role has drifted and expectations need to be reset.
Sometimes the right next step really is a full time hire.
If that’s the case, don’t disappear and don’t get defensive.
Help them.
Offer to write the job description.
Review early candidates.
Sit in on final interviews.
You understand the role better than a recruiter does because you’ve been doing the job.
When you help them hire well, two things happen:
You leave on a high note.
And the new hire sees you as someone who made their life easier, not someone they replaced.
That’s usually who calls when they’re overloaded or something breaks.
Before you close the loop, do this:
Share a short recap of what changed and why it mattered
Ask for 1 intro while results are fresh
Propose a lighter ongoing cadence (with a clear end date)
Confirm what happens next and who owns it
One good year doesn’t mean much on its own.
What matters is whether the next one feels more stable.
Pipelines are shaped at the end of projects more than the beginning.
That comes from ending work deliberately instead of letting it fade.
Most people don’t need to change what they do.
They just need to stop treating the ending like an afterthought.
If you want, reply with what you do when a project ends. I’ll send a couple tight templates for the referral ask and the “lighter retainer” offer.
Thanks for reading,
Gev