The AI Marketing and Systems Playbook

Chapter 01

See the recurring work

Most owners underestimate how much of their week repeats. The work is spread across inboxes, calendars and memory, so it never appears in one place. Before choosing anything to change, write it down by stage. Spend twenty minutes with last month's sent email and calendar and note every task that happened more than twice.

Walk a typical customer from first contact to repeat business and list what happens at each stage:

Lead intake

New inquiries arrive, get acknowledged, sorted and routed to the right person.

Quote follow-up

Sent estimates get a check-in, answers to questions and a clear next step.

Onboarding

New customers receive welcome details, forms, scheduling and what to expect.

Delivery updates

Customers and the team hear about progress, changes and completion.

Invoice follow-up

Unpaid invoices get reminders on a schedule, with exceptions handled by a person.

Marketing review

Someone looks at inquiries, reviews, campaigns and content on a regular rhythm.

For each task, note how often it happens, who does it now and what goes wrong when it is late. You are not judging anything yet. You are building an inventory. The downloadable CSV inventory has a row for each stage to get you started.

Chapter 02

Choose one small workflow

The first workflow should be small, frequent and low risk. A good candidate happens at least weekly, follows a recognizable pattern, has one clear owner and produces something a person can check in a few minutes. If it goes wrong, the cost should be an awkward correction, not a lost customer or a legal problem.

Avoid starting with anything that moves money, makes commitments to customers, changes prices or involves sensitive personal information. Those can come later, after you have a working method and evidence that it holds up.

Write the choice as one sentence: when this happens, this work gets done, and this person checks it. For example: every Friday afternoon, a draft of the weekly project update is prepared from current notes, and the project lead reviews it before it goes out. If you cannot write that sentence, the workflow is not ready to hand off yet. Pick a smaller piece of it.

A useful test is to imagine being away for two weeks. Which recurring task would you most want handled the same way you would handle it, with a short note waiting when you return? That task is often a better first choice than the one that feels most urgent today, because you already know what good looks like.

Score each candidate on your shortlist quickly: how often it happens, how much time it takes, how clear the pattern is and how bad a mistake would be. You do not need a formula. The point is to compare a few options side by side and choose deliberately rather than starting with whatever is loudest.

Chapter 03

Rules, AI drafting and human decisions

Not every step in a workflow needs AI, and not every step should use it. Separate the work into three kinds before building anything.

Rules automation

Predictable steps with a fixed answer: when a form is submitted, create a record and send the acknowledgment. When an invoice is fourteen days past due, send the scheduled reminder. Ordinary automation is suitable for fixed rules, but still needs exception handling and testing.

AI drafting and sorting

Steps that need language or light judgment on familiar material: summarize call notes, draft a follow-up from the quote and the customer's question, suggest which category an inquiry belongs to. The output is a draft or a suggestion that someone can check.

Human decisions

Steps that carry responsibility: pricing, discounts, refunds, scope changes, complaints, anything a customer will treat as a promise. A person decides. AI can prepare the information, but the decision and the send stay with a named owner.

Label each step in your chosen workflow with one of the three. Many workflows turn out to be mostly rules, with one drafting step and one decision. That is a good outcome. It means the AI part is small enough to review properly.

Chapter 04

Name the sources and owners

A draft is only as good as the information behind it. For each workflow, list the authoritative source for every fact the work depends on: the current price list, the service area, the project notes, the customer record, the approved wording for policies. Authoritative means it is the version you would defend if a customer questioned it.

Give each source an owner, the person who keeps it current. When the price list changes, who updates it? When a policy changes, who edits the approved wording? A source with no owner goes stale, and stale context produces confident, wrong drafts.

Also note what the workflow should never use: old proposals, personal inboxes, notes from a different customer. Writing down the excluded sources prevents the most common mistakes before they happen.

Keep the list short and visible. A single page that says where each fact lives and who owns it is more useful than a large folder nobody opens. When someone asks why a draft said what it said, this page should answer the question.

Chapter 05

Set approval boundaries

Approval boundaries say what the workflow may do on its own, what needs a person to approve first and what it must never do. Write them in plain language that anyone on the team could follow.

May do

Prepare drafts, gather information from approved sources, create internal tasks, send pre-approved acknowledgments.

Needs approval

Anything sent to a customer that is not pre-approved wording, anything that mentions dates, amounts or scope.

Never

Change prices, promise delivery dates, issue refunds, delete records or reply to complaints without a person.

Name the approver and a backup. Decide how they will be asked and how quickly they need to answer. If approval is slow or unclear, people will skip it, so make the request easy to answer with yes, no or a correction.

Chapter 06

Test five situations

Before you rely on a workflow, test these situations in a staged or simulated setup, or with harmless approved examples. Never intentionally break production, alter live source records or send test messages to real customers. Record what happened each time and what you changed.

Happy path

A normal, complete example. Does the output match what a careful person would produce?

Missing input

Remove a required detail from the test example. The workflow should stop and ask, not guess.

Conflicting sources

Put two different answers in simulated sources. The workflow should flag the conflict and name the authoritative source, not pick one quietly.

Duplicate or repeated request

Repeat the same test request twice with any customer send disabled. The workflow should recognize it and avoid doing the work or contacting the customer twice.

Failure

Simulate a failed step, such as an unavailable source or a rejected approval. Someone should be told, and the work should not be marked done.

Keep a short test log: the situation, what you expected, what happened and the fix. Repeat the tests after any change.

Chapter 07

Hand off with a receipt

A handoff is finished when the owner can see that the work was done correctly without redoing it. Every run should leave a short receipt: what was done, which sources were used, what was approved and by whom, and anything flagged for attention.

The receipt helps you review the work without redoing it. At first, review every receipt. Move to sampling only when the workflow's risk allows it and the responsible owner has documented approval, including what to sample and which exceptions still need individual review. Several weeks of correct receipts alone are not enough. When something looks wrong, the receipt shows where to look.

Tell the people involved what changed: who now owns the workflow, where receipts appear and who to contact when something looks off.

Chapter 08

Review health and change safely

Workflows drift. Prices change, staff change, customers ask new questions. Put a recurring review on the calendar, monthly to start, and check a few things: Did it run every time it should have? How many runs were flagged or corrected? Are the sources still current and still owned? Has anyone started working around it?

Change one thing at a time. Write down what you are changing and why, rerun the five tests and keep the previous version of any instructions or templates so you can go back. If the workflow stops being useful, retire it on purpose and tell the people who relied on it.

Watch for quiet signs of trouble: approvals that are always granted without reading, receipts nobody opens, or a team member who keeps a private spreadsheet to double-check the work. Each one tells you something about trust, and each is easier to fix early than after the workflow has been ignored for months.

Once one workflow is stable, return to your shortlist and choose the next one. The method stays the same, and each round is usually faster because your sources, owners and approval habits already exist.

Orientation, not a full workbook

Four sentences to describe your workflow

Fill in the brackets for the workflow you chose. If any sentence is hard to finish, that is the part to work out before building anything.

• When [trigger], [work] is prepared, and [owner] checks it.
• This work uses: [authoritative sources and their owners]. It never uses: [excluded sources].
• It may [actions]. It needs approval to [actions]. It never [actions].
• Done means [evidence], recorded in [where receipts appear].

Free tool

Workflow shortlist

List the recurring tasks you noticed, then choose one as your first workflow. Choose it yourself: small, frequent, low risk and owned by one person.