Import templates, approve content, publish online.
Typical tasks.
- Import existing PDFs, Word files or scans as online applications
- Review sensitive fields for visibility before publication
- Control workflows, branding and notification text per form
- Map organisational units with their own forms and ownership
- Budget AI usage and trace it in the audit log
From template to form draft
Upload a PDF, detect its structure, review the draft in the editor. The department remains responsible and publishes only after approval.
Schema editor with plain-language corrections
Adjust fields, set validations, configure dependencies. Changes can be made in the editor or by chat.
Organisational structure, permissions and ownership
Ownership, routing and permissions follow the organisational chart of the administration, not the software architecture.
AI usage and audit
Cost caps per tenant, audit log of AI usage and breakdown by context. That keeps AI governable.
Demo, PoC and proposal
First, we clarify the use case in a demo. If we agree that a PoC makes sense for your organisation, we define which materials are needed. After that, we provide transparent pricing based on tenant size, channels and operating model.
Departments start with existing templates and review the draft before publication.
Data-protection-relevant fields become visible during authoring, not after go-live.
Also of interest
Request a demo around a real use case.
In the meeting, we clarify together whether a PoC makes sense for your organisation and which materials would be needed.
Request a demo