Free tool  ·  7 questions  ·  Private to your browser

Which workflow should you automate first?

Most automation programs stall by starting with the wrong workflow — too many exceptions, the wrong system of record, or a compliance constraint discovered at Week 4. Seven questions identify where to start and which engagement path fits, using the same routing logic a discovery conversation applies.

Your answers are evaluated in your browser and are never sent anywhere unless you choose to have a tailored read emailed to you. The recommendation is a starting point for a conversation — not a scoped proposal.

How to read your result

An honest routing, deliberately

What it is

The routing logic a discovery conversation applies, in a form you can run yourself: whether your situation calls for a diagnostic first or a single governed workflow taken straight to production — and whether the data involved requires the evidence layer. It names the answers that drove it, so the logic is transparent.

What it is not

Not a scoped proposal, a price, or a commitment. It cannot see your exception rates, your integration surface, or what your compliance team will actually approve — the three things that most often re-order the “obvious” starting workflow. Scoping happens in the engagement, against reality.

FAQ

About this tool

Nowhere, unless you choose to send them. The finder evaluates your answers locally in your browser. Your answers are only transmitted if you fill in the optional form to have a tailored read emailed to you — and even then, please don’t include regulated data in free-text fields.
Three signals decide it. If several workflows compete, the systems are unclear, or the time cost has never been measured, the honest starting point is a diagnostic — mapping before building. If one workflow is well-defined with a known system and a clear output, it can go straight into a production engagement. And if the data involved is regulated — PHI, MNPI, privileged content, claimant or student records — the evidence layer applies regardless of path. The result names which of your answers drove the routing.
Because a menu is not a recommendation. The catalog of workflow patterns we maintain is a discovery instrument, not a storefront — what matters is which single workflow reaches production first in your environment, under your constraints. Sequencing is most of the value; a list would hide it.
Whatever you choose. Run the ROI calculator to put an annual figure on the workflow, request the tailored read by email, or bring the result to a consultation — a senior practitioner responds with a preliminary read on feasibility and sequencing. There is no automated follow-up sequence.
Next step

Turn the routing into a plan

Bring the workflow this tool surfaced — or the one it ruled out — to a short conversation. We respond with a preliminary read: whether it is the right first workflow, what the compliance path looks like, and what production would take.

Request a consultation Price the workflow first  →