about
We build the paperwork layer insurance teams keep rebuilding.
Mezdoc is a small, founder-led team building document automation for US MGAs, wholesale brokers and program administrators: one template engine, one workflow engine, and a record of every document.
- built for
- Insurance teams in the United States
- built in
- Ahmedabad, India
founder note
Why we are building this.
Document code tends to grow in the same order. A PDF that starts as a one-off render becomes a templating layer, then a workflow, then a signing flow, then an audit log. By the time it is production-grade, a team has spent months rebuilding what a document platform already does.
We are building Mezdoc so the next team does not have to. Fillable PDFs for fixed forms, smart documents for the ones that change shape, and workflows that bundle them into one packet. The condition language is the same in all three places, and so is version pinning.
We picked US insurance as our focus because those teams feel this pain first. ACORD packets, quote letters, binders, certificates and premium finance agreements, rebuilt by hand for every account. That is the paperwork Mezdoc is built for.
from the founder, Mezdoc
What we believe.
- 01
Documents are infrastructure.
A PDF is not an output, it is a flow. Mezdoc treats documents as something you version, test and monitor.
- 02
On the record by default.
Every submission records its template version, the signature details it captured and a SHA-256 of the PDF, so you can check the file has not changed. On every plan, not just Enterprise.
- 03
Insurance first.
We go deep on one industry: the quote, bind and issue paperwork of US MGAs, wholesale brokers and program administrators.
- 04
No coordinate hell.
Drag a rectangle, pick a type, done. If the editor feels like desktop PDF software from 2010, we did something wrong.
- 05
Developer experience is product.
Idempotency keys, signed webhooks, an open Postman collection and a reference that matches the API.
- 06
Honest by default.
We say exactly what Mezdoc does, show it working on your own documents before you commit, and tell you when it is the wrong tool.
How we work with a new team.
Small on purpose: you talk to the people who build the product.
- 01
Send us the form
The one your team dreads: an ACORD form, a binder, a packet with an endorsement that only applies sometimes.
- 02
We build it with you
On a call, we build the first template and its rules with you, on your own document.
- 03
You keep it
It stays in your account on the free plan. Upgrade when the watermark gets in the way.
Documents are the next API surface.
Every business produces documents. Almost none of them treat documents like product. We think the next decade of paperwork runs through a templating layer with versioning, signing and a record built in. Mezdoc is the bet that this layer is worth building once, properly, starting with insurance.