I’m building this, here is the problem I’m exploring, does anyone else have this pain?

I’m building Pritset — an API that generates PDFs from DOCX templates.

The idea came from a problem that looks simple at first:

“We just need to generate a PDF.”

But then the product grows.

You need invoices, reports, contracts, receipts, booking confirmations, certificates, statements, or other customer-facing documents.

At some point, developers start maintaining HTML templates, PDF rendering logic, styling issues, layout bugs, async generation, file storage, retries, and customer-specific document changes.

I’m trying a different approach:

Let teams design documents in Microsoft Word, then generate PDFs from those DOCX templates through an API using JSON data.

The goal is simple:

• developers keep the integration simple

• non-technical people can edit document layouts

• companies do not need to rebuild document generation from scratch

Right now, I’m doing customer discovery and trying to understand where document generation is actually painful.

I’d love to hear from other founders and developers:

Do you generate PDFs in your product?

If yes:

• What do you use today?

• Is template editing painful?

• Who owns document changes — developers or business users?

• Would DOCX-based templates be useful for your workflow?

I also created example integrations for Node.js, .NET, Java, and Python:
https://github.com/daviatorstorm/pritset-examples

Happy to hear honest feedback.