Sales-Led Growth

When growth was treated as one undivided thing, the product team and the sales team sat in the same meeting working from opposite assumptions. Product wanted to cut a step out of signup so people could reach checkout on their own. Sales wanted the price off the website so every number came through a quote. Both proposals are about revenue and they point in opposite directions, so the meeting usually went to whoever argued harder.

What actually settles it is the price of the product and the approval path it has to travel. Attach a salesperson to a product that costs $8 a month and the cost of closing one deal passes the revenue from it almost immediately. Go the other way and nobody pulls out a personal card for a contract worth $75,000 a year. An executive holding the budget, a security reviewer, and a lawyer each ask about different things, and someone has to answer those questions before anything gets signed.

So the field split the question of what leads customers in and gave each answer a name. With the answer written down, whether to invest in one screen or in one proposal deck becomes a thing you check rather than a thing you argue about. It also explains why priorities reshuffle the day a company decides to take on an enterprise contract.

People produce the contracts one at a time. That means revenue is calculated from stage conversion rates and headcount rather than from product usage. A single deal usually passes through the same sequence.

1. Build the list of accounts to approach. Filtered by headcount, industry, and what tools they already run.
2. Reach out first. Email, phone calls, and first conversations at a conference sit here. The model does not start from waiting for people to arrive on their own.
3. Meet and demo. The material splits by audience: the daily screens for the people who will use it, the numbers that change after adoption for the executive.
4. Try a small slice. One team gets access for two months to see whether it holds up; when the question is purely whether something is technically possible, that narrower version is a proof of concept (PoC).
5. Clear the reviews. Security questionnaires and contract clauses live here, and weeks disappear at this step.
6. Quote, negotiate, sign.

The span from first contact to signature is the sales cycle, and in this model it usually runs three to six months. Costs run the whole time while revenue does not, so the model needs cash to sit through that gap.

Whether the arithmetic works is worth checking directly. If a salesperson costs $90,000 a year and closes ten contracts in that year, the cost of landing one customer — the customer acquisition cost (CAC) — is $9,000. Against a $20,000 annual contract that pays back inside the first year with room left over. Against a $2,000 annual contract you need to hold the customer for four years to break even. In a market where the second number is the realistic one, this is the wrong model.

The shape of how a team works its accounts — which customers, approached which way — is its sales motion, and that is where the six steps above get turned into an actual routine.

Three moments bring this distinction into a product conversation.

1. Planning and hiring. Next year's revenue target gets divided by what one salesperson closes to decide how many more to hire. Double the target usually means roughly double the people, which makes the plan easy to draw.
2. Pricing. Whether the price list goes on the website or only into quotes gets decided here. Terms vary per customer, so a published list price often blocks the negotiation instead of helping it.
3. What gets built next. A feature blocking one contract moves to the front. Single sign-on (SSO), which lets a company log its whole staff in through one corporate account, and an audit trail recording who opened which document when, are the usual examples. Hundreds of current customers have never asked for either, but a stalled contract changes the order.

Pagedeck started out letting teams try the product and pay on their own, and this model arrived anyway. One team inside a 2,000-person company had been on the free plan and wrote in to say they were evaluating a company-wide rollout. Sofia ran that deal for four months. Theo spent two weeks answering a 300-question security review, and Grace joined the final negotiation. For four months the work looked nothing like a team upgrading itself.

"This one won't close self-serve. It needs a salesperson on it."

Judging from the price and the approval path that a person has to be in the loop.

"If next year's target doubles, we double the sales team — is that math right?"

Testing the assumption that headcount and revenue move together.

"Current customers don't use this feature, but one contract is stuck on it."

Asking to pull an item forward because it's blocking a deal.

Lines like these turn up in quarterly planning. Sofia reads the list of open deals and what each one is stuck behind, and Mia picks out the items where the blocker is the product. The rest are pricing or contract terms, which the product can do nothing about. Skip that sorting step and every request sales carries in lands on the build list, which leaves no room to improve what hundreds of customers use every day.

The common reading is that this model is outdated. Letting the product sell itself sounds newer and more elegant, so that framing comes easily. But which model fits is settled by price and process, not by the decade. No company has ever landed a $75,000 annual contract through a web signup form alone. Decide it by fashion, push ahead without any sales capacity, and every large contract that arrives has nobody to answer it and gets let go.

The other frequent belief is that hiring immediately raises revenue. Headcount and revenue do move together in this model, but on a delay. A new salesperson needs two or three months to learn the product and the customers, and a deal started after that signs four months later — so the first revenue from a January hire lands in August. And when the list of accounts to approach runs dry, more people does not mean more contracts.