Expansion: vertical and horizontal scaling

Most companies that reach 10M+ ARR face the same strategic fork: go deep into existing customers or go wide into new customer segments and geographies. The two paths are not equivalent. They are fundamentally different expansion modes with opposite economics, opposite timelines, and opposite risk profiles.

Vertical scaling is the land-and-expand motion: you win a narrow footprint inside an existing customer and expand to adjacent users, teams, or use cases within that same account. Horizontal scaling is the new-segment-or-geography motion: you take the motion that works in segment A and deploy it to segment B, or you replicate the motion in a new geography with a different buyer.

Confusing them is one of the leading causes of expansion failure. Companies build sales teams for horizontal scaling while the motion supports vertical scaling. Or they build customer success infrastructure for vertical expansion when the unit economics require horizontal acquisition. The result is high burn, low NRR, and neither scaling strategy succeeding.

Understanding which mode your motion supports is the first operational decision of scaling.

Vertical scaling (land-and-expand)

Vertical scaling deepens the footprint in existing customers. It is the opposite of acquiring new customers; it is expanding inside customers you already have.

The unit economics of vertical scaling

Vertical expansion revenue has a fundamentally different cost structure than land revenue.

Expansion CAC is near zero. The customer already knows who you are. The adjacent user or team is aware of your product (often, you are the default tool they use). The buying process is shorter, the negotiation is lighter, and the internal champion is often a peer of the original buyer, not a procurement committee. Expansion CAC is typically $0–2K per account, even in enterprise.

Expansion margin is high. Because there is no (or minimal) CAC, nearly the full ACV of the expansion revenue flows to gross margin. If your gross margin is 70% on land revenue, expansion revenue can be 80–90% margin because you are not acquiring; you are converting.

Payback is fast. Because expansion CAC is low, payback is months, not years. A $100K expansion deal with $80K gross margin (80%) and zero expansion CAC pays back in 1.5 months. This is not the typical SaaS unit economics; this is a different economic model.

Net revenue retention can exceed 120–150%. When vertical scaling works, NRR compounds because expansion revenue accumulates. If your land cohorts grow to $100K customers and then 40% of them expand to $150K within two years, your cohort’s NRR is 140%. This is the economic engine of the most profitable SaaS companies.

The downside of these beautiful economics is that they come with constraints.

The constraints of vertical scaling

Timeline: long. Vertical expansion takes time. You must land a customer, achieve success with the initial footprint, build proof of value, identify the adjacent footprint, and then expand. The full cycle is typically 12–24 months from land to expansion stickiness. If you need new revenue in 6 months, vertical scaling will not deliver it.

Product depth required. Vertical expansion requires the product to have sufficient depth to solve problems for adjacent user types without fundamental redesign. If you sell to the engineering team, can the product solve a problem for the data team? Or the security team? If not, expansion will not happen, regardless of sales effort.

Concentration risk. All expansion revenue comes from existing customers. If one large customer churns or reduces usage, your NRR collapses. Your revenue is concentrated in a smaller number of large accounts. This is efficient until a single customer leaves, and then it hurts.

Requires the right team structure. Vertical scaling requires customer success over sales. You need people who understand your customer’s business deeply, who can identify expansion opportunities, and who can navigate internal consensus. A sales team optimized for land (quick close, large value promise) will not excel at expansion (slow, proof-driven, internal politics).

Horizontal scaling (new segments / geographies)

Horizontal scaling widens the customer base into new segments or geographies. It is not going deeper into existing customers; it is replicating your motion in a new market.

The unit economics of horizontal scaling

Horizontal scaling revenue requires the same motion as land.

Expansion CAC is non-zero and scales with motion CAC. When you enter a new segment or geography, you are essentially starting acquisition over. You need marketing to build awareness, sales to convert, and customer success to enable. The CAC for a horizontal-scaled segment is often 70–90% of your core-segment CAC, because some economies of scale and brand have transferred, but you are still acquiring.

Expansion margin is lower. Because you have significant CAC, gross margin on horizontal-scaled revenue is lower than on vertical-expanded revenue. If vertical expansion is 80% margin with zero CAC, horizontal expansion is 50–60% margin after accounting for segment-specific acquisition costs, localization, and support.

Payback is slower. Because horizontal expansion carries CAC, payback is longer. A $30K ACV horizontal-scaled deal with 60% margin and $15K CAC pays back in 2.5 years. This requires patience and capital.

NRR grows more slowly. Because expansion CAC is significant, NRR growth in a horizontal-scaled segment mirrors the NRR of your core segment, not the 120–150% of vertical expansion. If your core segment NRR is 115%, your horizontally-scaled segment NRR will start around 110–115%.

But horizontal scaling has advantages that vertical does not.

The advantages of horizontal scaling

Time to first revenue is fast. Because you are acquiring new customers in a familiar way, you can start generating new revenue in 3–6 months. You do not have to wait for expansion proof; you are landing new accounts.

Reduces concentration risk. Instead of depending on deep expansion in a few customers, you are diversifying across new customers and segments. If one segment underperforms, you have others.

Does not require product architecture changes. Horizontal scaling replicates an existing motion in a new market. The product does not have to be architected for depth; it just needs to work for the new segment’s use case.

Easier to scale operations. Because you are repeating the same motion (acquire customer, enable, expand), you can standardize it across new segments. You do not have to rebuild the motion each time.

Opposite case study: Same product, opposite scaling strategies

Consider two companies selling the same product: a compliance automation tool.

Company A: Vertical scaling. They land a compliance solution for banks (narrow footprint). Banks must handle regulatory requirements for deposits, lending, and derivatives trading. Company A achieves strong product-market fit with bank compliance officers. Now they expand to the same bank’s lending-compliance team (different use case, same customer). Then to their derivatives team. Each expansion is 12 months apart, but because the bank is already a customer, expansion CAC is near zero and expansion margin is 85%.

By year 4, their core cohort of 10 customers has expanded to $2M ACV. Their NRR is 140%. They have 12 employees: 2 in sales (landing only), 6 in customer success (managing and expanding), 2 in product (adding depth), 2 in admin. They are profitable on 50% margins.

Company B: Horizontal scaling. They land the same compliance solution for banks, but instead of expanding within banks, they move to insurance companies. Insurance has different compliance needs (underwriting, reserves, claims), a different regulatory framework, and different buyer personas. Expansion CAC is $15K per customer; expansion margin is 55%.

By year 4, they have 40 customers across three segments (banks, insurance, wealth management). Their NRR is 110% (low churn, some expansion). Their revenue is $3M. Their team is 15 people: 5 in sales (landing in three segments), 4 in customer success (retention), 3 in product (breadth over depth), 2 in admin, 1 in partnerships. They are less profitable on 30% operating margins.

The difference: Company A has $2M ACV (10 customers), Company B has $3M total revenue (40 customers). Company A is more efficient (higher margins, smaller team), but is concentrated in one customer category and risky if banks reduce compliance spending. Company B is more diversified, less efficient, but more resilient.

Which path should they have taken? That depends on the product’s depth and the market structure. If compliance automation can genuinely solve 5+ distinct use cases within a bank, Company A’s path scales better. If the product is shallow (point solution for one compliance need), Company B’s path is the only option.

The diagnostic: Knowing which mode your motion supports

You cannot choose between vertical and horizontal scaling. The market structure and your product architecture constrain which is viable. The diagnostic is in three measurements:

1. NRR by cohort. Cohorts that land 12+ months ago: what is their NRR? If NRR is 120%+, vertical scaling is working. If NRR is 105–115%, vertical scaling is marginal; horizontal scaling is the stronger path.

2. Expansion rate. Of the customers who landed 6+ months ago, what % have expanded to a second use case, team, or buyer type? If expansion rate is >30%, vertical expansion is working. If <15%, vertical scaling is not viable in your market, and you must go horizontal.

3. Expansion CAC vs land CAC. Measure the CAC to win an expansion deal. If expansion CAC is <20% of land CAC, vertical scaling has extraordinary economics. If expansion CAC is >50% of land CAC, you are essentially acquiring again; go horizontal.

If NRR is 120%+, expansion rate is >30%, and expansion CAC is <20% of land CAC, your motion supports vertical scaling. Build customer success, build product depth, and invest in expansion. If NRR is <115%, expansion rate is <15%, or expansion CAC is >60% of land CAC, your motion supports horizontal scaling. Build sales repeatability, build segment-specific positioning, and go wide.

Founder mistakes in expansion strategy

Mistake 1: Attempting both vertical and horizontal simultaneously

The most common founder mistake is trying to do both. You build a customer success team to expand within customers (vertical). You also build a new sales team to land in a new segment (horizontal). You are attempting two opposite motions with the same capital and team.

The result is that neither motion executes well. The sales team does not have enough ramp time because you are also building CS. The customer success team is stretched across existing-customer expansion and new-segment support. Your burn rate is high, your NRR is mediocre (you are not expanding fast enough), and your new segment is not ramping (you did not give sales enough runway).

The fix: Pick one. If the data shows NRR 120%+, commit to vertical scaling. Build a world-class customer success organization. Do not hire sales to expand into new segments; hire sales to land in the same vertical where vertical expansion is proven.

If the data shows NRR <115%, commit to horizontal scaling. Do not try to squeeze more expansion out of existing customers. Focus on repeatability, segment-specific messaging, and sales motion in the new segment.

Mistake 2: Scaling horizontally before vertically

The second founder mistake is the reverse: you land a product in segment A and immediately expand to segment B, before you have proven that vertical expansion in segment A is working.

The result is that you acquire customers across two segments at high CAC, with low NRR in both. Your unit economics are poor because you are not getting leverage from expansion in either segment. You have twice the operational complexity and half the economics.

The diagnostic: Measure NRR in your original segment. If it is not 115%+, do not go horizontal. Spend 6–12 months improving vertical expansion in your core segment. Once NRR is healthy, then expand horizontally.

Mistake 3: Confusing “we want both” with “the motion supports both”

Some founders correctly understand that vertical and horizontal scaling are different, but then assume: “We can do both because we have the capacity.” The issue is not capacity; it is operational focus.

Vertical and horizontal scaling require opposite org structures, opposite comp schemes, opposite product roadmaps. If you build a CS team for vertical expansion, they are measured on NRR and expansion rate. If you build a sales team for horizontal expansion, they are measured on new customer acquisition and segment coverage. These are not compatible metrics for one person to optimize.

The fix: Accept that you will be very good at one and adequate at the other. Choose which one your product and market structure supports best. Build the organization for that mode. The other will happen as a side effect, but it will not be your primary engine.

Rules for choosing and operating at scale

Rule 1: Let your NRR tell you which mode to commit to

Do not choose based on what feels strategic or what other companies do. Compute your NRR. Measure expansion rate. If the data shows vertical scaling is working, go vertical. If not, go horizontal.

Checkpoint: What is your NRR by cohort for customers who have been with you 12+ months? If >120%, vertical expansion is your engine. If 105–115%, you are ambiguous; stress-test the expansion timeline and CAC. If <110%, go horizontal.

Rule 2: Design your org for one mode, not both

Once you choose, structure your organization and comp for that mode. If vertical scaling, your top-heavy costs are customer success and product. If horizontal scaling, your top-heavy costs are sales and marketing.

Checkpoint: Who are your three highest-paid people? If they are VP Sales, VP Marketing, VP RevOps—you are built for horizontal scaling. If they are VP Customer Success, VP Product, VP Sales (small team)—you are built for vertical scaling. If you have both, you are built for nothing.

Rule 3: The pace of scaling follows the mode

Vertical scaling is slower but more efficient. You will reach $50M ARR with 30–40 people and 70%+ margins. But it takes 4–5 years.

Horizontal scaling is faster but less efficient. You will reach $50M ARR with 80–100 people and 40% margins. But it takes 3–4 years.

Choose the mode that matches your capital and timeline constraints. If you need profitability quickly, go vertical. If you need scale quickly, go horizontal.

Checkpoint: What is your capital runway? What is your board’s growth expectation? If you have 24 months of runway and need to demonstrate unit-profitability, vertical scaling. If you have 36+ months and need to demonstrate land+expand, go horizontal.

Rule 4: Switching modes mid-scale is expensive

Once you have built a vertical-scaling organization, switching to horizontal scaling is costly. You must hire sales and marketing, rebuild positioning for a new segment, and retool your product. Similarly, switching from horizontal to vertical requires hiring and reorienting customer success, which you may have deprioritized.

The cost of switching is 6–12 months of lost momentum and $500K–2M in org restructuring. Avoid it by choosing the right mode early.

Checkpoint: Before you hire a VP Sales or VP Customer Success, know which mode you are optimizing for. That hire commits you.

Asymmetric rules: How they play out differently

Rule: Go vertical if your product is deep and your market is consolidating. Banks, insurance, healthcare, and regulated industries see consolidation (large players buying smaller ones). If your product is architected for depth, vertical expansion compounds NRR. Example: Workiva in compliance automation. 4 large customers, 130%+ NRR. They went vertical.

Rule: Go horizontal if your product is broad and your market is fragmenting. SaaS categories where many small companies exist (project management, communication, design tools) see horizontal expansion work better. Slack went horizontal: consumer, enterprise, new verticals. Example: Monday.com across work management, CRM, HR. They went horizontal.

Rule: Go vertical in B2B; go horizontal in B2C or freemium. B2B land-and-expand is common (enterprise accounts expand across teams). B2C and freemium have weak expansion signals; growth is new user acquisition. Example: Figma is B2B freemium and went horizontal (education, enterprise, Asia).

Teaser: Expansion sequencing

Once you have chosen vertical scaling and proven the motion works, the next question is sequence: which adjacent use case or team should you expand to first? Expanding to Team A first might open a path to Team C that is blocked if you expand to Team C first.

This is the problem of expansion sequencing, and it is where the most sophisticated operators diverge. You have proven you can expand. Now you need to expand in the right order.