Daily limits are set per account by verified status, with a hard ceiling, human-like random gaps, and sending-hours windows.
Trade-off: fewer DMs per day than a user might want.Case study · 05 XAutoDM
Cold outreach on X is a pacing problem.
Solve it, and it books calls.
A cloud platform that finds people on X who fit an offer, sends each a personal DM, and runs follow-ups until they reply—while keeping every connected account inside safe limits.
FIND↓MESSAGE↓BOOKXD
Live at xautodm.com
Product
Lead sourcing and DM automation for X (Twitter)
Built for
Founders, agencies, and small businesses
Model
Three plans priced by accounts; every plan gets every feature
Live
The problem 01
The buyers are on X. Reaching them by hand doesn’t scale.
Many of the people a founder or agency wants to reach are active on X but have no public email. Finding them means digging through followers, replies, and keyword searches; reaching them means writing personal DMs one at a time and remembering who to follow up with.
Doing it faster isn’t the answer: blasting messages gets accounts restricted. The product had to make outreach scale while sending fewer, better-timed messages—pacing every account so it stays safe.
Requirements 02
Scale the outreach without risking the account.
- Connect with an X login or session cookies—no API keys
- Run in the cloud, so campaigns continue with the laptop closed
- Per-account daily ceilings that can’t be overridden
- Stop the sequence the moment someone replies
- Honour a Do-Not-Contact list across every campaign
- Encrypt account credentials and never show them in the app
The system 03
Connect X account→Build lead list→Warm up→First DM→Follow-ups→Unified inbox→Booked call
From a lead list to a booked call, with pacing built in.
A customer connects an X account in about two minutes, then builds a lead list by scraping an audience, uploading a CSV, or importing a starter list. A campaign warms each lead up with a follow and a like, sends a personal first DM, and follows up on day 2 and day 5—each only after checking for a reply. Replies land in one inbox with pipeline stages, notes, and a booked button, and analytics track replies, reply rate, and calls booked per campaign and account.
Follower scrapingReply + retweet scrapersKeyword monitoringList membersCSV importMerge fieldsA/B variantsUnified inboxREST APIChrome extensionClaude skilln8n
Under the hood 04
Ten ways to find a lead
Leads come from the followers of any account, the accounts it follows, verified followers, keyword searches on bios and names, the people replying to or retweeting a tweet, @mentions, X List members, a CSV upload checked for open DMs, or ready-made starter lists. Large scrapes run in the background and land in the Leads tab when they finish.
Sequences that know when to stop
Every DM is written once with merge fields—name, handle, bio, follower count, or any CSV column—and can be A/B tested with a spam-hint checker and live preview. Live triggers DM new followers and engagers within minutes, follow-ups only send if there’s been no reply, and marking a lead “not interested” adds them to Do-Not-Contact.
Key decisions 05
Plans differ only by the number of X accounts and the daily limit—leads are unlimited on all of them.
Trade-off: no feature gating to drive upgrades.Scraping, sending, campaigns, and replies are all available from a public REST API, so outreach can be scripted or run from other tools.
Trade-off: a public API is a contract to keep stable.With opt-in, an expired X session is refreshed automatically, and the user is alerted if it can’t be.
Trade-off: stored sessions must be encrypted and handled carefully.What’s live 06
A live outreach platform, from lead list to booked call.
- Cloud web app with campaigns, inbox, and analytics
- Ten lead sources and live auto-DM triggers
- Day-2 and day-5 follow-ups that stop on reply
- Public REST API at api.xautodm.com
- Chrome extension that scores X profiles for lead fit
- Open-source Claude skill and an n8n integration
Building automation people can trust? 07
Let’s make it scale
without breaking things.
If your product needs to automate work on someone’s behalf, let’s talk about the limits and safeguards that keep it dependable.
Start a conversation ↗