Built an AI tool that skips screen-recording for SOP docs — curious if this solves a real pain point

by

Hey Product Hunt 👋

I've been building solo since April, and wanted to get this community's take before I go further.

The problem: every SOP/process documentation tool I looked at (Scribe, Tango, etc.) makes you re-record your screen to capture a workflow — even if you've already explained that exact process to a teammate in Slack an hour ago.

So I built something that skips that step: paste in the messy text (a Slack thread, a rambling explanation, whatever), and it generates a clean, structured SOP — steps, owners, time estimates, all of it. You can edit, save, and export to Word from there.

I'm not 100% sure this is a real enough pain point to build a business around, so genuinely curious:

- Does your team actually struggle with SOP/process docs, or is this a non-issue for most?

- If you use Scribe/Tango/similar tools, what do you like/dislike about the screen-recording approach?

- Would "paste text → get SOP" actually save you time, or am I solving the wrong problem?

Link if you want to poke at it:

Would love to hear real experiences, even if the answer is "nobody cares about this." 🙏

10 views

Add a comment

Replies

Be the first to comment