A question tree that your employee or customer clicks through, and at the end a correct contract, policy or report rolls out, with the right clauses, the right prices and the right legal text. For law firms, accountancy, insurers, HR, banks and healthcare.
Anyone who has ever pieced together a mortgage quote or rental agreement by hand knows the problem. Ten variants of the same clause. The wrong version of the general terms and conditions. A VAT rate that differs per situation. A name that didn't make it onto page three. A document configurator catches this structurally by explicitly modelling all choices and variations in a question tree, and having the output generated by a template engine that makes no substitution errors. The customer or employee answers questions, and the system generates the correct PDF or Word document with the right text variants, prices and legal clauses.
We build these configurators to order for organisations that can't get by with standard packages such as HotDocs, PandaDoc, DocuSign CLM or Conga. Often because the industry-specific clauses, the integrations with CRM and accounting, or the white-labelling for partners need to run so deep that a commodity tool falls short. The result: documents that are legally sound, legally up to date, and produced in seconds instead of hours. Also read about document workflow automation for the part that comes after generation: review, approval and archiving.
A good configurator always consists of three layers that work together. A question-tree engine that asks the right questions at the right time, with conditional logic (if the answer is A, also ask questions B and C). A template engine that can render Word or PDF templates with placeholders, conditional blocks and repeating sections. And a clause library in which your legal or tax team manages, versions and approves the legal wording centrally — separate from the templates themselves, so a change to one clause automatically carries through everywhere.
Depending on who uses the configurator — your own employee, your customer via a portal, or multiple partners under a white label — we choose a different set-up. We'll advise which one fits in our first conversation.
The legal, tax or HR department answers questions in a wizard and receives a correct Word or PDF document from a validated set of templates. Suitable for lawyers generating standard contracts, HR teams drawing up employment contracts, or accountants producing parts of annual accounts.
Your customers work through the question tree themselves and get a document back straight away — optionally signed immediately via DocuSign, Signhost or Itsme. Suitable for insurers (policy applications), banks (credit quotes), estate agents (tenancy agreements) or B2B SaaS companies offering tailored master service agreements per customer.
A document platform that you offer to your customers — think of an accountancy firm that lets its SME clients generate documents themselves, or a law firm that connects partners under its own brand. Multi-tenant architecture, per-customer branding, separate clause libraries, and deep integrations with accounting and CRM systems.
A production-ready document configurator, plus everything around it so you can manage and extend it yourself without needing us every time.
Standard packages such as HotDocs, PandaDoc, Conga, Contractbook and Templafy cover many basic scenarios perfectly well. Custom pays off when one of these patterns sounds familiar — otherwise we'll advise you to open an off-the-shelf tool.
Deeds, mortgage agreements, articles of association or administrative decisions require sector-specific clauses and formal legal requirements that generic CLM tools do not support.
The configurator has to pull data from your CRM, accounting system and a DMS, and write the result back with an e-signature status. That kind of orchestration is not part of an off-the-shelf package.
An accountancy or advisory firm wants to offer its clients a configurator under its own brand. Multi-tenancy with per-client branding and separate clause sets is not a standard feature.
When documents must comply with VAT provisions, GDPR clauses or sector rules (DORA, NEN 7510), and you want an AI check step to catch defects, a custom solution is the right route.
Document configuration applies to every sector where the output is a standardised, legally sound or regulated document. Below are the patterns we come across most often — your industry is probably among them.
Tenancy agreements, sales contracts, wills, articles of association and deeds of incorporation. The client or employee works through an interview flow, and the configurator drafts the right document with the right clauses — including references to legislation and general terms and conditions.
Standard sections of annual accounts, compilation reports, VAT return explanations or tax reports. With an AI check step that flags when the VAT determination does not match — a common error in borderline cases.
Policy terms that vary by cover, customer segment or risk profile. Follow-up claims correspondence that is ready within seconds in your house style and the right legal framework — often linked to your claims or policy administration.
Employment agreements, NDAs, dismissal letters, appraisal forms. Often with multi-collective-agreement logic: depending on the collective labour agreement, different provisions end up in the document. Integration with your HRIS (AFAS, Visma, Personio) for automatically populated master data.
Credit agreements, mortgage quotes, master agreements. Often with deep BKR (credit registration) and source-file integrations, strict compliance validations and direct integration with digital signing (DocuSign, Validsign).
Tenancy agreements (residential, commercial, ROZ models), estate agency agreements, purchase deeds. The variables are generally easy to model in a question tree, and it saves estate agencies hours of manual work per file.
Treatment plans, treatment agreements, discharge and referral letters. Linked to the EHR for validated patient data, and with GDPR-aware storage of the generated document.
Diploma extracts, learning agreements, certificates. For government clients: decisions, administrative orders and permit documentation with the required legal structure and archiving rules.
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →We choose tools based on your existing landscape — no one-size-fits-all stack. We do have a few firm favourites that scale well in practice and need little maintenance.
For Word output we use docxtpl (Python + Jinja) or the Open XML SDK in .NET. For PDF rendering we usually use WeasyPrint, Puppeteer or Playwright — depending on the complexity of the layout. Specialty: pandoc and LaTeX for scientific or heavily formatted documents.
For mid-sized question trees, we build a custom engine with JSON schemas and a React front end. For heavy compliance flows (banks, insurers), we use Camunda DMN or a comparable rules engine, which makes the logic auditable and versions traceable. For lighter cases, n8n also works as a low-code orchestrator.
We integrate e-signature as standard via DocuSign, Adobe Sign, Signhost or Validsign. For stronger authentication, we use Itsme, iDIN or eHerkenning. We build GDPR and sector-specific compliance (DORA, NEN 7510) into the audit trail and the hosting strategy, preferably on an EU-only cloud.
Together we map out which documents you currently produce, which variants exist and where the pain points are. We often find that the number of genuinely distinct template variants is smaller than it feels, which is an important insight for scoping.
A workshop with your legal, tax or HR team to model the decision logic. Which questions lead to which clauses? What are the conditional blocks? We map out the decision tree and validate the logic against sample documents.
A working build every sprint: first the question tree engine, then the template engine, then the integrations. Your key users test along and flag edge cases early. The MVP is ready after a number of sprints for one document type, and we then scale out type by type.
Existing templates are migrated to the new platform, key users receive hands-on training, and we roll out in phases, often starting with one department or one customer group before going wider.
A document configurator is never "finished": laws change, new document types are added and the question tree has to evolve. We offer an ongoing maintenance contract or a fixed-capacity model for further development.
What clients usually want to know before we start.
A no-obligation introductory call of half an hour. We listen to which documents you currently produce, where the pain points are, and where a configurator would genuinely help versus where your current approach works perfectly well. If relevant, combine it with a conversation about a product configurator or smart API integrations.
Appfront uses cookies and similar technologies to make the website work properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
