Small and Medium Business

The trouble started with treating every customer account the same way regardless of size. Run the same sequence at a 30-person company and a 3,000-person company and it fits neither. For the smaller one the process is heavier than the decision needs, so it only burns time; for the larger one it isn't heavy enough, and the deal stops at the security review.

The arithmetic shows it first. If one salesperson spends four months on a single 30-person company, their salary for that period exceeds what the contract brings in over a year. That isn't a reason to turn the customer away. Five hundred companies of that size paying $2,000 a year each add up to $1,000,000, which is more than ten enterprise contracts. The problem was never the amount; it was that the two sizes justify very different amounts of human attention. The hours one deal can absorb differ by roughly an order of magnitude between them.

So the field split the territory by how large a single customer account is, and this segment — small and medium business (SMB) — is the low end of that split. Once the line is drawn, it changes more than how you sell: it changes what you build, because whatever a person can't be spared for has to be covered by the product. If enterprise is the territory where problems get solved by assigning people, this is the one where things have to run without anybody assigned.

Everything else follows from the single fact that one deal is small.

1. Volume fills the gap. Five hundred customers at $2,000 a year make $1,000,000. Double the revenue target and you need roughly double the accounts.
2. A ceiling appears on what you can spend to win one account. The cost of landing a customer is the customer acquisition cost (CAC), and on a $2,000 annual contract a CAC above $1,500 leaves nothing in the first year. A salesperson visiting accounts one at a time cannot hold that ceiling.
3. The product covers that gap instead. When someone gets from signup through first setup with no human guiding them, that's self-serve onboarding, and in this segment it isn't a convenience — it stands in for a salesperson.
4. Decisions land fast. The distance between the person using the tool and the person holding the budget is short, so a team lead who likes it can pay for it that week. Adoption finishing inside a month is normal.
5. Cancellation is just as fast. Customers leaving is churn, and here a company under financial pressure cuts the subscription the following month, because billing is monthly and contracts often carry no minimum term.
6. Support points at many accounts at once rather than one at a time. When the same question arrives from twenty companies, you edit the help article instead of writing twenty replies. That trade only holds when the article is clear enough to actually answer the question.

Those six interlock, so breaking one breaks the structure. Price for this segment but have a person walk each customer through setup and the acquisition cost goes over the ceiling; build something people can run alone but never look at why they leave and the accounts you added drain away quietly.

Four places bring this distinction into the work.

1. Pricing and payment. The price list goes on the website and a card completes the purchase. Seat-based pricing, which charges in proportion to the number of user accounts, is common here because the customer can raise their own spend by adding people.
2. The build order. Removing one step from first setup outranks adding one large feature. Lift the signup completion rate across 400 accounts by a single percentage point and that alone is four contracts.
3. How support is organized. Instead of assigning an owner per account, you write help articles, templates, and automated guidance emails. People get assigned only to the handful of largest accounts.
4. Which numbers get watched. New contracts and cancellations get read together. Look at new contracts alone and 40 arriving against 35 leaving in one month reads as growth. Both numbers come out of the same month, and neither one reads correctly by itself.

Pagedeck sits in this segment right now, with a little over 400 customer companies, most of them between ten and a hundred employees. Sofia handles sales by herself, and the accounts she actually contacts are the top 40 by revenue. The other 360 go from signup to payment without touching a person. That's why Mia keeps returning to the first-setup screen when she sets quarterly priorities: that screen is doing the work of thirty Sofias.

"This one's SMB, so skip the onboarding call and send the guide instead."

At this deal size there's no room for a person in the loop.

"All 400 accounts touch this screen. Removing a step here beats shipping one big feature."

There are enough accounts that small improvements add up to more than a feature.

"Forty new this month, thirty-five cancellations. Hard to call that growth."

Naming a state that looks like growth if you only read one of the two numbers.

The monthly review runs through those lines in order. Sofia reads the new and cancelled counts, and Mia looks at how far the cancelled accounts got before stopping. Many stopping in the first week means the product failed to guide them; many stopping after six months means the value didn't hold up against the price. Asking each company directly isn't possible at this count, so reading them as groups is effectively the only window available.

The frequent belief is that small customers matter less. One deal is small, so losing one looks survivable. But in aggregate this segment is the floor under the revenue, and a few of those 400 companies will have a thousand employees in a few years. Treat the segment as secondary and the setup screen and the help articles keep sliding down the list — and in a territory where nobody is assigned to accounts, those two sliding is exactly how the cancellation rate climbs without anyone noticing.

The other common assumption is that moving upmarket makes this difficulty go away. Larger deals do buy room for human attention, so it reads that way. But moving up isn't a change of customer; it's a change of company. You rebuild the sales organization, keep someone who can answer security questionnaires, and build single sign-on and audit trails. Meanwhile the 400 accounts are still there, so without a real intention to run both territories for a while, you lose ground in each. The two want different pricing pages, different support, and different roadmaps.