BilagPilot in operation
From ongoing operations, September 2026.
- 8,000+entries without supporting documents found
Do you recognise a Bob?
You decide where the task should stop.
Bob retrieves and checks attachments. You agree on what runs automatically and what a responsible person must approve.
Example: checking submitted attachments.
See what Bob can access
Access is limited to what the specific task needs and documented before starting. Runs, stops and approvals are logged. A named person remains responsible for anything requiring judgement.
The attachment is completeChecked and ready for the agreed action
A required field is missingStopped. A responsible person checks and approves.
The call gives one of three clear answers.
- 1
Keep it manual
The volume or value is too low, or the task requires judgement every time.
- 2
Simplify first
Clarify the main steps, data and responsibilities before you build.
- 3
Test a limited pilot
When the rules can be described and someone takes responsibility for exceptions, the task can be tested on a small scale.
I build the task behind Bob.
I developed BilagPilot, which finds entries without supporting documents and brings follow-up together. I also build and maintain your workflow.
See BilagPilot
Systems and tools Kevin has worked with
Should this task be automated?
Map one task in 20 minFrom one selected task to a tested workflow.
If a pilot is the right next step, we agree on scope and timeline.
Define the scope
One task, clear boundaries and a measurable starting point.
Build
The first version connects to agreed systems and data.
Test
Real cases reveal exceptions, errors and adjustments needed.
Deliver or stop
You receive documentation and a basis for continuing or stopping.
How collaboration is priced.
- 1
Free discovery call
- 2
A clearly scoped quote
What will be built, the fixed price and what is excluded. Scope and systems determine the price.
- 3
Build at a fixed price
50% at the start and 50% on delivery. If I recommend stopping, the final half is not invoiced.
- 4
Optional operations
Hosting, monitoring, support and improvements are agreed and priced separately.
A twelve-month agreement with three months' notice on either side. You keep the solution and documentation.
Before you book.
01What do operations cost, and can we cancel?
Operations are optional and priced separately. A twelve-month agreement with three months' notice on either side. You keep the solution and documentation.
02Will Bob replace an accountant?
No. Bob is one clearly scoped workflow. Standard steps can be automated, while professional judgement, client responsibility and approval stay with the team.
03Do we need to change systems?
No, not as a starting point. We map the systems the task already passes through and only build when there is a safe, practical way to access them.
04What does the solution get access to?
Only what the scoped task needs. Access, actions, stopping points and logging are documented before starting.
05What happens when there are errors or exceptions?
The task is built with stopping points. Errors and exceptions do not proceed when an action requires judgement. A responsible person reviews the case, and the event is logged.
06What if the task is not suitable?
Then no is the right answer. Discovery may conclude with keeping the task manual, simplifying it first or exploring a limited pilot.
07Is 20 minutes enough?
Yes, to decide whether the task is worth investigating further. Final pricing and results require the systems, data and exceptions to be scoped first.
Which task should Bob try first?
Bring the task that keeps coming back. Twenty minutes is enough to find the next step.
