What enablement means when reps and CSMs work alongside AI, products ship daily, and "healthy" can't be measured by usage alone. Notion just turned 60 to 70 CSMs and renewal managers into Outcome Architects in a single month. Clay's CS team grew from 5 to 70, and Baseten went from about 120 to almost 500 people in eight months. Enablement leaders from all three explain who they hire now, where they draw the line between automation and human touch, and what replaces traditional health scores in a consumption world. If you lead enablement, ops or CS, this panel maps the new job.

If you've wondered what AI means for your career in customer success, start here. The hosts of the Customer Success Meetup open Moment 2026 with an optimistic argument: as intelligence gets cheaper, customer context rises in value, and the bottleneck has moved from building AI to making it work for real customers. John Gleeson makes the case, then Junan Pang (Fin) and Monica Perez (Lovable) share what that shift looks like inside their own companies. It sets up everything the rest of the day explores.

Most CS teams are still running the old motion (adoption dashboards, login-based health scores, quarterly check-ins) against a new scoreboard, where consumption pricing makes value realization the revenue model itself. At Lovable, the fastest company to reach $400M in revenue under that model, the CS team stopped asking "are they using it?" and started asking "if we disappeared tomorrow, does something break?" They call the answer load-bearing: less than 1% of what customers build clears the bar, but it's the one leading indicator of both retention and expansion, so they tied the whole team's goals to it, shifting from nurture to deployment motions and adding forward-deployed engineers alongside advisory CSMs. The playbook that got you hired won't keep you employed, and that CS isn't being disrupted but promoted, because proof is now the only differentiator.