Context
Powerful, but vets couldn't yet see the value
Companion is Scribenote's AI agent for veterinarians, like a veterinary assistant that vets can
ask about their cases. It began as a set of separate, specialist AI agents, each built to address a
different clinical workflow, and each in beta found real demand. But in beta, it was helpful in
only a limited way.
Companion 2.0 took the product from beta to launch in April 2026, and from free to paid. It
unified those separate agents into a single AI agent, and with new memory, context, and file
uploads, its capabilities expanded greatly. But that created the deeper problem: vets were still
using the newly-improved Companion the way they always had, because they didn't know what it could
now do. And it was a big ask for skeptical doctors to hand even a sliver of their clinical judgment
to an AI, now one they had to pay for. It had to feel worth paying for, not just worth trying.
Role
I was the product marketing lead for the launch. I owned the positioning and messaging, the
customer-education campaign, and the launch and lifecycle emails, and I shaped the pricing story
and the sales enablement that equipped the team selling it. I also built askcompanion.com myself in
Claude Code, writing and shipping the copy across the site using GitHub.
Approach
Show vets what to ask
The fastest way to fix a value problem is to make the value impossible to miss. So I built an
education campaign around the exact questions vets were already asking themselves. Working
together with our in-house veterinary team to turn real clinical scenarios into a series of
case-study emails: here's a situation you know, here's how you'd ask Companion, and here's what
it gives you back. I sent out six clinical use-case emails in all, each pairing a real scenario with
a walkthrough filmed by a member of our in-house clinical team.
Around that campaign, I owned product marketing for the launch end to end. I built pre-launch
anticipation with a waitlist that drew 200+ vets before go-live, and owned the
positioning and messaging, the launch emails, the blog timed to go-live, and one-page sales sheets
to equip the team selling it.
Then, I created askcompanion.com using Claude Code, refining the copy across
each page and shipping each change as a pull request to GitHub, then promoting it through staging
into production. The guiding rule throughout, which the team kept for the remaining content, was to
lead with the clinical question the vet is already asking, not the feature we want to announce.
Results
6x revenue growth in week one
In its first week live, Companion's revenue grew 6x. The relaunch did what it set out to do:
it turned a beta vets weren't sure what to do with into a paid product they reached for, and it
showed up on the revenue line almost immediately.
The education campaign carried it. The six case-study emails held a 41 to 52% open rate across
all sends with no dropoff, which is rare for a multi-week campaign. But the clearest signal wasn't
just in the numbers. I knew we had succeeded when our users started asking Companion the exact
questions from our case studies, word for word.