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?

posted to Icon for group Feedback
Feedback
on March 19, 2026
Trending on Indie Hackers
7 years in agency, 200+ B2B campaigns, now building Outbound Glow User Avatar 105 comments How I built an AI workflow with preview, approval, and monitoring User Avatar 53 comments The "Book a Demo" Button Was Killing My Pipeline. Here's What I Replaced It With. User Avatar 45 comments I built a desktop app to move files between cloud providers without subscriptions or CLI User Avatar 26 comments Show IH: I built an AI agent that helps founders find the right people User Avatar 24 comments My AI bill was bleeding me dry, so I built a "Smart Meter" for LLMs User Avatar 20 comments