2
1 Comment

Built an OpenXML engine that turns raw AI prompts into styled executive .docx files (Live Alpha)

Hey Indie Hackers,

Like many of you, I generate long-form reports, proposals, and briefs using AI (ChatGPT, Claude, Qwen).

The text quality is great, but the moment you copy-paste raw text into Microsoft Word, everything breaks:

  • Table borders collapse or vanish.
  • Headings lose hierarchy and default to plain text.
  • Bullet indents mess up page margins.
  • You spend 30–45 minutes adjusting typography, line spacing, and layouts manually.

I wanted something like Gamma, but specifically for native, editable Word documents (.docx)—without the flashy slide colors, focused purely on clean, executive-ready typography.

So, I spent the last few weeks wrestling with Word’s OpenXML (document.xml, styles.xml, and style inheritance chains) to build DocReplacer.


How It Works Right Now:

  1. You enter a prompt .
  2. You select a professional executive visual theme.
  3. The engine parses the structure and outputs a fully styled, editable .docx file in 1 click.

The Honest Catch (Alpha Status):

It's running on a live v0.8 Alpha engine. It currently accepts prompt inputs and runs at about ~80% formatting accuracy—complex multi-column tables or nested structures can still cause minor layout quirks while I fine-tune edge cases.

You can test your prompt directly on the interactive demo without signing up:
👉 docreplacer.online


What I’d Love Feedback On:

  1. Try entering one of your common document prompts in the generator. What formatting broke or looked weird in the rendered preview?
  2. For those who send proposals or reports to clients: Is having an editable .docx output better for your workflow than a flat PDF?

Roast the UI, test the engine, and drop your feedback in the comments!

on August 2, 2026
  1. 1

    The editable .docx angle feels like the more important bet here than the formatting engine itself.

    Have you seen people actually abandoning or working around existing AI document tools because they need to keep editing in Word, or did that mostly come from your own workflow so far?