Enterprise

In the early days of subscription software there was no reason to sort customers at all. A five-person team and a five-thousand-person company both typed in a card number and got the same screen, and the work of selling to them was identical.

That assumption always broke in the same place: right after someone at a large company said "this looks good, let me take it to the rest of the org." A few days later their security team sends over a 300-item questionnaire, legal sends their own standard contract, and IT adds a condition — employees have to sign in with their corporate account. That's usually when the vendor discovers the product has none of it, and answering "we don't support that" ends the evaluation on the spot.

Enterprise took hold as a word once companies accepted that this is a difference in kind, not in size. It isn't the same product sold to ten times as many people; it's a separate business with its own way of contracting and its own feature requirements. So companies started writing down small and medium business (SMB) and enterprise as two lines, picking one, and deciding what to build and who to hire from there.

What separates enterprise from the rest isn't headcount by itself. It's the four conditions that come with that headcount.

1. Several people decide. The person who uses it daily, the executive with the budget, the security reviewer and the legal reviewer each ask different questions, because each is weighing a different risk — whether it fits the daily work, whether it fits the budget, whether it exposes company data, whether the terms are acceptable. Any one of them can stop the deal.
2. The process is long and fixed. Six months to a year from first meeting to signature. Somewhere in the middle sits a proof of concept (PoC) — two or three months of real use by a few departments — and its write-up has to clear before procurement starts.
3. There's a distinct feature list. Single sign-on (SSO) so every employee signs in through one corporate account, audit logs recording who opened which document and when, and an admin screen that splits permissions by role. Passing security review takes an outside certification like SOC 2, and finance or public-sector customers may insist on an on-premise install on their own servers.
4. The customer writes the contract. Instead of clicking through terms on a website, both sides trade a master service agreement (MSA) and negotiate clauses. The service level agreement (SLA) attaches here, setting out how much money comes back if an outage runs past a certain number of hours.

That's also why the price is high. An annual contract clears $75,000, and winning that one contract takes six months of a salesperson's and an engineer's time plus features that didn't exist before, none of which comes back if the deal falls through. In return, these customers rarely leave. Replacing a tool the whole company uses means retraining thousands of people, so contracts renew on three- and five-year cycles and set a floor under revenue.

The pricing page gives it away first. When the last tier reads "contact us" instead of a number, the company sells to enterprise. Headcount and requirements differ per customer so there's no number to print, and printing one would lower the starting point of every negotiation.

On the roadmap it shows up as a force that reorders priorities. The day a company commits to its first large customer, SSO and audit logs move to the front. Neither has ever been requested by the hundreds of existing accounts.

In the org it shows up as headcount. An account executive (AE) owns a deal end to end, someone takes on security questionnaires as their actual job, and a customer success manager stays on after signature to drive adoption. None of those are roles a company selling only to small accounts needs to fill. This is where sales-led growth (SLG) comes from.

In investor material it's a word that describes the shape of revenue. The same $7.5 million in annual recurring revenue (ARR) is a different business coming from 3,000 accounts than from 30 large corporations.

"This one's enterprise, so budget two months just for security review."

Put the questionnaire work and certification checks on the schedule up front.

"We aren't enterprise-ready yet. SSO has to come first."

The product doesn't meet the feature bar for taking a large customer.

"If we're going after enterprise, the pricing page has to come down."

A public monthly rate becomes the ceiling in every negotiation, so switch to a contact form.

Pagedeck has only ever sold to hundreds of small and mid-sized accounts. Then a manufacturer with 4,000 employees asked about a company-wide rollout, and Grace and Sofia spent an hour on whether to take it. Sofia's summary had three parts: about $90,000 a year, two months for the security questionnaire and SSO work, and a permissions screen that only this customer would use.

Theo pointed out that two months wipes out the search improvements planned for the quarter. Grace's question came next: is this one deal, or are ten more customers with the same demands coming behind it? As a one-off it's a loss. As the opening of a segment, everything built here carries into the next ten. Deciding to do enterprise isn't a decision about one contract — it's an answer to that question.

The most common misreading is that enterprise just means a big-revenue customer. The contract value is what catches the eye, so the assumption is natural. But the dividing line is the buying process and the requirements, not the amount. A 30-person company on a $75,000 contract is a large SMB deal; a 5,000-person company where one team starts on $15,000 a year is still an enterprise motion. Judge by amount and you skip the security review and contract negotiation because the number looked small, which is exactly how a team gets missed as a foothold for land and expand across the rest of the company.

Reading enterprise customers as automatically stable revenue is half right. Long renewal cycles do make forecasting easier, but there are few enough accounts that losing one lands hard. One account out of 300 leaving costs 0.3 percent of revenue; one out of eight large customers leaving takes 12 percent at once. Stability here means predictability, not low risk.