Skip to main content

Workflow Assessment

When the workflow needs a closer look.

A Workflow Assessment is one option when uncertainty about the work blocks a useful decision. It is not a required first purchase. We agree the question, scope and terms before investigating.

Schedule a meeting
01Purpose

Use an assessment when the uncertainty warrants it.

First we discuss fit, worthwhile outcomes and what would show progress. If substantial client-specific diagnosis is needed, we scope it as paid work, separate from that brief conversation. An assessment may help us decide whether a process change, existing tool or custom software is justified. If enough is already known, we can agree implementation without an assessment. See how we choose the next commitment.

Not a vague discovery phase

Scope
One workflow, real examples, named systems, named owners, and a desired business outcome.
Recommendation
The assessment includes one primary recommendation, not a menu of equally weighted possibilities.
02Preparation

Bring reality, not a wish list.

You do not need a finished brief to get in touch. If we agree an assessment, we help choose the examples and evidence needed. The assessment works best when it starts from actual cases. Abstract requirements tend to hide the awkward parts. Real examples reveal missing context, review habits, exceptions, handoffs, and the judgment calls that decide whether automation is appropriate. Read why you should bring real examples, not abstract requirements.

Preparation we agree together

  • Agree the workflow to inspect
  • Gather useful real examples together
  • Include supporting artifacts
  • Identify the people involved
  • Name the systems involved
  • Describe the desired business outcome
03Deliverables

What you get back.

We agree the outputs around the decision you need to make. These are useful starting points, not a universal package. Our earlier writing explains the idea behind a decision packet.

Workflow map

A plain-language view of the people, systems, inputs, outputs, decision points, and failure modes.

Bottleneck analysis

An explanation of what actually limits performance: waiting, context switching, poor documentation, missing information, approvals, duplicated effort, or manual repetition.

Intervention recommendation

One primary recommendation: agent, conventional software, existing product, workflow change, documentation, hiring, more data, or no action.

Next commitment

A recommendation on whether further work is worthwhile. Any implementation scope and commercial terms are agreed separately.

04Possible Answers

An agent is one possible answer.

The point of the assessment is not to force every problem into an AI shape. It is to identify the highest-leverage next step. That means being explicit about when not to build an agent.

Recommendation may be

  • Build an AI agent
  • Build conventional software
  • Buy an existing product
  • Change the workflow
  • Improve documentation
  • Hire differently
  • Do nothing for now
05What Follows

Evidence informs the next decision.

If the recommendation is custom work, the workflow map, evidence, risks, and acceptance cases carry directly into the build scope. If the recommendation points somewhere else, you still have a workflow map, bottleneck analysis, and decision brief you can use internally or take to another builder.

What a build includes

Fixed scope
A defined objective, deliverables, exclusions, acceptance criteria, and timeline.
Responsibilities
We lead technical judgment and hands-on execution. You provide access, operating knowledge and consequential business decisions. Any ongoing support is agreed explicitly, not included by assumption.