SMB-to-Enterprise Expansion Ladder
Earn user love in small businesses before adding enterprise capabilities
- Difficulty
- Expert
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 98%
The SMB-to-Enterprise Expansion Ladder starts by winning demanding small customers who personally feel both the product's value and its cost. This pressure encourages a strong end-user experience and establishes genuine customer love before the company tackles complex enterprise requirements. The business then advances into mid-market and enterprise accounts gradually, adding integration, administration, security, and compliance without abandoning usability. Leaders must reject oversized opportunities when the product or organization is not ready, because an early enterprise customer can turn the company into an outsourced development shop and distort the roadmap. The desired output is a repeatable enterprise product built on proven user demand, not a collection of custom features purchased by one powerful account.
Origin
Santi Subotovsky described how Zoom began with SMB customers, moved into mid-market, and only accepted enterprise standardization when Eric Yuan believed the company was ready.
Core principles
- 01Small customers force products to deliver visible value
- 02User love should precede enterprise standardization
- 03Enterprise readiness requires security, compliance, and integration
- 04Large contracts should not dictate the entire roadmap
- 05Saying no preserves long-term product integrity
How to run it
- 1
Win the end user
Serve SMB or very small business customers who directly experience the product's benefits and costs. Build an experience compelling enough to earn voluntary use.
Pro tip Watch for customers adopting the product despite an incumbent company standard.
Watch out Do not hide weak user value behind centralized procurement.
- 2
Prove customer love
Measure retention, advocacy, expansion, and direct customer testimony. Confirm that customers care about the product before moving upmarket.
Pro tip Look for users who say they would change jobs or workflows to keep the product.
Watch out Initial sign-ups without continued use do not prove readiness.
- 3
Enter the mid-market
Pursue larger customers with manageable operational requirements. Use these accounts to discover repeatable needs beyond the end-user experience.
Pro tip Separate recurring segment requirements from one customer's preferences.
Watch out Do not promise enterprise-scale capabilities before the organization can support them.
- 4
Build enterprise readiness
Add security, compliance, administration, integration, and support capabilities required by CIOs. Preserve the customer experience that created adoption.
Pro tip Treat IT as an additional customer, not as a replacement for the user.
Watch out Enterprise checklists can overwhelm the product if usability loses priority.
- 5
Say no before ready
Reject large contracts when delivery would compromise reliability or force excessive customization. Use readiness criteria rather than contract value to govern the decision.
Pro tip Explain the missing capabilities and revisit the account after they become repeatable product features.
Watch out A prestigious early customer can consume the team and damage every other customer.
- 6
Standardize repeatably
Scale enterprise selling only after multiple customers can adopt the same core product and operating model. Build sales and customer-success systems around that repeatability.
Pro tip Track whether enterprise deployment effort declines across successive customers.
Watch out Revenue growth can conceal a services-heavy, non-scalable model.
In the wild
A large customer wanted to standardize on Zoom, offering a contract much larger than the company's SMB deals. Eric Yuan concluded that Zoom was not ready and declined, protecting the company from a potentially damaging first enterprise experience.
→ Zoom preserved its product and later scaled into enterprise markets on stronger foundations.
Zoom adoption grew within Uber from smaller groups toward organization-wide standardization. By the IPO filing, Uber was conducting 14 million meeting minutes per month through Zoom.
→ Bottom-up user adoption developed into substantial enterprise usage.
Common mistakes
Chasing the largest contract
Contract value can tempt a company to enter the enterprise market before its product and operations are ready.
Becoming a development shop
Building one-off features for a powerful customer can consume the roadmap and kill the scalable core business.
Serving IT but not users
Security and compliance matter, but abandoning the end-user experience destroys the customer love that powered initial growth.
Is it for you?
Best for
It is best for product-led SaaS companies that have strong SMB adoption and want to pursue larger accounts.
Not ideal for
It is not ideal for products whose first usable deployment inherently requires large-enterprise infrastructure.
From the transcript
“So I believe it's a great strategy to get that customer love early on.”
“he said, Oh, we have this big customer that wants to standardize on Zoom, but I told them that we're not ready.”
“Because if you're not ready, you might become an outsourced development shop for that enterprise. And that might kill the rest of the business.”
From the episode
The Zoom IPO (with Santi Subotovsky)
Santi Subotovsky