Coupa, Twilio, and The Acceleration of SaaS

In 2016, SaaStr founder Jason Lemkin made a point that still makes founders squirm in the best possible way:
the “law of large numbers” was starting to lose its intimidation factor in SaaS. Companies weren’t supposed to
keep growing like rockets once they hit serious scale. And yet… there were Twilio and Coupa, cruising past
nine figures in run-rate and still growing around 70% year over year. That wasn’t just impressiveit was a
benchmark reset.

This post isn’t a nostalgia tour. It’s a practical unpacking of what “SaaS acceleration” really meant then,
why Twilio and Coupa were such powerful examples, and what the lesson looks like now that SaaS is older,
noisier, and occasionally allergic to free money.

The original “acceleration” argument (in human language)

The heart of the SaaStr argument was simple: stop treating breakout growth at scale as mythical. Twilio had
gone public and was growing about 70% year over year at roughly $300M in ARR (per the post’s framing). Coupa
had filed to go public and was also growing roughly 70% year over year while already well beyond $100M in ARR.
The punchline was not “be Twilio.” The punchline was: if big, established categories like telephony and
procurement can still produce hypergrowth SaaS winners, your market probably has more headroom than you think.

Lemkin’s spicy takeaway was basically: if the “big numbers” didn’t slow them at $150M-ish ARR, why are you
accepting slower growth at $5M or $15M? The internet yelled. Which, historically, is how you know a benchmark
landed.

Why Twilio scaled so fast: API-first + “automatic expansion”

Twilio’s early magic wasn’t just that it sold software. It sold capabilitycommunications you could drop
into your product like Lego bricks. If you were building login verification, delivery notifications, appointment
reminders, customer support workflows, or two-factor authentication, Twilio wasn’t a “vendor.” It was
infrastructure with a developer-friendly interface.

1) Developer distribution beats “book a demo” when time matters

API-first companies can spread inside the internet the same way a useful code snippet spreads: one engineer,
one prototype, one “we can ship this today.” That pull is a growth accelerant because it compresses the distance
between interest and value.

2) Usage-based pricing creates compounding revenue (and forces discipline)

Twilio’s model made expansion feel “automatic.” If customers send more messages, make more calls, or trigger more
verification events, usage increases and revenue follows. It’s a beautiful flywheeluntil you forget it also
requires cost controls, forecasting, and guardrails so customers don’t get surprised by their bill (and then
surprise you by churning).

Usage-based pricing also makes the value metric obvious: you pay for what you use. That clarity can reduce
friction in adoption, especially for new products where buyers want to start small and scale only if it works.

3) Global scale is part of the product

Communications isn’t a “set it and forget it” feature. Reliability, deliverability, regulation complexity, and
global reach are all reasons customers don’t want to duct-tape their own carrier relationships. When the platform
can operate at massive scale across many countries, “build it yourself” stops sounding romantic and starts
sounding like a late-night incident report.

Why Coupa scaled: “unsexy” spend is a giant, trained-to-pay budget

Coupa’s superpower was not viral adoption by developers. It was something more enterprise and more inevitable:
businesses already spend enormous money through procurement, invoicing, expenses, and supplier managementand
they’re trained (sometimes forced) to invest in systems that control that spend.

1) Procurement is boring… which is why the budget is real

Coupa lived in a category where buyers understand ROI without needing interpretive dance. If you can prevent
waste, improve compliance, streamline approvals, and get visibility into where money goes, the business case
writes itself. “Spend management” may not sound thrilling, but neither does “leaking cash,” and the second one
shows up on the CFO’s face.

2) Growth proof points: the S-1-era numbers mattered

One reason SaaStr used Coupa as a benchmark was the public financial visibility. In its S-1-era disclosures,
Coupa showed rapid revenue growth over that period, reinforcing the point that you could be well past the
early-stage phase and still be expanding at a pace founders normally associate with much smaller companies.

3) Platform thinking: from process tool to spend intelligence

Over time, spend platforms aim to become more than workflow. They become systems of record for purchasing and
a source of insight: what you buy, from whom, at what price, with what compliance, and with what risk. That’s
how “a procurement tool” turns into “a strategic platform” (and how expansion happens without needing to invent
a whole new company).

So what actually accelerates SaaS? Seven real accelerants

1) Markets got bigger because cloud adoption stopped being optional

The acceleration thesis starts with a simple macro shift: more categories moved to SaaS, and budgets followed.
When the default becomes “buy software” instead of “build or host it yourself,” the total addressable market for
cloud vendors expandsfast.

2) Buyers became “trained” to adopt SaaS faster

In older enterprise cycles, adoption could mean multi-year migrations and political trench warfare. Modern SaaS
still has procurement drama, but buyers are more familiar with subscriptions, pilots, security reviews, and
renewals. Familiarity compresses cycle time.

3) PLG and self-serve raised the floor for speed

Product-led growth (and product-led anything) changes expectations. If customers can try, learn, and
feel value before a sales call, your funnel behaves less like a gated community and more like an airport:
lots of people moving through quickly, with the right ones upgraded to first class.

4) Expansion revenue became a strategy, not a happy accident

The modern best practice is to design expansion on purpose: seat growth, usage growth, multi-product cross-sell,
add-ons, or outcome-based packaging. The catch is that expansion has gotten harder in recent years as customers
scrutinize budgets and optimize tool sprawlso you need real value, not just clever pricing.

5) Benchmarks got louder (and more public)

SaaS operators now have an entire industry of benchmarks and playbooks: CAC payback targets, net revenue
retention norms, “efficient growth” frameworks, and investor expectations. The upside is clarity. The downside
is founders feeling like they’re being graded every quarter by a committee of spreadsheet enthusiasts.

6) Better capital markets (then) and better unit economics (now)

In boom times, capital can accelerate hiring, product, and go-to-market. In tighter times, the accelerant is
operational excellence: shipping faster, selling cleaner, retaining better, and scaling with fewer mistakes.
Acceleration doesn’t always mean “spend more.” Sometimes it means “waste less.”

7) Category clarity: Twilio and Coupa weren’t inventing demand from scratch

This is the underrated lesson. Twilio sold into communications spend that already existed. Coupa sold into
procurement/spend control that already existed. Both were “new” in execution, but “familiar” in value. That
combination is a cheat code: innovation without needing to educate the market from zero.

The catch: acceleration doesn’t remove physics

The SaaStr post had an almost motivational-poster vibe (“don’t settle!”), but the real world adds nuance:
hypergrowth at scale is possible, but not free. Competition is intense, customers churn if value is unclear,
and operational complexity increases fast.

That’s why metrics like the Rule of 40 became popular: they force an honest tradeoff conversation between growth
and profitability. If you’re sprinting, finebut make sure you’re sprinting toward something, not just away from
a board meeting.

How to apply the Coupa + Twilio lesson to your SaaS today

Pick a value metric that naturally expands

Twilio’s value metric (usage) expands when the customer wins. Coupa’s expands when the customer standardizes
processes, adds departments, and increases spend under management. Your job is to find a value metric that grows
with customer successthen make sure the customer can see that success.

Shorten time-to-value like your runway depends on it (because it does)

Acceleration is often just “getting to the aha moment faster.” If setup takes six weeks, you’re renting your
growth rate from patience. Improve onboarding, templates, integrations, and default workflows so customers feel
value early and often.

Engineer expansion loops, then protect customers from surprise bills

Usage-based models can supercharge growth, but they require transparency: budgets, alerts, caps, forecasting,
and “here’s what changed” reporting. Customers love paying more when they feel more value. They hate paying more
because they got accidentally popular on a Tuesday.

Sell into existing budgets whenever possible

Coupa’s procurement story and Twilio’s communications story both point to the same reality: it’s easier to win
when money is already allocated. Your product can be innovative, but your buyer needs a familiar line itemor at
least a familiar pain.

2025 lens: acceleration is real, but it shows up differently now

The 2016 benchmark reset happened during a strong SaaS expansion era. Fast forward, and SaaS has gone through
whiplash: boom, pullback, efficiency era, and now a new wave driven by AI and platform consolidation.
Recent benchmarking analysis has shown growth rates across top private cloud companies rebounding after a dip,
while broader private SaaS survey data suggests growth expectations are more modest and retention is steadier
than the “hypergrowth forever” narratives.

Translation: the bar is still high, but the playbook is more operational. Investors and buyers increasingly want
durable growth, clean retention, and sane unit economicsnot just a cool chart that goes up-and-to-the-right.

Field Notes: of Real-World Experiences Around Coupa + Twilio

If you’ve ever watched a company roll out spend management software, you learn quickly that the “hard part” isn’t
the feature listit’s behavior change. The first week feels easy: finance is excited, procurement is hopeful,
and someone says, “Once this is live, approvals will finally be consistent.” Then reality arrives wearing a badge
that says Legacy Process.

In many Coupa-style deployments, the earliest wins come from visibility: teams finally see where money goes, who
buys what, and which vendors show up on invoices like uninvited guests at Thanksgiving. But the next phase is
adoption. Employees don’t wake up craving purchase orders. They comply when the workflow is simple, the catalog
is clean, and the system doesn’t make them feel like they’re applying for a passport just to buy a keyboard.
Organizations that succeed treat rollout like a product launch: internal enablement, clear “why,” and small,
repeatable workflows before trying to boil the ocean.

Twilio-style growth stories often look different but rhyme in an important way: value shows up fast. A team adds
SMS notifications or verification flows and suddenly users complete onboarding more reliably, support tickets drop,
and the product feels more alive. The “experience lesson” here is that communications become part of your core
productso you inherit the responsibility that comes with it. Deliverability, carrier filtering, fraud prevention,
opt-in compliance, and geographic edge cases can quietly become your new full-time hobbies if you’re not careful.

The other big real-world lesson with usage-based platforms is emotional: customers love flexibility until they
get surprised. Smart teams build dashboards, alerts, and caps early. They make cost behavior visible to customers
and to their own finance team. They also learn that “usage” can spike for good reasons (growth) and bad reasons
(abuse). Your pricing model becomes a product surface area.

Put these together and you get the practical meaning of SaaS acceleration: it’s not just growing faster. It’s
reducing the time between “we bought it” and “we can’t live without it,” while designing expansion that feels
fair, predictable, and tied to real outcomes. Coupa and Twilio are different animals, but they both show what
happens when SaaS aligns with existing budgets, proves value early, and compounds inside accounts without forcing
customers to re-approve the relationship every quarter.

Final takeaway

The “Coupa + Twilio” benchmark wasn’t a dare to chase vanity growth. It was a reminder that SaaS markets expanded,
buyer behavior evolved, and product + distribution got faster. Acceleration is possiblebut it’s earned through
clarity (value metrics), speed (time-to-value), and compounding (expansion loops) more than sheer hustle.