Starting with one workflow

A read-only AI workflow pilot

A pilot should answer a specific business question with evidence your team can inspect. We start with a bounded workflow, agree what a useful result looks like, and keep decisions and system changes with people.

One question. Three clear stages.

What to bring to discovery

  • One question or decision your team currently works through.
  • Representative exports or sample records, with their source and date.
  • Definitions for the measures involved, such as revenue or margin.
  • An example of a correct result and a difficult exception.
  • The person who can review findings and explain current practice.

I check whether access, coverage and data quality are sufficient before proposing an integration. Sensitive data can be minimized or replaced with agreed samples during early scoping.

First engagement

Define → bounded pilot → review before extending

Proposed engagement · acceptance checks agreed first

  1. Input

    Define

    Agree the business question, representative data, access and how a useful result will be evaluated.

  2. Evidence and validation

    Bounded pilot

    Trace findings to sources, check calculations and surface missing data. Define permissions, review points and a fallback before any actions.

  3. Human review

    Review before extending

    Assess the result against agreed criteria, then discuss implementation and support. The proposal confirms the pilot’s exact price, timing and subsequent terms.

A read-only first engagement. Findings remain subject to human review; later actions require a separate scope and approval path.

Which workflows fit?

Good first candidates repeat often, draw on identifiable data sources, and produce a result that a reviewer can check. Examples include investigating a margin change, reconciling records across billing and CRM, or preparing a lead brief from supplied facts. A fixed calculation or simple rule may be enough for some steps; the pilot tests where an agent adds value.

Browse the synthetic demonstrations to see source references, blockers and review boundaries. They are examples, not customer results or promises about your data.

How the pilot stays controlled

  • A read-only first pass prepares findings without changing source records, sending messages or taking other operational actions.
  • We define the permitted sources, the output format, missing-data behavior and who may approve a result.
  • Any later write action needs a separate scope and approval path.

What you take away

  • A written scope with data definitions and acceptance checks.
  • A read-only prototype with source-linked findings and an explicit list of unresolved cases.
  • A review record against the agreed checks and a recommendation to extend, revise or stop.

When to start with something smaller

If the data has no identifiable owner, a correct result cannot be described, or no one can review the findings, start by clarifying those gaps. If a fixed calculation solves the whole task, use that instead of adding an agent. A first pilot is not suitable for unattended payments or other irreversible actions.

How to evaluate it

  • Agree expected checks

    Before a run, agree a small set of representative cases and expected checks.

  • Trace the evidence

    Review whether the output cites the right source lines, matches known totals, flags missing or conflicting inputs, and leaves uncertain decisions for a person.

  • Record measurements

    Record reviewer corrections, elapsed time and operating cost where measurable.

  • Review against criteria

    A pilot succeeds only against criteria agreed for that workflow; its results do not imply the same outcome elsewhere.

Have a workflow to investigate?

Tell me what needs checking, which tools hold the data and who reviews the result. We can scope a small pilot around that process.

Discuss your workflow