Jonathan Bayo
All case studies
AI systemsClient1 min read

Personalized video generator

A workflow that runs every five minutes, takes the leads with the highest pain score, writes each one a short video script with Claude and has Visla render a presenter video. The sales team opens the lead and the video is already there.

5 mincycle time
45 sper video
0manual steps
Trigger
every 5 minutes
Script
45 seconds
Render check
every 30 s
Manual steps
none

Why it exists

Video gets replies, but recording one per prospect takes hours. So teams either skip it or send one generic video to everyone, which defeats the point.

How it runs

Pipeline
Trigger
Schedule
every 5 minutes
Fetch
Supabase
high priority leads, no video yet
AI
Claude
45 second script
Fetch
Visla
HMAC signed request
Transform
Poll
until rendered
Store
Save URL
back on the lead
  1. Pick the leads

    Every five minutes the workflow pulls leads from Supabase that are marked high priority and don't have a video yet. Each one carries company context, pain signals and contact details.

  2. Write the script

    Claude writes a 45 second script that refers to the lead's specific pain point and keeps the tone conversational.

  3. Sign the request

    Visla wants HMAC signed requests, so the workflow builds the signature fresh before every call.

  4. Render

    Visla generates the presenter video from the script.

  5. Wait

    The workflow polls Visla every 30 seconds until the render is done, so slow renders don't break anything.

  6. Save

    The video URL goes back on the lead record in Supabase for the sales team.

What came out of it

From lead to video link is about five minutes plus render time, with nobody touching it.

Notes

Render time varies a lot, so the polling loop is what makes this reliable. The HMAC step was the fiddly part. The signature has to be rebuilt for every request or Visla rejects it.

Stack

Want something like this built?

Tell me what you're trying to automate. Most things can be built in a week or two.