SDR to AE: Build the Promotion Case Over 90 Days, Not the Week Before You Ask

13 min read

Most SDRs pitch themselves on meetings booked — the one number their manager already knows. Here is the evidence that actually earns the AE seat, and how to build it in 90 days.

The ask usually sounds the same. A rep books time with their manager, opens a doc, and walks through the number of meetings they set last quarter. Then they say some version of "I think I'm ready for an AE seat."

And the manager nods, because the manager already knows that number. They look at it every Monday. They report it upward. You just spent your one high-leverage conversation reciting a metric your boss could recite in his sleep, and worse, you spent it on the one metric that says nothing about whether you can carry a quota.

Booking meetings and closing deals are different jobs. They share a phone and almost nothing else. Prospecting rewards volume, resilience, and a tight fifteen-second reason to keep talking. Closing rewards patience, multi-threading, sequencing, the ability to sit in silence after you say a price. An SDR who is excellent at the first thing has given his manager exactly zero evidence about the second. That gap is the whole problem, and it is the gap your case has to close.

So build the case over ninety days. Not the week before you ask. The week before you ask, all you can do is assemble what already exists, and what already exists is a meetings number.

Why "meetings booked" is the wrong currency

Here is what your manager is actually risking when he promotes you. He gives up a producing SDR, which hurts him immediately and measurably. He takes on an unproven AE, which shows up as a hole in someone's pipeline two quarters from now. And he has to go argue for you in a room with other managers, some of whom have their own candidate.

That's the trade. Your job is to make it obviously worth taking.

Meetings booked does not do that, because everyone in the room knows the failure mode. The SDR who books everything that moves, whose meetings show up as no-shows, whose accepted opportunities get kicked back by AEs the following week. Volume without quality is a known pattern, and the number alone doesn't distinguish you from it.

What does distinguish you is evidence from the part of the deal that comes after the meeting is set. That is where AEs live. So that is where your proof has to come from.

The four things that actually make the case

One: held meetings that became pipeline, documented by you

Not meetings booked. Meetings held, and of those, which ones turned into a real opportunity, and of those, which ones closed.

Almost no SDR I have talked to tracks this. They hand off the meeting and the record ends. The CRM tracks it, in theory, but nobody has pulled that view and put your name on it. Do it yourself, starting today, and keep it as a running document.

A line per meeting. Account, title, how it was sourced, whether it held, what stage it reached, what happened to it. Keep the losses in. A rep who shows me twenty meetings, eleven that held, six that became opportunities, and can tell me exactly why five of the eleven died, is telling me he understands the sale. A rep who shows me only the winners is telling me he doesn't yet know what a pattern looks like.

The reason this matters more than the raw count: it moves you from "activity guy" to "pipeline guy." Pipeline is the currency AEs get judged in. Start speaking it three months before you ask for the title.

And there is a second-order effect. Once you're tracking held-and-converted rather than booked, your prospecting gets better on its own. You start disqualifying earlier. You stop dragging in the VP who agreed to a call to make you stop calling. Your AEs notice within a few weeks, which conveniently sets up the fourth piece of the case.

Two: two or three deals where you influenced the middle

This is the piece almost nobody has, and it is the piece that decides the conversation.

The middle of a deal is everything between the first meeting and the proposal. Multi-threading into a second and third stakeholder. Running a real discovery conversation instead of a demo request. Handling a pricing question in the moment without either flinching or blurting out a discount. Building the business case. Keeping a deal alive through a reorg.

You do not need a quota to touch any of that. You need an AE who will let you in, and most AEs will, because the middle of a deal is unglamorous work they'd love help with.

Ask for specific jobs, not vague involvement. "Can I sit in on the discovery call and run the last ten minutes?" is a real ask. "Let me know if I can help" is not. Some jobs that AEs hand over readily:

Build the stakeholder map for an open opportunity and go source the two people missing from it. You already prospect for a living; finding the director of RevOps who never got invited is your native skill. Bring the AE two warm names and you have influenced the middle of that deal in a way that shows up in the record.

Write the recap email after discovery. The one that mirrors back the problem in the buyer's own words and confirms the next step. This is harder than it looks and it is the fastest way to prove you were listening rather than waiting to talk.

Run the first fifteen minutes of a discovery call while the AE listens. If you want a structure to work from before you do that live, the twenty-five minute discovery framework for selling into VPs and SDR managers is the shape I'd steal — problem, impact, sequence, next step, in that order, with the impact question earning the right to everything after it.

Take the pricing question. When a prospect asks "what does this cost" on the first call, most SDRs hand it off, and reasonably so. But if you've prepped, you can answer it. Not with a discount, not with an apology, just a straight range and a redirect into scope. I've written up how I handle that when the buyer is a sales leader who negotiates for a living in the pricing negotiation script, and the core move is the same no matter who's across the table: give the number, then ask the question that puts the number in context. What that looks like out loud:

"It lands between X and Y depending on how many seats and whether you want the onboarding piece. Before I give you a real number — how many reps would be in it in the first ninety days?"

That's it. No hedge, no "well, it depends." You said a number and stayed in the conversation. If you can do that once, on a recorded call, in front of an AE, you have proof of something a meetings count can never show.

Three deals like this is plenty. You don't need a portfolio. You need enough that when your manager asks "can he close?", there's something in his head other than a shrug.

Three: evidence you can be coached

This is the one that separates the reps who get promoted from the reps who are merely good.

Managers are not looking for a finished AE. They are looking for someone who improves fast when told what to fix, because a new AE is going to be told what to fix constantly for the first two quarters. The safest bet in the room is the rep who has already demonstrated that loop.

How you demonstrate it: pick one objection, one you actually lose on, and gather two call recordings. One from early in the quarter where you handled it badly. One from later where you handled it well. Bring both.

A before-and-after on the same objection, in your own voice, is the most persuasive artifact an SDR can hold. It says: give me feedback and I will convert it into behavior. It also says you listen to your own calls, which more than half the reps I've talked to still don't do because it's uncomfortable. It is uncomfortable. Do it anyway.

Pick the objection that costs you the most, not the one you're closest to solving. "We already have a vendor." "Send me something." "I'm not the right person" from someone who is obviously the right person. Work one for three weeks, get the recording, move to the next.

When you present these, don't editorialize. Play thirty seconds of the bad one, thirty of the good one, and say what changed and who told you to change it. Naming the person who coached you is not sucking up. It's showing that the feedback loop in this org works on you, which is exactly the thing being evaluated.

Four: an AE who vouches for you without being asked

The promotion conversation does not happen in the room with you. It happens in a manager meeting you're not in, and someone says your name, and either an AE has already said something good about you or nobody has.

You cannot manufacture this at the end. You can earn it over ninety days by being useful to two or three AEs in a way that costs them nothing.

Be the SDR who shows up to their calls prepared. Who sends the account research before it's asked for. Who books meetings that hold. Who takes the callback at 5:40pm because the AE is in another meeting. Who never, ever makes them clean up a CRM record.

And then, separately, ask one of them directly: "If my name comes up for an AE seat, would you back me? And if not, what would have to change first?" That second half is the important half. Ask it early enough that the answer is still actionable. Day one, not day eighty-nine.

The answer you're afraid of — "honestly, your meetings are hit or miss" — is the most valuable sentence you'll hear all quarter. It gives you ninety days to fix it. Ask it in week twelve and it's just a rejection with extra steps.

The conversation to have on day one

Most SDRs treat the promotion ask as a single event. It should be a project you kick off with your manager, out loud, at the start.

Here's roughly what I'd say:

"I want to be an AE here. Not today — I know I'm not ready. I'd like to spend the next quarter building the case, and I want to build the case you'd actually need to see, not the one I'd guess at. So: what would have to be true about me in ninety days for you to put my name forward? And what's the thing that would disqualify me?"

That conversation does four things at once. It tells your manager you're ambitious, which he'd rather know than not know. It gets you the real criteria instead of the ones on the career ladder doc. It creates a checkpoint you can return to. And it makes him partly invested — a manager who told you what to work on has some stake in you doing it.

Then actually schedule the checkpoints. Thirty, sixty, ninety. Fifteen minutes each. Bring the pipeline doc, the deal involvement, the recordings. Don't ask for anything at thirty or sixty. Just show the work and ask what's missing.

If your manager is the kind who avoids these conversations, structure them yourself. The dynamic of a rep bringing evidence to a manager who'd rather talk about the number is a version of the problem I wrote about in the two-quarter miss 1:1 playbook — the conversation only gets useful when someone puts a specific artifact on the table instead of a feeling. Be the one who puts it there.

What to do when there's no open seat

Sometimes you do all of this and the honest answer is "there's no headcount." That's not a rejection, but it's also not nothing, and you should handle it precisely.

Ask two questions. When does headcount get decided, and what's the trigger — a bookings number, a fiscal year, a new territory? And: if a seat opened next month, am I the name that goes in it?

If the answer to the second is yes, you have a real commitment and you should get it in writing somewhere, even just a recap email you send after the meeting. "Just to confirm what we discussed — when the next AE seat opens on the team, I'm the first name up." Send it. People honor things they've seen in writing far more reliably than things they've said.

If the answer is vague, that's your answer.

Meanwhile, keep building. The case you assembled transfers. A documented pipeline record, three deals you influenced, before-and-after recordings, and a reference — that's a portfolio, and it works in an interview at another company at least as well as it works internally. Better, in some ways, because an outside hiring manager has nothing else to go on and you'll be the only candidate who brought evidence.

Reading whether the org promotes internally at all

Before you spend a quarter on this, spend an hour on this.

Go find the AEs on your team. How many of them were SDRs at this company? Not at any company — at this one. If it's several, the path is real and you should run at it. If it's zero, and every AE was hired in from outside with three years of closing experience, you are not looking at a career ladder. You are looking at a job description that happens to have "path to AE" in the recruiting copy.

A few other tells. Does anyone on the leadership team talk about internal promotions by name, publicly? Is there a written ramp for SDRs moving into a closing role, or does everyone describe it as "case by case"? When an AE quits, does the backfill get posted externally the same week?

And the direct one: ask your manager how many SDRs he's promoted, and where they are now. Managers who've done it will tell you the story in detail, because they're proud of it. Managers who haven't will change the subject to the career framework.

None of this is a reason to stop performing. It's a reason to know what game you're in.

When leaving is the faster path

I'll say the thing most sales content won't. Sometimes the fastest route from SDR to AE is a different logo.

If you've been an SDR for a while, you're hitting the number, you've had the day-one conversation and the thirty and sixty-day checkpoints, and the answer is still soft — the org has told you what it thinks. Believe it. The market for a proven SDR with documented pipeline influence is not thin, especially at companies one stage earlier than yours, where the AE bar is lower and the ramp is faster.

The move is not to quit in frustration. It's to interview with the same evidence you built for the internal case. When a hiring manager asks why you're ready to close, you don't say "I've booked a lot of meetings." You open the doc, walk him through the deals you influenced, play him the two recordings, and give him the name of an AE who'll take his call. Almost nobody interviewing for a first closing role does this. You'll be the only one in the process with proof.

The thing to avoid is leaving with nothing in hand. If you're going to move, move from a position where you've already done the ninety days. The work is the same either way — it just gets spent in a different building.

Where I'd start this week

Open a doc. Put every meeting you've set this quarter in it, with what happened after. That's an afternoon and it changes what you can say about yourself.

Then pick one AE and ask for one job on one open deal.

Then record your calls and listen to them, which is the part everyone skips.

That last one is where I'd point you at DrillCall. The reason before-and-after recordings are rare is that reps only get one live attempt at each objection, and the reps in the deal are the ones who get the reps. If you want to close the gap between the SDR job you have and the AE job you want, drill the pieces of the closing motion you don't currently get to practice — the pricing question, the multi-stakeholder discovery, the moment the champion goes quiet — until they're boring. Then go run them live, record it, and you'll have the artifact.

Ninety days from now, you'll either have a case or a meetings number. It's mostly a matter of what you started tracking today.

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