How to reach old leads after a product pivot
Re-engage old B2B leads after a product pivot without sounding like spam. Use specific bridges to turn past conversations into new sales today.
Get startedShort answer
To reach old leads after a product pivot, frame the change as a response to the feedback or problems you encountered while talking to them. Move from saying you have a new product to explaining how you solved the specific problem you discussed months ago.
Audit your old lead list
Not everyone in your old CRM or LinkedIn history is worth a message. Sending a pivot announcement to people who were never interested is a fast way to get marked as spam. Start by pulling every conversation where you have a real reply, not just a connection request that was accepted.
Separate the leads who had a real pain point from those who were just being polite. You want the people whose specific complaints align with the new version of your product. A lead who said 'we already use a tool for that' is different from a lead who said 'our current tool cannot handle multi-currency contracts.' The second person gave you a problem you can solve now.
Sort by recency and by how specific their complaint was. A conversation from eight months ago about a missing feature is stronger than a conversation from last week where they said they were too busy. Busy is a timing problem. Missing feature is a product problem. You can solve a product problem with a new offer.
Discard these
- Leads who gave one-word answers to your initial outreach
- People who were curious about the concept but had no budget
- Leads whose job titles changed to a role that does not use your tool
- People who explicitly told you the previous product was not a fit
Keep these
- Leads who attended a demo but did not buy due to a missing feature
- People who had high-intent conversations about a specific business pain
- Leads who complained about a problem your new product now solves
- Former prospects who liked you personally but hated the old product
Group leads by what they wanted
A single pivot message won't fit every old lead. The person who wanted a cheaper plan needs a different note from the person who wanted an integration you didn't have. Group your list by the reason they didn't buy. Then write one short message per group.
The groups usually look like this: missing feature, price, timing, and internal change. Each group gets a different bridge. For a missing feature, the bridge is the feature. For price, the bridge is the new scope or the smaller starting point. For timing, the bridge is a new reason to look again. For internal change, the bridge is a new person in the role.
Don't overcomplicate this. You can do it in a spreadsheet with three columns: name, what they said, and which group they belong to. If you can't remember what they said, leave them out. A vague memory produces a vague message.
You were missing a feature
- What they said
- They wanted a capability you did not have
- What it means
- Ask if that capability is still the blocker and show how the new product handles it
The price was too high
- What they said
- They liked the product but not the cost
- What it means
- Explain the new starting point or the narrower scope that fits their budget
The timing was wrong
- What they said
- They had a different priority that quarter
- What it means
- Ask if the priority changed and offer a short call to compare notes
They left the company
- What they said
- Your champion is gone
- What it means
- Write to the new person with a short reminder of the problem, not the old relationship
Write the pivot bridge
The bridge is the sentence that connects your last conversation to your current offer. If you just say you have a new product, you sound erratic. If you say you listened to them, you sound like a founder who builds based on market demand.
A good bridge has a reminder, a reason, and a question. The reminder proves you remember them. The reason explains why you're back. The question gives them an easy way to reply. Keep the whole thing under four sentences. Long messages look like newsletters.
Treat the pivot as an evolution. You found a more urgent problem that needed a better solution. Don't apologize for the change. Apologies imply failure. Say what you learned and what you built.
Weak bridge
- Hi, I wanted to let you know we have pivoted. We now offer a new platform for contract management. Let me know if you want a demo.
- Hope you are well. We have rebranded and launched a new product. Would love to catch up.
Strong bridge
- Hi Sarah, when we spoke in March, you mentioned that managing vendor contracts was a huge pain for your team. We spent the last few months building a way to automate that specific workflow. Do you still deal with that?
- Hi Marcus, you told me last year that your team was drowning in renewal paperwork. We rebuilt the product around that one problem. Is renewal paperwork still on your list this quarter?
Example
- You
Hi Sarah, when we spoke in March, you mentioned that managing vendor contracts was a huge pain for your team. We spent the last few months building a way to automate that specific workflow and I thought of you.
- Prospect
Oh hi! I remember that. I thought you were doing something with procurement software?
- You
I was, but after talking to people like you, I realized the contract part was the actual bottleneck. I have shifted my focus to solving that specifically. Do you still deal with that?
The re-engagement sequence
Don't try to close the sale in the first message. Your first goal is to confirm that the problem you now solve is still a priority for them. If the problem is gone, the lead is dead. If the problem is still there, you have a reason to talk.
Keep the sequence light. These people already know you, so you don't need a formal introduction. Use a direct, conversational tone that reminds them of the rapport you built. Space the messages over a few days. Don't send three messages in one morning.
The sequence has four moves. Each move has one job. If a move gets a reply, stop the sequence and talk to the person.
- 1
The observation
Send a message mentioning a specific detail from your last conversation and link it to the new solution. Example: 'You said your team was copying contract data into three systems. We now pull that data automatically.'
- 2
The low-pressure ask
Ask if that specific problem is still a priority for them this quarter or if they have already found a fix. This gives them an easy out and keeps the conversation honest.
- 3
The proof
Share a short description of a result the new product gets for a current user to show it is real. Keep it to one sentence. Don't attach a case study PDF.
- 4
The clean-up
Ask if they want to be removed from your list if the new direction does not fit their needs. This respects their time and often gets a reply because it is unusual.
Handling the 'why the change?' reply
Some leads will ask why you stopped doing the old thing. Use this to show your expertise and your commitment to solving the problem correctly. A short answer builds more trust than a long story.
Be honest and brief. You don't need to explain the internal struggles of your startup. Frame the change as a strategic decision based on data and user feedback. If the old product still exists, say so. If it doesn't, say what replaced it.
Don't badmouth the old product or your old team. That makes you look unreliable. Say what you learned, who you learned it from, and what you built next.
Avoid words like failure or experiment. Use focus and feedback instead.
Paste this job
Example response: We found that most people actually struggled more with [New Problem] than the original feature we built, so we decided to go all in on solving that specifically. If you are still dealing with [Old Problem], I can show you what changed.
What to do when they say no
Some old leads will say no. They may have bought a competitor, changed roles, or lost the budget. A clean no is useful. It tells you to stop spending time on that lead and it keeps your list honest.
Reply with one short line and one question. The line thanks them. The question asks if they know someone else who has the problem. Don't push for a meeting after a no. That turns a polite exchange into a reason to block you.
If they say the timing is wrong, ask when to check back. Put that date in your calendar. If they say the product is wrong, ask what would need to change. If they say they bought something else, ask what they chose and why. That answer is free research.
- Bought a competitor: ask what they chose and what almost made them pick you.
- Lost budget: ask when the next budget cycle starts.
- Changed roles: ask who owns the problem now.
- No longer has the problem: ask if they know another team that does.
Doing this with Kinlead
Re-engaging a large list of old leads manually is slow. You can use Kinlead to handle the outreach while keeping the personal touch required for a pivot conversation. Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept.
Start by importing your old lead list via a CSV of LinkedIn profile URLs into a lead group. Create a campaign using a sales playbook that defines your new product's goal and tone. The AI can write connection notes under 200 characters that explain why that specific person is being contacted again. Queued campaign messages can be read and edited on the Actions page before they send.
Set the reply mode to hand the conversation to you at the first reply so you can handle the nuanced pivot conversation personally. Outreach runs from your own LinkedIn account, connected through Unipile. Kinlead sends at a human pace: each LinkedIn account sends at most one action every 5 minutes, inside daily invite and message limits you set and inside a send window in the lead's time zone. Stale pending invitations are withdrawn automatically, and Settings shows pending invitations and acceptance rate with warnings.
- Use lead groups to keep each pivot message group separate.
- Edit queued messages on the Actions page before they send.
- Hand off replies to yourself at the first reply.
- Set send windows to match the lead's time zone.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to reach old leads after a product pivot.md