Enterprise Sales

Teams used to selling to small customers kept hitting the same wall when they went after big ones. Someone watches the demo, likes it, even says "my team wants this" — and then the thread goes quiet. Ask a few weeks later and the answer is that it's been passed upstairs and nothing has come back.

The problem was picking the wrong person to convince. At a company of 3,000 people, a new tool doesn't get adopted because the department that would use it agrees. The executive who holds the budget, the security reviewer who wants to know where customer data goes, the legal team that intends to edit the contract, and the procurement team comparing prices against other vendors all enter in turn. They ask different things, and one "no" ends it. The person who took the first meeting can bring those people into the room but cannot decide for them.

Enterprise sales is what you get when you accept that structure and re-sequence the work around it. Instead of trying to win on one conversation, you map who is involved in the decision and clear them one at a time. A company that decides to serve enterprise customers changes how it sells at the same time.

A single deal breaks into six stages, and at each one you decide whether to continue or drop it.

1. Qualify the opportunity. Does the customer actually intend to solve this problem now, and is there room in this year's budget? A no here means six months spent for nothing no matter how much they liked the demo.
2. Map the decision. Write down the buying committee — everyone involved in this deal and what each of them is checking. Then find one champion, someone inside who argues for you. They speak in meetings you can't attend, and without one the deal stalls quietly.
3. Get a small group using it. Put one department on it for two or three months of real work and write the results up as numbers. "Finding a document went from eight minutes to two" is what gets used to request budget in the next stage.
4. Clear the reviews. Answer the security questionnaire, work through the clauses in legal's draft contract, and submit a proposal setting out scope and price. This stage alone often runs two or three months, and it's where most deals die.
5. Settle the terms. Price, contract length, what happens financially during an outage, and the conditions for cancelling. Procurement's job is to cut the price, so quote with room to be cut.
6. Prepare for after signature. Signing starts the rollout rather than ending the deal. A tool nobody actually uses drops out at renewal a year later.

One person carries the whole sequence. That role is the account executive (AE). Since each deal runs half a year or more, one AE can hold fifteen to twenty accounts at a time, and only three or four of them will close.

The test is the average contract value. Work out what one deal costs to win and the answer falls out. Salary for the person running it, plus engineering support and travel, comes to roughly $23,000 per deal. At $15,000 a year the deal loses money in year one; at $75,000 or more the arithmetic works.

Time matters as much. The stretch from first contact to signature is the sales cycle, and here it runs 6 to 18 months. A rep who starts in January may produce no revenue that calendar year. Without cash to cover that stretch, this isn't a motion you can start.

There are three limits. First, forecasting is hard: a deal reported as nearly closed resets when the sponsoring executive changes roles. Second, there's no obvious way to grow revenue except by hiring more people. Third, what gets built serves one customer. Keep building what a single account demands and the product hardens around that account's requirements.

Smaller customers call for something else. Deals in the tens of thousands of dollars a year suit inside sales, run over video rather than in person, and anything below that is better off with no rep attached at all.

"This one needs to run as enterprise sales. Let's start by finding a champion."

The buyer can't decide alone, so secure someone inside who will argue for us.

"The pilot went well but we've been stuck in security review for two months."

The people who'd use it are convinced; there are still gates to clear.

"I'm pulling that deal out of this quarter's forecast. Their decision-maker changed."

Said by someone who knows a personnel change resets the stage you're in.

Pagedeck ran its deal with a 4,000-person manufacturer this way. The person Sofia met in the first meeting was a single planning team manager, and instead of presenting the product she asked how documents moved around the company. By the second meeting she had confirmed that five people were involved in the decision, and she had that manager as her champion.

Security review caught them in month four. Of 300 questionnaire items, the blocker was that employees couldn't sign in with their corporate account, and Theo spent two months building it. What Sofia reported back to Grace was that the feature wasn't for this one deal — it would carry into every deal of that size afterward. That's usually where the cost of a single enterprise deal starts to justify itself.

People often read enterprise sales as a question of individual talent. It's a big contract, so it feels like charm and connections decide it. In practice the work is closer to process management. Knowing which stage the deal is in, who hasn't agreed yet, and what document is needed next is what wins. It's why a rep everyone describes as likeable can lose deal after deal at the security review.

Reading a long timeline as waiting is the other mistake. Those six months aren't time that passes on its own; they're time filled by clearing something every week. A deal with no contact for two weeks isn't in progress, it's stopped. Spend a quarter holding onto stopped deals and the hours that would have created new opportunities are gone, and the loss shows up two quarters later as a gap in revenue.