On X, buyers say what they need in public. They ask their followers which tool to use, complain about the one they have and announce the hire or the funding round that means they're about to buy. Lead generation on X is the work of finding those posts early, showing up with something useful, and turning the conversation into a call.
This playbook is written for B2B SaaS founders, growth teams and the agencies that run X for them. It needs no ad budget and no list buying: just a clear idea of your buyer, a few saved searches and about five hours a week. Every step has examples you can copy, and a worked example near the end follows one lead from post to call.
Step 1: Define the buying signal
Start by writing down who buys and what they say before they buy. A role and company size isn't enough on X, because you can't search for "VP Marketing at a 50-person company". You can search for what that person writes.
- The problem in their words. How do customers describe the pain in sales calls and support tickets? Use those phrases, not your marketing copy.
- Competitor and category names. Everyone who mentions a tool you replace is a possible lead.
- Trigger events. Hiring for a role that uses your product, raising a round, launching, migrating or hitting a limit.
- Who doesn't fit. Students, job seekers, other vendors and people outside your markets. Write these down too, so you skip them quickly.
The result is a one-paragraph signal: "Founders or marketers at software companies who ask for a tool to do X, complain about Y, or mention hiring for Z." Here's one filled in.
ExampleSignal sheet for a fictional client-approval tool for small social media agencies
- Buyer: owners and account leads at agencies running 5 to 30 client X or LinkedIn accounts.
- Problem phrases: "chasing approvals", "client never replied", "posted the old version", "approvals over email", "sign-off".
- Competitors: the two scheduling tools with approval features that customers mention most in sales calls.
- Triggers: "signed a new client", "hiring a social media manager", a competitor's price change.
- Skip: freelancers looking for work, other tools' founders, giveaway and course posts.
The signal: "Agency owners who complain about chasing client approvals, ask what other agencies use for sign-off, or are leaving one of our two main competitors."
Step 2: Build saved searches
X's search supports operators that turn a vague topic into a list of people asking for help. Below are searches grouped by what the person is doing. Replace the words in square brackets with your own, paste each into X search, switch to Latest, and save the ones that find real buyers. Our Twitter advanced search tool builds the same queries from a form if you'd rather not type the syntax.
Asking for a recommendation
The warmest signal on X: someone asking their followers what to buy.
| Search | What it catches |
|---|---|
("anyone recommend" OR "can anyone recommend" OR "any recommendations") [category] -filter:replies lang:en | Original posts asking followers to suggest a tool in your category. The -filter:replies drops replies, so you see the question, not the thread under it. |
("looking for a" OR "looking for an") ([category] OR [job your product does]) -filter:replies lang:en | People actively shopping. Try both the category name and the job in plain words, because many buyers don't know the category name. |
("anyone use" OR "does anyone use" OR "thoughts on") [competitor] -filter:replies | People checking a tool before they commit. They haven't bought yet, so an honest comparison is welcome. |
Complaining about a competitor
Unhappy users of a tool you replace, often in the middle of a decision.
| Search | What it catches |
|---|---|
[competitor] (broken OR "so slow" OR "down again" OR frustrating OR "support is") -filter:replies lang:en | Public frustration with a competitor. Read the post first: a one-off outage gripe isn't a buyer, a pattern of problems is. |
to:[competitor handle] (cancel OR refund OR "still waiting" OR "any update") | Replies sent to a competitor's own account. Leave out -filter:replies here, because these are all replies. |
[competitor] (pricing OR price) (increase OR doubled OR "too expensive") since:2026-01-01 | People reacting to a price change. Set since: to the date of the change so you only see fresh reactions. |
Describing the problem
People who have the pain but haven't started looking for a tool. The biggest group, and the least crowded.
| Search | What it catches |
|---|---|
("spent all day" OR "wasted hours" OR "so tired of") [task your product removes] -filter:replies lang:en | The problem in the buyer's own words. Swap in the phrases customers use in sales calls and support tickets. |
("is there a tool" OR "is there an app" OR "there has to be a better way") [job] -filter:replies | People one step away from searching for a product. Reply with the approach, then the options. |
"how do you" [job your product does] min_replies:3 -filter:replies | Practitioners comparing workflows. min_replies:3 keeps posts that already have a conversation you can join. |
Switching or about to switch
People who've decided to leave a tool and are choosing what's next.
| Search | What it catches |
|---|---|
("alternative to" OR "alternatives to" OR "replacement for") [competitor] -filter:replies lang:en | Shoppers looking for a replacement for a tool you compete with. |
("switching from" OR "moving off" OR "migrating from" OR "leaving") [competitor] -filter:replies | People mid-move. They care about import, setup time and what breaks, so answer those. |
[competitor] (vs OR versus OR "compared to") min_faves:5 -filter:replies | Comparison posts with some traction. min_faves:5 skips posts nobody read, and the replies show who else is deciding. |
Trigger events
Companies about to buy because something changed.
| Search | What it catches |
|---|---|
("we're hiring" OR "now hiring") [role that uses your product] -filter:replies | Companies building the team that will use, and often choose, your product. |
("just raised" OR "announcing our seed" OR "closed our seed") [your market] -filter:replies | Newly funded companies that are about to buy tools. |
The operators in these searches
| Operator | What it does |
|---|---|
"exact phrase" | Matches the words in that order. |
A OR B | Either term. OR must be in capitals; group with parentheses. |
-word | Excludes a word or phrase, such as -hiring or -"job opening". |
-filter:replies | Original posts only, no replies. |
min_faves:5, min_replies:3 | Posts with at least that many likes or replies. |
lang:en | Posts in one language. |
since:2026-11-01 | Posts on or after a date (until: for before). |
to:handle | Replies sent to one account. |
A few habits make the searches pay off. Recent posts matter most: a post from this morning is worth ten from last month, because the person is still deciding, so add since: with a date from the last week or two. Add your skip list as exclusions, such as -hiring -giveaway -"DM me", once you see which words bring in noise. And keep the searches that find buyers two weeks running; drop the rest.
Step 3: Make your profile worth clicking
Every reply you write sends people to your profile. Before you start, make sure it answers three questions in five seconds: who you are, who you help and why they should trust you.
- Bio: the outcome you deliver for a named audience, not a list of job titles.
- Pinned post: your best proof, such as a customer result, a teardown or a demo, with one clear next step.
- Recent posts: at least a few posts a week on the problem you solve. A profile that went quiet a month ago looks like a company that did too.
Our X profile audit checks these in a minute.
Keep the link in your profile, not the post
Your own posts bring people to your profile too, and a link in the post costs them reach. In our X benchmarks:
Posts with a link got 32% less reach than posts without one: 86 views per 1,000 followers against 126. Put the link in a reply or your profile when reach matters.
| Posts | Median views per 1K followers | Against the median | Posts measured |
|---|---|---|---|
| No link | 126 | 1.0× | 614,667 |
| With a link | 86 | 0.7× | 85,034 |
Step 4: Reply before you DM
A public reply is the lowest-pressure way to start. It helps the person, shows your expertise to everyone else reading the thread, and gives them a reason to look at your profile. Good replies:
- Answer the question first. If they asked for a tool, name two or three good options, yours included, and say who each one suits.
- Add something specific. A number from your own experience, a mistake to avoid or a quick how-to.
- Mention your product once, honestly. "Disclosure: I build one of these" earns more trust than pretending to be a neutral fan.
- Skip the link unless they asked for it. Let them click through to your profile.
Here's what that looks like for three kinds of signal. The posts are made up, and the replies are examples to adapt, not scripts to paste.
| They posted | Example reply | Why it works |
|---|---|---|
| "Any recommendations for a tool to collect client approvals on social posts? Small agency, 6 clients." | "At 6 clients the thing that matters most is whether clients can approve without making an account. [Competitor A] and [Competitor B] both do it; A is quicker to set up. Disclosure: I build one too, so weigh my list with that in mind." | Answers the question, names real options including competitors, and discloses the bias. |
| "[Competitor] changed their pricing again and our bill doubled." | "If you do move: export your post history and approval notes first. Most tools only import a CSV, and the notes don't come across on their own." | Useful whether or not they ever buy from you. No pitch; your profile does that. |
| "Spent my whole Friday chasing clients to sign off on next week's posts." | "What usually helps: send the week's posts on Tuesday with 'these go out as written unless you object by Thursday'. Clients answer faster when silence counts as a yes." | Gives a fix they can use today. People who find a reply useful check who wrote it. |
What not to write: "Check out [product], it solves exactly this! Free trial here: [link]". It doesn't answer the question, it could be pasted under any post, and everyone reading the thread can tell.
Step 5: Move to DMs with permission
DM when the person replied to you, followed you after a conversation, or asked something that's easier to answer in private. Keep the first DM short, reference the public conversation, and ask one question. Don't paste a pitch deck.
| When | Weak opening | Better opening |
|---|---|---|
| They replied to your public reply | "Hi! I'm the founder of [product], the all-in-one approval platform for agencies. Would you be open to a 15-minute demo this week?" | "Thanks for the reply on the approvals thread. So I don't send you anything useless: is the pain mostly clients who won't log in, or keeping track of what's scheduled?" |
| They asked about pricing for their setup | "Pricing starts at $49/month, here's the sign-up link: [link]. Let me know if you have any questions!" | "You asked about pricing for 14 accounts. It depends on whether clients need their own logins, so rather than guess: do they, or would an approval link be enough? I'll send the exact number after." |
The weak versions ask for something (a demo, a sign-up) before the person knows why they'd want it. The better ones are about the person's situation and end with a question they can answer in one line.
Automation needs care. X's automation rules restrict automated and bulk unsolicited direct messages. Automate follow-ups only to people who opted in, for example by replying to a post that invited them to, and send everything else by hand.
Step 6: Qualify in the conversation
Before you suggest a call, find out four things. You can learn most of them from the person's profile and posts.
- Problem: do they have the problem your product solves, today?
- Timing: are they choosing a tool now, this quarter or someday?
- Fit: is their company the size and type you serve well?
- Buying path: can they buy, or who else decides?
If two or more are missing, stay helpful in public and check back later instead of pushing for a call.
Step 7: Track every lead in stages
A lead list beats memory. Use your CRM, a spreadsheet or Xholic's Contacts, with one row per person, the post that found them, and one of these stages. "What moves it forward" is the action that gets a lead to the next stage.
| Stage | Means | What moves it forward |
|---|---|---|
| Found | Matches your buyer and showed a signal in public | A useful public reply, ideally within a few hours of the post |
| Engaged | You replied publicly, or they replied to you | A second helpful exchange, or a question that's easier to answer in a DM |
| Conversation | A two-way exchange in replies or DMs | Learning the problem, timing, fit and buying path (Step 6) |
| Qualified | Has the problem, the timing and a way to buy | Offering a short call about their problem, with two times to choose from |
| Call booked | A call or demo is on the calendar | Showing their own example on the call and agreeing the next step before it ends |
| Won or lost | Closed, with the reason written down | Lost: a date to check back. Won: ask for a story or a referral |
Record which search found each lead. After a month you'll know which searches produce calls and which only produce likes. Tag links you share with UTM parameters, such as utm_source=x&utm_medium=social&utm_campaign=outreach, so signups from X show up in your analytics.
Step 8: Run a weekly cadence
Consistency beats bursts. This is a cadence one person can keep up alongside their main job:
| When | What | Time |
|---|---|---|
| Monday | Run saved searches, add new leads to the list, write 2 posts | 45 min |
| Daily | Reply to 5–10 lead or prospect posts with something useful | 20 min |
| Tuesday–Thursday | Follow up on public conversations, send DMs where people engaged | 30 min |
| Wednesday | Publish one proof post: a result, a teardown or a customer story | 30 min |
| Friday | Update lead stages, book calls, review the week's numbers | 30 min |
Step 9: Measure pipeline, not likes
Review four numbers every Friday. Each one points at a different step when it drops, so you know what to fix.
| Number | Formula | If it drops |
|---|---|---|
| Qualified leads found | New leads at Found that match your buyer, this week | Searches too broad or too narrow. Add competitor names and grow the skip list. |
| Reply rate | Leads who answered you ÷ leads you replied to | Replies too late or too generic. Reply sooner and answer the question first. |
| Call rate | Calls booked ÷ conversations | Weak proof or a vague ask. Check your pinned post and offer a specific call. |
| Close rate | Deals won ÷ calls held | Poor fit getting through. Tighten qualification in Step 6. |
Multiply them together with your average deal value and you have the pipeline X is producing: pipeline = qualified leads × reply rate × call rate × close rate × average deal value. With made-up numbers: 40 leads × 25% reply rate × 30% call rate gives 3 calls a week; at a 25% close rate that's about 3 new customers a month. Your own rates are the only ones that count. The X pipeline value calculator does the math and shows which stage to fix first.
When a rate is low, change one thing at a time: better-matched searches raise reply rates, clearer proof posts raise call rates, and sharper qualification raises close rates.
Worked example: from a post to a call
This follows one lead through the playbook for the fictional approval tool from Step 1. The people, messages and timings are illustrative, written to show the moves, not taken from a real account.
ExampleIllustrative: a three-person SaaS team, one lead
1. The signal (Tuesday morning)
The team's saved search [competitor] (overkill OR "too complex" OR "too expensive") -filter:replies lang:en surfaces a post from an agency owner:
"Running 14 client accounts and approvals are killing us. Half live in email, half in Slack, and last week a post went out with the old copy. What are other agencies using? We're on [competitor] but it's overkill for us."
It matches the signal sheet: agency owner, the exact problem, a named competitor. Stage: Found.
2. The public reply (within the hour)
"The wrong-version post is the worst one. What fixed it for agencies we talk to: one approval link per post, so the client signs off on the exact copy that ships. Disclosure: we build a smaller tool for this. Happy to share our approval checklist either way."
It answers the question, admits the bias and offers something free. No link, no pitch.
3. Their answer, then the first DM
"Checklist would be great. Our real issue is clients who never log in to anything."
They replied, so the team can DM. Stage: Engaged. The founder sends the checklist and one question:
"Here's the checklist: [link]. On clients never logging in: that's why approvals in our tool work from a link, no account needed. Is that the main blocker, or is it also keeping track of what's scheduled across 14 accounts?"
4. Qualify, then book the call
"Both, honestly. We're trying to sort it before two new clients start next month. Can you show me the link part?"
In two messages the four questions from Step 6 are answered: the problem (approvals and tracking), timing (before next month), fit (14 accounts, an agency) and buying path (the owner decides). Stage: Qualified.
"Sure. 20 minutes Thursday at 2pm or Friday at 10am? I'll use one of your real posts so you see exactly what a client would see."
They pick Friday. Stage: Call booked. The team logs the lead with the search that found it, so Friday's review credits that search with a call.
Common mistakes
- Pitching in the first reply. People ignore it, and everyone reading the thread sees it.
- Searching only for your brand. Most buyers don't know you yet; search for the problem and the competitors.
- Searching without -filter:replies. You spend the hour reading threads instead of finding the people who started them.
- Going quiet on your own account. Replies send people to a profile that needs to show recent, useful posts.
- No list. Without stages you can't follow up, and you can't tell which searches produce customers.
- Bulk cold DMs. X's automation rules restrict automated and bulk unsolicited direct messages, and accounts that send them get limited or suspended.
Run the playbook with Xholic
Everything above works by hand. Xholic takes over the slow parts, finding and sorting, and leaves the judgment and the sending to you.
- Finding leads: Signals agents watch X around the clock for people who match your description of a good lead, score each one with AI against it, and add good matches to Contacts. Each confirmed lead comes with why to reach out now, a suggested reply to their post and an opening DM to edit. Nothing is sent automatically, and marking a lead as not a fit teaches the agent.
- Starting from your product: Find customers builds a Signals agent from a saved product in one click. It watches the people engaging with your competitors on X and searches for people describing the problem your product solves.
- Following up, the same way this playbook does: for people who haven't talked to you yet, assisted DMs prepare each message in a daily queue for you to send yourself on X. Keep automation for people who opted in: Auto DMs answer people who reply to your post with a keyword, and DM campaigns support up to two follow-ups that stop as soon as someone replies, with daily caps and rules that skip anyone already messaged or already in a conversation.
Teams and agencies running this for several products or clients can see how it fits together on the lead generation page.