AI does the searching. Your people decide.
Every night GuardPilot reads your contracts, hours and invoices. Where something needs attention, the right person gets one question, with the source attached.
- 01
Agents search
Eleven agents, each with one task. Hours, invoices, work orders, absence, margin and terminations.
- 02
Checks verify
Before you get a question, the data and the reason for it have been checked. By 22 automated checks.
- 03
You decide
One question to the right person, with the source attached. Never an instruction. Every action waits for your approval.
- Hours watch
- Invoicing watch
- Work-order watch
- Absence watch
- Margin signal
- Termination reader
- Consistency check
- Financial summary
- The conductor
- Context finder
- Self-check
11 agents and 22 automated checks, as of 3 October 2026
This is not a dashboard. This is your company, alive.
Every dot is a document, a signal or a file. Every line is a connection the system drew itself. The pulses you see moving are information flowing from agent to agent, day and night. This is how GuardPilot looks at a business: not as separate processes, but as one living system in which everything is connected. What you see here is a representative rendering, not client data.
Here the field rotates on its own and scrolling stays scrolling. Zooming, dragging and isolating single points only start in the interactive view at /stelsel.
What AI across an entire business means →AI across your entire business
We take on a limited number of engagements per year. Look at the system yourself first, then decide.
You are not buying software
GuardPilot is not a package you install and tick off. It is a constantly evolving system, and nobody knows exactly what it will look like in two years, other than that it will be further along than today. Whoever steps in is at the front of the technology, while most companies are only just discovering their first AI assistant. That asks something in return. We ask every client to free up one of their own people, often a young, eager employee, who operates the system daily and grows with it. You are not buying a tool, you are building a head start.
See the seven-phase engagement →Nothing falls through the cracks any more
An invoice left hanging, hours that do not add up, a contract question nobody picks up. GuardPilot forgets nothing and asks one clear question with the context attached, answer a to d. As help, not as a reckoning.
See how that works in practice →Not bought. Not outsourced. Built ourselves.
GuardPilot is not software that was bought or commissioned. It is twenty-five years of running companies, every day, in every process of a business, translated into new technology. By one person, Erwin de Jong. Steered 116,482 times by himself, from a whole paragraph to a single yes or no, across 2,060 working conversations with the system, between 16 March and 20 August 2026.
The first attempt was to outsource it. That failed, and it taught us something. This can only be built if you know companies from the inside. Every process, how people communicate, what matters and what is noise. What is obvious to an entrepreneur is not obvious to a builder from outside, who sees only part of the puzzle.
Everything is tested immediately on real files in real environments. Not in a demo, but in live acquisitions, financial analyses and daily steering. Every outcome is validated by our own finance people before anything is said about it.
The transition that is now starting everywhere, we went through more than a year ago. We move with the newest technology and know what it can do, because we do it ourselves. This is only the beginning.
Own measurement 21 August 2026, one environment, earlier months and other environments not included.
How GuardPilot came about →Four domains. The same thinking model.
Per domain: pull the data, verify it in multiple ways, then ask a question. Every change, client, contract or personnel file, tested against law, CLA and internal agreements. In every domain the human decides.
Receipt chain, duplicates, credit checks and stalled invoicing, every night, source per euro.
Margin, payroll, absence and multi-year trend per client, site and period, against sector and own norms.
Hours over budget per site, periodic work tracked to invoice, costs that keep running on stopped sites.
End dates, renewal windows, termination signals and margin pressure, flagged while you can still steer.
The question does the digging.
Every question follows a fixed structure: what was measured, over which period, from which source, and what is the question. Your manager no longer has to look anything up. Just answer, or ask back.
Client X ran 18 hours over budget last week. Every hour direct from the source.
The system already checked: this also happened in prior weeks, but back then an extra-work number was created. Not now.
"Regular work over budget, why? Or forgotten extra work? Then we immediately create an extra-work number, rebook the hours and the invoice goes out."
"Forgotten extra work, rush job Tuesday." The system creates the extra-work number, rebooks the hours and prepares the invoice. Question and answer are tracked until the case is closed.
A repeat filter, materiality floors and a fixed ranking on financial impact keep it to a handful of questions. And the key rule: healthy clients get no question.
Never an action without you. Every question is a question with an offer of help, no accusation, no order, no automatic booking.
First cross out everything innocent.
A good question is what remains after crossing out the innocent. Over three quarters of clients are proven healthy every night, silent, with the reason recorded, 503 of 639 on 17-09-2026.
Read the full thinking model →What remains must be asked, with the measured numbers. Fixed rules in code calculate and choose. The question to the manager is built from a fixed template, without a language model.
The system audits itself
A control layer that does not check itself drifts away without anyone noticing. That is why self-audit is not a feature at GuardPilot, it is a foundation.
No number on a screen without a measurement moment and origin. When a reading gets stale, the screen says so honestly, a card that can lie is not a card.
The system measures its own engines, data flows and knowledge layers daily, using a fixed, repeatable protocol. What is red gets fixed or hard-explained, and the audit itself is verifiable too.
Anything with consequences waits for a human decision. One panel, one click, and every decision is logged with reason and timestamp. What the system learns is periodically presented to the owner for confirmation, knowledge without human validation stays marked as such.
The system organises its own counterforce
Self-audit tells you when something is broken. Counterforce keeps it from breaking. That is why GuardPilot admits no change to the system without critical review first, by a second, independent AI, and where it matters, by a human.
Every build decision passes a second, independent AI model with a single job: say what breaks, what is missing and what it would do differently. Only at 85 percent agreement or more does a change proceed. When the two cannot resolve it, the owner decides, not the system.
A screen that was right yesterday can lie today. So no change enters the system unless the dashboards are demonstrably fresh and working, a requirement enforced technically at four moments, all the way into the overnight engine.
The most dangerous faults are the ones doing nothing, until you touch them. A weekly hunter actively searches for slumbering drift: duplicate versions, references to things that moved, agreements without enforcement. Every lesson found becomes a self-running check the same day.
Stored knowledge is not working knowledge. What an organisation's people teach the system is enforced every night: questions that clash with established knowledge are stopped, and the tone of every question to an employee is guarded by a gate that allows no exceptions.
What your security review asks first
Before anyone looks at functionality, the question is where the data sits, who can reach it and who signs off. That answer is here, not behind a form.
Storage runs in a secured database of our own inside the EU, traffic to the site and the database goes over TLS. No resale, no marketing mail, no profiling.
Who sees what is enforced at database level with row-level security, not in the screens around it. Vulnerabilities can be reported confidentially through our security.txt.
No amount and no signal without the document, line and measurement behind it. That is what a controller needs before daring to use a finding in a supplier conversation.
Anything with consequences waits for a human decision, and that decision is logged. Responsibility stays where your accountant and your regulator expect it.
Controlled escalation, never a standstill.
Unanswered does not disappear: first a retry, then a proposal one level up. Escalation is always a proposal to a human, never an automatic decision.
Site or project, the person who actually knows the answer.
The chain never stalls.
From site via region and district up to the board. Always a proposal to a human.
A team of agents, one fixed chain.
Workflow over autonomy: a fixed sequence of steps with logging and verification per step, no free-roaming agents. The number is not the point, the operation is the point.
Ledger, hours, planning, documents, daily, with connection checks.
Contracts, work orders and terminations into structured facts.
The thinking layers: hours, invoicing, margin, trends, terminations.
Combines all lenses, runs the elimination, decides.
Quality gates, tone control, evidence per amount.
Knowledge-base management; client knowledge never generalises.
Monitoring, backup with restore proof, traceable logging.
Bulk and OCR on our own hardware, data stays inside the network.
- Four-eyes principle: models cross-check each other's outputs.
- No figure goes out without source, file and timestamp.
- If a change breaks a validated result, the change is reverted.
Five solutions, one system.
You choose where we start, the rest follows.
Missed revenue surfaced, source per euro.
View solution →Every night every contract line checked.
View solution →Deep audit without sampling, 100% of the portfolio.
View solution →Every invoice line matched to contract, hours and delivery.
View solution →From checking to reviewing and deciding.
View solution →How much revenue is leaking at your firm?
In contract-intensive services, structurally 5.2% of annual revenue leaks, missed indexations, forgotten extra work, under-invoicing. Slide to your portfolio size and see what it means.
Take the leakage scan →Who it is for, and who it is not for.
Owner-led and contract-intensive companies that have their figures and contracts in digital form, where the owner sits at the table, and that are willing to free up one of their own employees to operate the system.
Anyone looking for a stand-alone chatbot, a tool for one department, or a project that stalls after delivery is someone we cannot help. GuardPilot only works across the full width, with the owner involved.
- The measurement layer over the whole ledger
- Contract comprehension and interpretation, including history
- The question logic: first cross out innocence, then ask
- A safety net of validated checks on every change
- How your company deviates from the standard
- What should be included at your firm, and what should not
- Who decides on what.
Everything about GuardPilot, in one place.
Solutions
About the system
- AI for companies across the whole business
- AI implementation in Groningen and the northern Netherlands
- AI implementation step by step
- AI agents for companies
- AI for administration and controlling
- AI and compliance, evidence and approval
- Contract compliance reporting with evidence
- The system, the interactive graph
- How GuardPilot works
- Why contract monitoring is needed
- Cases from practice
- Frequently asked questions
- Contract monitoring glossary
Ready to lay this over your company?
Proven technology from our own operation, no demo, no theory. We show what already runs.
We take on a limited number of engagements per year. The first companies build along and notice it. Join the waitlist