DE Contact Review your process

Intro

Process readiness: how ready is your process for automation?

Not every process is equally ready for automation. Some run right away, others first need clean rules or a better connection. This readiness assessment checks in a few minutes how ready a concrete process is for automation and gives you a clear score plus the sensible next steps. It deliberately names no prices. It shows you whether a process is a good first pilot or where preparation pays off first.

Contact Review your process

What comes in: Current process, Time per case, Volume, Error rate, Systems, People involved. Assessment. Where it lands: Process list, ROI estimate, Roadmap, First pilot.

Interactive tool

Process readiness

The assessment checks in a few minutes how ready a concrete process is for automation and gives a clear score plus the sensible next steps.

0 = 0, 4 = 4

01 Is the process clearly documented or describable?

0 not at all, up to 4 fully, with steps and exceptions.

02 How stable are the rules?

0 constantly changing, up to 4 fixed and rarely changed.

03 How uniform are the inputs?

0 very varied and unstructured, up to 4 always the same, fixed format.

04 How well are the target systems connected (SAP, CRM, DATEV)?

0 no APIs, up to 4 real APIs for most steps.

05 How high are volume and frequency?

0 rarely, up to 4 high and regular.

06 How measurable is the value?

0 unclear, up to 4 clearly measurable in time and cost.

07 Are there clear owners and approvals?

0 unclear, up to 4 clearly defined.

Your result

0 of 7 questions answered

Answer all questions and your evaluation appears here.

Possible results

  • Not yet ready (0 to 39 %)
  • Partly ready (40 to 69 %)
  • Ready for automation (from 70 %)

How we workServicesProcess ROI calculator

Review your process

This is an orientation without prices. The assessment makes the final evaluation on the real process.

The calculation runs only in your browser, nothing is transmitted or stored.

How the tool calculates
  • Each question is answered on a scale from 0 to 4. The maximum total is 28.
  • Overall score in percent = sum divided by 28 times 100.
  • Readiness levels: 0 to 39 percent "not yet ready", 40 to 69 percent "partly ready", 70 to 100 percent "ready for automation".
  • Weak spots: every dimension with 0 or 1 point is marked as an action field, regardless of the overall score.
  • Question 3 (inputs) and question 4 (integration) are guiding dimensions. If question 3 is low (0 to 1), the note is that AI pays off for unstructured inputs. If question 4 is low, the note is that RPA can step in for interfaces, but real APIs have priority.
  • The one-time implementation effort is not estimated but placed in the assessment.

Assumptions

  • For question 4, "low" means 0 to 1 points, as for question 3.

Want to run the numbers on your own case? Book a slot via our booking calendar, alternatively info@prozessautomatisierung.co.

How the assessment thinks

Readiness comes from several factors: how clearly the process is described, how stable the rules are, how uniform the inputs, how well the systems are connected, how high the volume and how measurable the value. The assessment rates these dimensions individually and combines them into an overall score. So you see not just a number but also which dimension slows a process down.

Questions

  1. Is the process clearly documented or describable?

    (0 not at all, up to 4 fully, with steps and exceptions.)

  2. How stable are the rules?

    (0 constantly changing, up to 4 fixed and rarely changed.)

  3. How uniform are the inputs?

    (0 very varied and unstructured, up to 4 always the same, fixed format.)

  4. How well are the target systems connected (SAP, CRM, DATEV)?

    (0 no APIs, up to 4 real APIs for most steps.)

  5. How high are volume and frequency?

    (0 rarely, up to 4 high and regular.)

  6. How measurable is the value?

    (0 unclear, up to 4 clearly measurable in time and cost.)

  7. Are there clear owners and approvals?

    (0 unclear, up to 4 clearly defined.)

Scoring

  1. Each question is answered on a scale from 0 to 4

    The maximum total is 28.

  2. Overall score in percent = sum divided by 28 times 100.

  3. Readiness levels

    0 to 39 percent "not yet ready", 40 to 69 percent "partly ready", 70 to 100 percent "ready for automation".

  4. Weak-spot detection

    every dimension with 0 or 1 point is marked as an action field, regardless of the overall score.

  5. Question 3 (inputs) and question 4 (integration) are weighted guiding dimensions for the recommendation: if question 3 is low (0 to 1), the note is that AI pays off for unstructured inputs. If question 4 is low, the note is that RPA can step in for interfaces, but real APIs have priority.

  6. Recommendation per readiness level

    "not yet ready" means first do preparation on the marked action fields, then check again. "partly ready" means a pilot is possible, focused on the weak dimensions. "ready for automation" means this process suits a first pilot well.

  7. Output without prices

    The one-time implementation effort is not estimated but placed in the assessment.

  8. Output always with the note that this is an orientation and the assessment makes the final evaluation on the real process.

Output

The assessment clearly shows the overall score in percent, the readiness level and the marked action fields. Plus a plain-text line, for example "This process is partly ready. Strengthen the integration, then it suits a pilot." The guiding dimensions inputs and integration produce the AI or RPA note when needed. One sentence makes clear that no prices are included and the assessment delivers the final evaluation.

From score to pilot

A good score is the starting signal, not the end point. We map the process more closely in the assessment, check the marked action fields, clarify integration and exceptions and propose a pilot whose ROI we prove. So an orientation turns into a result. More on How a project runs, Services for process automation and Process ROI calculator.

Want to see the ROI on your case? Book via our booking calendar, or write to info@prozessautomatisierung.co.

Book a strategy call

Straight into the calendar

Book your strategy call via the calendar: Book a strategy call. Alternatively, reach us by email at info@prozessautomatisierung.co.

Or send an email to info@prozessautomatisierung.co

Review your process

FAQ

What does a low score mean?
A low score does not mean automation is not worth it but that preparation is sensible first, such as clearer rules or a better connection. The assessment shows you exactly which dimension slows things down, so you can improve in a targeted way instead of forcing an immature process.
Why does the check include no prices?
Because the implementation effort depends on the specific process, the systems and the exceptions and cannot be stated across the board. The readiness check rates readiness, not cost. We place the effort in the strategy call on the real process instead of naming a misleading number.
Can I compare several processes?
Yes. Check the main candidates one after another and compare the scores and action fields. That way you find the process that suits a first pilot without much preparation. This prioritization is exactly the point of the assessment.
How does the readiness check relate to the ROI calculator?
The readiness check says whether a process is ready, the ROI calculator on Process ROI calculator says how much it saves. Together they give a good picture: first check whether a process is automatable, then estimate whether it is worth it. Certainty then comes from the assessment.