2
2 Comments

I sold my agency partly because of Fridays. So I built the thing that would've saved them.

Every Friday at my agency was the same ritual: record a Loom for each client showing what we shipped that week.

Six clients. Twenty minutes each, because I'd fumble a sentence halfway through and start over, or staging would break mid-recording and I'd wait for a redeploy. Half a day, every week, for years.

I tried killing it twice. Written updates got skimmed. Staging links got ignored harder — clients don't want to log into something and click around hunting for what changed. The video was the only format they actually watched, and it was also the most expensive thing I made all week.

So I built PushPlay. When a PR merges it reads the diff, rebuilds the changed screens from your actual React components, writes a script, voices it, and renders a 1080p MP4. Four to six minutes end to end.

The deliberate choice was to render rather than capture. No headless browser driving a staging environment, no screen recording. It parses the component tree, maps Tailwind classes to computed styles, and re-renders the UI as motion graphics with real props. Which means it works on repos that aren't deployed anywhere, and it never breaks because staging is down.

Where it falls down, honestly: component extraction only works properly for React, Next.js and Remix. Vue, Svelte and Angular get a narrated announcement with animated typography instead of rendered UI. Heavily dynamic or canvas-based UI doesn't render well either.

You can judge the output without signing up — the showcase is generated from public repos (shadcn/ui, cal.com, Supabase, Tailwind) through the same pipeline with nothing hand-edited: https://www.pushplay.dev/showcase

Three things I got wrong while selling this to agencies:

  1. "Saves you time" landed badly. Agency owners don't buy time back, they buy things that make them look good to a client. "Your client sees what they paid for" converts. "Get your Friday back" doesn't.

  2. Everyone asked about repo access before they asked about the video. Read-only had to become the first line on the page, not a reassurance three scrolls down.

  3. Requiring a card for the free trial killed signups dead. Four credits, no card, and people actually try it.

Question for the agency and freelancer folks here: how do you handle the weekly client update right now? And has anyone found a written format that clients actually read?

on September 18, 2026
  1. 1

    The written format that got read for us was written for the client's boss, not the client. Three lines in the body of an email, no attachment and no link to click: what changed for your users, what it does to your numbers, and the one decision we need from you by Wednesday. Clients skim a shipped list because it is your work log, but they read anything that helps them defend the invoice to the person above them, which is also a sharper version of your own pitch: not "your client sees what they paid for" but "your client can forward this to their CFO."

    1. 1

      Thanks for sharing this. It is a good insight indeed, create an update video that your boss want to share with his own boss..