# John Gaspar

John Gaspar works in customer success and shares practical ideas about SaaS retention, customer journeys, and using AI in customer success workflows.

- Profile: https://b2binfluencer.marketing/creators/john-gaspar/
- LinkedIn: https://www.linkedin.com/in/jpngaspar
- LinkedIn followers: 3,124
- Topics: artificial-intelligence, customer-success, customer-retention
- Based on 10 dated posts, latest 2026-10-06

## Summary

John Gaspar is useful for practical customer success retention and AI workflow ideas for B2B SaaS teams.

- Best for: B2B SaaS retention and AI adoption campaigns needing customer journey mapping and CS rollout planning.
- Not for: High-reach consumer awareness pushes measured by impressions, follower growth, or top-of-funnel leads.
- Check first: Confirm follower job titles, seniority, geography, engagement, and comparable post results.

### Takeaways

- Retention is won after go-live, not at onboarding.
- AI agents should augment customer success work, not replace it.
- AI is becoming an assumed workplace baseline, and unease is part of transition.

## Main ideas

- **Retention is won after go-live, not at onboarding**: Gaspar's core argument is that strong customer success teams have moved past onboarding checklists to what they call value expansion arcs. The riskiest part of a customer relationship is the long stretch after implementation, when the customer can quietly stop seeing new value even though the product is technically live and working. Gaspar turns that into five decisions a team can make: treat post-go-live as its own stage; segment the journey by persona, since admins, executives, and end users move differently and expansion signals differ for each; define lifecycle metrics rather than one-time health scores, such as adoption stickiness by month six and business value realization by month nine; document who internally owns each milestone touchpoint; and build in proactive risk detection rather than reacting at renewal. Journey maps are living frameworks that change with customer needs, product complexity, and revenue strategy — not documents completed once.
- **AI agents should augment customer success work, not replace it**: Gaspar frames AI agents in customer success as having crossed from novelty to necessity in about a year, but bounds the argument: the future of CS is "augmented, not automated." Agents are already good at defined, high-volume tasks that sit on top of existing systems, while the risk lies in letting them loose without rules. Gaspar recommends setting guardrails that specify when AI speaks to customers directly versus staying internal, piloting a few high-leverage use cases rather than everything at once, and integrating AI into existing processes so tools do not become isolated from the team's work. The post reads as a rollout plan in miniature. Gaspar ends by asking others what is working so they can compare notes, offering guidance in the spirit of shared practice.
- **AI is becoming an assumed workplace baseline, and unease about it is part of the transition**: Gaspar's second thread about AI is cultural rather than operational. It runs through a historical analogy: interview questions about email, Word, and Google Slides once mattered and now sound absurd, so saying "I use ChatGPT" will soon be unremarkable as AI becomes an invisible assistant threaded through ordinary work. The case for adopting it early is capacity — Gaspar points to routine work being handed to AI so people can invest more in the roles they already have. The post does not stop at enthusiasm: it names job shifts and a general "is this too much?" feeling before landing on staying curious and deliberately doing something uncomfortable. That willingness to hold both the practical upside and the unease at once is a recurring tone. It is the main tension across the posts: the same writer who describes AI agents as a necessity also treats discomfort as legitimate rather than something to argue away.
- **Automation does not remove the need for teams to stay connected**: A short post from a visit to the Frontify head office states a simpler priority that sits underneath the longer pieces: AI and automation are changing how people work every day, but they have not changed the need for connection. It matches the posture of the other posts — tools are added to a team's work, not swapped in for the coordination that holds the team together.

## Work to read

- [Mapping a Customer Journey That Drives Retention](https://www.linkedin.com/posts/jpngaspar_customersuccess-retention-customerjourney-activity-7325571418534961154-RHMp)
- [AI Agents in CS — What’s Real, What’s Next](https://www.linkedin.com/posts/jpngaspar_customersuccess-aiincs-csops-activity-7326497431649402883-kfEa)
- [Remember when job interviews included questions like 'Do you know how to use email?'](https://www.linkedin.com/posts/jpngaspar_remember-when-job-interviews-included-questions-activity-7379648686605099008-7aMM)

## Brand relationships

- **Frontify** (employment)

## Partnerships

The four posts read in full target customer success practitioners, offering advice on retention and journey mapping and explaining where AI fits into CS work. IBM, Gainsight, Gartner, TSIA and Totango appear as cited research and news, not disclosed commercial arrangements. A brand mention or campaign-style hashtag does not establish a paid deal. The Frontify reference in the April 2026 post reads as an employer or workplace connection—a visit to a company head office—not a sponsored placement. John Gaspar's posts include no media kit, rate card, sponsorship policy, advertiser audience specification or disclosure of past brand collaborations. No official inquiry route for partnership or sponsorship requests is published. Treat a paid partnership as unconfirmed; ask through a direct professional contact if pursuing one.

## Alternatives

- Craig Blum: Choose Craig Blum when customer success has no standing in executive decisions, or when the account base is too large for named CSM coverage and the job is to design a scaled programme. Blum's two posts focus on position and operating model, not the mechanics of a customer success journey. One argues that CS leaders need a place in decisions about NRR, churn, feature stickiness, expansion readiness, adoption gaps, and renewal and advocacy blockers, bringing data, story, and commercial impact rather than unread Slack updates. The other defines scaled success as a designed mix, not neglect: onboarding that drives adoption, content matched to customer maturity, in-app guidance that solves problems fast, signals separating accounts that are thriving, drifting, or ready to expand, targeted plays that feel personal, a community users want to join, and education that turns casual users into power users. This is the stronger starting point for a workshop with the executive team on the scaled-coverage model, rather than one with the CS team on journey mechanics.
- Auste Foster: Choose Auste Foster when the platform is already bought and underused. Her founder post describes that situation exactly: a company spends five or six figures a year on a customer success platform and eighteen months later the CSMs are back in Outlook. She writes from inside that stack, having worked in Medallia and then Gainsight as the first person on the EMEA professional services team and later a senior solutions architect, across sixty implementations. She says the projects she valued most came after go-live, once the implementation team had left. For a customer success platform configuration and automation engagement, the work she describes happens inside the platform you already own: pick the twenty things that matter for the next two quarters, build journeys that run without a human in them so a stretched team can focus on accounts that need attention, and leave the team something they can run, with an honest answer about whether they have the hours. Her second post adds a diagnosis Gaspar's posts do not make. When a CRO is measured on growth and a CCO on retention, each leader can be doing exactly what they were hired for while the company struggles to move in one direction. The friction is a measurement problem wearing a collaboration costume, and technology will not solve a disagreement about what success means.
- Chris Patin, MBA, CCSM, CSM: Choose Chris Patin when the immediate problem is the first 30 days and the renewal date rather than the whole journey. The onboarding post works through quick wins as the mechanism for early momentum: look for use cases that solve an immediate pain point, prioritise features that are easy to adopt but deliver visible results, and celebrate those wins loudly through dashboards, shoutouts, and executive summaries. The example is concrete — a client with low engagement after onboarding pivoted to a single reporting feature that saved the team ten hours a week, and adoption rose because value arrived fast. The renewal post extends the same logic: start the conversation months in advance rather than weeks, treat renewal as a milestone inside the success journey rather than the end of it, and make the case from data, stories, and outcomes rather than from the relationship. Clients renew because they have seen results. For a brief centred on onboarding adoption and renewal preparation, that is a tighter operational match than a journey-wide map.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/