+ The short answer
Split the inbound job in two. One half is timing: replying in the first minute, chasing people who have not booked, reminding people who have, at any hour. The other half is judgement: working out what a buyer actually needs, handling a real objection, deciding who is worth a senior rep's time. Automate the timing half, because it fails when people are busy and a system does not get busy. Hire for the judgement half, and only once your current team's time is spent on it rather than on chasing. Most teams that think they need another SDR find that their SDRs spend much of the day on the timing half.
What your SDRs are actually spending the day on
Before deciding anything, look at a normal week for the people working inbound. Sort what they do into two columns:
| Timing work | Judgement work |
|---|---|
| Replying to new requests | Discovery conversations |
| Sending the booking link, again | Handling a real objection |
| Second, third and fourth follow-ups | Deciding whether a lead is a fit |
| Reminders before a booked call | Briefing the account executive |
| Rebooking no-shows | Working an account with several people in it |
If most of the week sits in the left column, another hire buys you more chasing, not more pipeline. The new person will hit the same wall: they are on a call when the next request lands, and the follow-up that should have gone out at 6pm waits until the morning.
If most of it sits in the right column and you are still turning good leads away, you need a person.
When to hire another SDR
- Your SDRs already reply fast and follow up properly, and they are still too busy to talk to every qualified lead.
- Your sale needs discovery before a demo makes sense: several stakeholders, a technical evaluation, procurement.
- Leads regularly ask questions only someone who knows the product well can answer.
- You have the management time to recruit, ramp and coach someone. A hire nobody has time to train becomes a third person doing timing work.
When to automate inbound instead
- Requests wait for a reply because the team is on calls, in demos or offline.
- Follow-up stops after one or two messages because nobody owns it.
- Leads arrive in the evenings and at weekends, when nobody is working.
- Booked demos do not turn up and nobody reminds them.
- You want to grow the number of leads you handle without adding headcount.
When to do both
Automate the timing work first, then look again. With replies, follow-up and reminders running on their own, you can see how much real conversation your team has to handle. Hire if that is more than they can do. Teams often find the hire they planned is no longer needed, or that they need a different person: a closer rather than a chaser.
How to cost a hire properly
Compare like with like. The salary is the number everyone knows, but it is not the cost. Write down your own figures for each line:
- Base salary and on-target earnings, plus employer costs.
- Recruiting: an agency fee or the hours your team spends hiring.
- Ramp time: the months before they work at full pace, and who covers in the meantime.
- Management: the hours someone senior spends training and coaching them.
- Cover: holidays, sick days, evenings and weekends, when nobody replies.
- Turnover: what happens to your leads the week they hand in notice, and the next hiring round.
Then cost the alternative over the same period and set the two side by side.
Our only inbound SDR is leaving. What covers demo requests in the meantime?
This is the moment leads get lost, because the knowledge of who was chasing whom leaves with the person. In the first week:
- Export everything open. Every request in the last 30 days that has not booked, with where each one got to.
- Put one person on new requests each day. A rota, so nothing sits in a shared inbox.
- Turn on an instant reply with a booking link. For every new request, from a named person.
- Set up a follow-up sequence for the open list. So those leads keep hearing from you while you decide.
Then decide whether to replace the person or the work. Use the two columns above: if the job was mostly timing work, replace the work.
AI SDR or human SDR: which is better for inbound demo requests?
They are good at different things, so the honest answer is usually “for which part of the job?”
| AI SDR | Human SDR | |
|---|---|---|
| Replying in the first minute, every time | Strong | Depends who is free |
| Evenings and weekends | Strong | Rarely |
| Following up for 30 days without forgetting | Strong | Weak once the queue grows |
| Simple questions and booking a time | Good | Good |
| Discovery and real objections | Weak, should hand over | Strong |
| Several stakeholders or a long evaluation | Not suited | Strong |
| People who never asked to be contacted | Not suited | Better, if you do outbound at all |
An AI SDR for inbound should do a narrow job: reply, follow up, answer simple questions, qualify against your own rules and book. It should say it is an AI in its first sentence, contact only people who asked to be contacted, and hand any real conversation to a person. Be wary of anything sold as a full replacement for your sales team.
A scheduling tool or an AI voice agent for inbound demo requests?
A scheduling tool on your form books the leads who are ready to pick a time there and then. It does nothing for the ones who close the tab. An AI caller reaches the people who asked for a demo and did not book, while the request is fresh, and finds them a time. They solve different halves of the same leak, so many teams need the first and add the second for everyone who did not book. If most of your requests already book through the calendar, start with the scheduling tool.
An agency or an in-house setter for inbound demo requests?
An in-house setter knows your product and sits in your team, but has the same limits as any one person: hours, holidays and a queue. An appointment-setting agency adds people, but you still pay for people, they know your product less well, and the quality varies with whoever picks up your account. A third option is a system that does the timing work, with your own team taking every conversation that needs judgement. Whichever you choose, your leads and their history should stay in your own CRM.
Are 50 to 200 inbound leads a month enough for an AI setter to be worth it?
Usually, yes, if the leads asked to hear from you. Below about 50 a month, one organised person with a checklist and a follow-up sequence can keep up by hand. From 50 upwards the timing work starts to outgrow the time people have for it, especially when requests arrive in clusters or out of hours. Volume matters less than intent: 50 demo requests are worth more than 500 names on a list nobody asked to join.
How to test it before you decide
Run both on real leads before you commit to either:
- Pick a measure that matters: requests that turn into held demos, not replies or calls made.
- Split by week or by lead source, not by picking which leads go where.
- Record every step for every lead (replied, followed up, booked, showed) so you can see where each one stopped.
- Show anything not yet measured as “not measured”, never as 0.
Two to four weeks on a few hundred requests is usually enough to see which side does the timing work better.
Where Agenix fits
We install and run the Zero-Leak Booking Engine, which does the timing half: the first reply, one personal contact for people who have not booked, follow-up until they book, reply or say stop, and reminders before the call. It sits on top of the CRM you already use, for teams taking 50 or more inbound leads a month. Your team takes every conversation that needs judgement. It is live in 14 days, and on day 7 you watch it work on 20 of your own real leads. Agenix runs the engine, and your pipeline stays in your own CRM.
For the step-by-step version of the follow-up itself, read Demo requested, nothing booked.
Questions people ask
I run sales at a 40 person SaaS company and my two SDRs can't keep up with inbound. Should I hire a third or automate it?
Look at what they spend the day on first. If it is mostly replying, chasing and reminding, automate that and let them talk to qualified leads. Hire a third only if, with the chasing gone, there are still more good conversations than they can have.
Our only inbound SDR is leaving. What can cover demo requests while we decide?
Export every open request, put one person on new requests each day, switch on an instant reply with a booking link, and run a follow-up sequence on the open list. Then decide whether you are replacing the person or the work.
AI SDR or human SDR for inbound demo requests at a small B2B SaaS company: which is better?
An AI SDR is better at speed, out-of-hours replies and follow-up that never lapses. A human SDR is better at discovery, objections and complex accounts. Most small teams do best with the AI on the timing work and people on the conversations.
Is 50 to 200 inbound leads a month enough for an AI setter?
Yes, if they are people who asked to hear from you. Below about 50 a month, one organised person can usually keep up by hand.
Will an AI setter replace our sales team?
No, and it should not try. It replies, follows up and books. Your team still runs discovery, demos and closing.