What to Build First: The AI Workflows That Pay Off Early

Four jobs make good first AI workflows: an inquiry that gets sorted and answered in draft, documents assembled from your own templates, a weekly report written from your records, and an assistant that answers questions from your own files. Any one of them can be the single job in The First Workflow, which is $7,500 fixed and takes about three weeks.

They have things in common, and the common points are the reason they are worth starting with. Here is each one, and then what to leave alone for now.

How do you choose the first AI workflow?

Look for a job with four traits. It repeats every week, so there is something to see working. It has the same shape each time, so the system can learn the shape. A person can check the result before it matters, so a mistake is caught rather than sent. And the material it needs already exists in digital form, in your email, your documents or your records.

A job that comes up twice a year, or that is a different judgment call every time, makes a poor first choice. So does anything where nobody can say what a good result looks like. If you cannot describe working, you cannot tell whether you have it.

What is intake triage with drafted replies?

A new inquiry arrives by email or through a form. The workflow reads it, sorts it by type, pulls out the facts you need to decide what to do, and writes a draft reply for a person to edit and send. The draft is waiting when your person opens the inbox, instead of the inquiry waiting for them.

Nothing is sent by the workflow. A person reads the draft, changes what they want to change, and sends it. The decision about whether to take on the work, and on what terms, stays with you. What changes is that nobody is starting from a blank page, and that no inquiry sits unread for days because everyone was busy.

What is document assembly from your own templates?

Many firms write the same few documents over and over: an engagement letter, a proposal, a notice, a confirmation. Each time, someone opens the last similar one, changes the names and dates, and hopes they caught everything.

In this workflow the documents are assembled from your own approved templates and from facts you have already collected, so the draft arrives complete and in your voice. It waits for review. Nobody retypes a document that already exists in ten earlier versions, and the template stays yours: we build around what you already use.

What is a weekly report from your records?

Somebody in your business writes a summary every week or month: open matters, new inquiries, invoices outstanding, what is due next. It takes an hour or two and it is always the same kind of hour.

This workflow reads the records you already keep, writes the summary in plain language, and puts it in front of the person who sends it. The figures come from your records, not from the model's imagination, and the person reads it before it goes anywhere. You get the Friday summary without anyone staying late to write it.

What is a records assistant with a review gate?

An assistant that answers questions from your own documents. A colleague asks what your standard terms say about late payment, or what was agreed on a particular file, and the assistant answers from the documents and names the document it used. When the documents do not settle the question, it says so and passes the question to a person.

The review gate is the important part. Anything that leaves the business, such as an answer to a client, waits for a person to approve it. Which records the assistant may see is a decision for you, made on purpose and written down before anything is connected. If you are in a profession with rules about client confidences, whether a particular setup meets them is a question for your own counsel.

Where does the person stay in charge?

At the point where something leaves your business. In each of the four workflows above, the system prepares and a person decides. The reply is a draft until someone sends it. The document waits in a review folder until someone approves it. The report goes to one person who reads it before it goes to anyone else. The assistant's answer to a client is held until someone signs off.

That design is deliberate, and it is also what makes a first project calm. Your people are not asked to trust a machine. They are asked to look over a draft, which is a job they already know how to do, and to say yes or change it. Over a few weeks you learn how often the drafts are right, and you decide how much you want to hand over next.

What should you not build first?

Anything that sends, files, signs or pays on its own. A first workflow prepares work and a person decides. Leave out any job that depends on records that are not in order, because the system will only be as tidy as the files it reads. And leave out any job you cannot describe. If your team disagrees about what a good result looks like, settle that first.

None of this means those jobs are off the table forever. They are better second projects, after you have seen one workflow behave and your people trust the approval step.

How will you know the workflow is working?

Decide before we build. We agree in writing what working looks like, run the workflow on your own real examples, and show it to you working before we hand it over. That gives you something concrete to judge, instead of a promise.

We cannot tell you how much time a workflow will save you. What you will have is one job that runs, a plain-English guide to what it does and how to turn it off, and a clear view of whether you want a second.