From your system.In your house style. Every day.
Certificates, quotes, work orders or reports you now fill in by hand in Word or InDesign. We connect them to the system where the data already lives and let them appear by themselves every day, in your house style. With a check against the source, so you know nobody is missing.
It ran at our place first.
A training company made every certificate of attendance by hand in InDesign. Now a flow reads attendance from their planning system every day (read only, nothing is written back), fills a template that looks exactly like their own certificate, and prepares the PDF. When checked against the source, the first version turned out to skip three quarters of the participants, because of one way of writing surnames. After the fix: 35 expected, 35 made.
Does this sound familiar?
- 01The data is already in your planning tool or CRM, yet the document is retyped anyway.
- 02Every document is a copy of the previous one, and an old name or date slips through now and then.
- 03You are not sure everyone received their document.
- 04Introducing a new system is not an option, the current one works fine.
What you get.
- A template that looks exactly like your current document
- A daily connection to your existing system that only reads data: nothing in your system is changed
- A check against the source: expected and made must be equal
- No duplicates, even when the flow runs again
- A draft email with the document attached, sending is up to you
Operating it yourself says more than a description.
Create the certificates for a fictional group of participants, first with the first version and then after the check. Watch the counter: expected and made must be equal. This is a demo on sample data, not client work.
Demo · prepared in advance · illustrative · no live model
Planning system (read only)
| Surname, first name | Attended |
|---|---|
| Berg, van den, Jeroen | 2 of 2 days |
| Yilmaz, Fatima | 2 of 2 days |
| Jansen, Lars | 2 of 2 days |
| Vries, de, Esther | 2 of 2 days |
| Haddad, Mohamed | 2 of 2 days |
| Bakker, Inge | 2 of 2 days |
| Smit, Tim | 1 of 2 days |
| Wit, de, Noor | 2 of 2 days |
| Mulder, Pieter | 2 of 2 days |
| Kok, Sofie | 2 of 2 days |
The planning system is only read. Nothing is written back.
Illustrative demonstration with examples prepared in advance. No live AI call and no API key needed; the answers are fixed and contain no invented figures or names.
Four steps, in this order.
We sit in
We put your current document next to the data in your system and trace where every field comes from.
We build alongside
The connection only reads from your system and writes nothing into it. If you stop, nothing in your system has changed.
You keep the last step
Whatever the system produces is first ready as a draft. Only when you give the go-ahead does anything leave the building.
We connect only once it works
Once it proves right in practice, and only then, we connect it to your systems for good.
Lead time: one to three weeks for a working first version.
n8n · Gotenberg · HTML templates · REST/Webhooks · Python
What people ask us about this.
Q1Is anything changed in my system?
No. The connection only reads data. Nothing is written back and nothing in your system needs to be adjusted.
Q2Will the document still look like ours?
Yes. We rebuild the template until it cannot be told apart from your current document: typeface, logo, layout and wording.
Q3How do I know nobody is missing?
On every run the system counts how many documents should have been made and how many were made. If they differ, you hear about it straight away, with the names. That count found an error at the training company that nobody would otherwise have seen.
Q4Does this work for quotes too?
Yes. The pattern is the same: data from your system, a template in your house style, a check against the source. For quotes your own rates and terms go in, and you approve every draft before it is sent.