Start with an SOP, a loose checklist or someone who can show us the job. The know-how does not need to be documented first. These checks are about whether the work has a useful, testable role for AI.

  1. Who uses it, and who sets the standard?Name the person who will run the workflow, the person who approves its output and the person whose work sets the standard. One person may fill more than one role. Make sure they can take part in the build and testing.
  2. What starts the job, and what should come back?Write the trigger and the finished output: a closed deal becomes an onboarding checklist; an export becomes a weekly exception report. Ask your best person what makes a good result. That is the beginning of the standard we will build to.
  3. What will the workflow need each time it runs?List the files, records and exports needed for the job, and where they live. These are the inputs for each run; your SOPs and expert's know-how supply the instructions. A first sprint uses files and exports your team can already bring into its workspace. Any new integration is separately scoped.
  4. Where does the work need judgment?List the main exceptions and the rule for each. Which can the workflow handle, and which need a person? Decide when it should stop and ask. A missing billing contact and an unfamiliar customer arrangement may need different responses.
  5. How will you know the result is good?Have past cases ready, including awkward ones with missing information or an unusual format. Note what a good result contains. Your person runs these in your own account while we observe; we don't receive copies. We use invented examples for the build.
  6. Is the workspace ready for the team and the information?Confirm your ChatGPT, Claude, Copilot or Gemini plan, who can access the workflow and who approves this use of the information. A subscription alone does not settle those questions. Your business must approve the data use before work starts, including any sensitive information.

Establishing a function you do not yet have? Build what's missing starts with selected methods and templates tailored to your business. Bring the capability you need to the fit call.

When the clock starts.

The $750 3-Day Workflow Sprint starts once your agreed written procedure, examples, people and workspace are ready. The $3,500 2-Week Team Sprint runs about two weeks from the first interview, after readiness is confirmed. It captures one team's procedures and builds one priority workflow.

For either, the user and approver need time booked, real examples ready in your account, team access checked and data use approved. Both are introductory offers, once per client.

What your answers tell us.

A clear, agreed procedure can go straight to a build. Know-how that needs capturing can be addressed in the Team Sprint or a broader implementation. If the work needs redesign, or a feature you already own is the better answer, we'll identify that before agreeing a sprint.

If nobody can yet describe a good result, start there with the person who owns the work. They choose the standard; we help make it clear enough to build and test.

In a law firm.

Confirm that the responsible lawyer sets the review standard, the firm approves this use of client information in its workspace, and the firm approves our builder seeing real examples on screen during testing. We keep no copies of those records. Your lawyers interpret the firm's professional obligations.

Before we start, in a law firm

Bring the work, even if some answers are missing.

The fit call turns these checks into a practical next step. In 30 minutes, we'll talk through one recurring job, identify what to settle and recommend where to start. Bring the person who knows the job, and involve the person sponsoring the work before we write a proposal.