A senior operator's practice — built on systems, not slogans.

Numbers first. Anecdotes second. Opinions third — and only when asked.

Every recommendation that leaves my desk traces back to a number you can audit. Gross retention. Net retention. Time-to-value by cohort. Logo churn by segment. Health-score precision against actual outcomes. If a recommendation can't be tied to a number, it's a hunch wearing a suit — and you can find hunches more cheaply than you can find me.

The anecdotes still matter. Three customer interviews surface what a year of NPS scores won't. But anecdotes are evidence, not conclusions. They go in the margin of the diagnostic, not at the top.

Retention is a system.

Health scoring is not a sentiment. QBRs are not an event. Expansion is not a hope. They're a system — instrumented, owned, reviewed on a cadence, and tuned against last quarter's misses. Most CS orgs I walk into have one or two of these working and the rest aspirational. The work is to build the missing pieces, retire the ones that aren't earning their keep, and connect the survivors so they tell one story to the board.

The CS org isn't broken because the team isn't trying. It's broken because no one drew the system, named the metrics, and held a Tuesday to them.

Built to your stage, not a template.

A health score that works at Series B doesn't survive Series D. A QBR cadence that runs for forty enterprise accounts breaks at four hundred mid-market. A comp plan that retains a five-person team becomes the reason the eighth hire leaves. Stage matters — revenue band, segment mix, churn baseline, sales-CS handoff maturity, the shape of the renewal forecast. The diagnostic surfaces the stage; the engagement is sized to it.

The fractional VP exists to make itself unnecessary.

Three to six months minimum, because anything shorter is theatre. But every engagement is built around the successor — the full-time hire who eventually owns the seat. The fractional VP runs the standing, owns the forecast, writes the board materials in the principal's voice. And, in parallel, hires and onboards the replacement. The day the replacement is forecasting on their own is the day this engagement ends. No retention play. No expansion play. The seat goes back to the company.

What we don't do.

• Slide-ware. The deliverable is a written assessment, an action plan, or a working system — not a deck for the deck's sake.
• Frameworks for their own sake. If a framework isn't producing a number the board can read, it's a craft project.
• "Transformation." Operators rebuild. The word's on the banned list for a reason.
• Long discovery. Two weeks of interviews is enough to know whether the work is real. If it isn't, the engagement doesn't start.

How it goes, in practice.

Every engagement starts with the same conversation — thirty minutes, no slides, no pitch deck. You describe where the CS org is breaking. I tell you which of the three engagements applies, or that none of them do. If a diagnostic makes sense, it runs two to four weeks and ends with a written document and a sixty-minute readout. From there, fractional or project work picks up, or doesn't. The honest answer is sometimes the answer.