How to Build an AI SDR Workflow a Founder Can Actually Run

After sending a lot of cold email, Chris (coldemailchris) wrote on X: "I'm sure founders have AI backwards. Half of them bought an AI SDR to run outbound for them. The other half still won't let AI write a single email. Both groups are wrong, in opposite directions."

Pramod Kumar, co-founder of Kingdom of Kumar. On X

·

That is the article, in three sentences. Autopilot is how you burn a domain. Refusing all assistance is how you stay the bottleneck. The useful design is a workflow that researches and drafts, and a human who approves.

People are trying to buy this as a package. In r/coldemail, one post was titled, almost as a brief, "looking for consultants that could automate end to end lead gen". Another founder tried an "AI lead gen SDR thing" and published the results: autopilot was weak; things improved when they moved to a copilot, rebuilt targeting around buyer triggers, and stopped treating the tool as a finished employee.

This is how I would build that copilot for a founder-led team. A comparison of the seats is in AI SDR vs a human SDR. The approval step, in more detail, is in An AI SDR approval workflow. The work sits inside GTM engineering; the offer is on GTM engineer.

"Founders have AI backwards"

The first half bought a product that promised to "run outbound." They connected a website, let it find people, and let it send. When the replies were thin or the wrong people were contacted, they could not see why. The second half treated any generated sentence as a contamination of their voice, so they still write every line, and they still have no volume and no system.

Both misses are the same miss: they skipped the design. An AI SDR is not a hire and it is not a personality. It is a pipeline with stages, each of which can fail.

If your product itself is not ready to sell, do not build this yet. Take the App Launch Score and go talk to users first.

What the workflow actually is

Draw it on one page before you buy anything.

  1. 1Fit rules. Who is allowed on the list, and who is never contacted. Written down, not "we'll know it when we see it."
  2. 2A signal. Why this account, this week. A hiring post, a job change, a comment, a funding note, a form fill. Not "they are in the database."
  3. 3Enrichment. A verified email, a real title, a link to the evidence. If you cannot verify it, it does not go to the sender.
  4. 4A draft. A short message that opens with the evidence. A model can write this. A model should not send this.
  5. 5Approval. A human reads the full body, the recipient, and the reason, then says yes, edit, or no. See the approval piece for the daily pass.
  6. 6Send and follow-up. From infrastructure you set up properly. Cold email infrastructure comes before volume.
  7. 7Reply handling. Replies go to a person. A model can suggest a classification (interested, not now, unsubscribe, out of office). A model should not run the conversation until you have earned that trust, and even then I would be slow.
  8. 8Review. Once a week, look at replies and meetings by signal and by message. Cut what is polite and useless.

That is "end to end lead gen" without the fantasy that nobody is involved.

Autopilot vs copilot, without inventing a benchmark

I will not treat the r/coldemail test as a universal result. It is one team's experiment, published by them, with their tool and their list. What I take from it is the direction: when they treated the product as an autopilot, they were disappointed; when they reworked targeting around triggers and kept a tighter loop, it got more useful.

A comment under the "dirty secret behind every AI SDR demo" thread made the point I would tattoo on a vendor deck: even with a clean API, "send the email" should be gated on per-message approval until you have solved deliverability and the blast radius of a confident, false first line. Models will invent "I saw you recently expanded to Europe." If you auto-send that, you deserve the reputation you get.

A build order for the first two weeks

Day 1–2. Write the fit rules and the "never contact" list. If you cannot, stop. How to define an ICP your team will actually use is the companion.

Day 3–4. Pick one signal and the source you will watch. Do not watch six. Signal-based prospecting is enough.

Day 5–7. Enrichment and verification on a small batch (start with 30–50, not 5,000). Check 10 records by hand.

Day 8–9. Prompt or workflow that drafts a first line from the evidence field. If the evidence field is empty, the draft must be empty. No invented signals.

Day 10–11. Approval inbox. You should be able to clear it in a sitting. If a pass takes hours, your volume is too high or your drafts are too long.

Day 12–14. Send a small approved batch from warmed, authenticated domains. You take the replies. You log failures.

Tools: use what you have, in this order

I am not going to name a winning "AI SDR" product. The market is noisy, and the products change. The order of decisions is more stable:

  • A place to keep the list and the evidence (CRM, sheet, or a table tool)
  • A way to find and verify emails
  • A model for research and drafting (we use Grok and Claude)
  • A sequencer with proper domain authentication
  • An approval surface you will actually use, even if it is a shared inbox or a Slack channel of drafts

If a vendor will not show you the approval step, or buries it, you are buying an autopilot. Comments in that Reddit demo thread also argued that some "agents" are still clicking a human UI. Ask how the send actually happens.

Who this is for, and who it is not

This is for a founder or a very small team that already closes when the right person is in the room, and needs a repeatable way to start conversations. This is not for someone who wants to "set it and forget it." It is also not a substitute for a human SDR once you have more conversations than you can work — at that point you have a volume-of-conversations problem, not a drafting problem.

At Kingdom of Kumar we build and run this kind of system on Grok and Claude for $500 a month, with a three-month minimum. You approve what goes out. If you want a bot that sends while you sleep, we will tell you no.

FAQ

Can I skip the approval queue once quality looks good?

I would be very slow to do that, and I would never skip it on first-touch mail that mentions a fact about the account. A weekly audit of a sample is not the same as reading the one that will embarrass you.

Do I need a GTM engineer to build this?

You need someone who can design and maintain the workflow. That can be you, a hire, a fractional, or a done-for-you team. The title is optional. The weekly operation is not.

Where do consultants fit?

The "looking for consultants" thread split, as those threads do, between "hire a cheap setup" and agencies offering an "AI SDR." Setup without a weekly owner is how these systems die. Buy operation, or be the operator.

What should I measure?

Replies and meetings by signal and by message. Not emails sent, not "personalisation score," not a vendor dashboard of activity.

Contact

hello@work.kingdomofkumar.com