Start with a reason to reconnect
A past client already knows what it is like to work with you, but that does not mean they need the same service again. Their priorities, team, budget, or way of working may have changed. Reconnecting gives you a chance to understand those changes before deciding whether you can help.
Choose a small group of people with whom you had a constructive working relationship. Look back at what you delivered, the goals they described, and any loose ends they mentioned when the project ended. This preparation helps you write a relevant message rather than sending the same offer to everyone. Respect any preference they have expressed about future contact, and avoid reaching out solely because you want to fill an empty calendar.
Send a brief, low-pressure message
A useful message reminds the client of your shared work, gives a genuine reason for getting in touch, and leaves room for them to decline. For example: “I was thinking about the handoff process we worked on together and wondered how it is working for your team now. If you have time for a short catch-up, I would be interested to hear what has changed.” Adapt the wording to the relationship and the time that has passed.
Do not disguise a sales pitch as a request for feedback. If you hope to discuss possible work, be comfortable saying so when it becomes relevant. You can also make it easy to reply by offering an email exchange instead of a meeting. If there is no response, one polite follow-up may be reasonable; after that, leave the decision with them.
Ask what has changed before suggesting a solution
In a conversation, begin with the client’s situation rather than your list of services. Ask which parts of the earlier work remain useful, what has become harder, and what the team handles differently now. If they mention a challenge, ask for a recent example. Concrete examples can reveal whether the issue is occasional, ongoing, or already being addressed.
Listen for constraints as well as problems. A client may have a need but no time to start a project, or they may prefer to solve it internally. Avoid treating every frustration as an invitation to propose work. It is often more helpful to clarify what outcome matters to them, who would be involved, and whether they want outside support at all.
Keep a record without overinterpreting it
After each exchange, note the client’s stated priorities, relevant changes, and any next step you agreed on. Separate what they actually said from your interpretation. “The team now reviews requests weekly” is an observation; “they need a new intake system” is a hypothesis that would require more discussion.
Over several conversations, look for recurring needs, but do not assume that a handful of similar comments represents every client. Differences matter too: one client may need clearer documentation, while another has the documentation but struggles to use it. Keep notes limited to information you need for the relationship, and handle anything sensitive with care.
Offer a next step only when it fits
If a client describes a problem you can help solve and seems open to discussing it, propose a modest next step. That might be a separate scoping call, a review of the current process, or a short outline of possible approaches. Explain what the next step would clarify rather than promising a result before you understand the work.
Sometimes the best outcome is simply an updated understanding of the client’s situation. Thank them for the conversation, follow through on anything you promised, and avoid repeatedly checking in without a useful reason. Thoughtful reconnection is not about turning every former client into a new project. It is about maintaining a respectful relationship and recognizing a genuine fit when one appears.
