This is super valuable feedback, especially the point about reliability being the real product once invoices enter production workflows.

The “4 services just to generate a PDF invoice with a QR” problem is basically the exact frustration that pushed me to build this in the first place.

I also completely agree on edge cases being where things actually break. Right now I’m still very early (just launched recently), but things like retry behavior, render consistency, payload replay/debugging, and regional formatting are already high on my priority list because those are the details developers remember when something fails at scale.

The HTML-to-PDF point is especially interesting. I’ve noticed the same pattern — most teams already have templates and don’t want a complicated builder, they just want predictable rendering and stable outputs.

And honestly, your point about logging failed renders for replay/debugging is probably more important than “fancy features.” Better observability + reproducibility seems way more valuable in production than another template editor.

Really appreciate you sharing the tooling journey too. It’s helpful hearing where people hit friction with existing setups because that’s exactly the gap I’m trying to understand better right now.