How SDR Pilot Works.

Onboarding reads your website and drafts the playbook from it: company information, your offer, the persona you sell to, the rules you want followed, the goal of a conversation, and a set of FAQs. It also drafts a knowledge base and a first ideal customer profile, meaning the titles, industries, company sizes and countries a person has to look like before they are worth a request.

You then edit all of it in the app. This is the part worth spending an hour on, because the same document does three jobs: it writes the replies, it qualifies the leads, and it writes the connection note on the rare occasions you have asked for one. You can test the agent on sample prospects before it talks to anybody real.

Before the first login, a dedicated residential IP is bought in your account's own country and assigned to that sender alone. Then you connect. SDR Pilot holds an encrypted session cookie rather than your password, and captures the browser identity from the real login so every later request carries the same user agent, timezone and locale.

The sender then warms up. It sends 5 connection requests on its first day and one more each day after, reaching the default of 20 on day 16. Messages start at 30 a day and reach 100 on day 15. Profile reads and searches ramp on the same schedule. You set the hours and days it is allowed to act, on your own calendar.

Within minutes it is reading posts in your niche, pulling the people who engaged with them, and opening profiles. Every profile is read in full and scored against your ICP before anything is sent, and most people get a no. The ones that pass go into the day's queue of connection requests, paced across your active hours, one action at a time.

The connection request goes out with no note by default. A note is what makes a stranger read the invitation as a sales pitch, so the personalisation waits for the opener message after they accept. If you would rather send a note, the AI writes one from the person's profile and the live business context.

The agent answers, from the playbook and from what it read on their profile. It holds the conversation, answers questions, qualifies, and hands the thread to you when the lead is ready. Put your booking link in the playbook and it will send it when the playbook says so. It does not connect a calendar of its own and it does not book meetings by itself.

If you reply yourself, from the app or from LinkedIn on your phone, the agent stands down on that thread. It does not talk over you and it does not start again behind you.

Everything above is the app path, and it is how most people will use it. There is a second path for people whose planning already lives in an agent: point Claude Code, Claude Desktop, Cursor or n8n at SDR Pilot over MCP, ask for the work in your own words, and let SDR Pilot execute it.

The two paths share one product. An agent can ask for the same things the app does: search people on your ICP, add and research leads, queue a connection request, read the inbox, reply in a thread or hand it over, post and pull the engagers in. What it cannot do is go faster. The caps, the warm-up, the one-action-at-a-time lock, the active hours and the ICP score are not parameters, so an agent asking for two hundred requests gets the day's twenty and a queue.

The MCP server and the API are in early access, not shipped. There is no endpoint, no package and no tool list today. Ask for early access in the same DM you would use to ask for an account, and see the MCP page for what the surface is meant to be.

1. 1Find: six lead sources feed candidates in, in a priority order you can change.
2. 2Research: the profile is opened and read, up to 250 profiles a day.
3. 3Score: the profile is scored against your ICP, with a different pass mark per source if you want one.
4. 4Decide: below the bar, the person is disqualified and never contacted.
5. 5Send: the ones that pass get a connection request, up to 20 a day, paced inside your hours.
6. 6Talk: on acceptance the agent opens, then answers every reply until the lead is ready for you.
7. 7Hand over: you take the thread whenever you want and it stands down.

Nothing is required to keep it running. There is nothing to approve, nothing to schedule and no sequence to build. Open the inbox when you feel like it, read what it has been saying, take over the threads that matter to you, and adjust the playbook when you notice it answering something in a way you would not have.