For GTM engineers. Bring your own agent.SDR Pilot for GTM Engineers.
SDR Pilot (sdrpilot.ai) is an AI SDR from $97 a month that runs on your own LinkedIn account and can be driven by your own AI agent. You already own the research, the scoring and the workflow. This is the part you should not build: a LinkedIn executor that paces itself.
- MCP and API on every plan
- Your stack keeps the thinking
- The pacer keeps the caps
connect with 20 SaaS founders in Berlin who posted about churn this week
Searching, reading each profile, scoring against your ICP. 14 of the 20 passed.
The agent asks. SDR Pilot's pacer decides what actually goes out, and when.
GTM engineering is mostly plumbing that nobody else will do: a scoring prompt that actually reflects how the company sells, an enrichment waterfall that stops when a cheaper source already answered, a workflow that turns a signal into a task before the signal goes cold. The work is real and the tooling for it is good now.
The thing that keeps breaking is the last mile
The list is not the hard part any more. Getting a message onto LinkedIn, at a human pace, from an account that survives the quarter, is.
Every team that builds this themselves goes through the same three months: a headless browser, a proxy, a rate limiter written from a Reddit thread, then a restricted account and a rewrite. The reason it is hard is not the API surface. It is that safety on LinkedIn is a hundred small defaults, each of which looks optional until the day it is not.
One identity per session.
One action at a time.
A warm-up with no cliff in it.
A country-matched residential IP that nothing else shares.
A pending-invitation ceiling, and a withdrawal sweep.
A calendar day that belongs to the user and not to the server.
The split that works
Your agent decides who and why. SDR Pilot decides whether, when and how fast.
That line is the whole product, and it is the line every raw LinkedIn API refuses to draw, because drawing it means saying no to the caller.
SDR Pilot keeps
- The LinkedIn session, the identity, the IP, the queue, the caps, the warm-up and the active hours.
- The conversation: when a lead replies, it answers from your playbook rather than handing you a webhook and a problem.
You keep
- The ICP definition, the research, the signal detection and the copy strategy.
- Your orchestration: Claude Code, Cursor, n8n, Clay, whatever the stack is this month.
What it looks like from your side
Over MCP, in a client you already use: Claude Code, Claude Desktop, Cursor or n8n.
You ask for the work in the terms you think in, twenty founders in Berlin who posted about churn this week, and you get back what actually happened, including the part where fourteen passed your ICP and six requests were left in today's budget.
The surface mirrors the app
Search people, add and research leads, send a request into the day's queue, read the inbox, reply or hand a thread over, post and pull the engagers in as leads. Nothing an agent can ask for is something a person could not do in the product.
MCP and the API are included on every plan. Create an API key in the app under Settings, then API, and point your MCP client at https://mcp.sdrpilot.ai/mcp. Setup steps are at help.sdrpilot.ai/api/api-and-mcp/.
The pacer is the feature
An external agent proposes, SDR Pilot disposes. The caps are not parameters.
- 20 a day
- Connection requests
- 100 a day
- Messages
- 250 a day
- Profile reads
- 16 days
- Warm-up
Per sender, with a ceiling of 25.
With a ceiling of 250.
Alongside 30 searches.
A new sender starts at 5 requests a day and reaches 20 on day 16.
One LinkedIn action at a time. One browser identity per sender on one dedicated residential IP in the account's country. Your active hours, your calendar day.
Ask for two hundred and you get twenty today, twenty tomorrow, and a straight answer about the rest.
If that is a dealbreaker, this is the wrong tool and a raw LinkedIn API is the right one. It is also the reason this exists.
Where it sits in a waterfall
At the end of it.
Enrichment, intent and scoring happen in your stack, in whatever order is cheapest, and the survivors arrive here. SDR Pilot then does its own profile read and its own ICP score before sending, which is a second gate rather than a duplicate: yours decides who is worth the budget, ours decides whether this specific profile, read today, is worth one of the day's twenty.
Both gates are yours to tune. The ICP lives in the app and the playbook is a document you edit, so the judgement is not buried in a prompt you cannot see.
What is not there
No raw LinkedIn tools. Your agent asks for outcomes; the pacer decides the pace.
No native CRM sync and no Zapier app. Webhooks and the API are there for your own glue.
No email or WhatsApp. SDR Pilot is LinkedIn only.
No way to raise the caps past the published ceilings, for you or for your agent.
No free tier. There is a 14-day free trial, card required at checkout.
FAQQuestions people ask
Can I drive SDR Pilot from Claude Code?
Yes, over MCP, on every plan. Claude Code, Claude Desktop, Cursor and n8n are the clients it is built for, with an API for anything else. Create an API key in the app under Settings, then API, and point your MCP client at https://mcp.sdrpilot.ai/mcp. Setup steps are at help.sdrpilot.ai/api/api-and-mcp/.
Why not just call a LinkedIn API from my agent?
Because the tools will do exactly what your prompt says, as fast as it says it, and the judgement about what is safe ends up living in that prompt. SDR Pilot keeps the pacing, the warm-up, the identity and the caps outside anything a caller can set.
Does SDR Pilot replace Clay or n8n?
No. Those build and enrich the list; SDR Pilot is what acts on LinkedIn afterwards and then holds the conversation. The intended integration is that your workflow hands leads over rather than being replaced by one.
Can my agent raise the daily limits?
No. The caps, the warm-up ramp, the one-action-at-a-time lock and the active hours are not exposed as parameters. An agent asking for two hundred connection requests gets the day's twenty and a queue.
Do I still get the AI replies if my agent is driving?
Yes, and that is most of the value. When a lead answers, SDR Pilot replies from your playbook and hands the thread over when the lead is ready, instead of handing you an unread inbox to automate yourself.
Start Your Free Trial. Live on LinkedIn Today. 
Every plan starts with a 14-day free trial. Create an account, add a card at checkout and connect LinkedIn; nothing is charged before day 15, and you can cancel in the billing portal any time. Plans start at $97 a month for one LinkedIn sender.