GuardPilot grew out of an internal control system and works on the history and context of a company or a person. All findings from this period were validated by our own finance people.
All processes of a business in one memory, with twenty-five years of experience in how companies actually work behind it, no standard answers but a living system in which the human asks the questions, brings in what is unique to the business and validates the outcome.
own production, 6–20 August 2026
Every point of light is one data point, an email, chat message, contract, change or appointment: from a loose trace, through movement toward each other, into one coherent shape. Only together do they function as memory.Daily steering
Five sources in, three actions out.
Every round, everything that arrives flows into one core. What comes out is never a decision, always a proposal.
Read the mail
Deduplicated per round, indexed, and checked at thread level for what stayed unanswered.
Read the messages
Business chats on request; the full thirteen-year export is searchable.
Prepare drafts
In the decision-maker's own mail application, in his tone. He sends them himself.
Track actions
One list: who is waiting, since when, until when. Answers through an input panel.
Counterforce
The system says so when something is off, with the source, without softening.
Counts
Fourteen days of production, counted.
Counts of our own work, not client figures. Source: own production, 6–20 August 2026.
15Logged work sessions9 of them at night
~70.000Mail messages searchable2009 to 2026
~144.000Chat messages searchable2013 to 2026
~270.000Attachments indexedsearchable per file
116.482times steered by the founderOwn measurement 21 August 2026, one environment, earlier months and other environments not included.
12Analysis reports deliveredin fourteen days
14Drafts prepared0 sent by the system
4Hard stopsdue to missing data
11Findings in the self-audit0 incorrect key figures
In practice
Four things this layer does.
What it recovers, what it flags, what it brings back and what it asks of the owner.
What a person can no longer find
The system combines data from years back, mail, chats, letters, bookkeeping and documents, that is no longer findable by hand, because nobody knows where to look or that it exists at all. Today's question decides what surfaces from that history.
Image: a seventeen-year timeline with three points of light pointing to one question of today.
Detail
Anonymised example from the period: with the four questions from the tax authority, the decisive evidence came from a chat two years earlier and a ledger card in an old mail attachment, not from the existing file.
It sees when a problem has no owner
At every unanswered measurement, each thread is checked for who had the last word and who should act. That makes visible when a problem has been circulating for weeks without an owner. It is reported first, not as a detail at the bottom of the list.
Image: a thread passing four people and landing nowhere, with a red marker.
Detail
The measurement runs every round across all open threads. A thread without an owner gets no estimate attached: the system reports the status and leaves the decision on who acts to the human.
What returns, steered with one word
Signing moments for important documents, deadlines, legal analyses and simple reminders return at the right time in one action list. The decision-maker answers yes, no or one word, and the system processes it. It works as a second memory, with experience of how processes in companies actually run behind it.
Image: the input panel with yes-no per item, stylised, without real content.
Detail
Each item keeps party, date and waiting time. An answer moves the item; the system executes nothing without that explicit instruction, and an item without an answer does not drop off the list.
Every company is different, and that part comes from the owner
The system recognises most processes by itself: purchasing, invoicing, contracts, staff, cash flows. But every company has something of its own, the way things run slightly differently, and that is what makes the company. So owners and directors get questions when they join.
Image: a circle mostly filled by the system and, for a recognisable segment, by the owner, with a label.
Detail
In our experience, fifteen to twenty per cent of the context is input from owner and board. That part makes it the system of that specific company, not standard answers.
Scale
What no human mind can hold
A full hard drive, every file and its history, seventeen years of mail, thirteen years of business chats, several years of bookkeeping. No person oversees that. Through fixed working rules the system combines those sources on one question of today and returns deepening answers, not a summary.
Image: a seventeen-year timeline on which separate source layers converge into one question.
Limit
The system shows the trend and the source; the interpretation stays human work.
Detail
Figure history and trend analysis are part of it: a ledger item or a client tracked over years, the turning point named, the source stated per figure. Every figure carries source, scope and reference date, so an outcome can be checked without taking the system at its word.
Working without loss
Nothing falls through the cracks any more
People in operations, administration and sales try to do their work well every day. What goes wrong is rarely unwillingness: an invoice left hanging, hours that do not add up, a purchase note without an owner, a contract question nobody picks up. GuardPilot forgets nothing and helps people do their work better, so employees and clients get better service.
What that looks like
No lists that leave you to work out the problem yourself. No flood of questions. One worked-out situation, with the context attached, and one clear question. The answer can literally be a, b, c or d.
Limit
GuardPilot asks the question and processes the answer; deciding and sending is done by the human.
Detail
The question is phrased so it is experienced as help, not as a reckoning. That is a deliberate setting. Internal communication becomes calmer and faster, mistakes are prevented, and nothing, truly nothing, is lost any more. The human keeps deciding; GuardPilot takes over the remembering and the channelling, so time goes to what really matters.
Example cards — stylised and fictional
Invoice
An invoice has been open for eleven days and has not been approved by anyone. The matching order line has been signed off.
What would you like to happen?
aApprove as it stands
bI will look at it myself
cAsk the supplier for clarification
dPass it to the project lead
Hours
Hours were logged on one project this week that do not map to an assignment. The planning does show work on site.
Where do these hours belong?
aTo the running project
bTo additional work
cTo internal work
dNot sure, leave it open
Contract
A contract expires in six weeks and no termination or renewal has been recorded. The client question about it has been open since last week.
How do we proceed?
aRenew on the same terms
bRenegotiate first
cLet it expire
dSet a reminder for next week
Cases
Six files, without names.
Each case is set out in five fields. The Limit field is always shown: what the system cannot see matters as much as what it finds.
A service company's profit drop
Situation
An operating company slides over three years; controller and board explain it differently.
Question
Where is the drop, when did it start, economic or administrative?
Did
Read source sheets, rebuilt per booking moment, dissected the invoicing run.
Outcome
Two fault lines identified, a suspected error refuted, an unknown entity found.
Limit
Pdf attachments fall outside the mail index; the ledger route stays necessary.
Detail
Per client, what was caught up later was tested, and the balance sheet was searched for technical entries. The report went to the controller as a validation document: measurements without judgements, every figure with source, scope and reference date.
An acquisition nearing closing
Situation
A purchase nears closing while sellers respond slowly.
Question
What waits on whom, and is the buyer entity in the deed right?
Did
Tested the response point by point, compared the draft deed with the board resolution.
Outcome
Deviating buyer entity found before signing; four transactions kept apart.
Limit
Follow-up running through a colleague's mailbox is invisible.
Detail
Alongside the purchase ran a sale and two other files. Each file kept its own action list with party, date and waiting time; nothing was merged.
Four questions from the tax authority
Situation
A company receives four VAT questions; the answers are scattered.
Question
Which evidence belongs to which question, and what contradicts what?
Did
Built a delivery list per item, set the evidence position per question, tested the memo.
Outcome
Nine contradictions visible before submission, an old piece of evidence recovered.
Limit
The tax judgement stays human work and sits outside the system.
Detail
Mail and messages were searched for contemporaneous evidence, evidence recorded at the time weighs more than a later reconstruction. The recovered item came from a chat years earlier.
Own tax return and private positions
Situation
Positions and loans run through several companies; sources differ.
Question
What is the actual position per entity, and where do the sources contradict each other?
Did
Processed fourteen position questions, placed both versions side by side.
Outcome
Three contradictions registered instead of averaged away; one claim refuted with a source.
Limit
The family domain is not recorded.
Detail
The dividend history was proven from the ledger card itself, not from a summary. Where two sources contradict each other both remain, with label and reference date, an average would hide the contradiction.
The whole structure on one page
Situation
Several holdings, operating companies and property; nobody had the whole picture.
Question
What does the structure look like, where is the money, who owes what to whom?
Did
Pulled fourteen source files from seventeen years of mail history and merged them.
Outcome
One overview, refreshed three times, with a source and reference date per cell.
Limit
An estimate is reasoning, not fact.
Detail
The result is an interactive working document for the controller, not a static report: every cell shows where the figure comes from and on which date it was measured.
An advisory file for a third party
Situation
Fourteen documents in one file, in successive versions.
Question
What changed between versions, and what quietly disappeared?
Did
Compared versions mechanically, named differences per clause with their location.
Outcome
One party had no counsel of its own; advice: do not sign before three repairs.
Limit
The system advises, the party decides.
Detail
Version comparison is the sharpest instrument in a file: the risk is not what is written, but what fell away between two versions without anyone naming it.
One night
22.30 to 04.20.
One logged night session, step by step. Five reports, zero sends by the system.
22.30
Harvest mail and messages; answer round processed.
23.30
Two reports delivered.
00.05
Follow-up questions; profit drop per booking moment, suspected error refuted.
01.30
Deep dive into source sheets; draft rewritten without imperative sentences.
02.25
Four-year search report, on request without judgements.
02.26
The decision-maker sends it himself, with four reports attached.
03.20
Night check.
04.20
Session log: five reports, zero sends by the system, one recovered incident.
What went wrong
Four incidents, with their measure.
A system that hides its own misses cannot be checked. This is the complete list from fourteen days.
Unproven claim in a draft.Removed; now a hard rule.
Focus loss in webmail: two mails archived.Restored; nothing was sent.
The answer panel lost the input.Now copyable text.
Clock error: monitoring ran late.Nothing executed on an expired GO; now a clock check.
What remains open
The receiving end is the weakest link. A question nobody picks up delivers nothing, however good the measurement. Measured in September 2026, and therefore now the priority.
Working rules
How it works, at the level of rules.
We answer the how-question with working rules, not with software. Here they are, all ten.
01Explicit instructions only.
02Missing data is a hard stop.
03Every fact carries a label: measured, reasoned or unknown.
04Every figure with source, scope and reference date.
05Conversation and live measurement beat any recorded fact.
06First check what already exists.
07Internal and external strictly separated.
08Drafts only with verified facts.
09Done does not exist without measurement.
10Propose; execute item by item, after a human GO.
Questions about this layer?
The thirteen most-asked questions are on the FAQ. Want to join: there is an orderly queue, no sales pressure.
