What Counts as One Workflow (and Why It Matters Before You Sign Anything)

"How many workflows do we get?" is usually the first question a firm asks about automation pricing. It is a reasonable question, and it is almost impossible to answer honestly unless everyone agrees on what a workflow actually is first.

The Definition

A workflow is a single end-to-end process with a defined trigger, a defined completion state, and one system of record.

That is a precise definition on purpose. Each piece matters:

• A defined trigger — something specific happens that starts the process. A new lead arrives. A signed retainer comes in. A treatment record gets requested.
• A defined completion state — the process has an endpoint where it is unambiguously done. Booked or declined. Sent or not sent. Logged or not logged.
• One system of record — the outcome lives in one place, not scattered across an inbox, a spreadsheet, and someone's memory.

An Example, and a Non-Example

New lead received, qualified, contacted, booked or declined, logged — that is one workflow. It has a clear trigger (the lead arrives), a clear completion state (booked or declined), and one system of record (the case management system).

Monitoring cases for treatment gaps is a *different* workflow, even though it touches some of the same case data. It starts and finishes in a different place: the trigger is a scheduled check rather than a new lead, and the completion state is a flag raised or cleared rather than a booking.

This is the distinction that gets blurry in casual conversation and expensive in a contract. "Automate our intake" sounds like one thing. It is usually at least two or three separate workflows once you write down the actual triggers and completion states.

Why We Name Them in Writing First

Every Workflow Deployment engagement starts with the three workflows named in writing, using this exact definition, before any work begins. Not because we expect a dispute — because vague scope is where disputes come from, and a clear definition removes the ambiguity before it has a chance to matter.

It also protects the firm from the opposite problem: a vendor bundling ten shallow automations together and calling it comprehensive coverage, when what the firm actually needed was three built properly. Additional workflows beyond the three are priced individually and quoted at the audit stage — not discovered, and re-negotiated, halfway through a build.

What This Looks Like in Practice

A Case Operations Audit identifies which processes in your pipeline are costing the most, in time or in leaked cases. Those get written up as discrete workflows using the definition above. Then we build the three that matter most, integrated with the case management system you already run, with a human review step in every path that touches a client outcome.

The precision is not bureaucracy. It is the difference between a scope you can hold someone to, and a scope that quietly grows until nobody remembers what was originally agreed.