Scaling Your Team: Lessons Cloudflare’s CRO Chris Merritt Learned Scaling from $1M to $1B ARR (Pod 638 + Video)

Scaling a revenue team from “we just hit $1M ARR” to “wait… are we really flirting with a billion?” is less like climbing a mountain and more like building an airplane while it’s already in the air, while the passengers keep asking if you can “just add a hot tub.”

In SaaStr Pod 638 + Video, Cloudflare’s founding CRO Chris Merritt shares a set of battle-tested lessons for growing teams through the messy middlewhen the company is too big to wing it, but still too small to hide mistakes behind “process.” The best part: these aren’t abstract leadership fortune cookies. They’re practical, stage-specific moves you can borrow immediatelyespecially if you’re building sales and go-to-market teams for technical buyers.

Below is an in-depth, no-fluff breakdown of what Merritt learned while helping scale Cloudflare’s revenue orgplus extra, field-tested experiences and examples to help you apply the ideas without needing a 47-slide “alignment deck” (aka the corporate version of a cry for help).

Why Cloudflare Is a Great “Scaling Lab” for Revenue Leaders

Cloudflare is a particularly instructive scaling story because it didn’t grow by selling cute dashboards to people who love dashboards. It grew by winning trust with technical usersengineers who can smell salesy nonsense from three ZIP codes away. That forced the revenue org to behave differently: less “always be closing,” more “always be credible.”

As the company expanded, it also had to evolve into a more enterprise-capable motionhandling larger contracts, longer decision chains, and customers who expect governance, predictability, and someone to answer emails that start with: “Per section 9.3 of the MSA…”

The takeaway: if your product is developer-friendly, PLG-leaning, or sold to deeply skeptical buyers, Cloudflare’s journey is a masterclass in scaling a revenue team without setting your brand trust on fire.

The 3 Phases Merritt Uses to Explain Growth (and Why They Matter)

One of the most useful frameworks from Pod 638 is Merritt’s simple, three-phase view of company growthbecause the “right” org design at $8M ARR can be painfully wrong at $80M, and borderline illegal at $800M.

• Phase 1: Less than $50M ARR uncertainty is the default setting.
• Phase 2: $50M–$250M ARR the metrics start talking (loudly), and you need to listen.
• Phase 3: $250M–$1B ARR endurance, governance, and board-level maturity become non-optional.

Let’s unpack what changes in each phaseand how to scale your team without accidentally scaling chaos.

Phase 1 (Under $50M ARR): Hire Builders, Not Tour Guides

Early-stage scaling is brutally simple: everything breaks, all the time. The product breaks. The onboarding breaks. The pricing page breaks. Your CRM breaks because someone “cleaned it up” with a spreadsheet.

Merritt’s advice is to prioritize builderspeople who take on ambiguous problems, create structure, and keep moving. In this phase, you’re not assembling a museum staff to politely explain exhibits. You’re assembling a construction crew to finish the building before the roof caves in.

What “Builder” Looks Like in Revenue Roles

• High tolerance for ambiguity: they don’t panic when the playbook is still being written.
• Process curiosity: they document what works and what doesn’t (instead of reinventing every Tuesday).
• Customer empathy: they can be helpful without being needy, confident without being pushy.
• Cross-functional stamina: they partner with product and engineering instead of treating them as “ticket machines.”

Celebrate Big Wins (Because the Work Is Long)

In Phase 1, Merritt emphasizes celebrating major company winsnot individual heroics. It’s easy to over-index on lone-wolf performance early on, but that creates a culture where collaboration is “optional” and burnout becomes a hiring strategy.

Practical move: create a lightweight ritual for wins that matterfirst enterprise customer, first major renewal, first quarter where onboarding doesn’t cause chaos. You’re not throwing confetti for every closed-won. You’re marking milestones that prove the machine is getting real.

Stay Under Capacity (Yes, Really)

This is counterintuitive but important: Merritt warns that leaving teams with too much excess capacity can harm morale. Early teams want momentum. If the calendar is suspiciously empty, people start wondering if the business is realor if they accidentally joined a very polite group chat.

The trick is to avoid “fake busy” while still ensuring the team is engaged: focus on customer learning, sales-cycle speed, and rapid iteration.

Sell Like a Peer to the Technical Buyer (Not Like a Stereotype)

In related discussions about Cloudflare’s growth, Merritt describes removing pressure-filled sales tactics in initial customer interactions. The goal: have the team behave like peerscredible problem-solvers who answer questions honestly, even when the answer isn’t “buy now.”

This approach is especially powerful when your buyers are engineers. Engineers don’t want a performance; they want clarity. When sales shows up like a helpful expert instead of a scripted closer, trust compounds fastand trust is the only “shortcut” that doesn’t come with a lawsuit later.

A Small Change That Signals a Big Philosophy

One story from the Cloudflare context: even role naming mattered. “Sales” can imply pressure; “Customer Development” implies help and learning. Whatever you call it, the principle is the same: optimize for customer truth early, not just customer conversion.

Phase 2 ($50M–$250M ARR): Let Metrics Be the Bad Cop

Once you’re in the $50M–$250M range, you can’t manage by vibes. That doesn’t mean you become a spreadsheet cult. It means you set up consistent metrics, interpret them honestly, and stop telling yourself bedtime stories like: “Churn is just a seasonal thing.”

1) Monitor Metrics Consistently (and Objectively)

Merritt’s guidance is straightforward: build consistency into how you track metrics and treat the numbers as realitynot as suggestions. In this phase, leadership teams often discover the difference between “we’re growing” and “we’re growing efficiently.”

At minimum, revenue leaders should have high confidence in:

• Pipeline health: volume, quality, conversion rates, and where deals stall.
• Sales-cycle length: especially by segment and product line.
• Expansion + retention: net revenue retention, gross retention, renewal risk.
• Sales productivity: ramp time, quota attainment, deal size trends.

2) Hone in on the Ideal Customer (Stop Collecting “Bad Revenue”)

Phase 2 is where “not all revenue is good revenue” stops being a cute phrase and becomes a survival requirement. Merritt warns that if you stack your customer base with the wrong profilescustomers who churn quickly or have no expansion potentialyour growth will eventually roll back.

Translation: if your ICP is “people with money,” you don’t have an ICP. You have a wish.

Practical moves:

• Segment customers by retention and expansion potential (not just by industry label).
• Audit churn by cohort and by source (PLG inbound vs outbound vs partners).
• Define “qualification” as long-term fit, not short-term persuasion.

3) Stay Humble and Curious (Even When You’re Winning)

In Phase 2, the questions get harder, expectations rise, and leadership is often asked to “go faster” even when performance is strong. Merritt’s guidance: don’t pretend to have every answer. Build a culture where “we haven’t cracked the code yet” is acceptableas long as the team is actively cracking it.

Bottom-Up Meets Top-Down: Don’t Skip the Middle Step

A recurring theme in Cloudflare’s go-to-market evolution is the hybrid motion: pairing bottom-up adoption (technical users solving urgent problems) with top-down enterprise selling (larger contracts, broader rollouts, executive alignment).

The middle step matters: early technical users often have existing budgets they can use quickly. Serve them well, solve the problem fast, and you earn the right to expandteam by team, department by department. This helps avoid the common mistake of leaping directly into big enterprise deals without enough product proof or internal champions.

How to Operationalize a Hybrid Motion

• Start with “pain-budget” deals: small, urgent problems that teams can fund without a six-month committee meeting.
• Build internal champions: make early users successful and visible inside their org.
• Convert usage into narrative: document impact (performance, security posture, cost savings).
• Then go top-down: expand into standardized rollouts with exec sponsorship and procurement support.

Phase 3 ($250M–$1B ARR): Endurance, Governance, and “Comfortable Uncomfortable”

By Phase 3, the company is no longer proving it can workit’s proving it can keep working. Merritt frames the key challenge as endurance: sustaining growth, building leadership depth, and operating with governance that doesn’t suffocate speed.

1) Embrace Governance (It’s a Framework, Not a Punishment)

Merritt’s point is refreshingly unromantic: governance exists because leaders can’t see everything anymore. A good governance framework helps you operate with confidence rather than anxiety. It clarifies ownership, decision-making, and accountabilityso execution isn’t dependent on one heroic leader holding the entire company in their head.

Governance in revenue orgs often looks like:

• Clear segment ownership and deal-approval rules (so big deals don’t become internal cage matches).
• Standardized forecasting and pipeline definitions (so “commit” actually means commit).
• Capacity planning and headcount discipline (so hiring matches demand, not optimism).

2) Get Comfortable Being Uncomfortable

In Phase 3, everything gets measuredand you get judged by those numbers. That creates uncomfortable conversations: performance gaps, comp changes, territory redesigns, team restructures, hard product feedback from large customers, and the occasional “why does this forecast look like a work of fiction?”

The leadership skill here isn’t avoiding discomfortit’s processing it quickly and turning it into decisions.

3) Maintain a Strong Board Relationship (No Surprises, No Theater)

As companies scale, boards often become more oversight-driven. The healthiest relationships are built on clarity, consistency, and trustnot on last-minute hero narratives. Don’t hide problems; contextualize them. Don’t overpromise; show the plan.

A simple, effective rhythm:

• Share leading indicators (pipeline, sales-cycle shifts, retention signals), not just lagging results.
• Bring tradeoffs to the board (e.g., growth vs margin vs risk), not just “updates.”
• Use pre-reads and structured metrics so meetings are decisions, not detective stories.

Solutions Engineers: Not Optional When the Buyer Is Technical

A key Cloudflare-aligned lesson: involving solutions engineers early helps keep technical engagements high-quality. If your buyer expects depth, you can’t “wing it” with shallow discovery questions and a demo that looks like a magic trick.

Practical ways to scale SE impact:

• Codify the technical “first call”: what must be answered, what can be deferred, what’s a red flag.
• Build repeatable technical assets: reference architectures, migration playbooks, proof-of-concept templates.
• Align SE staffing with segment strategy: enterprise vs mid-market vs PLG-assisted conversion paths.

Comp Plans Should Match How Customers Actually Buy

Modern go-to-marketespecially with PLG, freemium, and expansion-led growthdoesn’t always fit traditional comp structures that reward only the initial big deal. Merritt emphasizes evolving compensation to align with long-term customer success and retention, not just the dopamine hit of “closed-won.”

If your comp plan pays people to sell something customers don’t want to buy that way, you will eventually get what you paid for: short-term revenue and long-term regret.

What Alignment Can Look Like

• Incentives that encourage healthy land-and-expand motions (not rushed oversells).
• Credit for expansions and renewals where appropriate (so teams invest post-sale).
• Clear rules so reps don’t spend more time debating credit than serving customers.

A Practical Playbook: How to Scale Your Team Without Scaling Chaos

Here’s how to translate the lessons into concrete actions, broken into a simple operating checklist.

Phase 1 Checklist (Under $50M ARR)

• Hire builders: flexible generalists who can do discovery, close, and learn fast.
• Document learnings: calls, objections, onboarding patterns, technical pitfalls.
• Speed & feedback loops: shorter sales cycles beat perfect pitch decks.
• Company-wide wins: celebrate milestones that signal product-market proof.

Phase 2 Checklist ($50M–$250M ARR)

• Metrics discipline: consistent pipeline definitions and forecasting cadence.
• ICP clarity: stop chasing customers who churn quickly or can’t expand.
• Hybrid motion build-out: create a path from bottom-up usage to enterprise rollout.
• Enablement basics: onboarding, messaging, competitive clarity, technical playbooks.

Phase 3 Checklist ($250M–$1B ARR)

• Governance: decision rights, deal desks, forecasting rigor, capacity planning.
• Leadership depth: invest in managers, not just individual contributors.
• Board partnership: transparency, leading indicators, tradeoff framing.
• Endurance culture: sustainable pace, clear accountability, fewer heroics.

Common Scaling Mistakes (That Look Smart Until They Aren’t)

1) Hiring for “Experience” When You Needed “Adaptability”

A résumé packed with logos is not a guarantee someone can build. Early and mid-stage scaling requires people who can create structure from chaos, not people who require structure before they can function.

2) Skipping the Middle Step to Enterprise

If you jump straight to top-down selling without bottom-up proof, you’ll spend months chasing executive interest with no internal champions. Enterprise deals love internal momentum; they hate lonely optimism.

3) Confusing Activity With Progress

More meetings, more decks, and more “alignment” can be a symptom of unclear ownership. Scale doesn’t mean doing more; it means doing the right things repeatedly, with fewer surprises.

Conclusion: The Real Secret Is Stage-Fit

The most important message from Merritt’s scaling lessons is that great revenue leadership is stage-aware. You don’t run a $10M ARR team like a $200M ARR team. And you definitely don’t run a $700M ARR team like a scrappy startupunless you enjoy board meetings that feel like courtroom dramas.

If you take one thing from Pod 638, make it this: your job isn’t to scale headcount. Your job is to scale clarityclarity of who you serve, how you sell, what you measure, and how decisions get made.

Do that well, and the team scales with far less pain. Do it poorly, and you’ll still scalejust into a larger, more expensive version of confusion.

Extra: of Real-World “Scaling Team” Experiences You Can Steal

Here are some additional, experience-based patterns that consistently show up when companies scale revenue teams from early traction to serious scale. These aren’t Cloudflare-specific, but they line up tightly with the principles Merritt describesespecially around builders, hybrid motions, and governance.

1) The First Sign You Need to Scale Isn’t GrowthIt’s “Breakage”

Many teams wait for a revenue milestone to justify hiring. In practice, the better signal is operational breakage: reps can’t follow up fast enough, solutions engineers are booked out for weeks, onboarding quality drops, deals stall because approvals are unclear, or customer handoffs feel like a relay race where everyone drops the baton. When the system breaks, your best people spend their days doing damage control instead of compounding progress.

2) Your Best Early Reps Accidentally Become Product Managers

In technical markets, early sales conversations are often disguised product discovery. The strongest early reps don’t just “close”; they translate customer pain into patterns the product team can act on. A huge scaling unlock is creating a lightweight, repeatable way to capture that learningcall tags, objection libraries, win/loss notes, and a monthly “what we’re hearing” digest that engineering actually reads.

3) Comp Plans Break Quietly Before They Break Loudly

Compensation misalignment rarely explodes on day one. It decays: reps optimize for the easiest commission path, customers get oversold, churn creeps up, and leadership blames “execution” instead of incentives. The fix is not “pay people less.” The fix is paying people for outcomes that match your motion: healthy lands, expansions that stick, and customer success that becomes a growth engine. If your product is PLG-heavy, traditional “big upfront” comp can accidentally punish the exact behavior that creates long-term growth.

4) The Middle Layer of Management Is a Scaling Multiplier (and a Risk)

When you go from a handful of reps to dozens, the management layer becomes the lever. Great managers scale coaching, pipeline hygiene, and predictable execution. Weak managers scale confusion, politics, and forecast fantasy. One practical habit: promote or hire managers who can teach the craft, not just people who hit quota once and can talk loudly about it.

5) Governance Can Feel SlowerUntil You Measure the Rework It Prevents

Teams resist governance because it feels like “overhead.” But the alternative is hidden overhead: rework, inconsistent pricing, messy approvals, legal escalations, and reps making up terms to get deals over the line. A good governance layer makes the organization faster by eliminating avoidable chaos. If you’re allergic to bureaucracy, frame governance as “decision-speed insurance.” You’re not adding process to feel importantyou’re adding it to stop paying the same chaos tax every quarter.

If you combine these experience-based patterns with Merritt’s phase-specific approach, you get a clear north star: scale the team by scaling repeatabilityin hiring, in selling, in measuring, and in decision-making. That’s how you grow from $1M to $1B without turning your org chart into a haunted house.

SEO Tags