Skip to content

AI automation consulting · Process automation

Enter your data once

We automate recurring workflows between email, Excel, CRM and ERP: first measure how the workflow runs today, then a pilot at a fixed price, then the handover.

InputRulesDraftPerson
Fig. 1.1A person decides. The routine runs on its own.

AI check from €990 net·Pilot at a fixed price, agreed in writing beforehand·Handover with documentation

01Typical flows

Four workflows that often pay off first

We pick the workflow where effort and benefit match best.

Example scenario

  • Requests & email

    Sort and route incoming mail

    More use cases
    Before
    Requests arrive in a mailbox and are moved to the right place by hand.
    After
    Incoming mail is tagged by topic and created as a case in the right system.
    Stays with a person
    Your team answers the case. A draft reply is ready on request.
  • Receipts & invoices

    Read and assign receipts

    Before
    Invoices and delivery notes are retyped and filed by hand.
    After
    The details are read out, checked and entered where they belong.
    Stays with a person
    A person reviews anything unusual or inconsistent.
  • Appointments & reminders

    Confirm, remind, follow up

    Before
    Confirmations and reminders are written one by one, and follow-ups get lost.
    After
    Confirmation, reminder and follow-up run on fixed rules from the calendar.
    Stays with a person
    Your team handles cancellations and special requests.
  • Reports

    Generate evaluations automatically

    Before
    Figures are exported from several systems every week and merged by hand.
    After
    The report is produced at a fixed time from the source systems and sent to its recipients.
    Stays with a person
    Your team judges the figures and decides.

02Approach

Measure first, then build

We start with a single workflow. After each step you decide whether to continue.

  1. Step 01

    Map and measure the workflow

    in the AI check

    A workshop with the people who do the work. We record how the workflow really runs: handovers, tools, data and exceptions.

    1/4 · MeasureResult

    A baseline your team can verify, and a decision on what gets automated and what deliberately stays manual.

  2. Step 02

    One workflow goes live

    fixed price, in writing first

    We build the first automation and test it in daily work. Scope and fixed price are agreed in writing beforehand.

    2/4 · PilotResult

    A running automation with a log, error handling and a manual fallback.

  3. Step 03

    From pilot to daily work

    after the pilot, on request

    If the pilot holds, we carry it over to further departments or workflows and work in what daily use has taught us.

    3/4 · RolloutResult

    The workflow runs across the whole team, not just in a test.

  4. Step 04

    Documentation and source code

    operation monthly by agreement

    Documentation, access and, where there is any, source code go to your team. What is handed over, we put in writing before we start. If you want, we keep looking after the solution.

    4/4 · HandoverResult

    Your team gets what it needs to run the workflow itself.

03Tools

Tools that fit your workflow

We build with what you already have and add only where needed.

Microsoft Power Automate
Where Microsoft 365 is in place: approvals, documents and mailbox rules.
Make
For connections between cloud services when no standard connector is enough.
n8n
For workflows with sensitive data: can be self-hosted on a server in the EU.
Python
For special cases: reading files, checking data, generating reports.
CRM and ERP connections
Through interfaces and webhooks, so data is captured once and used everywhere.
Hosting
In the EU, on request with a provider of your choice or on your own infrastructure.

We do not sell licences. Accounts and access stay with you.

04Before and after

The same workflow, by hand and automated

As an example: an inquiry arrives by email and is meant to become a quote.

Example scenario

Today, by hand

  • The inquiry is read and copied into a spreadsheet.
  • Customer data is looked up in the CRM or created anew.
  • The quote is pasted together from a template.
  • The PDF goes out by email. The follow-up sits in the calendar, if someone remembers.

After automation

  • The inquiry is recognised and created as a case. The data sits in the CRM once.
  • The quote is prepared from the customer data.
  • A person checks and approves.
  • Sending and the follow-up reminder run on fixed rules. Every step is logged.

05Internal tools

From Excel list to a proper tool

If a workflow fits no standard software, we build a small tool for exactly that. Off-the-shelf software is often the better choice, and we tell you so up front.

  • Admin consoles

    Orders, exceptions and customer notes in one place instead of three tabs.

  • Dashboards

    Key figures and alerts from CRM, ERP and finance system in one view, without manual work.

  • Approvals and forms

    Queue, route and approve quotes, contracts or refunds with a full history.

  • Knowledge bases

    Search across your own documents, policies and FAQs.

  • Our own work

    OpSo

    For OpSo, our own product in its test phase, we built the dashboard, onboarding and admin console ourselves.

    Our projects

Common questions

Questions about process automation

Not always. A clean automation without AI is often enough. Where AI helps, for example reading receipts or sorting mail, a person checks the result.

AI check

Which workflow should be relieved first?

Describe it in a few sentences. In our first conversation we clarify whether an AI check makes sense.