Most SaaS customer success still runs on health scores that track activity instead of the signals that actually predict renewal and expansion. We rebuild the scoring, segmentation, and workflows so risk gets caught early and expansion opportunity doesn't sit unnoticed in a mid-market account.
The Problem
Health scores don't predict who actually renews or expands
Traditional health scores built from login frequency and support ticket volume correlate weakly with renewal and expansion decisions, so CS teams end up surprised by both churn and by expansion opportunities that never got flagged. A green health score two weeks before a cancellation notice is not a rare event, it's the default outcome of scoring the wrong signals. Fixing this means rebuilding the score around usage patterns that actually track with the value the customer is getting, not activity for its own sake.
At-risk accounts get flagged after the internal decision to leave is already made
By the time a declining usage trend, a champion departure, or a stalled onboarding shows up in a standard CS dashboard, the buying committee has often already started evaluating alternatives, which leaves the CS team negotiating from a weak position instead of intervening early. Catching this earlier requires tracking leading indicators – usage depth by feature, breadth of adoption across the buying team, time-to-value on new modules – well before renewal conversations start. Most CS teams have this data already; it's sitting unused in the product analytics stack.
Manual processes can't keep pace with account growth, and boards now ask why
A CS team that hand-builds account plans and tracks health signals for 50 accounts cannot do the same for 300 without either hiring at the same rate revenue grows or letting service quality slip on mid-market accounts. Most SaaS companies choose the second option by default, and the accounts that get the least attention are usually the ones with the most expansion headroom. With NRR now a standard line item in board decks and renewal cycles, scaling this requires segmenting accounts by revenue tier and risk, and automating the tail that doesn't need a human touch every week.
How We Help
We start by auditing your current health scoring model against actual churn and expansion outcomes from the last 12-18 months of account history. This tells us which signals in your existing data actually predict renewal behavior and which ones are noise, before we touch your CS tooling or process.
From there we rebuild the scoring model around usage depth, feature adoption breadth, and buying-committee engagement rather than login counts, and we tie every score directly to a specific playbook – what a CSM does differently for a red account versus a green one. This is growth strategy work, not just a CS process tweak, because the goal is connecting customer success activity to expansion revenue, not just satisfaction.
For scale, we segment your book of business by revenue tier and risk profile, and build automated workflows – lifecycle emails, in-app prompts, proactive outreach triggers – for the segment that doesn't need a dedicated CSM relationship. This frees your human CS team to focus on the accounts where a relationship actually moves the renewal or expansion outcome.
We work embedded with your CS and RevOps teams to implement the new scoring model in whatever tool you're already using – Gainsight, Vitally, or a homegrown dashboard – rather than pushing you toward new software. The goal is a system your team owns and can run without us, built on the data infrastructure you already have.
What makes this different from a typical CS consulting engagement: we build the measurement first, so every recommendation gets tested against real renewal and expansion data instead of best practices borrowed from a different business model. We operate as an extension of your team on a fractional basis, not as outside consultants who hand off a framework and leave.
Every engagement tracks net revenue retention, at-risk account identification lead time, and CSM capacity utilization as the core metrics. Monthly reporting to your leadership team shows whether the new scoring model and segmentation are actually catching risk earlier and surfacing more expansion opportunity, not just producing a prettier dashboard.
What we deliver
- Renewal-predictive health scoring model
- Risk-tiered account segmentation and playbooks
- Automated lifecycle workflows for tail-segment accounts
- NRR and capacity measurement framework
A health score that turns red the week before a cancellation notice isn't an early warning system, it's a post-mortem. The fix isn't more dashboards, it's scoring the signals that actually predict the decision instead of the activity that's easiest to measure.
Our Methodology
Our 90-day approach for SaaS customer success starts with a data audit: we pull 12-18 months of account history and test your current health scoring model against actual churn and expansion outcomes to find out which signals predict behavior and which don't. This phase typically takes 2-3 weeks and produces a clear picture of where the current model is failing.
Days 20-60 focus on rebuilding the scoring model around the signals that actually predict outcomes, building the playbooks tied to each score tier, and segmenting your account base by revenue and risk so the right accounts get human attention and the rest get automated workflows. We implement inside your existing CS tooling wherever possible to avoid a costly platform migration.
Days 60-90 shift to rollout and measurement – training your CS team on the new scoring model and playbooks, standing up the NRR and capacity reporting that tracks whether it's working, and handing off a system your team can run independently. This is different from typical CS consulting because we're building a measurement system first, not delivering a framework and moving on.
How We Work
The first 2-3 weeks are diagnostic: we pull your account history, current health scores, and renewal and expansion outcomes, and interview your CS, sales, and RevOps teams to understand what's already been tried and why it hasn't stuck. We come out of this phase with a data-backed list of what's actually predictive in your business.
Weeks 3-8 are where we rebuild the scoring model, design the tiered playbooks, and build the automated workflows for lower-touch accounts. We're in weekly working sessions with your CS leadership during this phase, testing the new model against live accounts before full rollout.
From week 8 on we move to a monthly cadence: a leadership review of NRR trends, early-warning lead time, and CSM capacity, plus ongoing support as the team adapts to the new system. Most engagements run 10-15 hours a week and last 3-5 months.
We typically work alongside your existing VP of Customer Success or Head of CS rather than replacing that role – our job is to bring the measurement rigor and the playbook design, while your team keeps the customer relationships and domain knowledge.
- Improved net revenue retention
- Earlier at-risk account identification
- CSM capacity freed for high-value accounts
If your saas / tech company needs customer success strategy leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
How much does a customer success strategy engagement cost for a SaaS company?
Customer success strategy engagements typically run $12K-$24K per month depending on the size of your account base and how much of the scoring and tooling needs to be rebuilt. Compare that to hiring a VP of Customer Success or Head of CS Ops, which now runs well into six figures in base salary alone before equity and benefits – you get senior strategic expertise without that hiring commitment, and the engagement scales down once the system is running.
How long before we see impact on net revenue retention?
Early warning improvements – catching at-risk accounts sooner – typically show up within 30-45 days of the new scoring model going live. Net revenue retention is a lagging metric tied to your renewal cycle, so if most of your contracts renew annually, expect 6-9 months before the full NRR impact shows up in the numbers, though expansion wins from better-targeted upsell conversations often surface faster.
How does this integrate with our existing CS team and tools?
We build inside whatever CS platform you're already using – Gainsight, Vitally, ChurnZero, or a homegrown dashboard – rather than pushing a new tool. Your CS team keeps the day-to-day account relationships; we bring the scoring model redesign, the playbook structure, and the measurement discipline. Weekly working sessions during the build phase, then a monthly leadership cadence once the system is running.
What makes Winston Francois different from a CS consulting firm or a platform vendor?
Platform vendors sell you software and leave implementation to your team. Generic CS consultants often bring frameworks that weren't built against your actual churn and expansion data. We start by testing your current signals against real outcomes before recommending anything, and we work fractionally embedded with your team rather than delivering a report and moving on to the next client.
How do you measure ROI from a customer success strategy engagement?
We track net revenue retention, the lead time between an account showing risk signals and that risk getting flagged, and CSM capacity utilization across account tiers. These get baselined in week one and reported monthly, so your leadership team can see whether the new scoring model and segmentation are actually moving the numbers that connect to revenue, not just producing more dashboards.
What type of SaaS company is the right fit for this service?
This works best for B2B SaaS companies at $5M-$100M ARR that already have a CS function and some health scoring in place, but suspect the scoring isn't actually predicting churn or expansion. If you don't have a CS team yet, that's a hiring conversation, not a strategy engagement. If your CS team exists but is drowning in manual account reviews with unclear ROI, that's exactly where this engagement starts.
