← All Episodes
Jerez · Appega SaaS ·

Scale Customer Success Team B2B: Lessons from $100M ARR

How Appega scaled customer success to $100M+ ARR using trust, cultural brokers, and AI automation. Tactical guide for B2B SaaS founders and GTM leaders.

Also listen on: Spotify
Contents

Scale Customer Success Team B2B: Lessons from $100M ARR

To scale a customer success team in B2B SaaS, you need three non-negotiable pillars: a trust-first team culture where failure is openly discussed, AI-powered automation that eliminates repetitive compliance and workflow tasks, and deliberate cross-functional connectors—what Jerez calls “cultural brokers”—who bridge CS, product, and sales. Jerez led customer success at Appega from early stage through $100M+ ARR, and the playbook he used centers on empathy, intimate customer engagement, and psychological safety before any headcount scaling decision is made.


The Problem With How Most Teams Scale Customer Success

Compliance is unglamorous. Security is unglamorous. And customer success, particularly in B2B SaaS companies where the core product handles regulatory automation, rarely makes the priority list when founders are planning the quarter.

Jerez, a Harvard Business Review Council member and cybersecurity veteran since a startup acquired by Sun Microsystems in 2008, now leads customer success at Appega—a SaaS company specializing in compliance automation that has crossed $100M ARR. He opens with a statement that reframes the entire scaling problem:

“Write down 10 things you want to do — you only have time for seven or eight. Compliance? None of them are security compliance. It’s not sexy, but it’s essential and it’s a bit boring.” — Jerez, Customer Success Leader at Appega

That’s the market reality your CS team is selling into. Your customers are not waiting for your QBR deck. They are already behind on the tasks that matter to them, and compliance sits at the bottom of that list by default. Scaling a CS team without understanding this operating context produces high-activity, low-impact teams.


Key Takeaways

Scaling customer success in B2B SaaS requires more than adding headcount. Jerez’s approach at Appega—reaching $100M+ ARR—centers on psychological safety within teams, AI-driven automation of repetitive tasks, and a go-to-market motion built on genuine customer empathy rather than transactional selling. Cultural brokers who connect cross-functional teams, intimate engagement formats over mass conferences, and education-first positioning are the operational levers that compound over time.


Deep Dive: How Jerez Scaled CS at Appega to $100M ARR

How Do You Build a High-Performing Customer Success Team From the Ground Up?

Building a high-performing CS team starts with psychological safety—the leadership-created environment where team members feel empowered to make decisions, share failures without fear, and engage in uncomfortable conversations. Without this foundation, scaling CS headcount creates a larger dysfunctional team, not a more effective one. Jerez’s model at Appega prioritizes trust-building as an operational prerequisite, not a cultural aspiration.

Every CS scaling conversation starts with organizational health. Jerez is direct about where most teams fail:

“It all starts with trust. When you have a team that by and large distrusts each other…it’s upon the leadership to create that kind of culture or ecosystem so that people come to work and they feel empowered to be able to make decisions.” — Jerez, Customer Success Leader at Appega

This is not a soft management insight. The operational implication is concrete: CS reps who distrust leadership or colleagues hide bad news. They delay surfacing churn signals. They under-report customer dissatisfaction. By the time the data shows a problem, the renewal is already lost.

The fix is behavioral, not structural. Jerez’s approach:

  1. Normalize failure sharing — create explicit forums where losses are debriefed without blame
  2. Support relationship-building outside work — team activities and social gatherings accelerate trust faster than any internal program
  3. Empower decision-making at the rep level — leaders who over-escalate destroy confidence; leaders who trust reps build it

The Cultural Brokers Model: Your Missing Cross-Functional Layer

Once individual trust is established, the next scaling challenge is cross-functional collaboration. CS teams that can’t communicate effectively with product, engineering, and sales are structurally limited in what they can deliver to customers.

Jerez’s solution is not to redesign the org chart. It’s to identify and empower cultural brokers:

“Find bridges and atlases who are people who are very good at making connections or people who are very good at bringing people together due to their aptitude and the technical abilities.” — Jerez, Customer Success Leader at Appega

Cultural brokers are not managers. They are individuals—at any level—who have both the interpersonal credibility and the technical fluency to connect functions that would otherwise operate in silos. Their formal role may be CS account manager or solutions engineer, but their informal role is organizational connective tissue.

How to operationalize this:

StepActionOutput
1. IdentifyMap who people go to informally for cross-team questionsBroker candidates list
2. AssignGive brokers explicit permission to facilitate cross-functional discussionsReduced escalation loops
3. EnableProvide time and access for relationship-building across departmentsFaster internal alignment
4. SupportInclude brokers in leadership-level planning sessionsUpstream influence for CS
5. MeasureTrack how quickly cross-functional issues resolve pre- and post-broker activationOperational improvement data

This model works because it operates through existing social capital rather than creating new bureaucratic layers. The brokers already have the trust—you’re formalizing their influence.


How Does AI Automation Change the CS Scaling Equation?

AI automation removes the per-headcount constraint from repetitive compliance and workflow tasks, allowing CS teams to scale impact without proportional headcount growth. The efficiency gain is concentrated in eliminating “mundane tasks”—status checks, compliance monitoring updates, regulatory change alerts—and making them repeatable and automated. This frees CS reps for strategic customer conversations that AI cannot replace.

The compliance automation market has a specific AI opportunity that Jerez identifies clearly:

“Automation is a huge driver for this space and obviously with the infusion of AI there’s expectations that…the most important thing is how can we take some of the mundane tasks and make it repeatable and automated. I think that’s where the biggest efficiency gain is.” — Jerez, Customer Success Leader at Appega

For CS leaders, this translates to a prioritization framework: automate the layer that consumes time without producing customer insight, then redirect that time toward conversations that do.

The compliance space is particularly ripe for this because customer education needs are growing faster than compliance teams can staff for them. Emerging areas like AI governance, quantum computing security implications, and cross-jurisdictional regulatory changes all require CS teams to be educators, not just account managers. Automation buys back the time to do that.


What’s the Most Effective Go-to-Market Motion for Scaling CS-Driven Revenue?

The most effective GTM motion for CS-driven revenue in B2B SaaS compliance is a community-led education model paired with intimate customer engagement—not conference-heavy demand generation. This approach pairs software automation infrastructure with partner-delivered expert guidance, uses educational content to build mind share before commercial conversations, and prioritizes smaller gatherings where real business decisions get made.

Community-Led Compliance Education: The Framework

Jerez’s three-pronged GTM model at Appega operates at the intersection of software, expertise, and community:

Framework: Community-Led Compliance Education

  1. Build the platform — create a community where end-users and partners interact, not just a customer portal
  2. Bring in third-party SMEs — identify compliance domain experts who can provide industry-specific guidance that your internal team cannot scale to cover
  3. Lead with education on emerging topics — AI governance, quantum computing implications, and new regulatory frameworks are where customers have the highest anxiety and lowest knowledge
  4. Combine automation with expertise as a bundle — the differentiated offer is not just the software, it’s the access to guidance
  5. Let education create the commercial conversation — mind share earned through education converts without hard selling

This model addresses a structural challenge in compliance software sales: customers don’t know what they don’t know about regulatory change. They are completing 7-8 of 10 planned compliance initiatives—not because they’re negligent, but because resource constraints force triage. A vendor who reduces that cognitive load through education earns a strategic partnership relationship, not just a vendor relationship.

Intimate Engagement Over Mass Market Presence

On the demand generation side, Jerez challenges the default B2B conference playbook:

“The actual business happens in more intimate, smaller gatherings where the platform is there for true collaboration and unfettered discussion.” — Jerez, Customer Success Leader at Appega

Large conferences serve one function: industry awareness. The pipeline is built elsewhere. Jerez’s team at Appega combines:

The underlying principle is one he applies to all of marketing: “That real empathy and connection. It’s the most powerful part of marketing.”

This isn’t a philosophical statement. It’s an operational directive: engineer your CS team’s customer touchpoints to create genuine connection, not transactional check-ins. That empathy—understanding that your customer is already stretched thin across 10 priorities and compliance isn’t their first—is the foundation of every renewal and expansion conversation.


Who This Is NOT For: Constraints & Failure Modes

This approach does not work for CS teams with no leadership commitment to trust-building. The Cultural Brokers Model and psychological safety framework require active leadership investment. If your executive team is unwilling to normalize failure publicly or create forums for honest conversation, adding brokers and running team activities will not move the needle. The prerequisite is behavioral, not structural.

Intimate engagement over mass marketing requires patience and pipeline tolerance. If your organization needs immediate pipeline volume from event presence, curated small gatherings will underperform in the short term. The ROI is in deal quality and conversion rate, not raw top-of-funnel volume. This model works for teams with a 90-day-plus time horizon on pipeline.

The education-first GTM model assumes customers need regulatory context—not all markets do. If your B2B SaaS product solves a problem customers fully understand without vendor guidance, the community-led compliance education framework adds overhead without proportional return. Jerez’s approach is specifically calibrated for markets where regulatory complexity is high and customer knowledge is low.

AI automation at scale requires data quality and process documentation first. Automating “mundane tasks” only produces efficiency gains if those tasks are already defined and consistent. CS teams with ad-hoc, undocumented workflows will automate chaos, not eliminate it.

Cultural brokers are not a substitute for management infrastructure. If your CS team lacks basic operating cadences—QBRs, health scoring, renewal tracking—brokers will improve collaboration but cannot compensate for missing operational fundamentals.


About Jerez

Jerez is a customer success executive and Harvard Business Review Council member who scaled Appega’s CS function from early stage through $100M+ ARR. His background spans cybersecurity and SaaS, beginning with a startup acquisition by Sun Microsystems in 2008. His perspective on scaling CS teams is grounded in operational reality: trust-first culture, AI-driven automation, and community-led customer education as compounding growth levers—not theoretical frameworks.

Appega operates in the compliance automation space, serving CTOs, compliance officers, and security leaders at mid-market and enterprise B2B SaaS companies navigating rapidly changing regulatory environments. The $100M+ ARR milestone reflects both the scale of the compliance automation market and the compounding effect of the CS strategies Jerez has built and refined over more than a decade of SaaS execution.


Ready to Build a CS Team That Scales to $100M ARR?

The gap between a CS team that stalls at $10M ARR and one that scales through $100M is not headcount—it’s the cultural and operational infrastructure underneath the headcount. Jerez’s work at Appega demonstrates that trust-first leadership, deliberate cross-functional connection through cultural brokers, and AI automation of repetitive tasks are the compounding levers that separate high-retention CS organizations from high-churn ones. If you’re a B2B SaaS founder or GTM leader building or restructuring your CS function, the frameworks in this episode give you a concrete starting point—not a theory.

Talk to a Growth Strategist →


Frequently Asked Questions

How do you scale customer success as a B2B SaaS company grows?

Scaling customer success in B2B SaaS requires three foundations: trust-first team culture, automation of repetitive tasks, and deliberate cross-functional collaboration. Jerez at Appega scaled to $100M+ ARR by building psychological safety so CS reps could share failures openly, deploying AI to eliminate busywork, and installing “cultural brokers”—individuals with both technical credibility and relationship-building aptitude—to connect CS with product, sales, and engineering. Without these foundations, CS teams fragment as headcount grows and churn signals go undetected until renewals are already lost.

How do you build trust and psychological safety in customer success teams?

Trust in CS teams starts with leadership explicitly normalizing failure. As Jerez puts it: when things don’t go right, team members should be able to share that openly, with the expectation that the team learns from it. Practically, this means creating forums where losses and missed renewals are debriefed without blame, supporting relationship-building outside of work through team activities, and empowering reps to make decisions without constant escalation. Trust is not a culture initiative—it is a daily operating decision made by leadership, and its absence makes scaling CS headcount counterproductive.

What role does education play in compliance software sales?

Education is a primary go-to-market motion for compliance software, not a supporting activity. Prospects—CTOs, compliance officers, security leaders—realistically complete only 7-8 of every 10 planned compliance initiatives due to resource constraints. They need vendors who reduce cognitive load by explaining regulatory changes, not just automating workflows. Appega’s approach pairs software automation with third-party subject matter experts and community platforms, so customers receive both infrastructure and domain guidance. Vendors who skip education cede the strategic relationship to competitors who own the conversation before any commercial pitch begins.

What is the difference between conferences and intimate gatherings for B2B sales?

Conferences generate industry awareness and brand presence but rarely produce pipeline directly. The actual sales conversations happen in smaller, curated gatherings where prospects can speak candidly about their challenges without performing for a crowd. Jerez’s approach uses large conferences for high-level visibility only, then converts that awareness through intimate engagements—small dinners, focused roundtables, one-on-one discussions—where unfettered dialogue builds the trust that precedes a commercial decision. Combining this with outbound, inbound, BDR motions, and educational webinars creates a full-funnel demand generation system rather than event-dependent pipeline.

How can small CS teams punch above their weight in customer success?

Small CS teams maximize impact by automating the mundane task layer—status updates, compliance monitoring alerts, regulatory change notifications—freeing reps for high-value strategic conversations. The Cultural Brokers Model is particularly effective for small teams: rather than hiring for every cross-functional gap, identify one or two individuals already trusted across departments and formalize their bridge role. Education-led customer engagement also scales CS reach without headcount, as community platforms and partner SMEs extend the team’s expertise surface area far beyond what internal staff alone can cover.


Frequently Asked Questions

How do you scale customer success as a B2B SaaS company grows?

Scaling customer success in B2B SaaS requires three foundations: trust-first team culture, automation of repetitive tasks, and deliberate cross-functional collaboration. Jerez at Appega scaled to $100M+ ARR by building psychological safety so CS reps could share failures openly, deploying AI to eliminate busywork, and installing 'cultural brokers'—individuals with both technical credibility and relationship-building aptitude—to connect CS with product, sales, and engineering. Without these, CS teams fragment as headcount grows.

How do you build trust and psychological safety in customer success teams?

Trust in CS teams starts with leadership explicitly normalizing failure. As Jerez puts it: when things don't go right, team members should be able to share that openly, with the expectation that the team learns from it. Practically, this means creating forums where losses and missed renewals are debriefed without blame, supporting relationship-building outside of work through team activities, and empowering reps to make decisions without constant escalation. Trust is not a culture initiative—it's a daily operating decision by leadership.

What role does education play in compliance software sales?

Education is a primary go-to-market motion for compliance software, not an afterthought. Prospects—CTOs, compliance officers, security leaders—are resource-constrained: they realistically complete only 7-8 of every 10 planned compliance initiatives. They need vendors who reduce their cognitive load by explaining regulatory changes, not just automating workflows. Appega's approach pairs software automation with third-party subject matter experts and community platforms, so customers receive both infrastructure and domain guidance. Vendors who skip education lose to those who own the conversation.

Ready to accelerate your B2B SaaS growth?