Email sequenceConcept project · fictional product

RevisionDesk: seven-email onboarding sequence for trial users

RevisionDesk is a fictional client-review tool that keeps files, versions, feedback and approvals on one review page. I wrote its seven-email onboarding sequence for this concept project. The sequence runs from signup to the day the 14-day trial ends. The emails are written to get one live client review completed in the product, so the reader can choose a plan on the strength of it.

Product: Client-review software. Each uploaded project gets one review page where comments, versions and approvals stay together. Clients comment and approve by link, with no account. 14-day trial, no card taken.
Audience: Teams managing client feedback, file versions and approvals.
Conversion goal: A paid plan chosen before or after the 14-day trial ends. No card is taken at signup, so nothing renews on its own.

The copy challenge

The reader's last round of feedback arrived as an email from the client, a Slack message, comments on the file and a request from a call that only one person wrote down. Then a project manager spent a morning working out which version was current. The tools involved work, and the sequence says so. The emails have to make that cost concrete, get one real client review into the product, and answer the comparison honestly once the reader has had a week to form it.

My role and key writing decisions

I wrote all seven emails for this concept project. No client was involved.

I built the sequence around one live client review rather than a product tour. The welcome email asks for a project "that's already in review", Email 3 calls sending the link to a client "the real test", Email 5 asks for one whole project run through and compared with the last one. Email 7 treats a trial without a real project as a reason the reader may not be able to decide.
I sold the client's side of the product as the absence of steps. Email 3's subject line says the client does not need an account. The body lists what the client is spared, "No account, no password, no software to install", and the reason follows: "Every extra step gives the client another reason to reply by email instead." The no-account link returns in Email 5 as the closing line of the comparison.
I conceded the objection before answering it. Email 5's subject puts the objection in the reader's words, "We already do this in Figma and Slack", and the preview answers "Mostly fair". The body gives Figma, Slack and email their due before naming the one gap: the point where the review moves between them. The email then says who does not need the product and makes the test the same action as the earlier emails: one live project, compared with the last one.

Finished copy: the sequence

#EmailSend timingIntended action

1Welcome and first uploadDay 0 — on signupUpload a first project

2The cost of scattered feedbackDay 1Create a review page

3Invite the first clientDay 3Send the review link to a client

4Version history and approval trackingDay 6Check pending approvals

5The "we already use email, Figma and Slack" objectionDay 10Run one live project through it

6Trial ends tomorrowDay 13Choose a plan

7Trial endedDay 14Choose a plan, or reply with feedback

Email 1 of 7, Day 0, sent immediately after signup

Intended action: upload a first project

Subject: Your RevisionDesk trial is live
Preview: Start with one project. Upload takes about two minutes.

Your 14-day trial is active. We never took a card, so nothing renews unless you choose a plan.

The fastest way to see whether RevisionDesk fits your workflow is to upload a project that's already in review.

Designs, PDFs, videos, and documents all work. RevisionDesk creates one review page for that project. Comments, versions, and final approval stay together on that page.

Use a live project if you can. You'll get a much better sense of how RevisionDesk fits your actual review process.

Upload Your First Project

Secondary link: Watch the 3-minute walkthrough

Reply to this email if you get stuck. It comes to me.

Daniel Price, Customer Success, RevisionDesk

Email 2 of 7, Day 1

Intended action: create a review page

Subject: Where your last round of feedback ended up
Preview: Email, Slack, a Figma thread, and one note nobody wrote down.

Think about the last project you sent for review. The feedback may have arrived in several places: an email from the client, a Slack message from your account manager, comments on the file itself, and one request from a call that only one person wrote down.

Then someone asks which version is current, and your project manager spends a morning reconstructing the answer instead of moving the project forward.

RevisionDesk keeps that information in one place. One review page per project. Comments attach to the asset and to the specific version they were written on. When a client asks to go back to Tuesday's version, Tuesday's version is still there with its comments intact.

If you have not uploaded a project yet, use one that's already under review today.

Create a Review Page

Daniel Price, Customer Success, RevisionDesk

Email 3 of 7, Day 3

Intended action: send the review link to a client

Subject: Your client does not need an account
Preview: They open a link, comment on the file, and approve. No signup.

The real test starts when you send a project to a client.

Pick one project and send the review link. Your client opens it in a browser and comments directly on the file. No account, no password, no software to install.

That matters more than it sounds. Every extra step gives the client another reason to reply by email instead. The review link keeps the process simple: open it, leave feedback, approve when ready.

Comments stay pinned to the place and version they refer to. You mark each one resolved as you work through it, so both sides can see what is left.

Invite a Client to Review

Prefer to test internally first? Send the link to a colleague. Same flow.

Daniel Price, Customer Success, RevisionDesk

Email 4 of 7, Day 6

Intended action: check pending approvals

Subject: Find earlier versions and check pending approvals
Preview: Plus the dashboard showing which approvals are still sitting with clients.

Version history. Upload a new revision and RevisionDesk keeps the earlier versions with it. If a client asks to go back to something you sent last Tuesday, open the earlier version and see the feedback that came with it.

Approval tracking. The approval dashboard gives you the other half of the picture. It shows which assets are still waiting for review, who has them, and how long they've been sitting there. You can set a review deadline and let RevisionDesk send the reminder. Once something is approved, the approval stays attached to the project with the date and reviewer.

Check Pending Approvals

Daniel Price, Customer Success, RevisionDesk

Email 5 of 7, Day 10

Intended action: run one live project through it

Subject: "We already do this in Figma and Slack"
Preview: Mostly fair. Here is the specific gap.

Fair objection. Those tools work. The problem starts when the review moves between them.

Figma works well when the review stays inside Figma. PDFs, videos, copy documents, and other deliverables may still end up elsewhere.

Slack keeps the conversation moving, but feedback can get separated from the file it refers to. A message from three days ago does not automatically become part of that asset's revision history.

Email keeps a record, but the record is split across threads and nobody can tell which attachment is current.

RevisionDesk gives the project one place for files, versions, feedback, and approvals. Clients can open the review link without creating an account.

If your projects are single file, design only, and rarely revised, you probably do not need this. If they are not, run one live project through RevisionDesk this week and compare it against your last one.

Run One Project Through It

Daniel Price, Customer Success, RevisionDesk

Email 6 of 7, Day 13

Intended action: choose a plan

Subject: Your trial ends tomorrow
Preview: No card on file, so nothing happens automatically. Here are the plans.

Your trial ends tomorrow. We never took a card, so nothing gets charged and nothing renews on its own.

Pick the plan that matches how you work:

Solo, $19/month. One user managing their own client reviews.

Studio, $49/month. Small teams sharing projects and approvals.

Agency, $99/month. Teams managing several clients and reviewers.

Choose a plan and your existing projects, comments, versions, and approvals stay where they are.

Choose Your Plan

Not sure which plan fits? Reply with your team size and how many active client projects you run, and I will tell you which one to pick.

Daniel Price, Customer Success, RevisionDesk

Email 7 of 7, Day 14

Intended action: choose a plan, or reply with feedback

Subject: Your trial ended. Your projects are still here.
Preview: Upgrade picks up where you stopped. Or tell me what did not work.

Your RevisionDesk trial ended today. If you used it on a live project and want to keep the workflow, choose a plan and your account picks up where you stopped.

Your projects, versions, comments, and approvals are still there. If you never got a real client project into the trial, you may not have seen enough to make the call. Either way, I'd like to know what happened.

If RevisionDesk worked for you, choose a plan below. If something stopped you, reply and tell me what it was.

Choose a Plan

Secondary: Reply with feedback

Daniel Price, Customer Success, RevisionDesk

Concept scope

RevisionDesk is a fictional product. Its review pages, its no-account client links, its approval dashboard and reminders, its pricing and its 14-day trial terms are assumptions made for this portfolio project. The sender, Daniel Price of Customer Success, is fictional, and so are the send timing and the scenario in Email 2.

Figma and Slack are real products, named only as tools the reader already uses. The project has no client and no measured results.

Delivered

A seven-email trial onboarding sequence over fourteen days, with send timing for each email
Subject line and preview text for every email
Full body copy with one call to action per email, and a secondary link in the welcome and trial-ended emails

Need onboarding emails for your product?

Tell me what users need to do before their trial ends.

Discuss a project ← All work Service: Email sequences Next project: FlowPilot nurture emails →