Stacey Justice

They propose a concrete standard instead: enablement teams should deliver business outcomes such as ramp time, win rate, and productivity, not training for its own sake.

In a post about the Grow & Tell podcast with guest Alex Kracov, Stacey Justice lists the topics covered: a detect-prescribe-practice-validate flywheel run internally at Gong, why AI role play falls flat unless it is built on real call data, how onboarding was rebuilt to deliver 53% more ARR from new hires, and why saying no to sales leadership built credibility. The flywheel, role-play point, and onboarding result are their account of Gong practice; the 53% figure is a claim from the post, not an independently verified result.

Read original

They ask whether an activity serves the overall goal or merely optimizes a local process.

A RevOps and enablement team started a book club with 'The Goal' by Eliyahu Goldratt to give the team a shared vocabulary and a clearer sense of its objective before building anything.

• The book's goal is making money; in Stacey Justice's framing, the team's goal is revenue.
• Questions from the book started showing up in ordinary conversation: What is the goal?
• Is this the constraint?
• Are we optimizing the system or just a local process?
• How does this impact the goal?
• Is this the highest-leverage thing we could be working on?

Read original

The approach is intensive joint work on shared problems, not a status meeting.

The full go-to-market operations organization met in Dublin to build blueprints for the year.

• The week covered how RevOps is evolving, workshops on driving growth rather than supporting it, breaking down revenue motions and the 'golden formula' behind them, clarifying roles and responsibilities, working through a real new-hire ramp use case to expose how interconnected the work is, and setting quarterly OKRs.
• The post tags colleagues including Shawn Killpack, Matt Flotard, Griffin Bell, Lee Tennant, Gerry Cunningham, and Leif Jacobsen, and notes a pub trip and scavenger hunt alongside the working sessions.

Read original

The program aims to improve performance, not completion itself.

Gong asked its customer success team to evolve from CSMs into Revenue Architects, then built Mastering Revenue Architecture, a 12-week program covering GTM fundamentals, revenue process design, consulting, data storytelling, and executive influence.

• Stacey Justice writes that the completion badge was never the point; improving capability to affect business performance was.
• They credit colleague Hannah Finn with turning the idea into a finished program.

Read original

Individually, these tasks look small; across a revenue organization, they add up. They propose placing better data inside the environment sellers already work in, making the process from prospecting to forecasting more intelligent.

The post describes Gong Enrich as bringing trusted third-party account and contact data directly into Gong, connecting it to prospecting, account research, prioritization, engagement, coaching, forecasting, and execution.

• It links to a Gong Enrich page.
• The product claims come from the post and reflect Stacey Justice's framing as part of Gong's revenue AI messaging; ask for independent evidence when assessing them.

The post applies the argument about removing friction from seller work to a specific product announcement, while keeping the focus on outcome-driven enablement.

Read original

Newcomers can start here to understand the standard they apply to revenue enablement work.

Stacey Justice calls enablement their least favorite word because every company and practitioner defines it differently.

• They say enablement teams should deliver business outcomes—ramp time, win rate, and productivity—not training for its own sake.
• The post also points to a podcast conversation with Alex Kracov covering a detect-prescribe-practice-validate flywheel, why AI role play falls flat unless built on real call data, how onboarding was rebuilt to deliver 53% more ARR from new hires, and why saying no to sales leadership built credibility.

For brands planning a campaign

A keynote or advisory engagement can use this as an opening argument: anchor the discussion in measurable revenue outcomes, then show how onboarding, coaching, and role play connect to them. The post cites results such as 53% more ARR; treat these as Stacey Justice’s stated results and talking points to explore with them, not independently verified facts.

It’s the strongest starting point for anyone evaluating their ability to design and run an enablement program with clear business intent.

Stacey Justice describes asking a Customer Success team to evolve from CSMs to Revenue Architects.

• To support that shift, they built Mastering Revenue Architecture, a 12-week program covering GTM fundamentals, revenue process design, consulting, data storytelling, and executive influence.
• They say the completion badge was never the point; the goal was to improve capabilities that affect business performance.
• The post credits Hannah Finn for turning the idea into a program and mentions an article about the enablement flywheel and performance at Gong.

For brands planning a campaign

For a B2B SaaS company focused on onboarding and revenue enablement, this is a concrete example of curriculum design tied to a role transformation. A keynote or advisory engagement can examine how the program was scoped, how it connected to customer-facing work, and what a similar 12-week path could look like for the client’s teams.

It’s useful for understanding how they connect enablement to broader revenue architecture.

Stacey Justice describes bringing a full GTM Operations organization together in Dublin to develop blueprints for the year.

• The week included pressure-testing how RevOps is evolving, workshops on driving growth rather than supporting it, breaking down revenue motions and the “golden formula” behind them, clarifying roles and responsibilities, working through a real new-hire ramp use case, and locking in OKRs.
• The takeaway: when RevOps functions as a connected system rather than adjacent teams, decisions and execution improve.

For brands planning a campaign

This is a useful reference for an advisory engagement on operating model design or onboarding. It offers a real example of a cross-functional workshop connecting enablement to revenue motions, role clarity, and quarterly goals.

It’s a good entry point for readers interested in their approach to creating a common language around business outcomes.

Stacey Justice describes starting a book club for a RevOps and Enablement team, beginning with “The Goal” by Eliyahu Goldratt.

• The team needed a common language and a clearer understanding of the goal before building anything—not just a business school classic.
• In the book, the goal is making money; in their world, it is revenue.
• They say the language is already showing up in questions such as “What is the goal?”, “Is this the constraint?”, and “Are we optimizing the system or just a local process?”

For brands planning a campaign

A keynote or workshop can use this as a practical way to align a revenue team before planning. It supports the message that enablement should improve business outcomes, not just add frameworks, and offers a low-cost way to build a shared vocabulary across functions.

It’s worth opening to see how they connect AI and data to everyday seller workflows rather than treating them as separate tools.

Stacey Justice argues that seller productivity is often lost in the seams between systems: finding contacts, researching accounts, filling in missing information, switching tools, and updating CRM.

• They say Gong already understands a great deal about customer interactions, and Gong Enrich adds trusted third-party account and contact data directly into that environment.
• The post connects better data to prospecting, account research, prioritization, engagement, coaching, forecasting, and execution.

For brands planning a campaign

For a B2B SaaS audience, this shows how Stacey Justice frames revenue AI as process improvement, not just more intelligence.

• A campaign or advisory engagement can explore where data and AI reduce seller friction and how those improvements affect onboarding, productivity, and revenue execution.
• The post is tied to Gong’s product messaging; confirm any partnership or sponsorship separately.

The stated outcomes are ramp time, win rate, productivity, and business results. One post calls enablement their least favorite word because every company and practitioner defines it differently, then argues that teams should deliver outcomes rather than training for its own sake.

Uses shared language and simple diagnostic questions to reframe work: What is the goal?

• Is this the constraint?
• Are we optimizing the system or a local process?
• How does this affect the goal?

For brands planning a campaign

A brief should ask for measurable enablement outcomes and a shared operating language, not a list of workshops. A keynote or advisory engagement can focus on how enablement earns credibility by tying programs to ramp, win rate, and productivity.

Examples: Source 1 · Source 2

The program covered GTM fundamentals, revenue process design, consulting, data storytelling, and executive influence. The post says the completion badge was not the point; improved capability that affects business performance was.

Built a multi-week program around role change, with modules, iteration, feedback, and measurement. The post credits the team behind the program and names an internal partner as key to turning a big idea into a finished program.

For brands planning a campaign

This is direct evidence for an advisory or keynote engagement on revenue architecture, role transformation, and enablement program design. Buyers can ask how the program was measured, how it changed customer-facing work, and what parts are reusable in another revenue organization.

Examples: Source 1

The team pressure-tested how RevOps is evolving, ran growth workshops, broke down revenue motions and the “golden formula” behind them, clarified roles and responsibilities, worked through new-hire ramp as a shared use case, and locked in quarterly OKRs. The takeaway: connected RevOps functions move faster and make better decisions than adjacent teams.

Used a full-team offsite with workshops, cross-functional role clarity, a real use case, and OKR setting. The post also notes social activities, making the format a mix of intensive working time and team building.

For brands planning a campaign

Brands can evaluate Stacey Justice for a workshop or keynote on cross-functional revenue operations, operating cadence, and alignment between RevOps, enablement, and field teams. For an offsite or workshop, ask for a practical plan, not just a speech.

Examples: Source 1

It describes Gong Enrich as adding trusted third-party account and contact data into the Gong environment, making the revenue workflow more intelligent from prospecting through forecasting and execution.

Explains the problem through everyday seller friction, then positions better data inside an existing revenue-AI environment as the fix. The post includes a product promotion link for Gong Enrich.

This post is product-oriented. It shows a topic area a brand can evaluate, but the claims about Gong Enrich come from the post and were not independently verified here.

For brands planning a campaign

Useful for a campaign aimed at sales technology, data quality, and seller workflow. A campaign can ask how revenue AI reduces tool switching and manual CRM work, while separating the workflow argument from product-marketing language.

Examples: Source 1

References an internal flywheel for diagnosing and improving seller behavior. The onboarding claim is a concrete metric tied to a rebuild.

The LinkedIn summary does not include the full podcast episode or linked article. Ask for the underlying material before relying on the ARR claim or flywheel details.

For brands planning a campaign

A brief can ask for an onboarding and seller-readiness engagement with a measurable ramp target. An advisory or keynote can cover using real call data in AI role play, rebuilding onboarding around outcomes, and managing sales leadership expectations.

Examples: Source 1

Their post about Gong Enrich describes expanding the capabilities of the company’s Revenue AI platform.

View example

View example

Both describe fractional or consultative enablement leadership and name specific programmes, including onboarding and ramp design.

Kate Redfern frames the work as a portfolio of fractional services companies can buy, including BDR/SDR roadmaps and methodology rollouts, and pitches Omni Enablement directly to buyers. Stacey Justice's posts describe programmes and operating practices from inside a revenue-AI company, focusing on how RevOps, enablement, and field teams work as one system.

Read original · Original 2

She describes building a 10-week onboarding programme with pass gates, hiring intentionally, and judging success a year later by whether the work survived in the field. That aligns with Stacey Justice's argument that enablement should be measured by ramp, win rate, and productivity.

Aimee Roberson uses a named diagnostic, the SCALE framework—strategy, capabilities, alignment, learning, and execution—and describes it as a consulting engagement. Stacey Justice tends to show the same ideas through internal Gong programmes and a detect-prescribe-practice-validate flywheel.

Read original · Original 2

Stacey Justice makes a related case in a post on seller productivity: better data inside sellers' existing tools makes the revenue workflow smarter.

Ben Hood focuses on talent sourcing and data capture as fuel for AI, including call recordings, renewals, and sales-cycle length. Stacey Justice focuses on programme design, revenue architecture, and removing friction between systems—not hiring or data-plumbing questions.

Read original · Original 2

The two posts describe Omni Enablement, a fractional offer that bundles revenue enablement leadership, sales leadership and coaching, BDR/SDR roadmaps, manager development, methodology rollouts, onboarding and ramp programmes, QBR design, and AI-powered coaching, and lists results such as a 33% improvement in conversation rates, 23% uplift across a 500-plus person organisation, 17% retention gain, 27% net new revenue growth, and 43% capability improvement across 350-plus professionals.

• They also address a specific commercial problem absent from Stacey Justice's posts: how to get enablement leadership without funding a full-time hire.
• For a company that wants one named provider covering several enablement functions at once, or a sales-leadership gap as well as an onboarding problem, that bundled scope is the practical reason to switch.
• The second post adds a diagnostic angle worth having in the room when a campaign is aimed at explaining why senior buyers disengage: sellers follow their own sales process and qualification checklist while the buyer is already deep into their own buying cycle, so the recommended posture is decision facilitation rather than information delivery.

The tradeoff is that Stacey Justice's posts read as service promotion rather than programme detail.

• The outcome percentages appear in a launch post for Omni Enablement, but the posts do not describe the programmes behind them or provide client context beyond organisation size.
• Ask for the programme details, client context and measurement behind the figures before treating them as verified.
• Their posts go further into method: a 12-week Mastering Revenue Architecture programme naming its curriculum areas, an onboarding rebuild with a stated 53% ARR improvement from new hires, a detect-prescribe-practice-validate flywheel, and a cross-functional GTM Operations week that worked through new-hire ramp as a shared use case.
• If the engagement depends on inspecting how an enablement system was designed, that level of internal detail is the stronger reference.

Examples: Source 1 · Source 2 · Source 3 · Source 4

One post sets out a five-part SCALE framework — strategy, capabilities, alignment, learning, execution — and argues that when revenue gets harder, the default response of pushing harder on sales is usually wrong because the sales team is where the problem shows up, not where it starts.

• Symptoms the post names are recognisable inside most buyer organisations: stalled deals, confused buyers, founders still in every opportunity, marketing content that fails to convert, pipeline reviews turning into symptom-chasing.
• For a company that wants a structured diagnostic before commissioning anything, that framing is the clearest reason to pick this alternative.
• The second post is the strongest onboarding case study in the comparison set and the reason to prefer Aimee Roberson for pure onboarding design: a 10-week programme built from the ground up with mandatory weekly pass gates, presentations, role plays and exams, deliberate over-hiring in anticipation of onboarding attrition, a super interview day with leadership, and a stated outcome a year later when the first cohort dominated the awards ceremony.
• The argument that enablement is usually judged on launch day while what matters is what managers reinforce and what holds under pressure twelve months on is directly useful for a buyer setting success measures.

The tradeoff is that the onboarding account is a personal recollection of one programme, with no client name, cohort size, or measured ramp or win-rate figures.

• Ask for those details if repeatable results are central to the decision; the account explains judgment better than it proves outcomes.
• The SCALE diagnostic is presented as a productised offer tied to this practitioner's own practice, so a buyer is evaluating a method and a service simultaneously, which is harder to separate than the internal programme detail in Stacey Justice's posts.
• Their posts also show current work at vendor scale — a 12-week revenue architecture programme run for a whole customer success function and a GTM Operations week that clarified roles and set quarterly objectives across RevOps, strategy, field ops, and enablement — where Aimee Roberson's posts describe work largely from an earlier stage of a career.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The two posts argue that the best SDR candidates are often missed because companies screen for prior software experience instead of demonstrated resilience: the pitch is to recruit people who have sold pest control, roofing, or other home services door to door, on commission, and who already know how to absorb a day of rejection.

• The second post shifts to data foundations, arguing that recent acquisition activity is largely a play for data because AI platforms are only as useful as the data feeding them, and lists concrete checks for a sales leader: whether interactions are captured, whether call recordings are linked to the CRM, how renewal success is measured against email frequency for customer success, and how sales-cycle length affects lifetime value.
• For a company building or rebuilding an SDR function, or fixing data capture before an AI rollout, that is a sharper contribution than anything in the Stacey Justice posts.

The tradeoff is that the same campaign decision is only partly served.

• The posts give a hiring thesis and a data checklist, not an enablement or onboarding method: there is no programme structure, curriculum, pass gates, measurement of ramp time or win rate, or example of work surviving in the field a year later.
• Stacey Justice's posts include those things, including the 12-week revenue architecture programme, the onboarding rebuild with its stated 53% ARR improvement from new hires, and the position that AI role play falls flat unless it is built on real call data — a direct answer to the data-foundation problem Ben Hood raises, carried through to how coaching is delivered.
• The material is also older, from mid-2025, and both posts are short, opinion-led, and close with named colleagues invited to respond rather than with developed argument.

Examples: Source 1 · Source 2 · Source 3 · Source 4