See the process clearly before you pay to automate it.
I reconstruct one recurring piece of work from real cases, show where your judgement belongs and set a practical build boundary.
The work repeats, but the useful version still changes depending on who asks you.
An enquiry arrives. Someone checks an old email, asks you which template applies and waits while you reconstruct the rule. The work is familiar, yet it has no stable route.
A Blueprint makes the route visible before software hardens the wrong behaviour. Recent examples matter more than a polished procedure because the awkward case usually exposes the real decision.
Processes with this shape
- Enquiry handling and qualification
- Proposal preparation and approval
- Client or employee onboarding
- Recurring reporting and follow-up
- Invoice preparation and accounting handover
The map is built from evidence the business already has.
One ordinary case shows the route. One awkward case shows where the route stops being real.
- Recent case
- The messages, records and handoffs from work that actually finished.
- Awkward case
- A missing input, unusual promise or late decision that changed the route.
- Owner decision
- The point where your judgement changes price, risk, quality or customer expectation.
- Completion
- The observable state that lets the next person begin without reconstructing the work.
When this engagement fits
The repeated work should already be real enough to examine.
- The same work returns every week or month
- People need private context before they can move
- The process changes depending on who handles it
- You want to improve the work before choosing software
How the engagement moves
Usually one to three weeks, depending on access to real cases and the people who own the decisions.
Bring recent cases
I use ordinary work and one awkward example instead of designing from memory.
Reconstruct the route
I trace inputs, handoffs, decisions, waiting and recovery as they happen now.
Settle the rule
You settle the business judgement; I show what can move automatically and what another person can own.
Choose the boundary
You receive the design and a clear recommendation, whether or not a Build follows.
What leaves the engagement
Each item has a use after the conversation ends. The proposal turns it into a specific delivery and acceptance condition.
- A map of the process as it actually works
- The future route, with decisions and handoffs named
- Rules for ordinary cases and visible exception routes
- A recommendation on what to keep, hand over, automate or remove
- A build boundary that can be priced and tested
Fee, pace and additions stay explicit
- Typical fee
- €1,500–€3,000 fixed engagement
- Pace
- Usually one to three weeks, depending on access to real cases and the people who own the decisions.
- Provider costs
- Licences, hosting and usage charges stay visible and are paid directly by you where possible.
- New additions
- A new rule, branch, integration, process or feature is a separate engagement.
What I need, and what counts as done
From you
- A few recent examples, including one awkward case
- The people who do, approve or receive the work
- Access to the fields and tools involved
- Your answer where the business rule is still unclear
Acceptance
- The start and finish are unambiguous
- Every decision and exception has an owner
- A capable person can follow the route without private context
- A build can be estimated as one bounded piece of work
A Blueprint can lead to automation, a clearer handoff, a smaller process or no build at all. It covers one named process. Another process or a material new branch is separate work.
Where this sits in the service path
- Free starting pointOwner Work Audit
- BlueprintSystemisation Blueprint
- BuildProcess Build
- Process careOngoing Process Care