Requirements — Process mapping and automation

You can start writing workflows down today. Running them through AI needs the other checkpoints in place first.

Before you start

To write workflows down: nothing but time and the people who do the work.
To run them through AI: the tools each workflow touches connected, ideally at a 3 or better. That usually means the platform and marketing tracks.

One shared place for your process maps that everyone who runs the store can open.
The connections from the other tracks: Figma, your store platform and your marketing platform.
A Claude plan that lets you connect MCP servers, and a way to keep shared instructions and context that every operator works from.
Access to the places your reporting comes from, such as your store, your email platform, your analytics and your ad accounts.

A list of your recurring workflows, with how often each one runs and who runs it today.
For each one, what it produces: a live product, a sent campaign, a report.
The tools and logins each one touches.
Where each one tends to go wrong.

Time with whoever does each workflow today, while they do it. That’s where the steps nobody wrote down come out.
A second person, or a fresh pair of eyes, to test a map by following it.
One owner for the maps, who updates them when a tool or a process changes.

Which workflows are core. Start with the few the store can’t run without.
What stays human. Approvals, judgement calls, anything that spends money or talks to customers. Decide where the human steps are before you automate around them.
What “the same result” means. For each workflow, what done looks like, so you can tell whether anyone, or Claude, got it right.
Where outputs land, and who gets told when a workflow has run.
Upkeep. Who updates a map when the tools change.

Next: the Checklist, so you know what a 4 looks like before you start.