← All work
Rev2023–2025Director, Product Design

In one year, Rev went from a transaction-based service to a SaaS product

Stop the churn. Shift from transactional to SaaS. Quickly. How a small design team rebuilt mobile, activation, meetings and checkout around the behaviors that make people stay.

Executive summary

7 min read
What I did
Directed product design (3 designers, 1 researcher) through Rev's shift from one-off transcription orders to a SaaS product: the mobile app overhaul, Day 1 activation, the Meeting Hub and a unified checkout.
Who with
A High-Value Actions tiger team: a product manager, a growth marketer, a UX researcher, an engineering lead and me. Plus product, engineering and marketing partners across Rev.
Intent & reasoning
Churn was rising, freelance transcription cost far more than AI, and speech recognition had passed 90% accuracy. Competitors were catching up, so the shift to SaaS had to happen quickly, and it had to be built on what users actually do.
Outcomes
22%42%Day 1 activation
69%80%retention, paid subscribers
+38%mobile app installs, year over year
15 flows1unified checkout, from 15 flows across codebases
The hook
Users were already recording meetings. They just weren't doing it where we had built for it. Read the story ↓
Rev project cover
01Context

A transcription marketplace facing an AI cliff

Rev was established in 2010 as a freelancer transcription service. Its speech recognition now beats models like Whisper in accuracy, but in 2023 the business model hadn't caught up.

Problems to solve in 2023

01

Churn

Rapidly increasing.

02

Cost

Freelancer transcription costs far more than AI transcription.

03

Models

Speech recognition was improving fast, to above 90% accuracy.

04

Foundations

Rev was never built in a future-proof or scalable way.

“Stop the churn. Shift from transactional to SaaS. Quickly.”
The mission
02The shift

From ordering a file to building a habit

A transactional service optimizes the order. A SaaS product earns repeat use. That changed what we measured and what every screen was for.

Before: transactional

  1. 01Capture
  2. 02OrderConversion, add-ons, premium artifacts, turnaround time
  3. 03Share

After: SaaS

  1. 01CaptureAcquisition, time to value
  2. 02ManageRetention, repeat usage, files per user
  3. 03SynthesizePerceived value beyond transcription
  4. 04ShareSharing and k-factor
03Mobile

An app people avoided, rebuilt in one quarter

A heuristic evaluation of the mobile app surfaced the top offenders. Within the first quarter of 2024 we rebuilt the core of it, then kept testing and iterating through the year.

The before: top offenders

01

No connection to the web experience

02

A coin system users didn't understand, built to skirt the app store tax

03

Recordings sometimes failed without telling the user

04

With the phone locked, you couldn't tell if it was still recording

05

Login sat halfway through checkout

06

Not HIPAA compliant, and failed AA accessibility

Rapid design process

  1. 01PrioritizeStagger the timeline with PM plans and engineering foundations
  2. 02ConceptV1 designs, with feasibility talks
  3. 03SocializeStakeholder feedback
  4. 04TestRapid usability and value-concept testing
  5. 05ShipIterate, implement, instrument tracking
  6. 06MeasureIterate where needed

What shipped

Rev recorder with waveform
One-click record
Rev recorder with live transcript
Live transcript
Save recording sheet
Save & transcribe
Rev file list
Files, synced with web
Transcript view
Transcript & sharing
Summary templates
AI summary templates

Login up front on the same identity as web. Live transcription with bookmarks. Minutes from your subscription instead of coins.

Outcome

+38%monthly app installs, year over year
4×files created by people who use the mobile app

Store ratings

App Store rating4.0 → 4.4
Google Play rating3.5 → 4.0

The app also secured renewals from high-volume clients like ESPN and opened the app to HIPAA-compliant accounts.

04Activation

Ten experiments in two months

After VoiceHub launched on September 9, 2024, a tiger team set out to find the High-Value Actions: the behaviors that make Rev a habit. Our product gains value when it becomes System 1, not System 2, so we cross-checked what people said against what they did.

October–November 2024

  1. 01Week 1Data & discovery: interaction data, a Pendo survey, users via sales
  2. 02Week 2Goals & hypotheses: key metrics, dashboards, test plans
  3. 03Weeks 2–4Design & launch 10 prioritized experiments
  4. 04Weeks 3–8Measure, synthesize, set next steps
Experiment 01

If we simplify the first action to a single task, creating or uploading a file, Day 1 activation will increase.

  • Paste-a-URL and one-click recording in the top navigation, on web and mobile
  • Deprioritized the Meeting Hub container in the hierarchy
  • Direct, concise messaging about getting started
Day 1 activation

22% 34%

Files per user

1.8 2.9

Time to first file

4.1m 3m

Experiment 02

If we automatically generate a summary for every transcript and put it in the notification email, retention will increase.

  • Users of summaries and transcript chat transcribed 53% more files, so we stopped making people ask for a summary
  • Summaries with timestamps in email, so people engage instead of download and leave
  • Searchable templates with automated tags
Summary engagement / day

1.7k 10.1k

Retention

69% 74%

Experiment 03

A trainer file to explore will increase engagement with synthesis and improve Day 1 activation.

  • With marketing, a trainer file with an educational video, sent to every new account
  • Low-fidelity onboarding guides for key flows
Day 1 activation

34% 38%

Chat queries / session

2.3 4.2

Time to file action

6m 3.7m

Where it landed

Day 1 activation22% → 42%
Retention, paid subscribers69% → 80%
Files per user1.8 → 6.4
Customer acquisition cost$26 → $19

The new real-time transcription and summary features have produced more than 66,000 AI-generated summaries for users.

05Meeting Hub

The feature nobody used was the second most common job

Almost no one connected a calendar, and those who did barely recorded. Then I realized we could run conversation types through our secure LLM, and “Meeting” kept ranking second. People were recording meetings, just not through the Meeting Hub.

What we knew

<2%of subscribers connected a calendar
~80%of connected calendars had zero events load
~37meetings recorded per week, across everyone

How we classified what people record

  1. 01SampleA targeted smart sample of the data
  2. 02ClassifyThe model labels conversation types and explains why
  3. 03GroupSynthesize similar categories
  4. 04TrackWatch leading types over time to steer features and marketing
Meeting Hub welcome screen on mobile
We A/B/C/D/E tested dashboard prompts, tested value messaging in paid media with marketing, built onboarding that set up the mental model, and added recording preferences so nobody had to toggle every meeting.

Results

Subscribers with a calendar connected<2% → 8.5%
Connected users recording meetings<12% → 55%
Meetings recorded per week~37 → 2,000+
Month 2 retention, paid43% → 49%

Meeting adoption up 5×, files shared per user up 6.5×, and calendars with zero meetings down from 80% to 2%.

06Foundations

Fifteen checkouts became one

The SaaS shift needed plumbing people never see.

15 flows1unified checkout flow and codebase
3 platforms1payment and entitlement hub, in Zuora
01

Roles & permissions

A framework for enterprise admin control.

02

File parity

Collect, manage and synthesize files across devices.

03

File architecture

Many artifacts from one original file.

04

File management

Better organization, importing and sharing.

07The team

How we worked

Design was in high demand with few designers, so I built ways of working that let a small team move fast.

01

Token Studio

Scalable, consistent design tokens across design and engineering.

02

No-code AI prototyping

Faster validation, fewer desk checks.

03

UX Hub

Artifacts, context, planning and onboarding in one place.

04

UXR repository

Research insights organized, closing an institutional gap.

05

Silent critiques

Async feedback through Loom.

06

CREATE framework

Templatized for behavior change: cue, reaction, evaluation, ability, timing, experience.

Next case studyCharles SchwabBuilt the Schwab Assistant: a 27% average reduction in calls and chats.