Insights

How to brief an AI automation project

The brief for an AI project is not “add GPT.” It is a workflow diagram with a success number. Without that, you are buying a prompt, a licence, and a demo that worked on the vendor’s laptop.

We use this checklist on every AI workflow we take. If you cannot fill it in, you are not ready to automate , you are ready for a discovery week, which is cheaper than a failed production rollout.

Name the input and the output

What arrives (email, PDF, form, ticket, WhatsApp, a row in a sheet)? What must leave (CRM fields, a draft reply, a classified queue, a JSON payload into an ERP)? If you cannot name both, you are not ready to automate. “Make it smarter” is not an output.

Write one example of a good input and a good output. Then write one ugly example. The ugly one is the real project.

Put a human where the model is wrong

Every production workflow we ship has a review step on low-confidence or high-cost actions. Automation without a checkpoint is how you send the wrong invoice at scale, or tell a customer something your policy does not allow.

The human does not need to review everything. They need to review the cases where being wrong is expensive. Confidence thresholds, sampling, and an audit log are part of the product, not extras.

Pick one metric

Minutes saved per item, error rate versus a human baseline, or conversion of qualified leads. One is enough. Three is how projects never launch because nobody can agree what “working” means.

Baseline it before you build. If you do not know how long a human takes today, you cannot claim the model saved time tomorrow.

Data, region, and tools

Can the content leave your region? Is there a system of record the output must land in? If the answer is a CRM, an ERP, or a commerce platform, this is also an integration project. The model is a step. The destination is the architecture.

We will not train a foundation model. We will use proven models, EU-hosted when required, with retrieval over your own documents when the job is Q&A. If you need a strategy deck with no build, we are the wrong studio.

A one-page brief you can send

  • Input (and an ugly example).
  • Output (and where it lands).
  • Human checkpoint.
  • One metric and a baseline if you have it.
  • Volume per week.
  • Region / data constraints.

Send the input, the output, and the metric. We will tell you whether that is a workflow in weeks, a discovery sprint, or not us.