Use cases

Documents that carry real business.

Pagr came out of client work, not a pitch deck. These are the shapes of document it was built for — and the ready-made templates to start from if yours looks like one of them.

In production

A wealth overview for every client, owned by the broker.

DORI is the platform Belgian insurance brokers manage their offices on — client records, contracts, compliance and the client portal in one place. Metanous developed it, and still maintains it.

The platform delivers many kinds of documents, including the vermogensoverzicht: a wealth overview of everything a client holds. It is different for every client. A different number of contracts, different products, different totals, and legal wording that only applies to some of them. It is not a form with the name swapped out — the shape of the document follows the data.

And the people who own that document are brokers, not developers. When a regulator changes the required wording, or an office wants its own branding on the overview, that cannot be a release. So DORI needed two things at the same time: PDFs rendered on demand from each client's own data, and a template a non-developer could actually change.

That combination is one of the reasons Pagr exists at all. It was the engine behind documents like this one long before it was a product.

Why we built Pagr →

What this document has to do

✓Tables that grow with the number of contracts a client holds

✓Charts and totals computed per client, not baked into the template

✓Legal paragraphs that appear only when they apply

✓Each office's own branding on the same overview

✓Generated on demand from the platform, and identical every time

vermogensoverzicht — cover

vermogensoverzicht — one product in detail

Two pages of a vermogensoverzicht, rendered by Pagr. The names and amounts are sample data; the layout, the per-client value chart and the tax rows that only appear when they apply are the real template.

More use cases

The same problem, in four other industries.

Different documents, same two requirements: the layout has to follow the data, and the person who owns the wording has to be able to change it.

Regulated compliance

Certificates a regulator will read

A fixed legal layout filled with data that varies per building — a score on a scale, a photo of the façade, remarks that apply to some properties and not others. The wording is prescribed, so the template has to be exact, and it changes when the rules do.

✓Conditional fields: remarks and exemptions render only when present

✓Photos by URL; barcodes generated from the value in your JSON, not sent as images

✓A template version pinned per call, so a reissued certificate matches the original

Volume

Invoices at the speed transactions close

Billing is where volume shows up first: an invoice per transaction, a credit note per refund, and a statement per customer per month — all of them at once, on the first of the month.

✓One synchronous call in the request path, or a queued job with a signed webhook for the monthly run

✓Per-document status, so one malformed record does not take the batch down

✓Finance changes the VAT wording or a footer without a deploy

People operations

Contracts HR can change themselves

Employment contracts, addenda and payslips come out of the HR system, but the wording belongs to HR and legal. Every clause that varies by country, contract type or seniority is a condition in the template, not a branch in someone's code.

✓Clauses that switch on country, contract type or role

✓One template covering every language you employ in

✓Legal edits the paragraph in the editor; nothing ships

High volume, printed

Paper that has to come out identical

Delivery notes, labels, waybills and work orders get printed, scanned and filed. They have to fit a physical format exactly, carry a code a scanner will read, and look the same on the ten-thousandth document as on the first.

✓Fixed formats and label sizes, with pagination you control

✓Barcodes and QR codes generated from the data in the render call

✓Stream the PDF straight through to a print queue with nothing persisted

Example templates

Start from one of ours.

Ready-made Pagr templates for the documents teams generate most. Download a real example below, or upload the PDF you send today and start from that instead.