DocumindsLetter text and components
You write the letter on the paper it will be printed on. Fields come from your data. A fixed paragraph (a salutation, a payment instruction, an objection clause) is a component: the letter names it and does not copy it.
When a new version is approved, every letter that names it prints that version. Studio tells you beforehand how many templates that touches.
House style, header and footer
One brand and one set of text styles per company. Letterhead in millimetres: first page, continuation, last. Studio shows per page which paper it gets, and a one-page letter never says "continued".
Approval
A change travels as one bundle along the route you draw yourself: phases, people, order. An approver needs no account; they get a one-time link, see what changed and judge once.
The new version exists only when the last phase has approved. A rejection always has a reason.
Proof letters
Test a letter with ordinary data, with edge cases, with an empty column. Studio tells you what stands out before a recipient sees it.
Automation and API
A flow fetches the data, makes the letters and sends them: on a schedule, by hand, or from your own system through the API. The same reference twice is one run; nothing leaves the building twice.
Every run writes down what happened, including what failed and why.
202 · reference DEB-20931 is queued
Four environments
Development, Test, Acceptance, Production. A version moves up one environment when it is ready. In Development and Test all post goes to one test mailbox.
See it with your own letter.
We reply within one working day.