Skip to content

Your first useful AI workflow.

Ten working days to turn one repeated process into a tested prototype and a clear production decision.

Start with work you can describe.

For operations leaders with a repeated task, an available business owner and access to representative examples. Customer-operations requests are one useful starting point.

A workflow and baseline

Map the current task, systems, exceptions and owner. Agree the measures: handling time, output quality, review effort and operating cost.

A working prototype

Build one bounded workflow using approved sample data. Show the evidence, decisions and human handoffs, then test it with your operators.

A build decision

Deliver the findings, prototype code, evaluation results, integration plan and a separately costed production proposal. Stop, revise or move to a pilot.

A bounded engagement.

  1. Days 1–2

    Map the workflow, inspect sample quality and agree the acceptance criteria.

    Owner and baseline
  2. Days 3–7

    Build the prototype and review the evidence and handoffs with your operators.

    Working prototype
  3. Days 8–10

    Run the agreed evaluation, document limits and present the production options.

    Decision and handover

Timing starts after scope, access and sample data are agreed. Production rollout is a separate engagement.

Before we start.

What do we need from you?

A business owner, a technical contact, operator feedback and representative examples you are authorised to share. Agree data handling and environment access before any transfer.

What fits in the sprint?

One workflow, one operating team, approved sample data and one prototype environment. Live write integrations, full migration, round-the-clock support and a company-wide rollout require separate scope.

How do we price it?

We agree a fixed fee and written scope before work starts. Model and third-party costs, ownership and delivery conditions are stated in the proposal.

What happens after ten days?

You receive the work and a recommendation. A production pilot proceeds only with an agreed owner, integration scope, acceptance criteria and budget. If the workflow is a poor fit, the findings should say so.