zavorContact us
← All guides

Guide 04 · 6 min read

Choosing your first AI workflow

A decision framework for selecting a small, repeatable process that can prove value without creating unnecessary risk.

01

The best first workflow is boring

Start with work that is repeated, rules-based and visible. Enquiry classification, quote follow-up, meeting actions, onboarding reminders, document intake and recurring reports are often better pilots than a general-purpose chatbot.

02

Write the workflow in seven lines

  1. TriggerWhat event starts the process?
  2. OwnerWho is accountable for the result?
  3. InputWhat information is required?
  4. Routine pathWhat happens in the normal case?
  5. ExceptionsWhat must stop and go to a person?
  6. OutputWhat record, message or action is produced?
  7. MeasureHow will you know the change worked?
03

Good pilot boundaries

  • One workflow and one accountable owner.
  • A defined set of routine cases.
  • Human approval for financial, sensitive or customer-facing commitments.
  • Real examples for testing, including difficult exceptions.
  • A baseline and target for time, quality and completion speed.
  • A rollback path if the workflow behaves unexpectedly.
04

Avoid these first projects

  • Rare processes with little measurable cost.
  • Work that changes every time and relies heavily on judgement.
  • Processes nobody can clearly explain.
  • High-risk actions with no approval or audit trail.
  • Large integrations before the value of the workflow is proven.
05

Pilot decision

Proceed only when the workflow has meaningful volume, a stable routine path, identifiable exceptions and a result you can measure within 30–60 days.