Rate your process in 5 minutes
Answer 5 short questions about your process and receive a detailed analysis with concrete recommendations
Process Basics
Let's start with basic information about your process
Process Category *
How large is your company in total?
Helps us judge whether this process pays off at your organisation size.
What the bottleneck assessment asks — and why
The assessment looks at exactly one process, not your entire company. Across five steps it captures how often the process runs, how much time it ties up, how standardized it is and how far the systems involved are digitized. From that it derives an automation readiness score, a maturity level and a position in an effort-versus-impact matrix. The questions in detail:
1. Process Basics
Let's start with basic information about your process.
- Process Name
- e.g. Invoice Processing, Customer Orders, ...
- Process Category
- Core (Core Business), Support (Supporting), Enabling (Enabling).
- How large is your company in total?
- Helps us judge whether this process pays off at your organisation size.
2. Frequency & Volume
How often and how much is this process executed?.
- How often does the process run?
- Daily, Weekly, Monthly.
- Number of runs per day
- Example: For 10 invoices per day → 10
3. Time & People Involved
How much time is needed per run?.
- Time per run (minutes)
- How long does a single run take on average?
- Number of people involved
- How many people are involved per run on average?
- Average hourly rate per person (optional, for Euro calculation)
- Fully loaded cost (incl. overhead) of the people running the process. If left blank we show hours only.
4. Standardization & Quality
How standardized and error-prone is the process?.
- Is the process documented?
- Yes or no. Without documentation there is no reliable description of what would be automated.
- Are there clear rules and standards?
- Yes or no. Rules that live only in people's heads cannot be translated into a workflow.
- How error-prone is the process? (1 = very low, 5 = very high)
- Error-proneness raises the value of automating — and at the same time the effort for handling edge cases.
5. Automation Readiness
How ready is the process for automation?.
- Are all involved systems digitized?
- Yes — All digital. No — Partial/Paper.
- Are there many exceptions or special cases?
- Yes — Many exceptions. No — Standardized.
How the result is produced
Three figures are derived from your answers, and together they carry the actual verdict: the maturity of the process, its position between effort and impact, and a score that condenses both into one number.
Maturity Level
Maturity describes how dependable a process is today. A level 1 process cannot usefully be automated — automation would only make the chaos run faster.
- Level 1: Ad-hoc — Chaotic, no standards
- Level 2: Defined — Process documented
- Level 3: Standardized — Consistently executed
- Level 4: Measured — KPIs are tracked
- Level 5: Optimized — Continuous improvement
Prioritization
Not every automatable process deserves to be tackled first. Effort and impact produce four fields:
- Quick Wins — High impact with low effort - perfect for quick wins!
- Strategic — High impact justifies the effort - strategically important
- Later — Low impact - plan for later
- Avoid — High effort with low impact - not recommended
Automation Readiness Score
The score condenses every answer onto a scale from 0 of 100. The five bands mean:
- Excellent — Outstanding! This process is optimally prepared for automation. All important prerequisites are met.
- Good — Good starting point! The process is well suited for automation. Some optimizations recommended.
- Medium — Medium potential. The process needs preparation before automation. Focus on standardization.
- Low — Low score. Significant optimization required before automation can begin. Build foundations.
- Very Low — Very low score. The process is not yet ready for automation. Fundamental process improvement needed.
What you get at the end
The result is an assessment, not a quote. Alongside score, maturity and prioritization it contains an estimated time saving per week and per year, a rough implementation duration and a list of concrete preparatory steps. Typical recommendations are:
- Document process completely (Process Mapping)
- Define clear rules and standards
- Conduct bottleneck analysis
- Optimize process BEFORE automating
- Digitize and integrate systems
- Identify and eliminate error sources
- Standardize exceptions or define separate process
- Evaluate automation potential
- Define and continuously measure KPIs
Estimated implementation duration ranges from 1-2 weeks to 2-4 weeks or 1-3 months, depending on complexity.
No warranty: The values shown are based on your own answers and industry averages. They serve as a first orientation, not as an individual analysis or a binding forecast. For a reliable assessment we recommend a short call.