A 20-minute call. A written map in 48 hours. The first system live in 14 days. Here is exactly what happens at each stage, and what the guarantee covers if month one falls short.
€399, one-time assessment fee. You keep everything from the call whether or not you proceed.
You walk through your three highest-volume workflows
Not the org chart version. The real one. What actually happens from trigger to completion, including every decision point, every handoff, and every place things go wrong.
Krister maps every step as you describe it
Every input, every decision, every tool the workflow passes through. The map is built in real time, on screen, as you talk. By the end you can see the whole workflow as a single document.
Three time-sinks are named
The specific steps where the most hours are spent on work that does not require a human judgment to complete. These become the build targets.
You see exactly what a system would do at each point
Not in general terms. Specifically: what the system receives, what it does, and what comes back to your team. This is the basis for the written proposal.
After the call, Krister documents everything: the workflows as you described them, annotated with the three identified bottlenecks, time estimates for what your team currently spends on each task, and a specific proposal covering what gets built, in what order, at what cost, and the measurable output target for day 30.
You keep this document regardless of whether you proceed. The map has value on its own. Most principals who read it decide within 24 hours.
Written workflow map
The process as you described it, documented step by step and annotated with the three identified bottlenecks.
Time estimates
Hours per week your team currently spends on each identified task, calculated from what you described in the call.
Written proposal
What gets built, in what order, how long it takes, what it costs, and what the measurable output target is for day 30.
The first build is narrow by design. One workflow, done properly, integrated into the tools your team already uses. Running on real work by day 14. Total time commitment on your side: two to three hours across the full build.
Access handover
You share access to the relevant tools: the email inbox, CRM, scheduling platform, wherever the workflow lives. This is the total technical involvement required from your side. One to two hours, at a time that suits you.
Krister builds and integrates
Days 2 through 10. The system is built, connected to your tools, and tested against real examples from your workflow. No new software required in most cases. No migration. An addition to how the work already flows.
You review the first run
30 to 60 minutes. You check the output against what you expected. Krister adjusts based on what you see. This is the only review session required before the system goes live.
Day 14: live on real work
The system processes real work from your team. The first workflow runs without the manual step that used to sit in its place.
After month one, the relationship is a managed service. The systems already built keep running. Krister monitors them, receives alerts when something drifts, and addresses it before it becomes a problem for your team.
Work also continues on the third and fourth workflow, in the same order of priority as the first two: highest volume first, highest time cost first. The ongoing retainer covers monitoring, adjustments to existing systems, new builds, and direct access to Krister when something changes in the business.
One service, one price. No separate charges for additional workflows. No premium tier for faster response. If a system breaks, fixing it is part of the service.
The benchmark is a number, attached to a workflow, agreed in writing before the build begins. Not assessed after the fact. On day one of the engagement, you and Krister agree a specific measurable target for the first system. For a recruitment desk: the CV screener processes the full weekly intake and surfaces only candidates who meet the brief. For an estate agency: every enquiry received outside office hours gets an initial response within 90 seconds. The number is specific. The workflow is specific. This is the structure of every engagement, not a promotional offer.
Measurable output in the first 30 days, or the first month is free.
You do not need to be. The audit call is about how your team works, not about technology. You describe what happens. Krister maps it. The only technical step on your side is granting access to the tools you already use, which takes one to two hours and does not require any technical knowledge.
Show up to the 20-minute call and describe how your team works. After that: two to three hours total for access handover and one review session. Everything else is handled. The system does not require ongoing management from your side once it is running.
Month one is free. The benchmark agreed before the build begins is the measure. If the system does not hit it by day 30, you are not charged for the first month. The guarantee is the answer to this question, not a marketing claim.
Week two. The first system is live and processing real work in 14 days. Not week six, not after a pilot period. The first build is narrow precisely so the timeline is this short. You can see what the system produces before the end of the second week.
The engagement is month to month after the first month. No annual contracts, no lock-in beyond the initial period. If you want to end the service, give notice before the next billing date and the systems are handed over in a documented state. You keep everything that was built.