Contract generator driven from Telegram
A manager sends a quote and company details into a chat — and gets back a finished contract plus a report of exactly what changed in it.
- A contract is assembled from chat in minutes instead of by copying fields by hand
- The master template physically cannot be altered — only a copy is
- Every substituted value is highlighted, and the changes are written up as a separate report
The problem
Contracts were assembled by hand from a master: copy, swap the details, check. One wrong field is expensive — but the real risk is that somebody eventually edits the master itself, and the defect quietly propagates into every contract that follows.
How it works
A script on the documents side first verifies the master's fingerprint and only then makes a native copy into the working folder. Only permitted fields are changed, new values are highlighted, and the list of changes goes out as its own report in its own folder. The chat sources are archived, so it is always visible what a given contract was built from.
The hard part
The decisive choice was fingerprinting the master before every generation. Without it the system works right up to the day somebody tweaks the template 'for a second': from then on it confidently prints wrong contracts, and nobody notices quickly. The check turns a silent failure into a loud one.
Evidence
- The master is not writable by construction: only a copy is edited
- A change report is produced on every generation — what was substituted is visible after the fact
- Source quotes and company details from chat are retained, so generation is reproducible