Top-Down vs Bottom-Up: Should You Call the Executive or the Person With the Problem?

There is a version of this argument on every sales floor. The AE says go to the top, always, because the VP can sign. The SDR who is actually dialing says the VP never picks up and the manager does, and the manager will tell you everything. Both people are right about their own week and wrong about the general case.

Top-down and bottom-up are not personality preferences. They are two different deals that happen to end with the same logo on a contract. They have different cycle shapes, different failure modes, and different reasons you lose. Picking one on instinct, or picking whichever one your last deal came from, is how territories go quiet for a quarter.

So let me lay out what each door actually gives you, what it costs, and how to tell which one your market rewards.

What you get from the executive door

When you open at the VP, the CISO, the COO, the CMIO, you are buying three things.

The first is authority. Not signature authority in the procurement sense — that matters less than people think — but the authority to say "this is a priority, go look at it." That sentence collapses weeks. The second is speed. An executive who is interested does not schedule a working session in three weeks, they say "grab twenty minutes Thursday and bring whoever needs to be there." The third, and the one people undervalue most, is the ability to override the org's immune system. Every large company has a set of reflexes designed to stop new vendors: security review, a preferred-supplier list, a procurement calendar, a team that already bought something adjacent last year and does not want to admit it is not working. A sponsor high enough to be annoyed by those reflexes can walk them.

Here is what it costs. You are talking to someone who does not have the problem. They own the outcome. They have a version of the problem that has been summarized for them twice, by people who had reasons to shade it. Ask an executive what is broken and you get the board-deck version, which is directionally true and operationally useless. You cannot build a business case on it, and if you try, the person who actually does the work will read your deck and quietly kill it.

And then there is the real risk: delegation. You get the meeting, you do a decent job, and the executive says "this is interesting, let me connect you with Sarah, she owns this." Most reps treat that as a win. It usually is not. It is usually a demotion, and Sarah can smell it. She got an email with no context saying take this call, from a boss who is not going to follow up, about a vendor she did not choose. She takes the meeting because she has to. She does not advocate, because nothing about the handoff told her she should. Then the deal dies in a way nobody can point at.

I have watched this happen to good reps more times than any other single pattern in enterprise prospecting. The executive meeting was fine. The handoff was the whole game and nobody played it.

What you get from the practitioner door

Open at the analyst, the plant manager, the ops lead, the person who touches the thing every day, and you buy something the executive cannot sell you: truth.

You find out what the workflow actually is, not what the process document says. You find out that the tool they bought two years ago is only used by two people and everyone else exports to a spreadsheet. You find out the real number of tickets, the real cycle time, the real reason the last vendor got dropped. You get language you can repeat back to an executive that makes you sound like you have been inside the building.

You also get someone who cares. That is not sentiment, it is mechanics. The person with the problem is the only person in the account who wakes up wanting your product to exist. Executives have twenty priorities and yours is not in the top five. The practitioner has one bad Tuesday a week and you might fix it. That energy is what carries a deal through the boring middle where nothing is happening and the AE is on to other things.

The cost is obvious and it is brutal. Bottom-up deals stall the moment they hit someone who has never heard of you. Your champion goes to their boss, who goes to their boss, and somewhere in that chain a person who was not in any of your calls asks a reasonable question — why this vendor, why now, why not the incumbent — and your champion cannot answer it in the language that person speaks. They can answer it in their own language, perfectly. That is the problem. The case that convinced them is an operational case, and it is arriving in front of someone who buys on risk, on strategy, on what happens to the budget line.

Bottom-up deals also get smaller. A practitioner scopes to their own team, because that is the world they can see and the world they can defend. You end up selling one department a pilot when the actual problem exists in six departments, and expanding later is a whole second sale against a much harder incumbent — you.

Comparing the two on the things that actually move

Cycle length

Top-down is faster when it works and slower when it half-works. A genuinely engaged executive compresses a deal in a way nothing else does. But a delegated executive meeting produces the longest cycles I have seen, because you now have to rebuild credibility from zero with someone who is annoyed, while the exec who introduced you loses interest.

Bottom-up is more consistent and generally slower. You spend real time on discovery, then real time building the internal case, then real time waiting for a budget conversation that happens on someone else's calendar. Fewer surprises, more elapsed weeks.

Win rate

The honest answer is that they lose in different places. Top-down deals lose late, at the point where the people who have to run the thing find something you did not know about their environment. Bottom-up deals lose late too, but at the budget line, where nobody senior enough was ever involved.

What that means practically: your loss reasons tell you which door you have been using. If your losses are "technical fit" and "they went with the incumbent after evaluation," you are running top-down without ever earning practitioner buy-in. If your losses are "no budget," "timing," and "deprioritized," you are running bottom-up and never getting above your champion.

Deal size

Top-down scopes bigger. An executive thinks in terms of the whole function, and they are used to signing for the whole function. Bottom-up scopes to the team in the room, then you fight for expansion.

If your product only makes sense at scale — if a single-team deployment is genuinely worse than nothing — you have to go top-down whether you like it or not, because the practitioner will scope you into a pilot that cannot prove anything.

Multi-threading risk

This is the one that decides most of it. Both entries are single-threaded at the start. The question is which one is easier to thread outward from.

Going down from an executive is structurally easy and socially hard. The exec can introduce you to anyone in one email. But every one of those people knows you came from above, and some of them will treat you as a thing being done to them.

Going up from a practitioner is structurally hard and socially easy. Your champion cannot summon their VP. But if they do get you in the room, you arrive pre-vouched by someone the VP trusts on the details.

So: top-down needs handoff mechanics. Bottom-up needs escalation mechanics. Most reps have neither, which is why most deals are single-threaded and most single-threaded deals die.

The rule of thumb by industry

The useful question is not which is better. It is: in this market, who owns the pain and who owns the decision, and are they the same person?

Executive-first: cybersecurity and clinical

Go top-down in security. The pain is owned at the top because the consequence is owned at the top. A CISO or a SOC leader is personally accountable for outcomes they cannot fully control, which makes them unusually willing to take a call from someone who has something specific to say about that exposure. Meanwhile the analysts are drowning, have no budget authority, and have watched leadership buy tools they did not ask for. Starting with an analyst in a security org gets you a friendly conversation and nothing else. Start at the leader and earn the room, which is exactly what our cybersecurity cold call script for getting a SOC leader to book 25 minutes is built around.

Same logic in clinical. Healthcare has the steepest hierarchy of any market I have sold into. A nurse manager or a department lead can describe the problem beautifully and cannot move a dollar. Clinical decisions route through people with titles like CMIO and VP of Clinical Operations, and those people are gatekept by design. But they are also the only ones who can reconcile the clinical case with the IT case with the compliance case, and if you have not got one of them, you do not have a deal. The healthcare cold call script for CMIOs and VPs of clinical operations exists because that first conversation has to carry more weight than it does in other verticals.

The common thread: regulated markets with concentrated accountability. When one person's name is on the risk, talk to that person.

Practitioner-first: manufacturing and freight ops

Go bottom-up in manufacturing. A plant manager owns their plant with a degree of autonomy that surprises people who have only sold into software companies. They know their line, their downtime, their labor problem, and in many organizations they can start something without asking corporate. They are also deeply, reasonably suspicious of anyone in a nice shirt who has never stood on a floor. Credibility here is technical and it is earned in the first ninety seconds, which is the whole premise behind our manufacturing cold call script for earning 20 minutes with a plant manager. Come in from corporate and you are one more head-office initiative.

Freight and 3PL is the same shape for different reasons. Brokerage operations run on the detail — lane mix, carrier relationships, how they actually cover a load at four in the afternoon. A COO can tell you margin is compressed. Only the ops lead can tell you where. And in this market a discovery call that stays abstract is a discovery call you lose, which is why the freight and 3PL discovery questions go straight at the operational specifics rather than circling strategy.

The common thread: operator-led businesses where the person closest to the work has real authority and real skepticism of outsiders.

The delegation handoff, which is the actual skill

Assume you went top-down and it worked. The executive says the sentence: "Let me put you in touch with Sarah."

Do not say thank you and hang up. That is a demotion. Turn it into a warm introduction, in the meeting, out loud, in about ninety seconds.

Step one: ask what Sarah owns and what she is measured on. "Before you connect us — what does Sarah own here, and what is she being measured on this year?" You now know how to open with her, and you have signalled to the exec that you intend to be useful to her rather than to use her.

Step two: ask what he wants out of it. "If Sarah comes back to you in three weeks, what would make you say this was worth her time?" This is the important one. You are converting a brush-off into a specification. If he cannot answer, it was a brush-off and you should know that now rather than in six weeks.

Step three: ask for the intro in his words, not yours. "Would you be willing to send two lines — what you want her to look at and why you thought of it? I will do the rest." Two lines from him beats two paragraphs from you. If he offers to have his assistant set it up, ask him to send the note first anyway.

Step four: propose the loop back. "After I have met with her, do you want a short summary from me, or would you rather hear it from her?" Either answer is fine. What matters is that you have established the executive will hear about this again, which is the single thing that changes how Sarah treats the meeting.

Then when you get Sarah on the phone, open by giving her control, not by leaning on the exec's name: "Mark asked me to walk you through this, but honestly you know this area far better than he does, so I would rather spend most of the time on what you are actually dealing with. If it is not relevant, tell me and I will go back and tell him that." Give her a real exit and she will stop treating you as an obligation.

The reverse move, escalating from a practitioner, runs on the same logic. You never ask your champion to "introduce me to your VP." You ask a smaller question: "When something like this gets funded here, whose budget does it come out of, and what does that person need to see?" Then you offer to build the thing that person needs to see, with your champion, and you ask to be in the room when it is presented — not to present it, but to answer questions. Champions say yes to that far more often than to an introduction request, because you are reducing their work instead of adding to it.

When you genuinely cannot tell

Run both, deliberately, at different accounts, and read the loss reasons after a quarter. Not the CRM dropdown — the actual sentence the buyer said. That will tell you which door your market opens.

And if you are in a market where the pain and the money sit in different places and neither is dominant, the answer is that you open wherever you can get a real conversation and then immediately buy the other thread. First meeting, always: "Who else would need to be part of this, and what do they care about that you don't?"

If I were building this into a team's habits, I would not do it with a memo. I would take the delegation handoff above, write it as a four-question sequence, and drill it until reps can run it under pressure without sounding like they are reading — which is exactly the kind of narrow, high-consequence moment we built DrillCall to rehearse, because it is the ninety seconds most reps have never practiced once.

Authority or truth. You need both. The only question is which one you are willing to work harder to go get.