Key Strategies for Scaling Revenue Today with Confluent President of Field Operations Erica Schultz (Pod + Video)

Scaling revenue “today” feels a little like trying to build a rocket while it’s already in flightand your investors are asking if the rocket can also be a submarine. The good news: you don’t need a miracle. You need focus, a connected customer experience, and an operating system that turns market signals into repeatable growth.

In a SaaStr pod + video conversation, Erica Schultz (President of Field Operations at Confluent) laid out a refreshingly practical playbook for doing exactly that: grow faster and operate cleaner. Not “growth at all costs.” Not “efficiency theater.” Real, durable revenue scalewithout your teams living in spreadsheet purgatory.

Why Erica’s perspective hits different: Field Ops is where strategy meets reality

“Field Operations” is one of those titles that sounds mysterious until you realize it’s basically the grown-up in the room for go-to-market execution: sales, business development, customer success, and the operating rhythms that keep it all from turning into improv comedy. Erica’s job is to scale those functions globallyso the revenue engine doesn’t just run, it runs predictably.

And that’s the heart of scaling revenue in 2026: not just winning deals, but building a system where winning deals becomes the normal Tuesday.

Strategy 1: Align on your ideal customer and personas (or prepare for friendly internal chaos)

If your marketing team thinks you sell to “mid-market fintech,” sales thinks you sell to “anyone with budget,” and product thinks you sell to “developers who love docs,” congratsyou’re about to scale confusion.

Erica’s starting point is almost boring in its simplicity, which is exactly why it works: everyone needs a shared understanding of the customer. In her words: “Everyone in your company should share a common understanding of who your customer is.”

How to make alignment real (not just a workshop with sticky notes)

• Lock the ICP: define firmographics (industry, size, maturity), pain signals, and “this will never work” disqualifiers.
• Map personas: list who shows up in the buying and adoption cycle (developers, architects, security, finance, exec sponsors).
• Define moments that matter: what does “value” look like for each persona (time saved, risk reduced, speed gained, cost lowered)?
• Use market signals: combine product telemetry, website intent, community engagement, support themes, and competitive context.

The payoff: cleaner messaging, tighter qualification, better pipeline quality, and fewer “why are we selling this to them?” meetings. (Those meetings will never fully disappear, but you can reduce them to a healthy, sustainable level.)

Strategy 2: Design a connected customer experience that accelerates adoption and expansion

Revenue scale doesn’t come only from closing. It comes from customers adopting, expanding, renewing, and becoming loud advocates who make your pipeline cheaper. Erica’s emphasis: design a customer experience that connects digital and human touch points, tailored by persona and context.

Three questions that unlock expansion

1. How do customers derive value? What outcome do they actually want?
2. How do they measure that value? What metrics, dashboards, or business results prove it?
3. What’s the next expansion story? What adjacent use case becomes obvious once the first one works?

This is where most companies accidentally slow themselves down: the handoffs are messy, the journey is generic, and the customer gets the same email nurture regardless of whether they’re a hands-on engineer or an executive sponsor.

Make the experience “connected” (not just “present”)

• Orchestrate touch points: digital onboarding + office hours + CSM check-ins + technical workshops.
• Keep context: every team should see the customer’s goals, current usage, blockers, and success plan.
• Build advocacy moments: don’t ask for a case study on Day 12; ask when the customer has a win they’re proud of.

When you do this well, expansion becomes less “sales push” and more “helpful next chapter.” And that’s how you scale without burning trust.

Strategy 3: Combine product-led growth and enterprise sales (the “multiplier,” not the identity crisis)

Many companies treat product-led growth (PLG) and enterprise sales like rival siblings fighting over the remote. Erica’s stance is more pragmatic: you can start with one model and grow into the other, creating a hybrid that matches how different personas prefer to buy.

A classic motion: start bottom-up with developers who want self-serve, then layer enterprise engagement as the account expands, stakeholders multiply, and governance/security needs get serious.

What hybrid GTM looks like in practice

• PLG for discovery: easy trials, clear docs, fast time-to-value, transparent packaging.
• Sales for complexity: multi-team rollouts, procurement, security reviews, architecture design, exec alignment.
• Customer success for durability: adoption programs, success plans, expansion roadmaps, renewal health.

The key is to avoid the awkward middle where sales “interrupts” PLG (forcing calls too early), or PLG “undercuts” sales (confusing pricing and entitlements). Your job is to choreograph, not to choose a favorite child.

Strategy 4: Promote a consumption-based culture (where revenue follows outcomes, not promises)

Erica highlights the shift from subscription-centric thinking to consumption-led thinking. In a consumption model, revenue tracks actual usage, which forces a healthy obsession with customer outcomes.

Here’s the part many teams underestimate: consumption is a culture change. You can’t just change pricing and hope everyone magically thinks differently on Monday morning.

How to operationalize consumption thinking

• Make usage everyone’s business: product, support, success, sales, and marketing all influence consumption.
• Instrument the value moments: track activation milestones that correlate with retention and expansion.
• Create “usage plays”: if a customer hits X threshold, trigger enablement; if they stall, trigger rescue.
• Align incentives carefully: reward the behaviors that grow sustainable usage, not short-term paper wins.

Done right, consumption models can create a cleaner alignment: customers pay more when they get more value. Done wrong, it becomes a surprise bill and a surprise churn event. (Nobody likes surprise billing. Nobody.)

Strategy 5: Maximize growth while increasing efficiency (focus, playbooks, speed)

The “efficient growth” era didn’t endit matured. Investors and boards still want topline growth, but they also want evidence that you can scale without lighting your operating model on fire.

Erica’s trio is refreshingly actionable:

1) Stay focused

Pick the segment, industry, or market where your product wins with the least friction. Expand once you’ve earned the rightmeaning you have repeatable wins, references, and a conversion story that doesn’t rely on heroics.

2) Invest in a repeatable playbook

Scaling isn’t hiring more reps; it’s enabling more reps to succeed faster. Capture what works into living playbooks: discovery prompts, qualification criteria, messaging by persona, objection handling, mutual success plans.

3) Solve for speed

Speed is a growth strategy disguised as an operations project. Look at every critical cyclehiring, ramp, onboarding, security review, implementationand ask, “What would it take to cut this in half?” Then do the unglamorous work that actually cuts it in half.

Strategy 6: Build a modern RevOps engine (the system behind predictable revenue)

If scaling revenue is the goal, Revenue Operations (RevOps) is the scaffolding. RevOps aligns marketing, sales, and customer success around shared data, processes, and executionso the customer experience is continuous, not a relay race where everyone drops the baton.

Forecasting that doesn’t cause migraines

A strong forecast is less about being psychic and more about being disciplined: clear stages, consistent definitions, and honest probability categories. Many teams use forecast categories like “pipeline,” “best case,” and “commit” to distinguish optimism from reality, which helps leadership plan hiring, spend, and targets without guessing.

Pipeline management: make it a habit, not a quarterly panic

• Define stage exit criteria: don’t let deals move forward because someone “feels good.”
• Track conversion rates by stage: bottlenecks usually show up as stage leaks or stage parking lots.
• Coach to leading indicators: meeting quality, stakeholder coverage, mutual plan progress, next-step clarity.
• Keep hygiene non-negotiable: bad CRM data scales into bad decisionsfast.

Capacity planning: stop hiring “because vibes”

Efficient growth requires capacity math: ramp time, quota attainment distributions, territory potential, and support coverage. If you want predictable revenue, your capacity model has to be more solid than “we’ll just add 10 reps and hope.”

Strategy 7: Drive transformation without breaking your team’s confidence

Scaling revenue often requires operational change: new personas, new metrics, new pricing, new motions. Erica’s guidance is basically change management in plain English: take the team on the journey, enable them to win in the new system, and be crystal clear about the metrics that matter.

Three rules for change that sticks

1. Share the logic: don’t just announce a changeexplain why it’s happening and what problem it solves.
2. Enable confidence: train, coach, provide examples, and give teams a safe way to practice.
3. Define the new scoreboard: name the behaviors, metrics, and expectations so leaders can coach consistently.

The transformation isn’t complete when leadership agrees. It’s complete when the front line behaves differently. (And yes, that takes longer than one all-hands. Sorry.)

Strategy 8: Make customer success a company sport (because expansion is the cheapest “new logo”)

One of Confluent’s stated values is “Earn Our Customers’ Love,” and Erica frames customer success as a whole-company responsibility, not a department you call when renewals get scary.

This matters because sustainable scale relies on retention and expansion. If your product solves meaningful problems, then helping customers realize value faster is a direct revenue strategy, not just “support being nice.”

Ways to operationalize “customer love” without being cheesy

• Customer Advisory Boards: get strategic customers into structured feedback loops.
• Technical architects: reduce time-to-value and de-risk complex implementations.
• Adoption playbooks: repeatable onboarding and enablement that matches persona needs.
• Advocacy programs: turn wins into references, reviews, and community credibility.

When customer outcomes are consistently achieved, you earn expansion with less frictionand your GTM engine becomes stronger as it grows.

Strategy 9: Treat your GTM like a “real-time system” (because customers move faster than your QBR slides)

Confluent’s world is real-time data streaming, and there’s a useful metaphor here: modern revenue scale depends on signals and response.

Think of the best GTM orgs as event-driven:

• Signal: product usage spikes, new team adoption, feature activation, support patterns, intent surges.
• Decision: categorize health, expansion potential, risk level, stakeholder coverage.
• Action: trigger the right motionself-serve enablement, CSM outreach, sales expansion, exec alignment.

This is how you scale revenue “today” without scaling chaos: you build a system that listens continuously and responds appropriatelyacross digital and human touch points.

30-day quick-start checklist (for leaders who want results, not just inspiration)

1. Write your ICP on one page and get marketing, sales, and product to sign it (metaphorically… or literally, if you’re dramatic).
2. Create a persona map that includes who buys, who builds, who blocks, and who benefits.
3. Define 3–5 activation milestones that represent real customer value.
4. Audit your customer journey for broken handoffs, duplicated touches, and missing “value proof” moments.
5. Pick one efficiency project that cuts a cycle time in half (ramp, onboarding, security review, implementation).
6. Standardize forecast categories and stage exit criteria so your forecast is a tool, not a bedtime story.
7. Launch one expansion play triggered by usage and outcomes, not random calendar reminders.

Conclusion: Scale revenue by scaling clarity

Erica Schultz’s approach is the opposite of flashy: align on the customer, connect the experience, combine the right growth motions, embrace usage and outcomes, and run your GTM like an operating systemcomplete with playbooks, metrics, and change management.

The result isn’t just more revenue. It’s more controllable revenue. And in a world where markets swing and buying committees multiply, controllable revenue is the closest thing we have to a superpower.

Field Ops Experiences: 7 “Been There” Lessons That Make Scaling Revenue Feel Less Like Doom

To make this practical, here are real-world style experiences (the kind that don’t show up on the “perfect funnel” diagrams). If you’ve ever tried to scale revenue while your org is growing, your product is evolving, and your customer personas are multiplyingwelcome home.

1) The ICP argument that saved Q4

A team I worked with had a “strong pipeline” that looked impressive right up until the moment deals started slipping in bulk. The post-mortem was painfully consistent: they were selling to companies that could buy, not companies that should buy. Once we tightened ICPexplicit disqualifiers includedthe pipeline got smaller for about three weeks…and then conversion jumped. The best compliment we got from a rep: “My calendar is less full, but my forecast is more real.”

2) The playbook that made onboarding boring (the highest praise)

New hires used to ramp by shadowing “the legend,” learning tribal knowledge, and picking up bad habits like souvenirs. We built a living playbook: discovery questions by persona, proof points by industry, a mutual plan template, and a “what good looks like” demo checklist. Ramp time dropped, but more importantly, ramp variability dropped. Leadership stopped praying for hero reps and started building consistent reps. Boring onboarding is scalable onboarding. Your future self will thank you.

3) The “solve for speed” experiment that felt illegal

We mapped the customer onboarding process and found it was slow for a silly reason: approvals and handoffs. The experiment was simple: pre-approve common configurations, standardize security artifacts, and give the CSM a “fast lane” option. Cutting time-to-value in half didn’t just improve customer happinessit changed expansion timing. Customers who saw wins earlier started asking, “What else can we do?” earlier. Speed created revenue gravity.

4) The forecast cleanup that ended the weekly panic

Forecast calls were emotional rollercoasters because everyone used different definitions of “likely.” We standardized forecast categories, tightened stage exit criteria, and forced next steps to be specific (“Security review scheduled with Jane on Tuesday” beats “Customer reviewing”). Suddenly, leadership could plan. Reps could coach. And the team stopped discovering problems only after the quarter ended. The forecast didn’t become perfectit became useful, which is the whole point.

5) The hybrid PLG + sales moment that unlocked the enterprise

A developer-led product had lots of grassroots usage, but enterprise expansion was inconsistent. The fix wasn’t “more sales pressure.” It was choreography: keep self-serve friction low, use product signals to identify serious internal adoption, then bring sales in when stakeholders and governance appeared. That timing shift turned sales from “interrupting” into “helping.” The same accounts that ignored outreach before started saying yesbecause the outreach was relevant.

6) The consumption mindset shift that changed internal behavior

The hard part of consumption isn’t meteringit’s mindset. Teams initially treated usage like a dashboard KPI someone else owned. Once we built cross-functional “usage plays” (product nudges, enablement content, CSM workshops, sales expansion), usage became an everyone sport. The funniest moment: marketing and support celebrating the same customer milestone. That’s alignment you can’t fake.

7) The customer love moment that made pipeline cheaper

A customer hit a major success milestone and casually mentioned it in a support thread. The CSM didn’t just close the ticketthey asked one question: “Would you be open to sharing how you did that with peers?” That turned into an advocacy story, then a reference, then two inbound opportunities that converted faster because trust was pre-loaded. “Customer love” sounds fluffy until it shows up as faster cycles and lower acquisition costs.

If there’s one theme across all these experiences, it’s this: scaling revenue is scaling clarity clarity about who you serve, how they get value, how you expand responsibly, and how your internal machine runs without constant reinvention.