From SDR to AE: The Evidence File That Actually Gets You Promoted

13 min read

Quota gets you on the list. What gets you the AE seat is a file of evidence: recorded discovery, a deal you multi-threaded, an objection you fixed, and one account your prep saved.

Every SDR I talk to who wants the AE seat opens the same way. "I hit quota three quarters in a row." Good. That gets your name on the list. It does not get you the job.

Here is the uncomfortable part. Quota attainment tells a hiring manager that you can book meetings. The job you are applying for is not booking meetings. It is running a discovery call that changes what a buyer believes, holding a price under pressure from someone who negotiates for a living, and keeping a deal alive when your champion goes quiet for eleven days. Nothing in your booked-meetings number speaks to any of that. So the manager has to guess. And when managers guess, they promote the rep who is loudest in the pipeline meeting, or they hire externally because at least the external candidate has closed something.

The fix is to stop asking to be trusted and start handing over evidence. Build a file over a quarter. Four exhibits. Make it so specific that the decision stops being a judgment call about your potential and starts being a review of work you have already done.

What the hiring manager is actually deciding

When a sales leader promotes an SDR, they are taking on a very particular kind of risk. They are giving up a producing SDR — someone who is currently generating pipeline for the team — and putting them into a seat where it will take a full cycle before anyone knows whether it worked. If it does not work, they have lost twice.

So the question in their head is not "does this person deserve it." It is "can I picture this person on a call with a VP of Sales who has already cut two tools this year, and not lose the room."

That is a visualization problem. You solve visualization problems with footage, not adjectives. Every claim in your case for promotion should be answerable with "here, listen to minute nine."

Exhibit one: two or three recorded calls where you ran real discovery

This is the centerpiece and most SDRs get it wrong, because most SDRs have never run discovery. They have run qualification. Those are different animals and a good sales leader can hear the difference in about ninety seconds.

Qualification sounds like a form being filled in. How many reps do you have. What are you using today. Who else is involved in a decision like this. When are you looking to make a change. Every answer gets a "got it, great" and then the next question. The buyer is being processed.

Discovery sounds like a diagnosis. You ask a question, the buyer says something imprecise, and you go after the imprecision. That is the whole skill. "We're having some pipeline issues" is not an answer, it is a headline, and the rep who says "got it, and what does that look like week to week?" is doing the job. The rep who says "got it — and timeline for fixing that?" is not.

So how does an SDR get discovery calls to record when discovery is not officially their job? Two ways, and both are available to you right now.

The first is to extend your qualification calls. You already get live conversations on the phone. Most SDRs treat those as fifty seconds of pitch and a calendar link. Take the ones that are going well and go three questions deeper than your script asks for. You are not trying to close anything. You are trying to walk into the AE handoff with a diagnosis instead of a checkbox. Your AE will love you for it, and you will have a recording.

The second is to volunteer for the discovery calls nobody wants. Small accounts, weird verticals, inbound leads that came in through a form and look like a waste of an AE's hour. Ask your manager if you can run those end to end with an AE listening. You will get a yes far more often than you expect, because the alternative is that nobody works them at all.

When you pick the two or three calls that go in the file, do not pick your best-outcome calls. Pick your best-question calls. A call where you diagnosed a real problem and the buyer said "we're not going to do anything about this until next year" is better evidence than a call where a buyer who was already sold agreed to a demo. One shows skill. The other shows luck.

If your discovery instinct is still rough, work off a structure rather than vibes. The 25-minute diagnostic structure I use for discovery is built around getting to a quantified problem before you get anywhere near a solution, and it is the fastest way I know to stop sounding like a form. Run it three times on real calls and the difference in your recordings will be audible.

The timestamps matter more than the calls

Do not send a manager three forty-minute recordings. Nobody listens to that. Send three calls with two timestamps each and a sentence per timestamp.

"Minute 12 — she said 'our forecast is always off.' I asked what off meant in dollars last quarter and she went and found the number. That number is what the AE used in the business case."

"Minute 26 — I got the answer wrong. I jumped to our reporting feature before I understood who actually builds their forecast. You can hear him disengage. I have stopped doing that."

That second one is not a weakness. That is the single most promotable thing in the file. Sales leaders are not looking for someone with no bad habits. They are looking for someone who can hear their own tape and correct without being told.

Exhibit two: a deal you multi-threaded

Every AE loses deals to single-threading. Champion leaves, champion gets reorged, champion turns out to have no budget authority and never said so. The reps who survive their first year as an AE are the ones who instinctively go wide early.

As an SDR you are actually well positioned to prove this, because going wide is prospecting, and prospecting is what you do all day.

Pick one live opportunity your AE is working. Go to them and say: "I want to build the org map on this one. Can I work the other two functions?" Then actually do it. Find the RevOps person who will own implementation. Find the frontline manager whose team will use it. Find the finance contact who will be asked to sign. Reference the champion by name in your outreach — not as name-dropping, as context. "Priya asked me to make sure the reporting side of this holds up before we go further, and I think that is your world more than hers."

Document what you got. Who replied, who did not, what each of them cared about, and — the part that makes this exhibit land — where those cared-abouts conflicted. The champion wants faster ramp. The RevOps lead wants fewer tools in the stack. Those two people are going to disagree in a room you are not in. A rep who can articulate that disagreement in advance is a rep who is ready to close.

Write it up as half a page. Not a CRM screenshot. Half a page of prose that reads like someone who understands an organization, not someone who added contacts.

Exhibit three: an objection you used to handle badly

This is the exhibit that separates the promotion cases I would say yes to from the ones I would not.

Pick one objection you know you fumble. "We already have something for this." "Send me some information." "We're not looking at new tools until next fiscal." Find a recording of you handling it badly. Yes, on purpose. Then work on it for six weeks and find a recording of you handling it well.

Before and after, in your own voice, on real calls. There is no substitute for it and there is no faking it.

What does the "after" version sound like? Mostly it sounds slower. Almost every rep I have watched handles objections by talking faster and adding more reasons. The good version does the opposite. It acknowledges the objection at face value, asks one question about it, and gets the buyer to say more.

Bad: "Totally understand you have something in place — a lot of our customers were using that too before they switched, because what they found was..."

Better: "Makes sense. When you rolled that out, what was it supposed to fix?" Then wait. Half the time the buyer tells you what it did not fix, and you are back in a conversation instead of a debate.

If the objection you are working on is a pricing one, get very precise, because pricing objections from sales leaders are a different sport. They discount for a living and they can smell a rep who has never had to hold a number. The pricing negotiation script I use for selling into sales leaders is built on the premise that the first concession you make teaches the buyer everything about how the rest of the deal will go. Learn to trade instead of concede before you are in the seat, not after.

Exhibit four: one account where your prep changed the outcome

The first three exhibits are about skill. This one is about judgment, which is the harder thing to prove and the thing managers actually promote on.

Choose one account. Ideally one that had gone cold or one everybody had written off. Then do the work nobody has time to do. Read the last two earnings calls or the funding announcement. Read the job postings — job postings are the most under-used signal in prospecting because they tell you what a company is spending money on right now. Find the LinkedIn post where the new VP said what she was going to change in her first ninety days. Talk to a customer in the same vertical if you can get one.

Then write the one paragraph that only you could write, and use it.

The evidence is the sequence. Here is the account. Here is what everyone assumed. Here is what I found. Here is the line I used. Here is what happened. If what happened was a meeting that turned into pipeline, say so. If what happened was a polite no that told you the account is dead for two quarters, that counts too — you saved the team the cycles.

When you present this one, be honest about the time it took. If it took you ninety minutes of research to book one meeting, say that, and then say what you would do differently at AE volume. That answer — knowing when deep prep is worth it and when it is not — is a senior answer, and it is exactly what your manager is checking for.

How to build the file over a quarter without becoming annoying

Do not announce this. Do not send a Slack message saying you are building a promotion case. Just start.

In the first month, get your recording habit fixed. Listen to two of your own calls a week. Not to feel bad — to find one specific thing. Pick the moment where the energy changed and figure out what you said right before it. Start a running document with timestamps. This is boring and it is the whole job.

In the second month, go get the reps you are missing. This is when you ask for the small discovery calls, when you volunteer to multi-thread your AE's deal, and when you pick your one objection to fix. Tell your manager what you are working on in your one-to-one, framed as skill development rather than as a campaign. "I want to get better at handling 'we already have something.' Can you listen to two of my calls this month and tell me what you hear?" Managers say yes to that every time, and now they are involved in the story before you ask for anything.

In the third month, close the loop and write it up. Two pages maximum. Four exhibits, the timestamps, the org map, the before-and-after, the account. Then ask for the conversation.

Getting shadow time on closing calls without stepping on your AE

AEs are protective of late-stage calls, and they should be. A stranger on a negotiation call is a variable, and variables cost commission.

The way to get invited is to make yourself worth having on the call. Offer a job, not your presence. "I'll take notes and send you the follow-up within the hour so you can go straight into your next one." That is a real trade. Most AEs are behind on follow-ups and will take that deal.

The other move that works: ask to listen to the recording first and bring the AE two questions about it. Not "that was great." Something like "at minute 31 you let the silence run after you gave the number — was that deliberate?" Ask two of those and you will be invited live to the next one, because now you are someone who pays attention rather than someone who is watching.

When you do get on a demo or a late-stage call, know the shape of it before you join so you are not just spectating. Understanding how a demo lands with a team that is already cutting tools — where the buyer's real question is which of their existing line items dies if they buy yours — will change what you notice on the call. Watching without a framework teaches you almost nothing. Watching with one teaches you a lot.

And never, ever debrief the AE's call in a group setting. Do it privately or not at all.

Answering "why do you think you're ready"

You will get this question, and it is a trap in the sense that the obvious answer is the wrong one.

The obvious answer is a summary of your performance. "I've hit quota, I've been here eighteen months, I've trained two new SDRs." All true, all about the past, all about activity. It gives the manager nothing to visualize.

The answer that works is a demonstration in miniature. Something like:

"Three things. First, I've been running full discovery on inbound that came in under the AE threshold — there are two calls I'd want you to listen to, and I'll send you the timestamps rather than the whole recording. Second, on the Northwind deal I built the org map and found the RevOps lead who was going to block it on integrations, and I can walk you through where his priorities and the champion's actually conflict. Third, I was bad at 'we already have something.' I've got a call from March where I talked over it and a call from last week where I asked one question instead and got twelve more minutes. What I don't have yet is reps holding a price, and that's the thing I'd want to work on with you in the first sixty days."

That last sentence is not weakness. Naming the gap yourself is what tells a manager you have an accurate model of the job. Every rep who says they are ready for everything is telling you they do not know what the job is.

Then stop talking. Let them ask.

If they say not yet

Sometimes the answer is no, and sometimes it is honest — no open headcount, a territory that will not carve until next year, a leadership change. Get the criteria in writing anyway. "What would need to be true for this to be a yes in the next two quarters?" If the answer is specific, you have a plan. If the answer is vague after you handed over a two-page evidence file with timestamps, you have learned something important about whether this is the company where you become an AE.

Either way you have not wasted the quarter. The file travels. An external hiring manager will be even more impressed by it than your own, because they have never once had an SDR candidate send them timestamped discovery recordings and an org map.

What I would do this week

Start with the tape. Pull one call from last week, find the sixty seconds where you stopped listening and started reciting, and write down what you should have asked instead. That single exercise, done weekly, will do more for your promotion case than another quarter of hitting number.

And if the gap is that you do not have enough live reps to build the file from — which is the real constraint for most SDRs, because you cannot practice discovery on calls you are not allowed to run — that is exactly what we built DrillCall for. Run the objection you keep fumbling twenty times against a buyer who pushes back the way a real VP of Sales does, then go take the real call with the muscle already built. The recording you put in your evidence file has to be real. The reps that get you there do not.

Practise these calls

The playbooks behind this post — a scripted opener, the objections you will actually hear, and an AI buyer to run it against.

About the author

Timothy Yang

Founder & CEO, DrillCall

I build products by getting on the phone. Four businesses built and exited, including a micro-task marketplace with 170,000+ users, and the common thread in every one was the same: nothing moved until I picked up the phone and sold. Cold outreach, discovery calls, closing. The unglamorous work that actually creates revenue. Right now I am building DrillCall, an AI-powered voice training platform where sales reps practice live calls against realistic AI buyer personas, 310 of them across 31 industries, and get a scorecard after every call. Think flight simulator, but for cold calls. I also run Vibe Coding Club, a community of over 3,500 builders shipping products with AI, and I have spent time inside AWS and Dell, so I have seen how enterprise sales machines work from the inside as well as from the founder seat. What I care about: expected value thinking, fast iteration, and talking to customers before writing a line of code.

← All posts