Enterprise sales from inside the buyer

Where this lesson sits. Lesson 5 of 7 in How Selling Works. Builds on: The pipeline and the math. Next: Personal sales (you are the product).

Imagine a deal that took 14 months from the first email to the signed contract. Tell the story from inside the buyer’s head, not yours.

Month one: a director at a 5,000-person company sees your post on Reddit, clicks through, signs up for your newsletter. They tell nobody. Month two: a problem at work makes them recall your name. They book a call. They do not have authority to sign anything. They just want to know if it’s real. Month three: they tell their manager. Their manager makes them a “small evaluation team” of two more people who do not quite know what they are doing. Month five: the team writes an internal memo. The director’s VP reads it, asks for a security review and a reference call. Month seven: legal gets involved. Legal re-opens three terms that the director thought were settled. Month nine: the CFO asks “do we need this now or can we wait six months?” The director has to write a justification. Month eleven: contracts go back and forth four times. Month thirteen: an exec from a different team walks into a meeting and says “wait, why this vendor?” The director has to re-defend the choice. Month fourteen: signed.

You, the seller, were in maybe 12 of those meetings. The other 50+ happened without you. The deal was won or lost in those rooms.

The shape of the buyer’s organization

Most public enterprise content names four roles: champion, economic buyer, technical buyer, blocker. Useful, but incomplete. Add three more: the coach, the executive sponsor, and the bystander who could become a blocker.

Champion. The person who wants this to happen and will spend internal capital to make it happen. They are usually not the budget owner. They are the person whose work gets noticeably better if you ship.

Economic buyer. The person who controls the budget line. Often a VP or a director-of-finance. They never care about your features. They care about ROI, predictability, and what happens if it fails.

Technical buyer. The person responsible for “does this actually work in our environment.” Security, IT, data engineering, infrastructure. Their default is no, because their job is to find reasons to say no.

Blocker. The person whose existing work or workflow is threatened by your thing. Sometimes obvious (the team that built the in-house tool you would replace). Sometimes invisible (a director in a different group who thinks budget should go to their initiative instead).

Coach. A friendly person inside the company who tells you what is actually happening, including things the champion does not know. The coach is sometimes the champion, but often not. A coach is invaluable and rare.

Executive sponsor. The level above the economic buyer. They usually do not engage until late. When they do, they ask one question: “why this vendor and not the other two.” The champion must have an answer ready.

Bystander turned blocker. The exec from another team who walks into the meeting at month thirteen. They were not in any prior conversation. They have no context. They have the political weight to kill the deal in one sentence.

Naming these roles is half the work. Knowing who plays each one in this specific deal is the other half.

The buyer’s career-risk map (the real decision driver)

Enterprise buyers are not deciding on features. They are deciding on personal career risk.

The champion is risking their reputation. If this works, they get a small career bump (and probably no credit, because the exec will take it). If this fails, they get a meaningful career hit (and they will definitely take the blame). The asymmetry is huge, and it is the single most important fact about how the deal will move.

The economic buyer is risking budget allocation. If they sign and it fails, they have to explain to their boss why this line item was a waste. Their default is to delay rather than to commit.

The technical buyer is risking incident calls. If your thing breaks something in production, they get paged. Their default is to delay too.

The way the deal actually advances is by lowering each person’s personal risk. For the champion: give them air cover (“here are three customers exactly like us who ran this in production for 12 months without an incident”). For the economic buyer: give them a clear, auditable rollback plan and a graduated commitment (“you can cancel for any reason in the first 90 days”). For the technical buyer: give them direct access to your engineers and a security pack before they ask for one.

When you read enterprise sales content that talks about “selling on value,” what it actually means is: find the person whose personal career is most affected by this decision, and lower their risk.

Procurement re-litigation

Here is something most early-career sellers learn the painful way. By month seven, you and the champion have agreed on most terms. The deal feels close. Then legal gets involved, and legal starts at the beginning. The MSA template they hand you reopens terms that were already settled. The liability cap. The indemnification language. The data-residency requirement. The termination-for-convenience clause. None of which the champion or the economic buyer cared about, but all of which legal cares about a lot.

This is not bad faith. It is how procurement works. Legal’s job is to protect the company from a hypothetical worst-case version of you that none of the buyers in the room ever imagined.

The seller’s job at this stage is patience plus preparation. Have a redlined MSA ready. Have a written response to the top 20 procurement objections you have heard before. Have a security pack (SOC 2, pen test summary, data-flow diagram, sub-processor list) ready before they ask. The deals that survive procurement are the ones where you make legal’s job easy, not the ones where you push back on every clause.

A 5-question stakeholder check before the first call

Most “enterprise opportunities” are not real. They are a director asking a curiosity question that will never become a budgeted line item. Spending six months on a fake enterprise deal is the worst time-cost mistake in B2B sales.

Before your first call, get answers (from the prospect or from public sources) to these five.

1. Do they have a budget line for this kind of thing, this fiscal year? If not, the deal is at least 6 months out and probably 18.
2. Is there a named project or initiative this would land inside? If not, the person you are talking to is exploring, not buying.
3. Have they evaluated and rejected a similar vendor in the last 24 months? If yes, ask what happened. The answer tells you everything.
4. Who else inside the company will care if this changes? If they cannot name two other people, they probably do not have the political weight to drive the decision.
5. What is their procurement process for software in this price range? If they hesitate or guess, they have not done this before, and the cycle will be longer than they think.

You can ask these in the first 15 minutes. If three out of five answers are weak, the deal is likely not real this year. That’s useful information.

When an enterprise deal is fake

The polite-and-curious meeting is the most common enterprise deal pattern, and almost nobody talks about it openly. A director takes the call. Asks intelligent questions. Says “very interesting” several times. Promises to “loop in the team.” Then disappears for three months. Then resurfaces with a vague timeline and asks for a longer demo.

There is no actual project. There is no budget. The director is doing market research, or filling time, or genuinely curious without authority. None of this is bad behavior. It is just not a deal.

The honest move, around month two, is to name it gently. “I want to be straight about something. I have spent a couple of meetings with you and I love the conversation, but I have not seen the signals that suggest there’s an active project on your side. If I am reading this wrong, I would love to know. If I am reading it right, I’d like to step back so we are not wasting each other’s time. We can stay in touch and pick it back up if the situation changes.”

Half of those messages get a reply that says “honestly, you are right, we are not actually buying anything this year.” That is great information. The other half get a reply that says “wait, no, we ARE serious, let me get you in front of [actual decision maker].” That is even better information. The third path, where they go silent, also tells you to close the deal in your CRM and move on.

Calling the fake deal a fake deal early is a high-skill move. It feels like leaving money on the table. It is actually one of the highest-return hours of your enterprise sales week.

---

A note from the team. This course is from TAKE INTEREST Inc. We build tools for people whose work depends on remembering context. Every conversation, every commitment, every reason a deal moved or did not. If you are in enterprise sales, every meeting that happened without you is the meeting that decided the deal. Remembering what was said, by whom, and when, is the difference between winning and losing month thirteen. We are open to design partners. The contact form is the door. Short message, ~48 hour response.

Take Interest Inc. (2026). Enterprise sales from inside the buyer. Take Interest. https://takeinterest.ai/blog/enterprise-sales-from-the-inside