Results

Field notes from the work

Real outcomes from teams I've led and built for. The problem, what I did, and what changed.

$3M

ARR saved in year one by a retention playbook

−15%

human support tickets after launching an AI chatbot

+20%

chatbot customer satisfaction (CSAT)

2→25

people on teams I've built and scaled

Superpower Social · Fractional Head of CX · 2025 to now

Scaling post-sale for a fast-growing AI tool

Problem
Rapid growth, manual onboarding and no single owner of the customer after the sale.
What I did
Mapped the full journey, automated customer communications, wrote three core SOPs and built cross-team dashboards and a feedback loop into the product.
Result
97% gross revenue retention and 6 weeks faster to launch new customers.

Wave · Associate Director, CX Enablement & Retention

An AI chatbot customers actually liked

Problem
Support volume growing faster than the team, and self-service that wasn't working.
What I did
Led the move to an AI chatbot, rebuilt the knowledge base, and partnered with data and analytics on a customer health score.
Result
15% fewer human tickets and 20% higher chatbot CSAT.

Geotab · Senior Customer Experience Manager

Keeping customers through a crisis

Problem
When the pandemic grounded customer fleets, a wave of cancellations was coming.
What I did
Built the retention playbook for the response team, used data to spot who needed help most, and planned the return to normal.
Result
75% of impacted fleets retained, and a CX analytics team built from scratch.

Rogers Communications · Post-Sales CX Manager

Turning around a public reputation

Problem
Escalations, poor reviews and sales promises that set customers up to churn.
What I did
Wrote the retention playbook, set up honest-selling QA for 120+ reps, and fixed the escalation path.
Result
$3M ARR saved in the first year, Better Business Bureau rating from C− to A, and 93% CSAT.

Built with AI, honestly

AI does the typing. I make the calls.

I build with tools like Claude Code, trained in forward-deployed engineering. AI speeds up the code and the first drafts. I decide what gets built, check every result, and own what ships. I'll always tell you which is which.

  • Your data stays in your systems, and keys never sit in code
  • A person approves anything a customer sees
  • Everything I build is documented so your team can run it

Busy week. Can we batch-cook Sunday?

Yes. Roast a double tray of chicken Sunday; Tuesday becomes tacos, Thursday a grain bowl. Here's the seven-day plan →

Sun Roast chicken Tue Tacos (leftovers) Thu Grain bowl

Something I built: a meal-planning app for many households with a Claude chat agent that plans the week and saves it in one tap. Live demo link coming.

Want results like these? Let's talk.

Bring one problem to a free 20-minute call.