Case Study - Collab Video: Removing friction from asynchronous video collaboration
Collab Video starts with a simple podcast problem: good conversations are hard to schedule. A host records a question, shares a link, and a speaker answers in their own time. Those responses become a conversation that can be shaped into a finished show.
I turned a niche we uncovered at Zync into an independent product: hosts record questions, speakers answer when they have time, and the conversation becomes an asynchronous podcast without the calendar chase.
- Client
- Collab Video
- Year
- January 2026 – Present
- Service
- Full-stack product engineering
Overview
I took Collab Video from a successful Zync spinoff into an independent product built around asynchronous podcasts.
Hosts record a question, share a link, and let speakers respond when they have time—without asking everyone to find the same hour.
The product turns those answers into a conversation that can become a polished short-form clip.
What I did
I led full-stack product engineering for Collab Video across the prompt, guest-response, and publishable-clip workflow.
I worked on the product that made an asynchronous podcast feel simple: one question, one link, and a thoughtful answer later.
- React
- Next.js
- Redux
- TypeScript
- Node.js
- GraphQL
- Python
- Remotion
- FFmpeg
- OpenCV
- GCP
- Azure
- Docker
- Kubernetes
- AKS
- GKE
- Azure Service Bus
- WebSockets
- Daily.js
- Stripe
- Product areas led
- 5
- Active users supported
- 1,000+
- Cloud compute cost reduction
- 90%
- P0 MTTR
- 30 min
Project snapshot
- Role and ownership
- I took a successful Zync spinoff into an independent asynchronous-podcast product.
- Product surface
- Hosts record questions, speakers answer in their own time, and responses become publishable short-form clips.
The problem
Useful video collaboration often starts with calendar coordination, guest onboarding, long recording sessions, and a separate editing process. The current public Collab Video product presents a narrower path: ask one focused question, collect responses asynchronously, and prepare a short clip for publishing.
The present-day UX question is whether that reduced-friction promise remains legible at every step for the prompt owner, the account-free guest, and the final output. This is product analysis, not a claim about measured user benefit.
Implementation - Implementation and product highlights
- Full-stack workflow leadership. I led full-stack product engineering across the prompt, guest-response, and publishable-clip workflow.
- Prompt creation and sharing. The public experience makes a recorded prompt the organizing object: an owner records a question once and shares one link.
- From guest response to clip. The public collaborator flow lets guests record or re-record a response without account setup. The public product connects that response to a polished short-form clip.
