Skip to content

Audit request

One process, looked at with a fixed scope.

The audit is where an engagement starts. Fixed scope, one process mapped end to end, a ranked list of what can be automated, and written success criteria — which you keep, whether or not we build anything afterwards.

We don’t publish prices because the audit price depends on process complexity; you get a fixed number before you commit to anything.

What the audit produces.

Four documents, written down, in the language you work in.

  1. A map of the process as it runs today

    The current process in BPMN, including the steps nobody documented: the spreadsheet in the middle, the re-keying between two systems, the approval that happens by email.

  2. A ranked list of automation candidates

    Each candidate with the effort it takes, the systems it touches, and the return we would expect — ranked, so the order of work is a decision rather than a preference.

  3. Draft success criteria

    Per candidate: the metric, its baseline today, and how it will be measured after go-live. This is what the work is judged against later, and it is agreed in writing before anything is built.

  4. A recommendation on what not to automate

    Some processes should be fixed rather than automated, and some are still too unstable to automate. You get that in writing too. A consultancy whose recommendation is always to build more has no recommendations.

Request the audit.

The questions below are the ones the first call would otherwise open with. Answered here, it opens with your process instead.

One of us replies within one business day.

Book a call instead.

A short call with one of the two people who would do the work — not a salesperson. Bring one process. Write to us and we will come back with times.

Book a call

About you

We reply in the language you choose here.

About the company

Systems in use (Required)

Tick everything that applies. The specific products go below.

Optional — but it saves a question on the call.

About the process

Describe it as it runs today: where it starts, who touches it, where it gets stuck.

A rough figure is enough.

Constraints, deadlines, an audit that has already been done.

What happens next.

  1. We read the submission

    One of the two founders reads it — not an assistant, not a routing rule. If anything is unclear we come back with questions before anything else.

  2. We hold a scoping call

    Thirty to sixty minutes on the process itself: where it starts, where it ends, who touches it, and which systems it crosses. In German, Romanian or English.

  3. You get a fixed-scope proposal

    Written scope, named deliverables, and the success criteria we would be measured against. If the audit is not the right next step, we say that instead.