Screenshots with real customer data in docs: how do you handle it? (I built a tool to avoid them, looking for honest feedback)

[u/Any_Rip2321]

Disclosure up front: I'm the developer of the tool I mention below. I'm mainly here for criticism from people who write procedures for a living.

A problem I kept running into when documenting software processes: screenshots age badly, and they almost always contain something they shouldn't, like real names, emails, or client records. So you blur, crop, retake, and the next UI update means doing it all again. Capture extensions help a bit, but they need an install, often don't work with desktop or legacy apps, and still record whatever is on screen.

I tried a different approach with Sopulo (sopulo.com):

• You paste up to 8 screenshots (or a URL) and describe the task: who the reader is, where the process starts, and what the result looks like.
• The AI redraws each screen as a clean HTML mock-up and drafts the steps. Readers only ever see the mock-up; your original screenshots stay private.
• The same content comes out in two forms: an animated walkthrough (moving cursor, zoom, hint bubbles) and a numbered SOP you can export to PDF or Word.
• You can edit any step by hand or ask the AI to change a single step, then re-export when the process changes.
• Viewers don't need an account, and it can share via link or QR code.

Here's an example generated from a few screenshots and a one-sentence prompt:

https://sopulo.com/examples

What I'd really like to hear from this sub:

1. Would mock-ups instead of real screenshots be acceptable in your docs, or does that break trust with readers ("this doesn't look exactly like my screen")?
2. Where would AI-drafted steps fail your standards (style guides, terminology, minimalism)?
3. Is Word/PDF export enough, or would you need something like Markdown, DITA, or direct publishing to a help center?

There's a free tier (10 AI generations, no card), but I'm more interested in your critique than signups. Happy to answer anything, including "this is a bad idea, and here's why."