The Front Lines
SubscribeContent Studio
Ashley Stamps-Lafont.
VP of Customer Success · QuotaPath
Ashley works with leaders navigating career transitions, helping them land new roles, grow in their careers, or define their next step with confidence. Through 1:1 and group coaching, as well as targeted advisory, she helps clients gain clarity on their goals, identify obstacles, and take actionable steps forward. Her clients consistently achieve meaningful career moves or land new roles within approximately 90 days.
Guest
Ashley Stamps-Lafont
VP of Customer Success
Company:
QuotaPath
Location:
Greater Montreal Metropolitan Area
Loading episode...
Listen onSpotify

QuotaPath: The Multi-ICP Bet That Unlocked a Stalled Retention Strategy

Ashley Stamps-Lafont spent a decade building customer success organizations across growth-stage startups, larger companies, and private equity-backed businesses before joining QuotaPath. That range gave her something most CS leaders don't carry into the role: a clear-eyed view of which playbooks transfer across stages and which ones collapse under different conditions.

At QuotaPath — which helps commissionable teams manage compensation processes and ensure comp plans drive the right behaviors — she would need all of it. The go-to-market motion she inherited was built around a bottom-up adoption thesis. Get enough individual sales reps using the tool, and they'd push it upward. "Hey CRO, hey VP of Sales — I've been using this tool to track my commissions." It was a reasonable bet. It partially worked. And then it hit a ceiling.

In a recent episode of The CX Front Lines, Ashley shared the strategic decisions behind QuotaPath's retention model, how she structures planning, and why she believes most CS organizations are leaving their most important lever untouched.

Why One ICP Is Almost Never Enough

The rep-led motion produced traction, but Ashley recognized it wasn't producing the right kind. Individual rep adoption didn't reliably convert into organizational commitment. The retention math didn't close.

The pivot was deliberate. QuotaPath moved upmarket, targeting finance professionals and RevOps leaders — buyers with budget authority, organizational mandate, and a fundamentally different relationship to compensation management software. The results were materially better.

Ashley's framework from this experience is explicit: "It would have been silly of us to think that there's only one ICP that we need to optimize for." Her rule is two to three ICPs maximum. More than that dilutes execution. Fewer, and you're optimizing for the wrong retention outcomes. "I tend to think that there can be two maximum three in order to improve on your retention and growth."

The underlying principle is about signal quality. Rep-led adoption tells you the product is useful. Finance and RevOps adoption tells you the product is embedded. Those are different signals with different retention curves, and confusing them is expensive.

Planning Backwards From Lagging Outcomes

Ashley kicked off QuotaPath's 2026 plan in mid-2025. That timing is deliberate. The gap between leading operational decisions and lagging retention outcomes is longer than most CS leaders account for, and starting in Q4 for Q1 means you're already behind.

Her planning structure maps backwards from the company revenue objective through net revenue retention, gross revenue retention, and implementation timelines. She flags implementation timelines specifically because she's identified a direct association between time-to-value and lagging retention outcomes. That connection dictates where resources go.

People, process, and tooling decisions all follow from that backward map. She runs a quarterly revenue plan in parallel — not as a replacement for annual planning, but so adjustments can happen without waiting for the next cycle. It's a planning architecture built for a startup environment where conditions change faster than annual plans accommodate.

Using AI to Solve a Specific, High-Stakes Problem

Ashley has been using AI tools daily for two years and has built agents for personal productivity. But the most operationally significant application at QuotaPath targets one of SaaS's most persistent churn-risk moments: platform migrations.

When a software company releases a new version of its platform, getting existing customers migrated is a known danger zone. Ashley's team built a solution in Claude Code that accelerates migration processing. Her description: it expedites "the processing of those migrations without any drawbacks to the actual customers." This is not AI as a productivity layer. It's AI applied to a specific operational bottleneck with a direct line to retention outcomes.

Her advice for leaders earlier in their AI journey: "Don't let that curiosity kind of result in decision paralysis. Just start with one and figure it out." She names Claude and Google Gemini as her preferred tools based on flexibility, and recommends starting with the freemium tier before building.

The Influence Problem Most CS Leaders Don't Acknowledge

Ashley's sharpest observation has nothing to do with technology. After a decade on executive and GTM teams, she's identified a consistent pattern: CS leaders are the least vocal people in the room. "CS leaders on a go-to-market or executive leadership team tend to be the least vocal. So speak up."

That silence has consequences. It reads as low conviction to peers who are actively advocating for resources, headcount, and organizational alignment.

Her diagnosis connects to how CS leaders position themselves broadly. CS is a jack-of-all-trades discipline, and many leaders lean into that identity. Ashley's view, borrowed from QuotaPath's CEO AJ: "You want to be good at most things, but excellent at one." Generalism is the price of entry. What earns organizational trust is being undeniably excellent at one thing and being vocal about it. "When you're able to do that, you can bring others along for the ride and project that confidence that makes others believe in what you are advocating for."

The same principle applies to hiring. Ashley's standard for founders evaluating CS leader candidates is unambiguous: "Every leader, if they are going to be impactful for your company, should have generally done it before at a company that just looks like yours." The interview test is simple — ask for stories that match your current stage and your next one. If the stories aren't there, neither is the fit.

QuotaPath's post-sales org covers implementation, account management, solutions engineering, and support. Ashley reports retention and productivity metrics directly to the board. The position she's built is the one she argues every CS leader should be building: not a service function adjacent to revenue, but the framework the revenue strategy runs on. "CS strategy is company strategy — that's been the way it's worked for me for the last 10 years as a leader."

Six takeaways from this conversation.

Actionable for undefined founders

  1. Reframe CS as company strategy to earn a seat at the revenue table.
    Ashley doesn't present CS as a cost center or retention function — she positions it as the operating framework the entire business runs on. That reframe is what gets her in front of the board reporting on revenue and productivity metrics. "CS strategy is company strategy — that's been the way it's worked for me for the last 10 years as a leader."
  2. Your first ICP hypothesis will be partially wrong. Build for two or three.
    QuotaPath started with a rep-led growth motion — get enough individual sales reps using the tool and they'd push it up to CROs and VPs of Sales. It worked to a degree, but the real retention and expansion unlock came when they moved upmarket to finance and RevOps buyers. Ashley's rule: assume you need two to three ICPs to optimize retention and growth, and don't let early traction with one blind you to the others. "It would have been silly of us to think that there's only one ICP that we need to optimize for."
  3. Start your annual plan in the middle of the prior year — and run it quarterly.
    Ashley kicked off QuotaPath's 2026 plan in mid-2025. She mapped from the company's revenue objective backwards through NRR, GRR, and implementation timelines — then made people, process, and tooling decisions from there. She runs a quarterly revenue plan in parallel so adjustments don't wait for annual cycles.
  4. Use Claude Code to solve the migration problem.
    Platform migrations — getting customers from one version of your product to the next — are one of the highest-churn-risk moments in SaaS. Ashley's team built a solution in Claude Code that accelerates migration processing without degrading the customer experience. This is AI applied to a specific, high-stakes operational bottleneck — not a generic productivity play.
  5. Hire CS leaders who've done it at a company that looks exactly like yours.
    Ashley's standard for founder hiring advice: the right CS leader should be able to tell specific stories about the challenges you're facing now and the stage you're trying to reach. Breadth of experience across company stages matters — but only if it maps to your current situation. "Every leader, if they are going to be impactful for your company, should have generally done it before at a company that just looks like yours."
  6. CS leaders lose influence by staying quiet.
    Ashley's observation from a decade on executive and GTM teams: CS leaders are consistently the least vocal in the room. That silence reads as low conviction, which makes it harder to get resources, alignment, and organizational buy-in. Her directive, borrowed from QuotaPath's CEO AJ: be good at most things, excellent at one — and be loud about it. "CS leaders on a go-to-market or executive leadership team tend to be the least vocal. So speak up."

More episodes

Dini Mehta
Operator in Residence · Peak XV