Async Video for Agencies: Fewer Calls, Faster Approvals

Async video for agencies means replacing some client calls and long emails with short recorded videos: design reviews, quote walkthroughs, status updates, handovers. The client watches when it suits them and replies in writing. It works when the whole team follows the same few rules about which touchpoints move to video, how videos are named, how long they are, what can be on screen and who sends them.

We’re Nube, a small web studio in Italy, and we built JustRec for the videos we send our own clients. This guide is the playbook, and it works with any screen recorder.

What changes when an agency goes async

A client call with an agency rarely has two people in it. The project manager joins, the designer joins to explain the choices, sometimes a developer joins in case there’s a technical question. Everyone blocks the slot, and half of the call is one person talking while the others wait.

A review video turns that into one person recording a few minutes, once. The client watches when they’re free, can rewatch the part they didn’t get, and can forward it to the person who actually decides. The rest of the team can watch it too, without joining anything.

That doesn’t mean no meetings. It means the meetings you keep are the ones where people need to talk to each other. The complete guide to async video for client communication covers the general principles; this article is about running it as an agency.

Which client touchpoints move to video

Go through a typical project and sort each touchpoint. A rule of thumb: if information mostly flows one way, it’s a video; if the client needs to react in the moment, it’s a call.

Touchpoint	Format	How
Kickoff	Call	Then a short video recap of what you need from the client
Proposal or quote	Video, then call if they want to negotiate	Walk through the numbers before they open the PDF
Design reviews	Video	What changed, why, one decision at the end
Weekly status	Video or text	Three minutes on the board: done, next, blocked
Bug reports and fixes	Video	Show the bug, then show it fixed
Handover and training	Video	One task per video, so they can find it later
Delays, mistakes, budget issues	Call	Written recap after
Strategy workshops	Call	A pre-read video the day before

If you’re unsure about a specific case, our meeting or video decision guide goes through the edge cases. For the weekly update in detail, see replace the weekly status call with a 3-minute video; for the end of the project, website handover videos.

The four rules to write down

A freelancer can improvise. An agency of five can’t: clients get one video titled “Screen Recording” from the designer and a twelve-minute one from the developer, and the format starts to look careless. Agree these four rules and put them where the team can find them.

1. Naming

Use one pattern for every title, so the client can find a video in their inbox and your team can find it in a library months later:

Client · Project or page · What · Round, for example “Bakery Rossi · Homepage · Review · Round 2”.

Keep it in plain words. The client never needs to see your internal codes. In the client’s inbox, it looks like this:

Hi Laura, here’s round two of the homepage (about 4 min). One question at the end: is the new menu OK to build? A reply in this thread by Thursday is perfect.

https://justrec.app/v/k3f9Qa

Bakery Rossi · Homepage · Review · Round 2JustRec · 3:40

2. Length

Set a default length per type of video and ask people to split anything longer. Suggested defaults:

• Reviews and approvals: two to five minutes, one deliverable per video.
• Status updates: about three minutes.
• Bug reports: under two minutes.
• Handovers: one task per video, as long as the task needs.

If a video needs more than one topic, it’s two videos.

3. Privacy

Every screen recording can show more than you meant to: an inbox, another client’s project, a customer’s name in an admin panel. The GDPR asks that personal data be “limited to what is necessary” (Article 5(1)(c), data minimisation), and the simplest way to follow that in a video is to keep personal data out of the frame.

The screen recording privacy checklist explains each point and what to do when you can’t avoid real data.

4. Who sends

Decide who records and who owns the follow-up, because they’re often not the same person:

• The person who did the work records it. They can explain the choices without notes.
• The project manager is in the thread and chases the answer on the agreed date.
• One thread per client. Videos, questions and approvals in the same email thread or channel.

The written reply is the record

Add one more line to the rules: the video explains, the reply decides. Approvals, scope changes and dates are confirmed in writing in the client thread. That matters even more if your video links expire, and it’s what you’ll look for when someone asks “when did we agree that?”.

How to introduce async video to your clients

Most clients are happy to get fewer calls, but nobody likes a change of process sprung on them. Introduce it on purpose.

1. Kickoff call

   Explain how it will work

   "For reviews and updates we'll send short videos you can watch when it suits you. You reply in the same thread. If anything needs a conversation, we book a call."

2. The day after kickoff

   Start with something easy

   A one-minute welcome video with the next steps and what you need from them. Low stakes, quick to watch.

3. Every video after that

   Keep the promise

   Short, clearly titled, one question at the end, every time.

4. Whenever a client asks

   Keep calls available

   Say yes when a client asks for one. The goal is fewer calls, not none.

5. After a few weeks

   Ask how it's working

   "Is the video format working for you?" Some clients will want more text, some more calls. Adapt per client.

For the closing question in review videos, see how to get client approval faster with video.

Measuring it without viewer analytics

You don’t need to know who watched which video for how long to see whether async video is working. Measure what your agency already records, on a few projects before and after:

What to compare	Where to find it
Client calls booked per project per month	Your calendar
Review rounds per deliverable	Your project tool or the client thread
Working days from sending a review to approval	The dates in the client thread
“Can we jump on a call to explain?” requests	The client thread
Hours of team time in client calls	Your time tracking

Compare a few projects of a similar size, before and after you switch.

Treat it as a sanity check, not a study: projects differ, and a handful of them won’t give you hard numbers. If calls and review rounds go down and clients don’t complain, it’s working. If a client keeps asking for calls, switch format for that client. The reply itself tells you the video was watched.

What the tool needs to do

For agency work, the recorder matters less than the routine, but a few things make the routine easier: a link ready the moment you stop recording, clients who can watch without creating an account, subtitles for watching on mute, and links that don’t stay online forever.

The details are on our page for agencies. JustRec isn’t released yet: join the waitlist to get one email at launch with the early-bird price.

Start with a one-page policy

You don’t need a handbook. A single page with the touchpoint table, the four rules and the kickoff sentence is enough for a team of two to fifteen. We’ve written one you can copy and adapt: the async communication policy template for agencies.

Try it on one project first, with one client you know well. If it works there, it becomes the way you work.