Article

The ISV Scaling Playbook: 10 Decisions That Separate $10M ARR from $100M ARR

Most SaaS founders treat the journey from $10M to $100M ARR as a bigger version of the journey to $10M. More leads, more reps, more features. The data and the scar tissue both say otherwise. Going from $10M to $100M is a different game, with a different set of decisions, and the companies that make those decisions early are the ones that compound.

ISV scaling strategies that worked at $5M tend to break at $20M. How to scale an ISV from $10M to $100M ARR comes down less to working harder and more to choosing differently across a small set of high-leverage decisions: who you sell to, how you ship, how you price, how you grow inside your existing accounts, and how you build the platform underneath all of it.

Why the path from $10M to $100M ARR is a different game

At $10M ARR, founder-led scrappiness still works. At $100M ARR, it cannot. The transition forces ISVs to redesign sales, product architecture, pricing, and operating model around predictability instead of heroics. Most SaaS companies that stall do so because they tried to scale tactics that were never built to carry them past the next milestone.

Battery Ventures general partner Neeraj Agrawal's T2D3 framework, introduced in 2015, lays out the canonical SaaS path: triple ARR for two years, double for three, and roughly $1M ARR becomes $100M ARR in about five years. The framework is a benchmark, not a guarantee. Hitting it depends on the 10 decisions below.

10 decisions that separate $10M ARR ISVs from $100M ARR ISVs

Each decision below is a real choice ISVs face on the way up. None of them is technology for its own sake. All of them show up as either an unlock or a ceiling, depending on which way the team chooses.

1. Tighten the ideal customer profile

The decision: stop selling to anyone who will pay. ICP looseness is what fills a $10M ARR pipeline with churn and discount pressure. Companies that reach $100M ARR pick a sharp, repeatable customer profile and walk away from accounts that do not fit. Sales reps close faster, customer success keeps more, and product gets a clear signal on what to build next.

2. Replace founder-led selling with a repeatable sales engine

The decision: build a sales motion that does not depend on the founder being in the room. Reps need to be able to close a deal the founder never touched, on the back of a documented playbook, with predictable ramp times. Companies that skip this step plateau the moment the founder runs out of hours.

3. Re-architect the product for multi-tenant scale

The decision: stop bolting customers onto a single-tenant architecture and design for multi-tenant scale. Manual provisioning, fragile scripts, and one-off environments are fine at $5M ARR. At $30M and up, they consume engineering capacity that should be going into product. A Tenant Orchestration Factory approach turns environment creation, compliance, and lifecycle management into something the platform handles automatically.

4. Shift pricing toward usage-based or hybrid models

The decision: move beyond fixed seat-based pricing toward something that follows customer value. Usage-based and hybrid models compound revenue inside the account because customers pay more as they get more out of the product.

5. Build for net revenue retention, not just new logos

The decision: design the product, sales, and customer success motions around expansion, not only acquisition. Net revenue retention above 115% means existing customers fund a meaningful share of growth before a single new logo signs. Without that compounding, every dollar of ARR has to come from net new acquisition, which gets harder at every stage. ISVs that lead with retention-led development tend to compound faster.

6. Get into cloud marketplaces and co-sell early

The decision: treat cloud marketplaces and co-sell as a primary go-to-market channel, not a side experiment. Microsoft commercial marketplace, AWS Marketplace, and Google Cloud Marketplace shorten enterprise procurement, draw on committed cloud spend, and put the product in front of buyers already inside a purchasing process. Co-sell motions with hyperscaler field teams expand reach without expanding headcount on the same curve. ISVs that ignore marketplace presence too long tend to rebuild their GTM around $30M ARR.

7. Make AI a product surface, with governance built in

The decision: embed AI inside the product as part of the core experience, and govern it from day one. Bolting on a chatbot to claim AI credit does not move retention; AI features wired into workflows customers already use do. Governance, audit, and access controls cannot be afterthoughts when AI is touching customer data. Teams that pair AI-driven app innovation with automated tenant management underneath can scale AI features safely across every customer environment.

8. Earn an enterprise-grade security posture early

The decision: invest in SOC 2, ISO 27001, identity, and observability before deal cycles force the issue. Enterprise buyers at the $25K and up annual contract value range will not move past procurement without a defensible security posture. ISVs that wait until a six-figure deal is on the line to start the audit lose months of revenue and trust.

9. Layer the operating model

The decision: add the management, RevOps, and customer success layer between executives and individual contributors before the cracks become public. At $10M ARR, the founders can still see everything. At $30M, they cannot. Middle managers, revenue operations, enablement, and a customer success function that owns expansion are not nice-to-haves at this scale. Skipping the operating-model build is the most common cause of growth deceleration between $15M and $40M ARR.

10. Expand geography and vertical last, not first

The decision: prove the model in one segment and one region before resources scatter. Premature expansion is one of the fastest ways to stall. Companies that scaled to $100M ARR typically dominated one ICP in one geography first, then expanded with the same playbook into the next, supported by cloud infrastructure built for multi-region, multi-tenant rollouts.

Pick the next decision

Most ISVs do not lack ambition or a market. What separates the ones that compound past $10M ARR is the willingness to make these decisions on offense, before the growth curve forces them. Pick the single decision on this list you have been avoiding and start there. If you want help turning your goals for next quarter into a reality, start a conversation with Valorem Reply.

Frequently Asked Questions