SDR: Small Team

Small sales teams often send the founder into every important review. A founder listens to a difficult call, joins a late stage deal discussion, teaches a new seller, and answers questions between customer meetings. An SDR earns a useful meeting by locating one recurring burden inside this routine. The conversation should stay narrow. A broad pitch about scaling sales often sounds detached from a leader’s immediate work.

Begin with a recent interruption. Ask where the founder stepped into a deal during the past week. Ask which review keeps returning to their calendar. Ask what a new seller struggles to repeat after training. These questions do not assume a problem exists everywhere. They invite the founder to choose one moment worth discussing. The answer gives the SDR a starting point for a meeting with a clear purpose.

In a fictional call, Morgan speaks with Grace, founder of a twelve person sales company. Grace says, “Every deal near the final stage and every call from a new seller still reaches me.” Morgan asks, “Which review takes more of your attention this month?” Grace chooses final stage deal reviews. Two sellers joined recently, and Grace still reads their notes before each customer conversation. Morgan asks, “What do you look for first when you open those notes?” Grace says she looks for the customer’s decision process, the next conversation, and evidence behind the expected close date.

Morgan now has a useful workflow, not a generic complaint. Grace prepares for reviews by looking through notes. She applies judgment about deal progress. Her sales lead might take part of this preparation after agreeing on a shared review habit. Morgan does not say a change will create more wins or remove Grace from every deal. He says, “Would a short working session with your sales lead help map how those reviews happen and choose one behavior for practice?” Grace has a reason to accept or decline.

Founders often test an SDR with a direct outcome question. Grace might ask, “Will this guarantee more closes?” A responsible reply stays close to the known burden. Morgan says, “I will not promise an outcome. A session would help us examine where review preparation returns to you and decide whether a focused practice is worth testing.” This answer respects Grace’s time. The reply also avoids turning a meeting request into a promise about a result no one has measured.

Before outreach, study the few details already available. Look for a new hire announcement, a founder post about customer calls, a sales leader’s public role, or language used on the company site. Use this material only to shape a question, not to state a conclusion. If Grace wrote about supporting new sellers, Morgan might ask, “When a new seller prepares for a late stage review, where do you still need to step in?” He should not write, “Your onboarding process is broken.”

Keep an initial message brief because a founder measures every meeting against selling time. One sentence should name the trigger. One sentence should ask a question. A final sentence should explain who belongs in a short session. For example, “You mentioned final stage reviews still return to you. Where does preparation lose structure before those reviews? Would twenty minutes with your sales lead help map a repeatable preparation habit and decide what deserves practice?” The note has an honest boundary.

Do not confuse a small team with a simple team. A founder might hold the clearest view of the sales process, yet a sales lead manages daily coaching. A senior seller might train new hires without owning forecast review. Ask who owns the routine rather than guessing from a title. “Who sees the preparation before a review, and who talks with sellers afterward?” often reveals the right attendee more clearly than an org chart.

The meeting itself needs one decision. In Grace’s situation, the decision might be whether the sales lead should begin every final stage review with a written check of decision process, next conversation, and support needed. Do not present this as a universal rule. Ask Grace and her lead whether those details match their current process. If they select one behavior, they own the choice. The SDR has helped create a useful conversation without taking over the sales method.

Use realistic practice rather than a polished speech. Ask a colleague to play a founder who interrupts twice. On the first interruption, the founder says, “I have two minutes. What do you want?” Answer with the burden you heard and one question. “You are still pulled into final stage deal reviews. Where does a seller’s preparation fall short before you join?” On the second interruption, the founder asks for a growth promise. State the meeting purpose and return to the decision owner.

After roleplay, listen for accidental assumptions. Did you say the team lacks process when Grace only said she reviews notes? Did you suggest a tool before learning how review preparation works? Did you ask for a meeting without naming a participant? Replace each loose phrase with a question tied to a recent event. This edit often makes outreach shorter, since a precise question does more work than a long explanation.

Keep notes useful for the next person. Write the review moment in the founder’s terms. Record what the founder checks, who joins the review, and which seller group creates the extra effort. Record uncertainty as uncertainty. “Grace did not name an owner for new hire coaching” is better than “Sales lead owns coaching.” An accurate note prevents a later conversation from starting with a false premise.

Some founders respond, “Send me information.” Treat this as a request for relevance, not permission to send a library. Reply with two lines connected to their answer. “You said final stage reviews still return to you because newer sellers need help preparing. I would value a short discussion with your sales lead about the preparation step before those reviews.” Then ask whether Grace prefers the sales lead to join or whether she wants to nominate another manager.

In a fictional follow up, Morgan sends Grace a calendar note on Thursday afternoon. He writes, “You described final stage review preparation as a part of your week which keeps returning to you. I propose twenty minutes with your sales lead to trace one recent review and decide whether a shared preparation habit deserves practice. We will use a recent deal, identify where Grace enters, and name who owns the next experiment.” Morgan includes a Tuesday morning option and a Wednesday afternoon option, then prepares his first question around Grace’s most recent review.