We deliberately guide a limited number of customers at once.
Gen8 — AI automation as a managed service
About this source
Gen8
Source: Gen8 — AI automation as a managed service
Managed AI service for SMEs. We set up, connect and manage; you stay in control.
© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft
Managed AI automation for SMEs
AI that does your work. With people at the wheel.
We automate recurring work in sales, finance and operations as a managed service. We configure workflows, connect them to your systems and manage them afterwards. You approve where it matters.
- Scoping first, then a proposal
- Human approval
- Processing in the EU
- A log of every step
New request in the shared inbox
Invoice in the shared inbox
By SMEs, for SMEs
We know your priorities because we are one too.
Gen8 is an SME too. We know revenue, customers and a small team come before new tools. That is why we work only for organisations with a working business model that want to scale while keeping their team small.
To safeguard quality, we start a limited number of customers at once. Currently 5 of the 8 places are filled: there is room to start 3 new customers in the next three months.
Room to start in the next three months.
The problem
Your team loses too much time to recurring manual work.
Not the decisions, but the quiet work that comes back every day and that no one misses when it is gone.
- Sales: retyping requests into the CRM and researching leads before someone can call
- Inbox: sorting and forwarding email and answering the same questions repeatedly
- Finance: extracting invoices and documents and recording them in the right place
- Operations: compiling reports and retyping data between systems
A chatbot vs. a Gen8 workflow
A chatbot
Gives an answer and waits for your next question. Work such as updating the CRM, recording the invoice or compiling the report stays with you.
A Gen8 workflow
Picks up the signal, assesses it against your rules and knowledge, and delivers a concrete proposal in the system where work happens. You approve; the workflow executes and records what happened. We keep it running.
In practice
What workflows do in practice.
Examples from SMEs, from sales to finance. Every workflow works in the systems you already use and records what it did.
Register requests and leads
A request by form, email or phone becomes a lead in your CRM, enriched and assessed against your criteria. No one needs to retype it.
Prepare and process customer conversations
A short brief before the conversation; notes, agreements and a draft follow-up in your CRM afterwards. You read and send.
Sort the shared inbox
Incoming email is recognised, routed to the right colleague and given a draft reply with source references.
Process invoices and documents
Invoices, orders and contracts are read and recorded in the right place. Exceptions go to a person for review.
Compile reports
Fixed questions from fixed sources, at a fixed cadence. Differences and assumptions are included rather than calculated away.
Turn meetings into actions
After a meeting, decisions and action items are ready, with owners and dates, in the system your team uses.
The same work returns every day in sales: registering requests, enriching and qualifying leads, preparing and processing conversations, preparing follow-up. That makes sales a good first step in many cases.
A separate page explains what a workflow does for your sales team, which organisations it suits and what the process looks like.
Every workflow follows the same pattern, whether it involves a new lead, a shared inbox question or an incoming invoice. The two examples at the top of this page work exactly this way.
We define what a workflow may read and propose in each system for each integration. Sending and final writing remain human decisions.
Signal
An email arrives, a conversation ends, an invoice lands in a folder.
Assess
The workflow classifies, retrieves context and checks against your rules and knowledge.
Proposal
A draft, task or update in your CRM or administration, with source references and a visible change.
Approval and execution
A person approves where needed; the workflow then executes and records it.
↻ every step is logged
What we do
Workflows that fit the processes you already have.
We fit the process as it runs today, including exceptions, rather than making your organisation fit a package. Processes change: we ensure AI grows with them and safeguard quality, so you do not have to worry about it.
Workflows that carry out work
A signal is assessed and turned into a proposal in your email, CRM or project system, with you as the final reviewer where consequences are significant.
Integrations with your systems
CRM, ERP, finance, telephony, email and documents. For each system, see what the integration can do, the permissions involved and the route it uses.
View the integrationsMake knowledge accessible with permissions intact
Make your documents and knowledge sources searchable, with a workflow seeing only what the user may see.
Reporting and monitoring
Fixed questions, fixed sources, a fixed cadence. Differences and assumptions are made visible instead of calculated away.
Scoping and first use cases
We map your goals and explain where a workflow saves time and where it does not. With a go/no-go decision at each phase.
View the approachManagement and ongoing development
We monitor, maintain and adjust when your processes or systems change. We agree resource ownership, access and a workable exit upfront.
Our approach
From scoping to management: we take the work off your hands.
Four phases, each with a clear result and a go/no-go decision. If something does not work, we adjust or stop: that is an outcome, not a failure.
Phase 01
Scoping
In around three days, we map and prioritise your goals: which processes deliver the most value and where to begin.
Phase 02
Onboarding
We connect your systems (CRM, ERP, finance, telephony, email), record your organisation's context and bring the first use cases live.
Phase 03
Management and iteration
We monitor, maintain and adjust. We introduce changes in manageable steps to safeguard quality.
Phase 04
Expansion
Does it work? Then we expand with new integrations, workflows and agents, at a pace that suits your organisation.
Possibilities
Workflows for sales, finance and development, each explaining what happens, where approval sits and where it stops.
Explore the possibilitiesIntegrations
For each system, from Microsoft 365 and your CRM to Google Workspace: what the integration can do, the permissions involved and the route it uses.
View the integrationsOrganisation types
The types of SMEs we work for, their recurring processes and where the boundaries lie.
View organisation typesKnowledge
Decision and design frameworks: what you leave to a model, where people decide and what management requires.
Read the knowledge articlesPricing
What it costs depends on six things.
We operate as a managed service and align price with the value we create together, rather than a package name. Six factors determine the work involved:
- Scope: how many steps and exceptions the workflow handles
- Usage: how often it runs and how much it processes each time
- Review: how much a person needs to assess
- Management: how often your systems and processes change
- Integrations: configuring an existing integration or building a new route
- Ownership and exit: what you want to be able to take over yourself
Do we need to use the platform ourselves?
No. We configure, connect and manage. You decide what happens and approve where it matters. Want to build on the platform yourself? You can, always with us by your side: see Builders under Platform.
What do you automate with AI and what do you leave out?
Work involving many handoffs, context and repetition fits well: following up requests and leads, sorting the shared inbox, processing documents and compiling reports. Decisions with major consequences, and anything better handled by fixed rules, stay with a person or a fixed rule.
Does a workflow write to my CRM or mailbox itself?
Not by default. A workflow makes a proposal with a visible change; a person approves. Read only where possible, automatic only where consequences are minor, and everything is logged. A workflow never sends email itself.
How does an engagement begin?
With an introductory meeting, then scoping: in around three days we map and prioritise your goals. Only then comes a proposal, with a go/no-go decision at each phase.
Which organisations is this suitable for, and which is it not?
Suitable: SMEs with a working business model that want to grow without growing their team, with daily or weekly work in sales, inbox, finance or operations. Sales is often a good first step because requests, conversations and follow-up recur every day. Not suitable: a standalone chatbot disconnected from your processes, or work requiring an individual professional judgment for every case.
Why do you only take on a few customers at once?
Because we handle management ourselves and want to safeguard quality. Currently 5 of the 8 places are filled; we can start 3 new customers in the next three months.
What if it does not work for my process?
We adjust or stop at that phase's go/no-go point. The process assessment can also conclude that your process is not suitable yet, with the reason. We prefer saying that upfront.
Who owns the workflow after delivery?
We agree resource ownership, access and a workable exit upfront. You are not locked into us to keep using the workflow.