Every company tracks meeting hours. Almost none of them do anything about it.
The average knowledge worker spends 21.5 hours per week in meetings, according to Microsoft’s Work Trend Index. For a team of 10, that’s 215 hours per week — roughly $112,000 in salary cost per year, assuming a modest $50/hour blended rate. And that’s before accounting for the hours lost to context-switching, the hour after a meeting where you can’t quite get back into flow, or the recurring weekly standups that could be a two-minute video.
Async-first teams using Zight are recovering a meaningful portion of that time. Here’s a breakdown of where the savings come from, what they actually look like in practice, and how to calculate what your team could get back.
The Three Workflows Where Time Goes to Waste
1. Customer Support: The Back-and-Forth Ticket
The average customer support ticket takes 11 minutes to resolve when the interaction is text-only, according to Zendesk’s Customer Experience Trends Report. When the issue requires back-and-forth clarification — which it does roughly 40% of the time — that average climbs to 23 minutes.
The core problem: customers can’t describe what they’re seeing, and support agents can’t show them what to do.
What async video changes:
- Customer clicks a “Request Video” link and records a 30-second clip of the problem happening in real time
- Agent sees exactly what’s wrong without a single follow-up question
- Agent responds with a 45-second annotated screen recording showing the exact fix
What was a 23-minute multi-message exchange becomes a 4-minute async interaction. For a support team handling 40 tickets per day, that’s roughly 12 hours recovered daily — over 3,000 hours annually. At $25/hour (typical support rate), that’s $75,000 in recovered productivity per year for a single 5-person support team.
Real numbers from Zight customers:
One SaaS company using Zight’s Request Video feature for customer support reduced average first-response resolution time by 42% in the first month. A three-person support team recovered an estimated 6 hours per week — time they reinvested in proactive outreach rather than reactive triage.
2. Product Teams: The Feedback Loop That Never Ends
Product managers and designers have a feedback problem: the people giving feedback (PMs, stakeholders, customers) and the people implementing it (engineers, designers) don’t share the same mental model.
“Make the button more prominent” means something different to a PM than it does to a designer. “The onboarding flow feels slow” is unactionable until someone specifies exactly which transition, on which screen, at which point in the sequence.
This ambiguity generates revision cycles. The average design iteration at a startup takes 3 revision rounds, according to InVision’s Design Maturity Report. Each round involves at minimum one meeting, one async message chain, and one round of questions. For a team shipping 8–10 features per quarter, that’s 24–30 revision cycles — each one burning 2–4 hours across the team.
What async video changes:
Instead of a text comment in Figma that says “this doesn’t feel right,” a PM records a 90-second screen capture with voiceover: “The transition here takes 400ms — I’d want it at 200ms, and the copy in this state should probably say ‘saving’ rather than ‘loading.’ Can you also look at the spacing here? It feels cramped on mobile.” The designer sees exactly what they’re looking at, hears the tone, and understands the priority — all in 90 seconds.
That feedback loop that previously required a meeting now happens async, at each person’s own schedule. For a 4-person product team, Zight customers typically report recovering 6–8 hours per week in meeting overhead and revision cycles — about $20,000–$25,000 in annual productivity for a mid-market team.
3. Sales Teams: Demos That Don’t Require a Calendar Invite
The average B2B sales demo takes 32 minutes, requires 4 days of scheduling back-and-forth, and involves at least two stakeholders who had to clear their calendars to attend synchronously.
For an SDR or AE with 20 active prospects, that’s 640 minutes of demos per week — not counting the scheduling coordination that gets each one on the calendar.
What async video changes:
Zight’s async demo workflow works like this: record a personalized 4-minute walkthrough of the prospect’s specific use case, share the link with a CTA to book a call only if they want to go deeper. Prospects watch on their own time, share with other stakeholders who couldn’t attend a live demo, and come to the first call having already seen the product.
The results: shorter sales cycles, higher conversion from demo to close (because the prospect has self-qualified), and fewer wasted 30-minute calls with people who weren’t the right fit.
For a 3-person sales team sending 15 async demos per week, the scheduling time savings alone recover approximately 5 hours per week. Add the time recovered from shorter, more productive live calls, and the total is closer to 8–10 hours per week — $25,000+ in annual productivity at typical AE compensation.
The Compound Effect: It’s Not Just About Time
Time savings are the obvious metric. But async-first workflows create secondary benefits that don’t show up in a time audit:
Fewer interruptions = higher quality work
Context switching — moving from deep work to a meeting and back — costs an average of 23 minutes of lost focus per interruption, according to research from the University of California Irvine. Replacing three synchronous check-ins per day with async video updates eliminates 69 minutes of lost focus time daily per person. For a 10-person team, that’s nearly 12 hours of deep work recovered every day.
Replacing three synchronous check-ins per day with async video updates eliminates 69 minutes of lost focus time daily per person.
Documentation as a byproduct, not an afterthought
Every Zight video automatically becomes a piece of documentation. The product feedback video gets saved to the team library. The customer support resolution gets added to the knowledge base. The sales demo becomes a template for future reps. Unlike a meeting — which evaporates the moment it ends — async video creates institutional memory automatically.
Better decisions from better information
Written descriptions strip out tone, pacing, and context. A 60-second video of a frustrated customer trying to navigate your onboarding flow conveys something that no support ticket can. Product teams that review async customer videos make different prioritization decisions than teams working from text-only feedback summaries. The information quality is categorically different.
How to Calculate Your Team’s Potential Savings
Use this framework to estimate what your team could recover:
Support teams:(Average tickets per day) × (Minutes saved per ticket) × (Working days per year) × (Hourly rate) = Annual savings
Example: 40 tickets/day × 7 min saved × 250 days × $0.42/min = $29,400/year
Product teams:(Features shipped per quarter) × (Revision rounds) × (Hours per round) × 4 quarters × (Blended team rate) = Annual savings
Example: 8 features × 2.5 rounds × 2 hrs × 4 × $75/hr = $12,000/year
Sales teams:(Demos per week) × (Scheduling hours saved) × (Working weeks) × (AE hourly rate) = Annual savings
Example: 15 demos/week × 0.33 hrs saved × 50 weeks × $60/hr = $14,850/year
Combined, a 10-person team with support, product, and sales functions can realistically recover $50,000–$100,000 in annual productivity — while also improving documentation quality, reducing context-switching, and creating a better experience for customers.
Getting Started: What to Change First
You don’t need to overhaul your workflows overnight. The highest-ROI starting point depends on your team’s biggest pain:
If your support team drowns in back-and-forth tickets: Start with Request Video. Add a Zight link to your support signature and encourage agents to respond to complex tickets with a screen recording rather than a text reply.
If your product team runs too many feedback meetings: Make async video the default for design feedback. Ask stakeholders to record their feedback on a Figma prototype rather than attending a review meeting. Review the videos, then hold a single 30-minute sync only if significant decisions need to be made.
If your sales team spends half its time scheduling: Build a library of product walkthrough videos personalized by industry or use case. Send the relevant one before the first call. Use Request Video to collect prospect questions async before the demo.
Each of these changes takes one day to implement and has a measurable impact within the first week.
Joe Martin is Chief Marketing Officer at Zight. He writes about async communication, remote team productivity, and the future of visual collaboration.
