Start here
Bring the bottleneck, not the brief.
Tell us which job eats the most hours and we will say what it would take to hand it over — or that it is not worth automating yet, if that is the honest answer.
Start a projectDashboards that show what your processes are doing
A process dashboard is one screen that shows what your automation and your systems are actually doing: what went through, what is stuck, and what is waiting on a decision from you. Not a wall of charts, but the answer to whether it works. Goudbeek builds these dashboards from Almere, on the sources you already have.
One screen that shows what happened, and what needs you
Automation you cannot see is automation you cannot trust. A dashboard is not a wall of charts — it is the answer to whether the thing is working, and what is stuck.
Who is a process dashboard for?
Anyone running an agent or a workflow and taking its word for it
Managers whose weekly number is assembled by hand from four tools
Teams who find out something broke because a customer told them
What does a good dashboard show?
- 01
What went through, and what did not
Handled, waiting, failed, and why. The failures at the top, because those need a person today.
- 02
The numbers you already ask for
Pulled from the systems you already keep them in, rather than typed into a sheet on Friday afternoon. The same figure, without the afternoon.
- 03
A queue, not just a picture
The things waiting on a decision are on the screen with the decision attached, so looking at the dashboard and doing the work are the same act.
- 04
It says when it is stale
A panel that quietly stopped updating is worse than no panel. If a source has gone quiet, the screen tells you that before it tells you a number.
What do you decide about who sees what?
Written down before anything is built, and changeable afterwards without a rebuild.
- Who sees which numbers, down to the team
- Which sources it reads, and at what interval
- What gets alerted, to whom, and how loudly
- Whether anyone outside your company can see any of it
How does a dashboard grow with you?
It grows with what you run. We start with the flows that already exist, and add panels when something new goes live rather than guessing at them up front.
Frequently asked questions about dashboards
Is your question not here? Ask it directly: you hear back within one business day.
What is a process dashboard?
A process dashboard is one screen that shows what your automation and your systems are actually doing: what was handled, what is waiting, what failed and why. The failures come first, because those are the ones that need a person today. It is not a wall of charts but the answer to whether it works and what is stuck.
Why do you need a dashboard with automation?
You need a dashboard with automation because automation you cannot see is automation you cannot trust. Anyone running an AI agent or an automated process wants to know what went through without taking the system's word for it. A dashboard makes that visible, and lets you deal with whatever is waiting on a decision straight away.
Where does the dashboard get its numbers from?
A process dashboard gets its numbers from the systems you already keep them in, rather than someone typing them into a sheet on Friday afternoon. You decide which sources it reads and at what interval. If a source goes quiet, the screen tells you that before it tells you a number, because a panel that quietly stopped updating is worse than no panel.
Who can see what on the dashboard?
Who sees what on the dashboard is yours to decide, down to the team: who sees which numbers, what triggers an alert, to whom and how loudly, and whether anyone outside your company can see any of it. Those agreements are written down before anything is built, and you can change them later without the dashboard having to be rebuilt.
Can you act from the dashboard as well?
Yes, you can act from the dashboard as well; that is the idea. The things waiting on a decision, such as a refund over your limit or a supplier who is not in your records, are on the screen with the decision attached. Looking and doing become the same act, instead of going from a chart to another system to finish the work.
Do you need a dashboard if nothing is automated yet?
A dashboard sometimes helps even when nothing is automated yet: anyone who assembles a weekly number by hand from four tools gets something out of it without automation. If automations are already running, the dashboard can start with those, and a panel is added when something new goes live. If you do not yet know where the time goes, read about improving business processes first.
What does a custom dashboard cost?
The price of a custom dashboard depends on the number of sources, the panels you need and who gets access. After a short intake you get one fixed price up front, not an open-ended bill. The dashboard can run on our managed hosting from €39 a month (self-hosting works too), and then grows with what you run, instead of us inventing every panel up front.
Read next
- Knowledge base Process analysis: how to map a business process Who does what, in which system, how often, and where the work waits.
- Business processes Improving business processes First map how the work really runs, then build.
- Web design Web design and websites A fast, findable site that you can edit yourself.
- AI security Using AI safely What a system may see, what it may do, and what waits for a person.