solutions
The same engine. Your paperwork.
Mezdoc was built for insurance first, because insurance has the hardest packets. Everything that survives an ACORD renewal handles a loan file or an onboarding pack without breaking a sweat.
You are in the right place if:
- One submission has to become several documents.
- A page belongs in the packet only when the answers say so.
- The same name is typed into four forms today.
- Months later, someone needs to show what was signed, when, and on which version.
Where we started: insurance.
Insurance, MGAs and wholesale brokers
ACORD packets, quote letters, binders and certificates, with the endorsement that joins only when there is an additional insured and the notice that joins only in the right state.
- ACORD 25
- ACORD 125
- ACORD 140
- Quote letters
- Binders
- Surplus lines notices
Homeowners and flood
Declaration packets assembled by rule: the state notices for that address, the flood forms for that zone, and nothing else. Try the live packet.
- Declarations
- HO 04 95
- NFIP forms
- State notices
Insurance document generation API
For teams whose documents are template files today. The core platform keeps the policy data and POSTs it; the packet comes back assembled, versioned and signed, and compliance can reword a notice without a deploy.
- Liquid and Velocity mapping
- Versioned templates
- Staging and production
- REST API
Beyond insurance.
- Lending and fintechNotes, loan agreements, ACH authorizations and addenda from one application.
- HR and payrollOffer letters and the whole onboarding pack behind one link, plus W-2 and 1099 copies.
- Healthcare operationsCredentialing, enrollment, vendor and staff paperwork. Never patient records.
- LogisticsRate confirmations, bills of lading, delivery receipts and invoices from the load.
- Tax and legalEngagement letters with clauses chosen by condition, and 1099s and W-9s in bulk.
Different paperwork, identical machinery.
Whatever the industry, the moving parts are the same three, which is why a new document type is a template and a few rules, not a project.
- 01
One set of answers
Collected once, by your customer or your code. Every document in the packet draws from the same values, so nothing drifts between pages.
- 02
Rules, not people
A rule decides whether the rider, the disclosure or the state notice belongs. Your team writes the rules; Mezdoc applies them the same way every time.
- 03
A record attached
Every PDF keeps its submission record: the template version that made it, the time, the signature details captured and a SHA-256 you can check later.
Not sure your paperwork fits?
Free plan, no card