Jan Young coaches Customer Success leaders to connect customer work to revenue, improve how their teams operate, and adapt to AI. Jan Young also leads the StepUpXchange CS Business Leadership Accelerator, writes the Customer Revenue Lab newsletter, and helped build the CxXchange Customer Success community.
Most useful for coaching Customer Success leaders to connect customer work to revenue and adapt to AI.
Best for
B2B SaaS customer success leaders working on revenue, usage pricing, AI, or community.
Not for
Paid social placements pushing products to broad audiences with promo codes and reach targets.
Key takeaways
Usage is only a health signal until it is revenue; activity can hide frustration
AI-era onboarding should stop teaching clicks and start verifying outcomes
Fix the most broken journey stage first, then turn it into a repeatable revenue system
Check first: Ask for recent reach, engagement, or survey data for comparable CS leadership content.
Main ideas
Customer success leaders get shut out of budget planning when they report activity instead of revenue evidence · Usage is only a health signal until it is the revenue, and then activity can hide frustration · AI-era onboarding should stop teaching clicks and start verifying outcomes
Jan Young coaches Customer Success leaders to connect customer work to revenue, strengthen how their teams operate, and adapt to AI.
Jan Young leads the StepUpXchange CS Business Leadership Accelerator, writes the Customer Revenue Lab newsletter, and helped build the CxXchange community.
The work is for leaders who want to show the business impact of Customer Success—not just report activity—and help customers reach outcomes with less friction.
Jan Young turns broad business goals into practical questions for Customer Success teams.
When usage is part of a pricing model, rising activity alone does not prove customer value: teams need to understand what the usage enables, what work comes before it, and whether the customer achieved a meaningful result.
The same outcome-focused lens reaches beyond metrics.
A comparison of work-organizing apps becomes a question for SaaS teams: are they teaching customers where to click, or helping them get useful work done?
And Jan Young’s account of starting open Office Hours shows how community can grow when people have room to contribute and learn from one another.
Jan Young's ideas center on making customer success commercially legible, treating usage and AI activity as evidence of delivered value rather than proof of health, and building communities and repeatable systems that outlast individual effort.
Read more
The through-line is that CS teams should stop reporting interface-level or activity-level proxies and start connecting customer work to revenue, outcomes and the customer's own goals.
Customer success leaders get shut out of budget planning when they report activity instead of revenue evidence
Jan Young argues that CS leaders are expected to hit retention and expansion targets but get treated like an operational escalations desk because they report CSAT, NPS and health scores rather than commercial numbers.
Read more
The remedy is a shared commercial language built on Customer Revenue Expertise, Business Acumen and AI Fluency. Jan Young names two coaching mistakes: leaders do not connect their team's work to what investors and the company are trying to achieve, and they do not fix the most broken part of the CS program first.
In the free NexGen CS Leadership Masterclass, Jan Young walks through a Modern CS Growth System meant to make revenue impact visible, credible and measurable to executive leadership. The same posts point to a common failure: renewal and expansion forecasts depend on who owns the account.
The argument recurs across the coaching posts. AI Fluency appears as a newer capability alongside revenue expertise and business acumen, extending rather than replacing the earlier revenue-evidence case.
Usage is only a health signal until it is the revenue, and then activity can hide frustration
Jan Young separates usage as something CS watches from usage as the number a company gets paid on.
Read more
When customers pay by consumption, usage is part of the number to predict, so looking at usage alone is too late.
High consumption can mean a customer had to prompt a tool five times to get a usable result.
Jan Young says usage-based pricing, committed credits and outcome-based pricing each raise a different question, and the practical test is to pick one core customer job before a business review, compare what the signals say with what the customer actually got done, and look at both sides of usage: what has to happen before usage grows, and what the usage is doing for the customer.
A customer burning through heavy AI usage without reaching the agreed outcome raises the cost to deliver while recognized revenue stays flat. With committed credits, a late start leaves the customer struggling to burn what they bought, so renewal becomes a negotiation about an extension rather than expansion.
This extends the revenue-evidence argument into pricing models and adds a tension: usage can be revenue and still not be value, so CS needs leading indicators before consumption and customer outcomes after it.
AI-era onboarding should stop teaching clicks and start verifying outcomes
Jan Young tested three work-organization apps and kept the one run by agents, with no interface to learn.
Read more
The lesson drawn for CS is that onboarding capacity spent teaching users where to click is hidden customer effort that delays value, while libraries of walk-through videos and how-to guides become maintenance work. In an outcome-driven model, value comes from domain judgment, customer context and verified outcomes rather than navigation skill.
The first app took three clicks in Slack and then pushed Jan Young into separate software to drag a cursor and type information it should have known.
The second accepted voice input but then presented a library of video tutorials.
Jan Young kept an app where agents organize the work and nudge when a decision is needed.
This sits beside Jan Young's argument that everyone needs upskilling. The point is not less skill, but different skill: less interface fluency, more AI fluency, business acumen and customer judgment.
Community is intentional and organic, and it grows by being additive rather than competitive
CxXchange grew out of office hours Jan Young ran while hiring for several roles and receiving about 80 responses.
Read more
The calls mixed CS leaders, experienced CSMs and people newer to tech, and the group became CS Office Hours and then CxXchange.
Jan Young's stated principle is that community is both intentional and organic: create the conditions for people to feel welcome, contribute and connect, but leave room for the community to become something you could not have designed alone.
Jan Young describes community as additive, not competitive, and partners with groups including Latinos in Success, Success in Black and CS Barcelona Afterwork.
CxXchange has grown to roughly 4,000 members with about 20 volunteer board members, virtual programs, YouTube recordings, website resources and a Slack channel.
Jan Young also names other community builders, including Cinthia Silva, Priscila Fletcher and Parul Bhandari, and notes nominations for Roxcee Stacker, Virginia D.
Bloom and Emma Lo.
Those are Jan Young's descriptions, not statements from the named people.
The origin story frames community as accidental. The awards post shows Jan Young now treats community building as a deliberate practice with volunteer leadership, cross-community partnerships and peer recognition.
Fix the most broken journey stage first, then turn it into a repeatable revenue system
Jan Young identifies a second recurring mistake: not fixing the most broken part of the CS program first.
Read more
That is often a stage of the customer journey where every CSM does it a little differently, the same customer problems get solved again and again, renewal and expansion forecasts depend on who owns the account, and account knowledge leaves when a CSM leaves.
The remedy taught is to turn that stage into a Repeatable Customer Revenue System.
Jan Young adds that effort is not the problem: most of these leaders and their teams are already working hard.
When a CSM leaves, what they knew about the account goes with them. Renewal and expansion forecasts then depend on who owns the account rather than a documented process the team can repeat.
Commercial generalists, not narrow role definitions, are what AI-era go-to-market needs
Jan Young was a full-cycle seller before moving from entertainment technology into SaaS, where sales and customer success roles were separated.
Read more
Jan Young chose customer success because it allowed more commercial strategy and continued account relationships.
That background shapes the skills argument: go-to-market people need to know the whole prospect-to-customer lifecycle, their ideal customer profile's workflows and pain points, AI tools and business acumen, and stay tech-curious.
Technical roles need the same lifecycle and business grounding plus technical depth.
The conclusion is that every role is changing, so upskilling is not optional for anyone.
The career move itself is the example: from full-cycle selling in entertainment tech to a commercial strategy role in customer success in SaaS. Jan Young lists the shared capabilities both go-to-market and technical people now need.
This retrospective post supplies the career context behind the coaching argument and sharpens a tension: Jan Young chose CS partly because it was more commercially strategic than a split sales role, yet still argues CS needs stronger commercial translation to leadership.
This answers what Jan Young thinks is blocking Customer Success leaders from being treated as revenue leaders, and it names the exact skills used in the coaching.
Read more
A newcomer can start here to understand the central problem the rest of the work addresses.
Jan Young argues that CS leaders are often accountable for retention and expansion yet shut out of executive budget planning because they lack a shared commercial language.
The post names three capabilities: Customer Revenue Expertise (knowing where each customer renews, expands and buys more), Business Acumen (presenting customer progress in commercial numbers), and AI Fluency.
The remedy offered is a free NexGen CS Leadership Masterclass on November 10.
For brands planning a campaign
Useful for a B2B SaaS session on making CS a revenue function: frame the session around translating customer progress into finance, sales, and product language rather than another CSAT or NPS discussion.
This answers the diagnostic question: what does Jan Young check first when a customer success team is underperforming commercially?
Read more
It is a compact entry point into the operational problems behind the coaching offer.
Jan Young describes two recurring mistakes from coaching: leaders do not connect their team's work to what investors and the company are trying to achieve, so they report CSAT, NPS, and health scores that leadership cannot tie to revenue; and they do not fix the most broken part of the CS program first, often a customer-journey stage where every CSM works differently. The post says renewal and expansion forecasts then depend on who owns the account, and account knowledge leaves when a CSM leaves.
For brands planning a campaign
Supports a workshop on creating a repeatable Customer Revenue System: start with one broken journey stage and standardize it before adding new tools or reporting.
This answers why Jan Young works in Customer Success and how they see the boundary between sales, success, and technical roles changing under AI.
Read more
It gives a newcomer the career context behind the coaching.
Jan Young describes moving from Entertainment Tech to SaaS Tech, where sales and success roles were separated, and choosing Customer Success because it allowed more commercial strategy and relationship building. The post argues that training is required because roles are changing: GTM people need to know the whole prospect-customer lifecycle, ICP workflows and pain points, AI tools, business acumen, and be tech curious; technical people need similar lifecycle and business knowledge plus technical depth.
For brands planning a campaign
Useful for a session on shared GTM and CS skills: position CS leaders as commercially strategic owners of the customer lifecycle rather than a separate post-sale function.
This answers how Jan Young's community work began and what they believe makes it work.
Read more
A newcomer should start here to understand CxXchange, a repeated part of the profile.
Jan Young tells the origin story of CxXchange: while hiring, about 80 people reached out, so instead of scheduling 40 hours of conversations, Jan Young invited everyone to Office Hours.
The calls mixed CS leaders, experienced CSMs, and people newer to tech.
The group grew into CS Office Hours and then CxXchange.
Jan Young says community is both intentional and organic: create conditions for people to feel welcome, contribute, and connect, but leave room for the community to become something you could not design alone.
For brands planning a campaign
Useful for a community-led growth brief: lead with the Office Hours origin story and the principle that community is intentional and organic, not a broadcast channel.
This answers how Jan Young evaluates AI usage and why activity metrics can mislead.
Read more
It is a concrete starting point for the usage-based model session in the reader brief.
Jan Young warns that high AI consumption can mean a customer had to prompt the tool five times to get a usable result.
The post separates usage-based pricing, committed credits, and outcome-based pricing: with usage-based pricing usage is revenue, but consumption from high effort and low return is temporary; with committed credits, late starts lead to renewal negotiations about leftover credits; with outcome-based pricing, usage is a leading indicator of delivery cost, and heavy usage without the agreed outcome raises cost while recognized revenue stays flat.
The practical test is to pick one core customer job and compare what the signals say with what the customer actually got done.
For brands planning a campaign
Strong basis for a session on usage-based models: use the three pricing models as a framework and ask teams to connect activity data to a specific customer job and verified outcome.
This answers what Jan Young is recognized for by peers and how CxXchange fits into a wider customer success community.
Read more
It gives a newcomer the network and recognition context in one place.
Jan Young announces nominations for Independent Voice and Community Builder in the SuccessHACKER CS Thought Leadership Awards, and CxXchange's nomination for community.
The post lists the work behind the nominations: coaching executive CS leaders, leading the StepUpXchange CS Business Leadership Accelerator, and writing the Customer Revenue Lab newsletter.
It also names CxXchange's roughly 20 volunteer board members and 4,000 members, and says the community will celebrate five years next spring.
Jan Young describes community as additive, not competitive, and highlights Latinos in Success, South Asian Success, and other groups.
For brands planning a campaign
Useful for a thought-leadership or community partnership brief: Jan Young can bring both a personal independent voice and a 4,000-member community with volunteer leadership.
This answers how Jan Young frames consumption-based customer success beyond dashboards.
Read more
A newcomer should read it to understand the leading-indicator approach behind the usage session.
Jan Young argues that when customers pay based on consumption, usage is not just a health signal but part of the number to predict.
That means looking at usage alone is too late.
The post says you need to know what has to happen before usage: which use cases go live, which teams adopt, which milestones are reached, and what has to be true for usage to grow.
It also says the customer does not have a usage goal; they are trying to accomplish something, so you need to know what usage is doing for them.
For brands planning a campaign
Supports a session on usage-based models and 2027 planning: build the session around pre-usage milestones and the customer's outcome, not just consumption trends.
This answers how Jan Young connects a personal AI workflow test to customer onboarding and adoption.
Read more
It is the most accessible example of the outcome-over-interface argument.
Jan Young tested three work-organizing apps.
The first needed three clicks in Slack and then dragging a cursor in separate software.
The second accepted voice input but then presented a library of video tutorials.
Jan Young kept an app that requires no learning or navigation because agents organize the work and nudge when a decision is needed.
The post then turns to customers: how much onboarding capacity is spent teaching users where to click, and how many walk-through videos and how-to guides teams maintain.
Jan Young argues that in SaaS, learning the software interface was treated as adoption, but in an outcome-driven model, time spent navigating screens is hidden customer effort that delays value.
For brands planning a campaign
Useful for a session on AI-era onboarding: audit interface-teaching effort and shift onboarding toward domain judgment, customer context, and verified outcomes.
Jan Young's recurring argument is that CS leaders already carry retention and expansion targets yet get shut out of executive budget planning, because the team reports CSAT, NPS and health scores instead of commercial numbers.
Read more
Two named mistakes: leaders do not connect their team's work to what investors and the company are trying to achieve, and they do not fix the most broken part of the CS program first.
The capabilities Jan Young points to are Customer Revenue Expertise (knowing where each customer renews, expands and buys more so sales, product and finance see the same picture), Business Acumen (presenting customer progress in commercial terms) and AI Fluency (building that evidence faster).
The practical claim is that showing business evidence lets CS shape company direction instead of staying defensive.
Coaching plus a recurring free masterclass and newsletter: reframe CS reporting in commercial language, then make revenue impact visible to executive leadership.
For brands planning a campaign
A B2B SaaS brand can build a session, workshop or accelerator module around translating customer progress into the numbers finance and the board already use. The audience is CS and post-sales leadership, and the pitch can be tied to a specific quarter's retention and expansion targets.
Usage, credits and outcomes: when consumption stops being a health signal
Jan Young separates usage as something CS watches from usage as the number a company gets paid on.
Read more
High AI consumption can simply mean a customer prompted five times to get a usable result, so celebrating activity without verifying completed work is a trap.
Three pricing models each raise a different question: usage-based pricing, where consumption is revenue but temporary if customer effort was high; committed credits, where a late start leaves the customer burning leftover credits at renewal instead of expanding; and outcome-based pricing, where usage is a leading indicator of delivery cost, so heavy usage without the agreed outcome raises cost to serve while recognized revenue stays flat.
Jan Young's method is to pick one core customer job before the next business review and compare what the signals say with what the customer actually got done, and to look at both sides of usage: what has to happen before usage grows — use cases live, teams adopted, milestones reached — and what the usage is doing for the customer.
Before a business review, choose one core customer job and compare activity data against delivered outcomes; treat usage as a leading indicator on both sides rather than a health score.
For brands planning a campaign
A usage-based, credit-based or outcome-based SaaS vendor could build a session, co-authored piece or workshop around which leading indicators actually predict renewal and expansion in its pricing model. The material is specific enough to land with CS, revenue operations and finance audiences at once.
Jan Young tested three work-organization apps and kept the one run by agents, with no interface to learn.
Read more
The conclusion drawn for CS: onboarding capacity spent teaching users where to click is hidden customer effort that delays value, and the library of how-to videos and guides becomes maintenance work a team can stop doing.
In an outcome-driven model, value comes from domain judgment, customer context and verified outcomes rather than navigation skill.
AI Fluency is named as one of three core capabilities for CS leaders.
Test the tooling yourself, then generalize the lesson: if the software works for the user, adoption is about results, not interface fluency.
For brands planning a campaign
A brand selling AI-enabled products can use Jan Young to reframe onboarding and enablement around customer outcomes instead of product tours. A session or newsletter collaboration aimed at CS leaders making that shift is a natural fit.
The second mistake Jan Young names is not fixing the most broken part of a CS program first — usually a journey stage where every CSM works a little differently, the same customer problems are solved repeatedly, renewal and expansion forecasts depend on who owns the account, and knowledge leaves when a CSM does.
Read more
The remedy taught is turning that stage into a Repeatable Customer Revenue System, delivered through the StepUpXchange CS Business Leadership Accelerator and the free NexGen CS Leadership Masterclass. Jan Young adds that effort is not the problem: most of these leaders and teams are already working hard.
Masterclass and accelerator format: identify the broken journey stage, convert it into a documented, repeatable system, and make the revenue impact visible to leadership.
For brands planning a campaign
A brand can sponsor or co-host a workshop where CS leaders audit one journey stage and leave with a standardized process. The offer suits an operations, enablement or customer success platform vendor whose product supports that standardization.
Community building as a practice, not a side effect
CxXchange grew out of office hours Jan Young ran while hiring for several roles and receiving roughly 80 responses; the sessions outgrew the roles, brought together CS leaders, experienced CSMs and newcomers, and became a community of about 4,000 members with around 20 volunteer board members, virtual programs, YouTube recordings, a website and a Slack channel.
Read more
The stated principle is that community is both intentional and organic: create conditions for people to feel welcome, contribute and connect, then leave room for it to become something unplanned. Jan Young describes community as additive rather than competitive, partners with groups including Latinos in Success, Success in Black and CS Barcelona Afterwork, and is nominated in the SuccessHACKER Thought Leadership Awards for Independent Voice and Community Builder.
Office hours grow into peer community, then into structured programs with volunteer boards, virtual and in-person sessions, and cross-promotion of allied communities.
For brands planning a campaign
For community-led growth briefs, the track record itself is the asset: a brand could co-host programming, sponsor CxXchange-adjacent events, or commission a piece on building a CS community in a specific market. The award nomination and hashtags are not evidence of a paid partnership.
A commercial generalist's view of CS and go-to-market roles
Jan Young was a full-cycle seller before moving from entertainment technology into SaaS, where sales and CS work split, and chose Customer Success because it allowed more commercial strategy and continued account relationships.
Read more
That background shapes the skills argument for the AI era: go-to-market people need to know the whole prospect-to-customer lifecycle, their ideal customer profile's workflows and pain points, AI tools and business acumen, and stay tech-curious; technical roles need the same lifecycle and business grounding plus technical depth. The stated conclusion is that every role is changing, so upskilling is not optional for anyone.
The career detail comes from a single retrospective post, so treat it as context for the skills argument rather than a complete career record.
For brands planning a campaign
A brand targeting teams that are merging sales and CS motions, or reskilling go-to-market staff for AI, can use Jan Young for a session or article on the hybrid skill set. The career history also gives Jan Young standing with both sales and CS audiences.
Jan Young's retained posts document her own coaching and advisory business, JanYoungCX, and her leadership of StepUpXchange, a CS business leadership accelerator.
Read more
She also promotes CxXchange, the Customer Success community she helped start, and mentions SuccessHACKER's Customer Success Thought Leadership Awards and its founder, Andrew Marks. No sponsored posts, affiliate arrangements, or client engagements are documented in the reviewed material.
JanYoungCX
Owned business
Jan Young names JanYoungCX as her practice, describing it as "Executive Coaching, Customer Revenue Advising & Training."
Read more
It appears in the signature of posts about coaching CS leaders, usage-based models, and how agents organize work.
Jan Young leads the StepUpXchange CS Business Leadership Accelerator, which she describes as a program where she coaches executive CS leaders and runs a free NexGen CS Leadership Masterclass.
Read more
She lists it as part of her own practice next to JanYoungCX.
Jan Young writes that she accidentally started what became CS Office Hours and then CxXchange, which she calls her community and which she says has around 4,000 members and roughly 20 volunteer board members.
Jan Young describes the Customer Revenue Lab as her newsletter and points readers to it for deeper writing on CS operations, usage signals, and community.
Jan Young writes that SuccessHACKER's CS Thought Leadership Awards nominated her for Independent Voice and Community Builder, and that CxXchange was nominated in the community category.
Read more
She names Andrew Marks and the SuccessHACKER team as having expanded the award categories. The post does not describe any commercial or sponsorship relationship.
Jan Young writes about customer success as a revenue function, for CS leaders who already carry retention and expansion targets.
Read more
The quickest way into the work is the LinkedIn posts that name two recurring failures: reporting CSAT, NPS and health scores instead of commercial numbers, and leaving the weakest stage of the customer journey to individual habit.
From there, the Customer Revenue Lab newsletter carries the longer argument, especially on usage-based, committed-credit and outcome-based pricing, where high consumption can hide customer frustration.
Jan Young also runs CxXchange, a customer success community that grew out of office hours into roughly 4,000 members with volunteer board members and regular programming, and teaches through a free NexGen CS Leadership Masterclass and the StepUpXchange accelerator.
Follow for commercial framing of CS work, AI-era onboarding and community practice; the posts are short, direct and built around a practical test rather than a framework lecture.
Both write short LinkedIn arguments about how customer success measures itself, and both push CS to tie its work to business outcomes rather than sentiment.
Read more
Seth Hansen contrasts NPS as a lagging indicator with time to value as a leading one, the same move Jan Young makes when weighing activity and usage signals against what a customer actually got done.
Seth Hansen's posts stay close to operating metrics and a career announcement, while Jan Young writes for CS leaders facing executive budget conversations and covers pricing models, AI-era onboarding and community building.
Like Jan Young, Jennifer Brown uses short LinkedIn posts to argue that a field is measuring the wrong thing: Jennifer Brown says performance thresholds built for paid media miss how creator influence compounds over time, the same shape of argument Jan Young makes about treating consumption as proof of customer value.
Read more
Jennifer Brown writes about creator and influencer marketing, including usage rights and paid amplification, which is a different field from Jan Young's customer success and revenue advisory work.
Both treat retention as work to be done early rather than at the point of risk.
Read more
Karyn Mullins lists the warning signals that precede churn and calls for a shared view of customer health with clear ownership, close to Jan Young's case for connecting customer activity to delivered outcomes and fixing the weakest journey stage first.
Karyn Mullins frames the problem across sales, CS, product, support and finance in a co-authored executive blog, while Jan Young addresses CS leaders directly and adds pricing-model and community angles.
Choose Jan Young for briefs aimed at Customer Success leaders and CS practitioners in B2B SaaS, particularly around connecting customer work to revenue, usage-based and outcome-based models, AI-era CS operations, and community-led growth.
Read more
The supplied posts are written to that professional audience: they address CS leaders, CSMs, and community members, and they repeatedly point to StepUpXchange, CxXchange, and the Customer Revenue Lab.
A dated LinkedIn account record showed 27,776 followers on October 11, 2026.
That measurement gives audience size on one platform, not a composition profile.
The supplied material does not measure geography, age, gender, employer, occupation, or job seniority; for those attributes, ask whether Jan Young has audience survey results or another documented source.
Before placement, request recent reach, engagement, or survey data for comparable CS leadership content so the buyer can judge whether the audience matches a narrow seniority or geography target.
Across the eight posts reviewed, Jan Young does not describe any brand sponsorship, paid-partnership, or affiliate format, and no media kit, rate card, sponsor policy, or partnership inquiry page appears in the material.
Read more
What the posts do document are Young's own programs: executive coaching and advisory through JanYoungCX, the StepUpXchange CS Business Leadership Accelerator, a free NexGen CS Leadership Masterclass series, the Customer Revenue Lab newsletter, and the CxXchange community, which she says has about 20 volunteer board members and roughly 4,000 members.
Those are offerings Young runs rather than formats a brand can book, and the material gives no pricing, audience metrics, deliverables, or contracting terms for any of them.
A brand planning a session on usage-based models or community-led growth should treat the specific scope, timing, and terms as an open question to settle directly with Young.
This is a documented absence in the reviewed posts, not a statement that Young never accepts sponsorships or paid partnerships.
Brief A: a B2B SaaS company selling a product priced on usage, credits, or completed outcomes wants a working session for its own customer success and post-sales leaders on how to spot churn risk when consumption is the revenue line.
Read more
Decision: strong fit.
Jan Young's recent posts address exactly this problem, not a general version of it.
She separates usage as a health signal from usage as the number a company gets paid on, warns that heavy AI consumption can mean a customer had to prompt five times to get a usable answer, and then walks through what each pricing model changes: with usage-based pricing, consumption is revenue but temporary if effort stayed high and return stayed low; with committed credits, a late start leaves the customer burning leftovers at renewal instead of expanding; with outcome-based pricing, usage is a delivery-cost indicator, so heavy usage without the agreed outcome raises cost to serve while recognized revenue stays flat.
That is enough substance for a session that ends with a task rather than a slogan: before the next business review, pick one core customer job and compare what the activity data says with what the customer actually got done.
A second, weaker version of the same brief also fits: a CS platform or enablement vendor that wants a session on standardizing one broken journey stage, which she frames as turning a stage where every CSM works differently into a repeatable revenue system, with the warning that effort is usually not the problem.
Two practical points for the buyer.
First, the deliverable shape that fits is a taught session or workshop plus a leave-behind, matching how she already works through coaching, the StepUpXchange accelerator, the free NexGen CS Leadership Masterclass, and the Customer Revenue Lab newsletter.
Second, none of the reviewed posts sets out a rate card, deliverable list, or booking terms, so scope, fee, and timing have to be agreed directly with her rather than assumed from the content.
When to choose a specialist
Brief B: a brand wants paid social placements that push a product to a broad audience, with a promo code, a swipe-up, and a target cost per engagement, and it expects the creator's follower count to predict reach.
Read more
Decision: weak fit, on the evidence reviewed.
The content is leadership education aimed at customer success professionals, not product-led persuasion aimed at shoppers or end users.
Every reviewed post makes an argument about how CS teams should operate, then points readers to her own newsletter, masterclass, or community; none is a sponsored demonstration or a purchase prompt.
The audience numbers are also thinner than the brief assumes: the only measurement available is a platform account record showing 27,776 followers on October 11, 2026.
There is no supplied geography, seniority, occupation, engagement rate, click rate, or past sponsored-campaign performance, so a cost-per-engagement target cannot be honestly planned from this material.
Partnership terms are a second gap: across eight posts there is no media kit, rate card, sponsor policy, affiliate arrangement, or inquiry page.
Her own programs and the CxXchange community are things she runs, not bookable ad slots, and award nominations plus partner hashtags are not evidence of any paid deal.
The same review holds for a narrower mismatch: a brand seeking technical developer or engineering reach will not find it here, since the posts are written for sales, success, and post-sales leadership.
This is not a claim that she never takes sponsorships, only that nothing in the reviewed material documents one, so the brief would need those questions answered before any placement decision.
Cheap next test for the buyer: ask for recent engagement and audience-composition data plus a stated deliverable and price, and treat a refusal of that request as a no-fit signal rather than a reason to guess.
A worked campaign example
Incoming brief: a B2B SaaS company whose product is billed on consumption wants help improving its customer success and revenue strategy, and asks for a session on usage-based models.
Worked angle: sell a 45-minute working session titled around one question, "what has to be true before usage grows," delivered to the sponsor's CS and post-sales leadership, followed by a one-page worksheet the attendees fill in for a live account.
Opening move, taken from her own framing: usage is now part of the number the company is trying to predict, so watching usage alone is too late.
Middle block, three cases the audience can self-sort into: usage-based pricing, where consumption is revenue but temporary when it came from high customer effort; committed credits, where a late start produces a renewal conversation about leftover credits instead of expansion; and outcome-based pricing, where heavy usage without the agreed outcome raises cost to deliver while recognized revenue stays flat.
Then the diagnostic the sponsor's leaders actually complete: pick one core customer job for one account, list the use cases that must go live, the teams that must adopt, and the milestones that must be reached, then compare that list against what the customer got done.
Close with the outcome-versus-interface point, because it is the most accessible thing she has published: her test of three work-organizing apps ended with the one she never had to learn, and the customer-facing lesson is that onboarding capacity spent teaching where to click is hidden effort that delays value.
Sponsor payoff: the worksheet makes the sponsor's product the place where pre-usage milestones and verified outcomes get tracked, without turning the session into a demo.
Suggested call to action, kept to one: invite attendees to the Customer Revenue Lab newsletter for the fuller argument.
Two things the buyer must settle before this is costed or promoted.
Her formats on record are her own coaching, accelerator, masterclass, and newsletter, and the reviewed material gives no price, exclusivity, lead time, or booking route, so treat those as open items to negotiate.
Also, the November 10 NexGen CS Leadership Masterclass is her own free class and described as her second-to-last, so plan a separate session rather than assuming a sponsor slot inside it.
The community-led-growth alternative brief is viable too, but lead with the origin story and the principle behind it rather than a reach promise: CxXchange began as office hours after roughly 80 people responded to a hiring post, grew into a community she says has about 4,000 members and around 20 volunteer board members, and she describes community as intentional and organic, additive rather than competitive.
Pick Seth Hansen for the same brief when the problem is the first ninety days rather than the billing model.
Read more
The reviewed posts argue that most companies lean on NPS as their primary customer success metric and that time to value tells them more: if a customer does not reach a first meaningful outcome quickly, the playbooks, the business reviews, and the roadmap for AI do not matter.
That gives a sponsor a session that ends with a measurement change instead of a pricing discussion, replacing or demoting a lagging satisfaction score in favor of the moment a customer decides the product is working.
His framing lands where Jan Young's does on tieing customer success to business outcomes, and he currently holds a customer success leadership seat, which suits a buyer who wants a working operator in the room rather than an outside advisor.
The reviewed material is two posts, and only one of them carries a method.
The other announces a job change and explains nothing about how customer success should run.
There is no material here on consumption pricing, committed credits, outcome-based contracts, or the difference between activity and delivered value, which is the core of Jan Young's usage work.
There is also nothing on community building, no workshop or teaching format, and no stated availability, rate, or booking route.
A session built only on time to value would still need the sponsor to supply the usage-economics depth that Jan Young has already published.
Choose Jennifer Brown when the decision moves from what to teach a customer success team to how the company should buy and structure creator partnerships.
Read more
The reviewed posts argue that creators are not paid media placements, that judging a single post against click-through and cost benchmarks misses trust, message alignment, repetition, and storytelling that compounds, and that when a brand puts advertising money behind creator content, the rights to use that content, voice, and likeness are a commercial asset rather than a favor repaid in exposure. For a sponsor whose real question is whether to run one campaign or a long collaboration, and what it should pay for usage rights, this is a closer match than a customer success session would be.
It answers a different brief.
Nothing in the reviewed material covers customer success operating models, usage-based or outcome-based pricing, retention signals, or post-sales revenue.
A sponsor that came for a session on usage-based models would leave with a campaign-structure conversation instead.
The reviewed material is also two short argument posts with no metrics, no sample contracts, and no stated rates, availability, or booking terms, so the commercial terms would have to be settled from scratch.
Choose Karyn Mullins for the same brief when the buyer's problem is ownership across functions rather than usage economics.
Read more
The reviewed posts describe retention problems that surface only when the customer leaves, list the earlier warning signs, and argue that a health score alone prevents nothing without a shared view of customer data across sales, customer success, product, support, and finance, an agreed set of signals, a consistent review cadence, and clear ownership of what happens next. For a sponsor whose teams already agree the account is at risk but disagree about who acts, that is a more direct starting point than usage-metric literacy.
The two reviewed posts are short pieces that point to a co-authored outside article and a panel conversation with other named contributors, so the published evidence shows the framing rather than the working method.
There is no detail on consumption pricing, credits, AI-driven consumption, or the value-realization questions Jan Young's posts work through, and no community-building or coaching program material.
The posts also promote rather than demonstrate a session, so a buyer should expect a framing discussion and plan to bring the account-level detail, rate, and format expectations to the conversation directly.
This profile is based on eight full LinkedIn posts from Jan Young's own account, covering customer success leadership coaching, usage-based and outcome-based pricing, AI's effect on CS work and onboarding, the CxXchange community, the Customer Revenue Lab newsletter, thought-leadership award nominations, and Jan Young's own route into customer success.
The posts carry no publication dates in the reviewed material; internal references point to an October 31 award-voting deadline and a November 10 masterclass, and account data shows 27,776 LinkedIn followers as of October 11, 2026.
Comparison used two retained LinkedIn posts each from Seth Hansen, Jennifer Brown and Karyn Mullins, published between October 2025 and September 2026.
Material gaps for any decision: no media kit, rate card, sponsor policy or booking route; no audience demographics, engagement rates or past sponsored-campaign results; and no long-form work reviewed beyond references to the newsletter.
Recent engagement
Across their last 6 LinkedIn posts, the median post got 22 reactions and 17 comments. Checked 2026-11-02.
