How it works

From a conversation to a working system.

There is no off-the-shelf software to configure. First we gather your company’s context: how you work today. Only then do we propose your operating system, and only when you approve it do we build it: from your procedures and your rules.

Two colleagues with a tablet walking between warehouse shelves.
Your people answer questions; a Blueprint, a picture of today with the risks, is written; from it a proposed solution; after your approval, a system that works at your site, on-premise.
  1. Question 4 of 9

    Who approves an order larger than usual?

    Head of sales. Above 10,000 € the director as well.

    Delivery note · PDF

    1. Your peopleshort questions, documents

    1. 1People and roles
    2. 2Steps of the work
    3. 3Software and documents
    4. 4Where it gets stuck
    5. 5Risks and opportunities

    Only one person knows the price list

    2. Blueprinta picture of today, with the risks

  2. WorkThe system takes overA person decides
    Orders by e-mailreads, enters, checks stock, prepares the replynew customer · price deviation · above 10,000 €
    Delivery notescompares with the order, flags differencesapproves the complaint

    3. Solutionwhat the system takes, where a person decides

    1. 08:12Order 4821 read: 6 lines entered into the business software
    2. 08:13Stock checked: 6 of 6 available, 3 days to deliver
    3. 08:40Delivery note 1193 compared with the order: price deviates → waiting for a person
    on-premise, at your site

    4. A system that workson-premise, at your site

1Getting to know you

We talk and gather how you work today.

Your people answer short questions online, when it suits them, and upload documents they already have: order forms, delivery notes, reports, instructions. No workshops that take whole days.

The questions are short and concrete: who does what, where it gets stuck, who approves. Everyone answers only their own. A question a colleague knows the answer to is simply forwarded to them.

Orders

Question 4 of 9

Who approves an order larger than usual?

Name and role. If you do not know, forward the question to a colleague.

Save and continue Not sure, forward to a colleague
Example screen with made-up data

2Blueprint

You get a picture of where you stand, with every risk.

The Blueprint is a written picture of how your work runs today: who does what, in which steps, with which software and documents, where it gets stuck and where the risks are. Every finding has a source. It is written in business language, so management can read and understand it.

You read the Blueprint in an hour. Every finding has a source: a colleague’s answer or a document. Before we go on, you review it and correct what is not right.

Blueprint

The Blueprint as a document with five layers: people and roles, steps of the work, software and documents, where it gets stuck, risks and opportunities; every finding with a source and a rated list of risks. Blueprint People and rolessourceSteps of the worksourceSoftware and documentssourceWhere it gets stucksourceRisks and opportunitiessource Risks and opportunities Only one person knows the price listRisk: highOrders wait over the weekendRisk: mediumDelivery notes are checked by handRisk: low

3Solution

We propose a solution, you approve it.

Based on the Blueprint we write down clearly which work the system takes over, where a person decides, what we need for it and what it costs. Nothing is built without your approval.

The proposal is written in business language: which work the system takes over, where a person decides, which approval limits apply and what it costs. If it does not pay, we tell you.

Proposed solutionApprove
WorkThe system takes overA person decides
Orders by e-mailreads, enters, checks stock, prepares the replynew customer · price deviation · above 10,000 €
Delivery notescompares with the order, flags differencesapproves the complaint
Weekly reportcompiles and sends on Monday at 6:00nothing: receives it

Approve before we build

Example screen with made-up data

4Build and run

We build it and run it at your site.

We build the solution and connect it to your software. Then we watch over it and make sure it works every day. What the system does is logged, so you can check every step.

The system runs at your site, on-premise. Exceptions go to your people on the portal, every step is in the log, and when something changes at your end, the system changes too.

Exceptions

Three are waiting for your decision

  • New customer on an orderOrder by e-mail · 12 min ago ApproveCorrect
  • Quantity ten times the usualOrder · 40 min ago ApproveCorrect
  • Price on the delivery note does not match the orderDelivery note · 2 h ago ApproveCorrect

Today, without you

41orders entered
18delivery notes checked
2reports prepared
Example screen with made-up data

At the end

What you get

NextWhat you get

Which work takes most of your time?

A few sentences are enough. A person will reply.