Retentionasasystem

A veterinary clinic doesn't win on the first visit — it wins on the tenth. Vaccines, dental cleanings, annual exams: the business is a long series of small, well-timed moments of care. Which makes retention the product, and lifecycle messaging the interface.

When I took over CRM at Sploot, the opportunity was obvious: the clinic knew things about each pet that no generic marketing tool would ever use — species, age, last visit, what's due next. Almost none of it reached the customer.

The default failure mode of CRM is entropy: every campaign built as a one-off, logic duplicated and drifting, nobody sure which automation fires when, and consent handled differently in every flow. It works at ten workflows and collapses at fifty.

And the stakes aren't abstract. Message a customer about the wrong pet — or after they've opted out — and you haven't just wasted a send. You've damaged a relationship built on trust in a care provider.

I mapped the whole customer journey into explicit stages with entry and exit criteria — new client, active, lapsing, lapsed, won back — and made every campaign declare where it lives in that map. No orphan automations.

• 01Identity unification first, so a client is one person across clinic software, web, and marketing tools.
• 02Consent and opt-in management as a single shared framework every flow inherits — never per-campaign logic.
• 03Personalization from real clinical context: the pet's name, what's due, which clinic they know.
• 04Naming conventions and documentation, so the fiftieth workflow is as legible as the first.

Any single flow is easy. Fifty coherent ones is architecture.

Over three years I built 50+ campaigns and workflows in HubSpot — onboarding sequences, recall reminders, lapsed-client winbacks, review loops — all running on the shared identity and consent layer, all personalized from unified profiles.

This system is also what taught me the data lesson the hard way — the ceiling on lifecycle work is the quality of the identity and event data underneath it. That realization became the data-stack project.

Clients hear from their clinic about the right pet, at the right moment, through channels they've actually consented to. The team ships new campaigns into a system with rules instead of a pile with history. And the whole thing survived my attention moving elsewhere — which is the real test.

50+

flows running in production

1

shared consent framework

3 yrs

of compounding instead of entropy