← Dissel AI · Perspectieven

Framework - Agentic AI

How to implement agentic AI for business growth: a framework for SMEs.

A practitioner-led playbook for moving SMEs from one-off chat tools to integrated agentic AI systems that compound. What agentic AI is, why it is different, and the seven steps to ship it into production.

Derk Disselhoff·Founder, Dissel AI·June 2026·11 min leestijd

Most SMEs have now tried AI. A team uses ChatGPT in a browser tab, a marketer drafts copy with Claude, an analyst pastes a spreadsheet into Gemini. The usage is real, but the leverage is not. The work still flows the same way it did a year ago, only with a faster first draft at the start of it. That is not agentic AI. That is autocomplete with better manners.

Agentic AI is the next step. It is the move from a person using a chatbot to a system that decides, acts, and reports back on its own work. For an SME, the prize is concrete: workflows that used to need three people and a week now finish overnight, with humans deciding only the cases that actually need judgement. The hard part is not the model. The hard part is the redesign of the workflow around it.

What is agentic AI

An agent is a piece of software that takes a goal, decides what to do, calls tools, reads and writes data, and loops until the goal is met or it asks for help. The model is the brain. The tools (CRM, inbox, database, browser, payment system) are the hands. The loop is what makes it agentic, rather than a one-shot prompt. A chatbot answers a question. An agent finishes the job.

For an SME, the practical definition is even simpler. Agentic AI is a workflow that used to need a person at every step and now needs a person only at the steps where their judgement actually changes the outcome. Everything else, the agent owns.

Agents on Notion · context in, action out
Always on
READ
CRM · docs · wiki
PLAN
Custom Agent · 20-min runs
ACT
Slack · Gmail · Stripe · API
An agent runs a loop: read the goal, plan a step, call a tool, check the result, decide what is next.

Why agentic AI matters for SMEs specifically

Large enterprises have always had a way to grow output without growing the workflow: hire another team, buy another tool, fund another committee. SMEs do not. Every new workflow lands on the same small group of people who are already running the business. That is exactly why agentic AI compounds harder in an SME than in a corporate. There is no middle layer to absorb the saving, so the throughput shows up directly in the P&L.

Three forces line up at the same time. First, model quality is now good enough to handle messy, real-world business workflows, not just neat demos. Second, the cost per task has collapsed: workflows that were prohibitively expensive in 2024 are routine in 2026. Third, the tools to build agents (orchestration frameworks, vector stores, governed integrations) are mature enough that an SME can ship one in weeks, not quarters.

The seven-step framework

Every successful agentic rollout we have run inside an SME follows the same shape. The order matters. Most teams that get stuck skipped step one or two and started building.

  1. 01Pick one workflow that hurts. Name it. Quantify it. Pick the one that costs the most hours per week or the most revenue per missed case.
  2. 02Map the current workflow on paper. Every step, every hand-off, every approval. Mark which steps need human judgement and which are pure execution.
  3. 03Redesign the workflow assuming the agent is reliable. Cut the steps that only existed because a person was the bottleneck. Keep the steps that genuinely need judgement.
  4. 04Unify the data the agent will touch. One source of truth for customers, products, pipeline, and history. Agents fail on fragmented data faster than people do.
  5. 05Build the smallest possible agent. One workflow, one tool set, one outcome. Ship to production with a human in the loop on the highest-stakes step.
  6. 06Measure throughput, accuracy, and deflection. Throughput is volume per hour. Accuracy is rate of correct outcomes. Deflection is the share the agent finishes without a human.
  7. 07Move the human review backwards. Each week, push the human checkpoint one step later in the workflow as confidence grows. Stop when the residual risk is what a senior reviewer would catch anyway.

Notice what is not in the list: a tool selection committee, a six-month roadmap, a generic AI strategy document. Those artefacts are how SMEs end up with a slide deck and no shipped system.

Operating model · four layers, one system
01Commercial
Source · qualify · quote · renew
02Operations
Plan · fulfil · exception handling
03Data
One schema · queryable by all
04Admin
Finance · HR · compliance
Each layer of the SME (commercial, data, operations, admin) gets rebuilt around the agent, not bolted onto it.

Where SMEs typically start

We see four workflows generate most of the value in the first six months. Outbound sales, where an agent qualifies inbound leads, drafts personalised first touches, and pushes only the ones above a quality bar to a human. Quote generation, where an agent reads a brief, pulls product data, drafts a tailored quote, and routes it for approval. Customer support, where an agent answers the routine 60 to 80 percent of tickets in the user's tone of voice and escalates the rest. Back-office finance, where an agent reads invoices, categorises them, matches them to POs, and flags only the exceptions.

These are not exotic use cases. They are the workflows that already eat the most hours in most SMEs. The agent does not replace the team. It removes the part of the team's day that they would happily have given up anyway.

The winning SMEs will not be the ones that use AI the most. They will be the ones that redesigned a workflow around it first.

- Derk Disselhoff

Common failure modes

Three patterns kill more SME agent projects than any technical issue. The first is treating agentic AI as a procurement decision: pick a vendor, run a pilot, hope it sticks. Agents are not SaaS. They change the shape of the workflow they touch, and that needs an owner at the table with the authority to redraw the workflow itself.

The second is starting with too much. A portfolio of seven workflows in parallel, none of them in production, all of them blocked on the same data problem. Pick one. Ship it. Then pick the next.

The third is leaving the human in the loop forever. A reviewer on every single decision turns the agent into the slowest part of the workflow. The whole point of the framework above is to move the reviewer backwards over time, based on measured accuracy, until the agent owns the steady state.

What it looks like done well

Six months in, the workflow has a different shape. The same team handles three to five times the volume. The agent reports its own throughput, accuracy, and exceptions in a weekly dashboard that the founder actually reads. The next workflow is already half-mapped, because the team that lived through the first one knows exactly where the second hour-sink is.

Capex does not go up. Headcount does not need to. Revenue and margin do, because the company is finally shaped the way the founder always wanted it shaped. That is the SME version of an agentic operating model, and it is now genuinely within reach for any owner-operator willing to pick up the pen.

The invitation

If you are running an SME and one workflow is eating your week, that is the place to start. Bring the workflow. We will bring the agent, the platform, and a team that has shipped this seven-step framework into production before. The first version is live in weeks, not quarters.

Verder lezen