Should You Hire an SDR or Build a System First?
This question sits in the same cluster as two earlier pieces, and I do not want to rewrite them. GTM engineer vs SDR is about the roles. How to build pipeline without an SDR is about the motion. This is the decision, in the order I would take it: do you need another person to work a queue, or do you need a system that makes the queue worth working?
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
The public arguments have been sharp. One line that keeps circulating is to hire a GTM engineer before the first SDR. Anna Svitlychna put the risk the other way: SDR, account executive, GTM engineer — hire the wrong one at the wrong time. In r/sales, people still argue whether GTM engineers are fluff or legit, which is often a proxy for "are we hiring a title because we did not want to fix the list?"
My short answer: if list quality, fit, approvals, and follow-up are not something you can already describe, build the system first — founder-led, or with a scoped partner — and do not hire an SDR to hide the mess. If the system is running and the bottleneck is hours on a proven queue, then an SDR can be the right next person. Timing for a GTM hire, if that is the other option, is in When to hire a GTM engineer. The work is on GTM engineer and GTM engineering. If the product is not ready, take the App Launch Score and hire no one for this.
"List quality" versus headcount
An SDR, used honestly, is a person who works a defined motion: they contact people who should be contacted, in a way you have already learned, and they hand over conversations. Headcount helps when the motion is true and the hours are not.
Headcount hurts when the list is a dump, the first line is generic or fake, nobody owns replies, and you are hoping energy will create a process. You will not only burn salary. You will teach a person that "activity" is the job, and you will teach the market a sloppy version of you.
List quality, here, is bigger than emails that verify. It is: the right companies, the right people, a never-contact list that works, a reason this row is in today's queue, and a CRM that knows who was already spoken to. If you cannot show an SDR that on a Monday, you are hiring them to design the system in the cracks of a quota. Some can. Many will just send.
The GTM-engineer-first argument is really a system-first argument. I agree with the system-first part. I do not think the only way to get the system is to hire that title at a mid six-figure US band, which many seed teams cannot carry. You can build a small system yourself. You can buy a scoped build-and-run engagement. You can hire a GTM engineer when the work would fill a job. Those are three ways to get a system. An SDR is usually not the fourth way. It is a way to run a system you already have.
"Hire the wrong one at the wrong time"
This is the line I would write on the whiteboard before a hiring conversation.
Wrong time for an SDR: no repeatable motion, no one to train against real examples, no owner of the list, no path for handoffs, a founder who will disappear from coaching. Wrong time for a GTM engineer: no offer that can be sold, no willingness to approve and review, a hope that the hire will also be your only closer and your RevOps team. Wrong time for an AE: no conversations to take, or no product worth a second meeting.
Right time for an SDR: you can describe last month's motion in sentences, you can show a list you trust, you have a cap and a reply path, and you are the bottleneck on first touches or on qualifying, not on "what should we even say." Right time for a system (build or GTM hire): you know who it is for, you are ready to run or supervise the work, and the process still lives in your head or in heroic bursts.
If you are in between, do not flip a coin between the two job posts. Spend thirty days making the system visible — write the rules, run the cap, do the Friday review — and then look again. Those thirty days are cheaper than a wrong salary.
A decision sheet you can fill in an hour
Answer yes or no, honestly:
- [ ] We can write who deserves a message and who never gets one
- [ ] We can show a list of this week's accounts that would survive a second look
- [ ] A person approves first touches, or writes them, and can explain why
- [ ] Replies are handled the same day, by a named person
- [ ] We have a Friday note we believe
- [ ] The product is ready to sell
- [ ] The bottleneck, if we had more hours, is running this motion — not inventing it
If the last box is the first yes, and the others are no, do not hire an SDR. If most boxes are yes, and you are declining conversations or skipping follow-up because of hours, an SDR (or a part-time executor) is in play. If you want the middle boxes to become yes and you do not have the weeks, a GTM engineer or a build-and-run team is in play — not as a synonym for SDR.
What I would tell a founder this quarter
Build the system first, at a scale you can see. Do not staff a queue you have not stood in. When you do hire, hire for the hole that is actually open, and write the first ninety days in verbs. If a recruiter or an agency wants to start with two SDRs and a stack, ask them what the motion is, in your accounts, and who approves the mail.
If you want help building the system before you hire, Kingdom of Kumar does that work on Grok and Claude for $500 a month, three-month minimum. You own the system, and you approve what goes out. That is not an SDR, and it is not a $135,000 GTM engineer. It is a way to get the middle boxes toward yes without pretending headcount is a process.
FAQ
Can one person be both the system-builder and the SDR?
For a while, at a small company, yes — often the founder, sometimes a very hands-on first hire. Call it what it is, and do not attach an SDR compensation plan to a job that is mostly building.
What if my investors expect an SDR?
Show them the decision sheet and last month's Friday notes. A quiet, true motion is a better story than a hired title on a bad list. If they still want headcount, ask which box they think a person will tick without a system.
Is "system first" just a way to sell your offer?
It is also how I would advise a team that never talks to us. You can build this with a sheet and a mailbox. Our offer is one way to have help. It should not be a reason you skip the honest yes/no boxes.