A copy for each customer
Each customer gets a separate copy that then takes on a life of its own. An improvement for customer A never reaches customer B, and no one knows which version is running where.
Build templates and reusable workflows
About this source
Gen8
Source: Build templates and reusable workflows
Managed AI service for SMEs. We set up, connect and manage; you stay in control.
© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft
Builders · templates
Build it well once, use it again
Do you work for several teams or customers? Build a workflow as a template: reuse its structure, while data and access stay with the organisation where they belong.
- Starts with a conversation
- No customer data in the structure
- A separate environment for each organisation
What can be carried over
What you reuse and what stays put
You reuse the structure:
- The steps: which signal starts it, what is read, what is proposed, who approves
- The instruction, including rules for uncertain cases
- The tools and control level for each step
- The list of exceptions from earlier implementations
What stays with each organisation:
- System access: each organisation connects its own systems, visibly and revocably
- The data itself and everything derived from it
- Examples and names belonging to one customer
On the platform
Templates on Gen8
On Gen8, an organisation builds templates: the instructions, tools and model settings together. Users run a template as a session in their own environment, with integrations configured per organisation.
We agree how to transfer a design to another organisation during guidance, case by case. The detailed considerations are in reusable AI workflows without customer data, and the steps from demo to customer process in from AI demo to customer process.