--- title: "Win back lapsed clients when they start hiring again | FirstSales" description: "Reconnect with past clients who stopped sending requisitions, timed to a new hiring spike signal at their company that's easy to verify." canonical: "https://firstsales.io/tutorial/playbook-recruiting-lapsed-client-reactivation/" --- [Home](/)/ [Tutorials](/tutorial/) # Win back lapsed clients when they start hiring again Reconnect with past clients who stopped sending requisitions, timed to a new hiring spike signal at their company that's easy to verify. Tutorials Playbooks min read 17 min steps 8 · Beginner 8 steps [01Define the lapsed-client ICP](#step-1)[02Bring in your lapsed-client list and enrich it](#step-2)[03Use research to confirm and describe the hiring spike](#step-3)[04Set up the reactivation campaign: Describe, Teach, Practice](#step-4)[05Teach a warm, familiar writing style](#step-5)[06Keep the sequence short given the existing relationship](#step-6)[07Handle replies with the relationship history in mind](#step-7)[08Expect relationship-boosted results within the standard band](#step-8) [All tutorials](/tutorial/) 1. ## 01 Define the lapsed-client ICP This play targets a specific, valuable list: companies you have placed candidates for before, who then went quiet, no new reqs sent in months, but who are now showing signs of hiring again. This is a warmer audience than pure cold outreach, since there is an existing relationship and, ideally, a track record of a successful placement to reference. Build the ICP around your own client history plus a trigger: a new hiring spike. That might mean multiple new job postings appearing at once, a funding announcement, a leadership change in a department you previously staffed for, or public news about expansion. The trigger is what separates a well-timed reactivation from a generic "just checking in" email that gets ignored. ![Define the lapsed-client ICP](/tutorials/app/contacts.webp) 2. ## 02 Bring in your lapsed-client list and enrich it This list starts as a CSV import from your own CRM or past client records, since it is your relationship history, not something AI Leads discovers cold. Import the contacts, then let FirstSales enrich company and role details so the outreach reflects their current situation, not the one from when you last worked together. If a past champion has left the company, AI Leads or enrichment can help you find their successor in the same function, so you are reaching out to the right current decision maker rather than someone who moved on. 3. ## 03 Use research to confirm and describe the hiring spike Automatic prospect research runs on each contact before drafting, and the transparency view shows what it found and what got used, company facts, role, and signals. For this play, that research is the whole point: it should surface the growth or hiring signal that justifies reaching back out now. Check the transparency view before launching. If the research is not consistently finding a real hiring signal for your list, narrow the list to companies where you can independently confirm the spike (new postings you have seen, funding news, a headcount announcement), since a reactivation email with no real hook reads exactly like the generic check-in it is trying to avoid being. Cross-reference the signal against what you already know about the account from your own history. If a former client paused hiring because of a budget freeze, a single new job posting might be a false start rather than a real spike, worth a lighter-touch note rather than a full reactivation push. If they paused simply because the last role they were filling got done in-house, a fresh posting is a much stronger, more reliable signal to act on. 4. ## 04 Set up the reactivation campaign: Describe, Teach, Practice Create the campaign with a get-a-reply or book-a-meeting goal. In Describe, be explicit about the relationship: this is a past client, you placed \[type of role\] for them before, and you noticed they are hiring again. In Teach, give the AI the tone of a genuine reconnection rather than a cold pitch, reference the shared history plainly instead of re-explaining who you are and what you do from scratch. In Practice, review the sample drafts for one failure mode specifically: does the email sound like it knows this is a former client, or does it read like it was sent to a stranger? If it reads generic, the campaign needs more relationship context fed into Describe and Teach. A first-touch draft built on that framing looks like the example below. > Subject: saw you're hiring again > > Hi \[First name\], > > Noticed \[Company\] has a few new \[role type\] postings up, looks like the team's growing again. We placed \[past role/context\] with you back in \[timeframe\], and would love to help again if the timing's right. > > Worth a quick call to catch up on what you're looking for this time around? > > \[Your name\] Keep the reconnection line specific to the actual past engagement rather than a vague nod to history. Precision is what separates a reactivation email from a form letter a former client can tell was sent to everyone in your CRM. ![Set up the reactivation campaign: Describe, Teach, Practice](/tutorials/app/kb.webp) 5. ## 05 Teach a warm, familiar writing style Paste in past emails you actually sent to this client, or write samples in the tone of someone reconnecting with a known contact: warmer and more direct than cold outreach, comfortable referencing the earlier relationship without over-explaining it. "Saw you're hiring again for the team we helped build out last year" does more work than a full reintroduction of your agency. If you are reactivating clients across different past specialties (engineering here, finance there), teach the style once at a relationship level and let each campaign's Describe step carry the specific placement history. 6. ## 06 Keep the sequence short given the existing relationship Two steps is typically enough. The first email reconnects and references the hiring signal directly. If there is no reply, one follow-up a few days later, brief, low-pressure, and offering to pick up wherever things left off, is enough. A past client does not need to be persuaded that you exist or that you do good work, they need a reason and a clear, easy next step. Sequence steps stop automatically on reply, which matters here since a past client might reply with something informal, like a quick "yes, let's talk," that should end the automated sequence immediately. If a former champion has moved to a new company entirely, this same reactivation approach works there too, since the relationship travels with the person even when the account does not. Track those moves separately from the standard lapsed-account list, since the pitch shifts slightly: you are following the person rather than watching for a signal at their old employer. ![Keep the sequence short given the existing relationship](/tutorials/app/c-steps.webp) 7. ## 07 Handle replies with the relationship history in mind AI reply handling reads the actual message and responds to what was asked, useful when a lapsed client asks something specific like current fee structure or turnaround time. Route anything that references the specific outcome of your last engagement, a complaint, a compliment, a request to revisit terms, straight to a human, since those conversations carry relationship weight that benefits from a personal reply. Bounce handling auto-suppresses any contacts who have moved on, which naturally cleans your client list over time as you run this play periodically. 8. ## 08 Expect relationship-boosted results within the standard band Reactivation to a past client with a real hiring-spike trigger tends to perform at or above the standard B2B range, roughly 2 to 5 percent reply and 0.5 to 1.5 percent meetings, tracked per campaign in FirstSales analytics, since the existing relationship and trust lower the barrier to a reply compared to fully cold outreach. If results land below that range, check two things first: whether the hiring-spike signal is real and specific enough to justify the timing, and whether the email actually reads as a reconnection rather than a repackaged cold template. Segment your results by how long the client had been lapsed before you reached back out. Clients who went quiet for a few months typically respond differently than clients who went quiet for a couple of years, the latter group may need a bit more context reestablishing who you are, since the relationship has faded more. Adjust the Describe step per segment rather than running one script across a mixed list. Keep a simple log of why each client originally went quiet, if you know it, budget freeze, dissatisfaction, or just a lull in hiring. Over several reactivation waves, that log becomes useful for deciding which lapsed clients to prioritize first the next time a hiring-spike signal appears across your list. ![Expect relationship-boosted results within the standard band](/tutorials/app/c-analytics.webp) ## Pro tips * 01 ### Reference the actual placement, not the relationship in general "The engineer we placed with you last spring" is more credible and specific than "we've worked together before," and it proves you remember the engagement. * 02 ### Reactivate in waves tied to real signals Run this campaign periodically against your CRM rather than once, timing each wave to fresh hiring-spike signals instead of blasting the full lapsed list on a fixed schedule. * 03 ### Address the reason they went quiet if you know it If a client paused for a known reason (budget freeze, a bad hire, a leadership change), a brief, honest acknowledgment before the pitch builds more trust than ignoring it. ## Frequently asked questions What counts as a hiring spike signal worth acting on? Multiple new job postings appearing at once, funding news, expansion announcements, or a headcount increase in a department you previously staffed for. What if my old contact has left the company? Use AI Leads or enrichment to find their successor in the same function, then reference the prior engagement by team or role rather than by the departed contact's name. How is this different from cold client BD outreach? You have an existing relationship and placement history to reference, which changes both the tone (warmer, more direct) and typically improves reply rates versus fully cold outreach. Should I mention why the client stopped sending reqs? Only if you know the reason and it is safe to reference. A brief, honest acknowledgment can build trust, but do not guess at a reason you are not sure of. ## Playbooks * [└ Pitch retainer contracts to in-house marketing teams 20 min ](/tutorial/playbook-agency-retainer-pitch/) * [└ Open cold outreach with a free channel audit 18 min ](/tutorial/playbook-agency-audit-opener/) * [└ Build white-label partnerships with other agencies 22 min ](/tutorial/playbook-agency-whitelabel-partnerships/) * [└ Win back churned clients after a results dip or team change 19 min ](/tutorial/playbook-agency-churned-client-winback/) ## Outreach that keeps going after you log off. Leads, emails, follow-ups and replies, handled. Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo. [Start your $1 trial T](https://app.firstsales.io)[See pricing](/pricing/) $1 for 3 days · Cancel anytime · No contract ## Install with AI Your coding agent sets up the FirstSales CLI and skills for you. Prompt for Claude Code I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code. Read these first so you know how FirstSales works: - Developer docs and API: https://developer.firstsales.io - CLI: https://www.npmjs.com/package/@firstsales.io/cli - Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md) Setup 1. Install the CLI: npm install -g @firstsales.io/cli 2. Install the FirstSales skills: claude plugin marketplace add firstsalesio/firstsales-skills claude plugin install firstsales@firstsales 3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up. 4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need. Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden: read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY 5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to. Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through: 1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product. 2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add. 3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own). 4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes. 5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads. 6. Inviting my team and giving each person the right access. Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email). Throughout, as you learn about my business, proactively suggest and help create: - Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them. - Campaign ideas and segments worth testing, with the reason for each. Safety rules: - Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes. - Tell me before anything that spends credits, and how many. Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options. [Developer docs ↗](https://developer.firstsales.io)[npm: @firstsales.io/cli ↗](https://www.npmjs.com/package/@firstsales.io/cli)[GitHub: firstsales-skills ↗](https://github.com/firstsalesio/firstsales-skills)