Business to Business

Product teams say "the user" and picture one person — someone who opens a screen, likes it, pays, and cancels when they stop liking it. In a product sold to companies, that person has no authority to press the pay button. Using the same word for both meant teams spent their effort satisfying the wrong person.

Pagedeck ran into this early. A document-sharing feature Theo built was a favorite of one customer's working-level contact, and four months on the contract still hadn't moved. The executive holding the budget had never once opened that screen, and the security lead was asking which country the documents were stored in. The person who liked it and the person who decided were not the same person.

So a word was needed to pin down who the buyer is before anyone argues about what to build. Business to business (B2B) is one of the answers that fills the slot. Attach the label and "the user" splits into several people, and two facts arrive with it — the sale takes months, and there is more than one person to convince.

A single contract has to pass through several people holding different jobs before it closes. Less a matter of convincing someone than of clearing a series of gates.

There are usually four.

1. The person who uses it — the working-level contact who opens the product every day. They care whether their own workload actually shrinks. They are also usually the one who proposes bringing it in.
2. The person who pays — the executive holding the budget. They ask about numbers rather than screens. Without an answer to what $38,000 a year improves and by how much, the approval never comes.
3. The person who can block it — security and legal. They check where the data sits, how access is revoked when an employee leaves, and how documents come back when the contract ends. Requirements like single sign-on (SSO), which lets every employee reach the product through one company account, come from this seat.
4. The buying procedure — procurement and finance. Quote and contract templates are fixed, and payment goes out on a date the company has already set. Weeks can disappear in this step alone, none of it about the product. A deal agreed in March can still be waiting on a vendor registration form in May.

Four gates make the sales cycle — the span from first contact to a signed contract — long. At Pagedeck a team-level contract averages 34 days, while a company contract runs past 90.

In exchange, customers rarely leave once they are in. A few months after rollout, hundreds of employees have piled documents inside and working procedures have been reshaped around the product. Moving to another tool is less about migrating files than about retraining everyone. Renewal rates run high, and next year's revenue is easier to predict.

The missing price page on so many company websites comes out of the same structure. A 30-person customer and a 3,000-person customer are hard to charge the same way, and conditions differ enough from one customer to the next that quotes go out individually.

The phrase turns up wherever a company decides what to build first and how to sell it. It isn't a statement of preference — it ties down the decisions that follow.

Build order changes first. Call the product B2B and admin screens, permission settings, and an audit log of who opened which document when all move to the front of the queue. A product for individuals might not build any of those for years.

The selling method gets settled alongside it. Sales-led growth, where a sales team meets the customer and walks them through the product, or product-led growth, where people try it free and convert on their own. B2B doesn't force the first one. Pagedeck sells to companies while leaving signup open to anyone, and sales joins once the number of people using it together starts to grow.

Inside the category, customer size splits it again. The enterprise end works with companies of several thousand employees, answers 300-question security review forms, and builds features one customer alone will use. The SMB end works with companies of a few dozen, finishes rollout within a month, and loses them just as fast when their business turns down. Two days of work at those two ends barely overlap, B2B or not.

The numbers on the wall change too. How many contracts closed and what the average one was worth come before how many people signed up today. Two hundred signups in a week is a fine number for a product sold to individuals; for Pagedeck it says nothing until someone checks how many of those names sit inside a company already in a deal.

"We're B2B, so admin permissions come first. Polishing the individual screens comes after that."

A priority call — the customer is a company, so organization-level features go ahead.

"They love it at the working level, but we still haven't got a meeting with the executive."

Goodwill from the people using it doesn't close a contract by itself.

"I think we keep prices off the site and quote each customer instead."

Deal size varies enough per customer that a public price page doesn't fit.

At Pagedeck the word comes up most often in quarterly planning. Mia lays out next quarter's priorities and Sofia brings in whatever requirement is blocking a company deal in progress — one item flagged in a security review holding up three contracts at once.

The decision is always a trade. Take the requirement and engineering builds something the existing hundreds of customers have never asked for; refuse it and the deal in front of them is gone. What Grace asks in that room is whether the feature will sell to other company customers too. A feature one customer uses keeps costing money long after it ships.

A common belief is that software for companies can look rough. The person deciding never sees the screen, the reasoning goes, so a long feature list is enough. It sounds plausible, because the executive who signs really does watch a 30-minute demo and no more.

But from the day the contract closes, working-level staff open that screen every day. If it's awkward to use, people quietly drift back to the old way, and a year later the renewal meeting opens with "we barely use this." Lately the path where a staff member tries the product free and pushes it upward has become common enough that an awkward first screen never reaches the executive at all. A product built on the belief that rough is fine wins contracts and loses renewals.