Start with one workflow

Describe the workflow

The button above opens a message with these three prompts already in it. Three or four lines against each is plenty. There is no form on this page and nothing to fill in.

• The workflow we would start with

  In your own words, the way you would describe it to a new joiner. The one that annoys you most is usually the right one, and the awkward exception is worth a sentence of its own.

• What it costs us today in hours a week

  A rough figure is fine at this stage. How many people touch it, and roughly how long each of them spends. The diagnostic counts this properly; we only need a sense of the size.

• Who owns it internally

  The person whose week gets better if this works, and who can say what the rules are. If the answer is that nobody clearly owns it, say that too. It is useful to know.

What happens next

A person reads it and replies. Sending this message does not book anything, and there is no calendar behind the button.

• We reply with questions, or with a straight no

  If the workflow is not a fit, we say so and say why. Work that is genuinely judgement based, or that changes shape every time it runs, is work we would tell you not to automate.

• A conversation, then a proposed diagnostic

  If it looks like a fit, we propose the two week diagnostic: eight to twelve workflows mapped and costed beside your team, and a ranked backlog with an expected payback against each one.

• The commercial shape is fixed and stated early

  A fixed fee for the diagnostic, credited against the first build. A fixed price per agent and a monthly fee to run it. Numbers are set after the diagnostic, and the reasoning is on the how it works page.

Where we work

We work with clients wherever their operations are, and we run engagements remotely with on-site time when a workflow needs it.