How to qualify leads during a company pivot

After a pivot, your old pitch stops working. Test a new ICP on LinkedIn, find people with the problem, and qualify them before you sell them anything.

Get started

Short answer

To find customers after a pivot, test the new buyer before you sell to them. Write down who you think now has the problem, check on LinkedIn that people are actually complaining about it in public, and send short messages that ask about their workflow instead of pitching. Qualify on whether they describe the pain in their own words.

Define the new ICP hypothesis

A pivot changes who buys and why they buy. The script that worked for your old buyer lands flat with the new one, because the new buyer has different priorities and uses different words for the same problem. Before you touch LinkedIn, write down who you think the new buyer is.

Write it as one sentence you can argue with. Skip the persona document. Something like: head of revenue operations at a 50 to 200 person software company that just moved off spreadsheets and is now fighting its own reporting. That sentence names a role, a company shape and a moment. You can check it against real profiles in an afternoon.

The test for a good hypothesis is whether the person is losing money or time right now. Curiosity is cheap. A person with a deadline and a broken workaround will answer a message from a stranger.

Job title

Dimension
Marketing manager
Old buyer (example)
Head of revenue operations

Trigger event

Dimension
New product launch
Old buyer (example)
Just moved off spreadsheets

Main pain

Dimension
Low brand awareness
Old buyer (example)
Reporting takes days and nobody trusts the numbers

Company size

Dimension
1 to 10 people
Old buyer (example)
50 to 200 people

Where they talk

Dimension
Marketing blogs
Old buyer (example)
Vendor comment sections and ops communities

Check the problem on LinkedIn before you write anything

You think the problem exists because you have talked to a handful of people. LinkedIn lets you check that at a larger scale for free, and it shows you the exact words people use when they are annoyed.

Start with the companies already selling into your new market. Their post comments are a list of people who care about the topic enough to type something in public. Read those comments and note the complaints. You are looking for the same frustration in different words.

  1. 1

    List the companies your new buyer already pays

    Open their company pages and read the posts from the last couple of months. These are the vendors your buyer is choosing between right now.

  2. 2

    Read the comments, not the post

    The post is marketing. The comments are where someone says the tool is too expensive, too slow, or missing the one thing they need. Copy the phrasing into a doc.

  3. 3

    Check profiles for a moment of change

    Phrases like building our first RevOps function or moving off a legacy CRM tell you someone is in the middle of a switch. A switch is when budgets and patience are both open.

  4. 4

    Write down the words they use

    If the comments say reporting is a mess and your website says data observability, you are using the wrong words. Use theirs in the first message.

A complaint in a public comment is worth more than a job title in a search filter. The title tells you who they are. The comment tells you what they are stuck on.

Write the first message in their words

The first message has one job: get a reply that tells you something. Aim for a reply first. Meetings come later, once you know the problem is real.

Keep it short, name the specific thing you saw, and ask about their workflow. No calendar link and no feature list.

The pitch

  • Hi Sarah, I see you are a Head of RevOps. We have built a platform that fixes reporting. Do you have 30 minutes this week?
  • I am pivoting my business to help companies like Acme. Take a look at my website and let me know if it is relevant.

The question

  • Hi Sarah, your comment on the Northwind post about CRM migrations stuck with me. When you moved over, was the reporting rebuild the part that ate the time, or was it the data cleanup?
  • Hi Sarah, I am asking RevOps leads one question this week: what breaks first when a company switches CRM? Curious how that played out at Acme.

Paste this job

Hi {first name}, your comment on {company}'s post about {topic} stuck with me. I am asking {role}s one question this week: {question about how they handle it today}? Curious how that works at {their company}.

Run a small validation sprint

You do not need a thousand leads to know whether the hypothesis holds. You need a sample small enough that you read every reply yourself and specific enough that a yes means something.

Pick people who match the sentence you wrote and who have shown a sign of the problem: a comment, a post, a job change. Send a connection request that mentions the specific thing you saw. When they accept, ask one question and stop.

  1. 1

    Pick a small, exact list

    Twenty people who match the hypothesis and left a trace of the problem is enough to learn from. If you cannot find twenty, the hypothesis is too narrow or the problem is not visible in public.

  2. 2

    Send a request that names the reason

    One line about what you saw and why you are reaching out. Keep it under 200 characters and leave the pitch out.

  3. 3

    Ask one question after they accept

    Ask how they handle the thing today. Do not offer a solution in the same message. Let them describe the workaround first.

  4. 4

    Log the answer in their words

    Keep a plain sheet: name, what they said, whether the pain sounds current, whether they asked what you do. That sheet is your evidence, not your memory of the calls.

  5. 5

    Set the bar before you start

    Decide in advance how many people need to describe the pain unprompted for you to keep going. Write it down so you cannot move the goalposts after the replies come in.

Example

  1. You

    Thanks for connecting, Marcus. I saw your comment on the Northwind post about CRM migrations. Is the reporting rebuild still the part that eats your week?

  2. Prospect

    Honestly yes. We spend most of Friday cleaning exports so the numbers match.

  3. You

    That is the pattern I keep hearing. I am building something that does that cleanup automatically. Would it be useful to see whether it handles your export setup, or is this already solved on your side?

  4. Prospect

    Not solved. Send it over.

Decide what counts as a yes

Replies are noisy. Some people are polite, some are curious, and a few describe the problem in enough detail that you know they have lived it. Sort them into buckets and be strict about which bucket is which.

A real yes sounds like a description of work: the Friday they lose, the spreadsheet nobody trusts, the hire they are about to make to fix it. A polite no sounds like interesting or will keep this in mind. Both are useful, but only one is evidence that the pivot is right.

They describe the workaround in detail

Signal
The pain is real and current
What it means
Ask what would have to change for them to fix it

They ask how it works

Signal
They are comparing options
What it means
Show the smallest useful version, then ask about their setup

They say interesting and stop

Signal
Polite, not in market
What it means
Leave it and keep them on a list for later

They push back on the problem

Signal
Wrong person or wrong hypothesis
What it means
Ask what the real bottleneck is, then rewrite your sentence

If nobody in your sample describes the problem without being prompted, the problem is your hypothesis, not your message. Rewrite the sentence and run the sprint again.

Doing this with Kinlead

Kinlead does the finding and the sorting, so you spend the sprint reading replies instead of hunting for commenters. The Steal Customers agent watches competitor company pages, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, so your first message can name the exact thing they said.

You describe the new buyer, or point Kinlead at your website, and it scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept, which matters when your old ICP and your new one look similar on a search results page. Leads sit in lead groups that any campaign can point at.

  • Connection notes are written by AI under 200 characters and open with why that person became a lead.
  • Messages and follow-ups come from the campaign goal, tone and your own sales playbook.
  • Queued messages can be read and edited on the Actions page before they send, and any campaign can be paused.
  • Replies from every campaign land in one inbox, classified by intent, with interested replies first.
  • Each LinkedIn account sends at most one action every 5 minutes, inside daily limits you set and a send window in the lead's time zone.

Kinlead connects through Unipile and never stores your LinkedIn password. It cannot promise LinkedIn will not restrict an account, so keep the first sprint small and inside limits you would use by hand.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to qualify leads during a company pivot.md