Flows, the automation engine

    Work that runs itself.
    With an owner behind it.

    Flows takes over the work that goes the same way every day or week: matching invoices, routing requests, reordering stock, sending out the figures. It runs on what the organisation has agreed, under a named owner. People keep their time for the work that needs judgement.

    ProcedureRuns itselfInvoice inMatch to orderException: buyingBook it
    What becomes possible

    The recurring work runs itself. The exception reaches a person.

    Automation pays off most where work comes back often and the rules are already known. Three examples of what that can look like.

    InvoicesMatchBookedException

    Invoices match themselves

    Every invoice is laid next to its order and receipt. What matches is booked. Only an exception reaches someone in buying, with the reason attached.

    RequestsFinanceHRITBuyingServiceSales

    Every request straight to the right team

    Mails, forms and tickets are read and sorted. The team gets a task with a summary, so nobody has to dig through the inbox first.

    MinimumOrder proposal7 items below minimumSupplier · fixed agreementOwner · buyingWaiting for approval

    A signal becomes a proposal

    When stock drops below the minimum, an order proposal is ready for its owner. One approval and the order goes out.

    The approach

    Start with one process. Every next one goes faster.

    The value is not in one clever automation but in an organisation that can trust it with more and more. That is why it goes in this order.

    1. 01

      Pick the work that comes back

      A process that is done by hand every week and whose rules are known. The procedure is written down the way the work really goes today.

    2. 02

      Agree the terms

      What counts as an exception, which margin applies, who owns it? Those agreements are recorded once and hold everywhere after that.

    3. 03

      Build, test, have it reviewed

      The flow first runs as a test, without sending anything. A colleague approves it before it goes live.

    4. 04

      Measure the time it frees up

      What it must deliver is set in advance, such as hours a week. The next process uses the same terms, so it is built faster.

    The growth path shows where an organisation stands and what the logical next step is. To the growth path

    The difference

    Other automation moves data. Flows acts on meaning.

    A link between apps knows which field goes where. Flows also knows what that field means, who owns it and what may happen.

    Automation that only moves dataFlows
    A step knows an app's fields.A step works with agreed definitions, metrics and data contracts.
    An AI step runs with the connection's access.An AI step runs as the flow's owner, with that owner's access and no more.
    Whoever builds it switches it on.Someone else approves before a version goes live.
    Control

    What, when, where, who and how: decided before it runs.

    A flow can only do what an administrator has allowed. That is why an organisation dares to hand it more work.

    Margin · v3Contract · financeLoose field ?

    What goes in

    Only what was agreed

    A flow reads through a data contract and works with agreed definitions. A message without the required fields does not get in.

    WhenWhatMon 07:00Weekly figures to TeamsNew invoiceMatchMargin < 20%Alert buyingIn 30 daysReminder

    When

    At the moment it should

    On a schedule, on a new invoice, when an alert fires or after a wait of up to thirty days.

    The organisationERPAllowed

    Where

    Only along approved routes

    Outbound calls go through connections an administrator has approved. A free address is not possible and code runs without a network.

    Run waitsOwner · buying

    Who

    A named person decides

    Every AI step runs as the flow's owner. Where a decision is needed, the run waits for the right person, and who decided travels with the run.

    Step 1Step 2Step 3Step 4Step 5Again from step 3

    How

    Reviewed, tested and replayable

    Every change is a new version someone else approves. A test sends nothing and every run can be replayed from any step.

    An AI assistant such as Claude can also draft, test and submit a flow. It never puts one live itself: a reviewer decides.

    Every plan

    Every plan has every Flows capability.

    No step, control or AI feature sits behind a more expensive plan. What a team builds in its first week works the same way when the whole organisation joins. See the plans

    Integrations

    Flows read from your systems and report where you work.

    • AFAS

      AFAS Profit

      Finance and HR, read live and never changed.

    • Exact

      Exact Online

      Customers, orders, stock and the ledger, read live.

    • Microsoft 365Google

      Teams, Outlook and Google

      Alerts and tasks to your channels. Sending only, never reading.

    • CopilotClaudeChatGPT

      AI assistants

      Copilot, Claude and ChatGPT on the same source, under the same rules.

    All integrations
    Get started

    Bring the process that comes back every week.

    In one conversation it becomes clear what can run on its own and what a person keeps deciding.