1
0 Comments

I got frustrated with Zapier handoffs, so I built this

A few weeks ago I asked a simple question on r/zapier:

"How do you handle client handoffs?"

Not to promote anything — I genuinely didn’t know what people were doing.

Most answers were:

  • Loom video
  • Google Doc
  • or just… hope nothing breaks

That matched my experience exactly.

You finish a project, send a walkthrough, everything works.

Then a few weeks later something breaks — and nobody remembers how it works anymore. Including me.

You end up reverse-engineering your own Zaps thinking:
"why did I build it like this?" 😅

So I started building something for myself.

You export your Zapier account (ZIP), drop it in, and it generates a structured report:

  • what each Zap does
  • dependencies
  • where it can break
  • basic troubleshooting paths

Runs locally in the browser (Rust/WASM), no uploads.

I’m calling it Relay Reports.

Right now I’m just trying to see if this is actually useful outside my own use case.

If you’ve done client automation work — would something like this help, or do Loom/docs work fine for you long-term?

on March 19, 2026