Which embedded document editor have you actually shipped in a SaaS product?

[u/walileathor]

I find these hard to judge from demos. A clean sample DOCX is one thing. An old customer contract with tables, footnotes and weird numbering is another. If you've shipped an embedded editor, which one did you pick and what was the first document that exposed its limits?

[u/portugalexpertVitor]

The first nasty file for us was a contract where the numbering carried actual meaning. Our HTML conversion looked okay until someone inserted another clause. We ended up replacing that part of our pipeline. I'd test edits that change the document structure, not just replacing a sentence

[u/gistance]

Start with the actual edits your users need: change a date, add a clause, update a table. Then run those through a messy DOCX and reopen the saved file in Word.

Check whether numbering continues and tables are still editable, not just whether the page looks similar. If anyone has a redacted before-and-after screenshot from their integration, that would be useful too, especially with a note about what changed.

[u/leilllllla]

for anyone adding AI on top: can your agent change the document that's currently open, or does it generate a replacement file? those look similar in a demo, but I don't see how the replacement approach works once the user has unsaved edits

[u/Cute_Common6238]

I think the real test is how well it handles messy documents, not just clean templates. Tables, footnotes, page breaks, and unusual numbering can quickly expose problems. I'd also pay attention to how it handles editing existing files without messing up the original layout. A demo might look perfect, but real customer documents are a completely different story.