Duncan Anderson

AI Readiness Sprint

Ten business days to map one costly workflow, decide where AI helps and where people stay in charge, and leave with a pilot you could start next month.

  • From CAD 6,500, fixed before we start
  • 10 business days
  • 50% to start, 50% at readout
  • English or French

Six things you keep

  1. Workflow map

    Current state end to end: steps, handoffs, systems, volumes and where time goes.

  2. Intake and status schema

    The fields and states a system would read and write, agreed with the people who do the work.

  3. Exception taxonomy and decision rights

    What goes wrong, how often, and who is allowed to decide each case.

  4. Review-first prototype spec

    Exactly what AI drafts, what a person approves, and what is never automated.

  5. Pilot and measurement brief

    Scope, baseline, success metric, stop conditions and a fixed-fee build quote.

  6. Executive readout

    Findings and a clear build / don't-build recommendation, with one round of revisions.

How the ten days run

  1. Days 1–2 · Map

    Interviews and walkthroughs with the people who do the work.

  2. Days 3–5 · Diagnose

    Volumes, exceptions, systems access and decision rights.

  3. Days 6–8 · Design

    Prototype spec, schema and pilot brief.

  4. Days 9–10 · Readout

    Executive readout, recommendation and revision.

Good fit / Not a fit

Good fit

  • One workflow costs your team hours every week
  • The work runs through email, spreadsheets, PDFs or a line-of-business system
  • Someone senior can own the decision to pilot

Not a fit

  • You want a chatbot on your website
  • You need a platform migration or an ERP rollout
  • There is no one who can give 3–4 hours across the ten days

If the answer is build

The pilot is quoted as a fixed fee in the pilot brief, scoped to one workflow and one team, with a handoff and runbook at the end. No retainer is required.

Questions

What happens to our data?
It stays in systems you control wherever possible. I work with the least access the job needs, I don't train models on your data, and I document every place data moves before anything is built.
Who owns what you build?
You do. Code, prompts, configuration and documentation are handed over at the end of every engagement.
What if the sprint says don't build?
Then you've spent ten days, not a quarter, finding out. You keep the workflow map, the exception list and the recommendation.
Do you work in French?
Yes. Discovery, delivery and documentation in English or French.

Send workflow details

A few plain sentences is enough. Current tools, volume, or urgency can go here if they matter.

Used only to assess and reply to this request. Do not include credentials or sensitive client records.