Portfolio
Proof that systems beat memory.
Different industries, the same operating problems — when the system is clearer the team spends less time rescuing accounts and more time moving them forward.
Different industries. The same operating problem.
Healthcare needs trust and implementation discipline. Retail needs visibility at scale. Consulting needs the journey made legible. Underneath, it's one job: make the system easier to operate.
The challenge
A clinical platform was closing deals faster than it could onboard them. Customers signed, then stalled — implementation lived in people's heads, adoption wasn't tracked, and renewals arrived as surprises.
What I did
I stood up the customer success motion end to end: a repeatable onboarding path, adoption checkpoints tied to clinical and operational use, account health signals the team could actually act on, and a renewal readiness review that started months before the date.
The result
Onboarding stopped depending on individual heroics. The team could see which accounts were healthy, which were drifting, and what to do next — before a renewal conversation forced the issue.
The challenge
A corporate account portfolio inside a premium brand had to feel personal to every client while still operating at scale. Relationships were strong but unevenly tracked, and growth depended on memory.
What I did
I connected the high-touch client experience to a real operating model — Salesforce segmentation and process, clear account ownership, executive-facing communication, and a cadence that kept the personal touch from breaking as the book grew.
The result
Account work became visible and repeatable without losing what made it feel bespoke. The portfolio had a system behind the relationships, not just goodwill.
The challenge
Service businesses with loyal customers but no lifecycle visibility — they couldn't tell you where customers stalled, why they churned, or which moments actually built loyalty.
What I did
I built customer journey diagnostics, onboarding and retention frameworks, and lifecycle maturity models, then translated all of it into a CRM and operating rhythm the team could run without me.
The result
Clients went from intuition to a map: a clear view of the journey, the stall points, and the handful of moments worth investing in. CX language became decisions a team could act on.
How I think
Operating principles.
- Customers feel the operating model.
- A weak handoff turns a closed deal into implementation risk.
- A dashboard is not an operating system.
- CRM hygiene is customer-facing, even when it looks internal.
- AI should reduce drag without replacing ownership.
- Renewal readiness starts long before the renewal.