Business teams automate workflows with AI by auditing the manual processes they already run, picking the steps that need judgement rather than rules (reading, sorting, summarising, drafting), and handing those steps to a tool the team already has, such as Microsoft 365 Copilot, ChatGPT, Claude or Gemini. Rules-based steps stay with rules-based tools. A person keeps sign-off on anything that leaves the team or changes a record. No developer is needed for most of this, and the useful work usually starts with a spreadsheet of what the team does each week, not with software.
The short version is in three parts.
Start with a manual-process audit. Ask each person in the team to list the tasks they do more than once a week that involve reading, writing, sorting or summarising. Most teams find fifteen to thirty of these in an hour. This list, not a vendor demo, is where automation comes from.
Automate the judgement steps that rules-based tools can't. Power Automate, Zapier, mail rules and Excel formulas have always handled steps with a fixed rule: if the subject line contains "invoice", move it here. What they could not do is read an email and decide whether it is a complaint, a query or a compliment, or turn forty minutes of meeting transcript into six actions with owners. Language models do that part. The best automations combine the two: rules move things about, the model reads and drafts, rules move the result on.
Keep a person on sign-off. Anything that goes to a customer, changes a system of record, or affects a person's employment gets a human check before it happens. This is not a temporary caution. It is how the process stays defensible when it is challenged, and it matches the direction of the NIST AI Risk Management Framework and the ICO's guidance on automated decision-making.
Everything below expands on those three ideas.
The table lists ten workflows we see in most UK organisations, the part AI actually takes, the tool that fits, and the risk you have to manage. The tool column reflects what most teams already licence, not a ranking.
| Workflow | What the AI does | Tool that fits | Risk to manage |
|---|---|---|---|
| Inbox triage | Reads incoming mail, labels by type and urgency, drafts a holding reply | Copilot in Outlook; Gmail with Gemini | Mislabelled urgent items. Keep a daily "unlabelled" review. |
| Meeting notes to actions | Turns a transcript into decisions, actions, owners and dates | Copilot in Teams; Gemini in Meet; Claude or ChatGPT on a pasted transcript | Actions assigned to the wrong person. Owner confirms before it goes out. |
| First-draft proposals | Produces a structured first draft from a brief, a past proposal and a pricing note | Claude Projects or a Custom GPT loaded with your best examples | Invented figures or scope. Commercial owner edits every number. |
| Data cleaning in Excel | Writes formulas, splits columns, standardises names and dates, flags duplicates | Copilot in Excel; ChatGPT with a file upload; Claude | Silent transformation of source data. Work on a copy and keep the original. |
| Customer email replies | Drafts a reply in the house tone from the thread and the policy | Copilot in Outlook; Claude Project with the tone guide and policy pack | Promises the policy does not allow. Agent reads before sending. |
| Report summaries | Condenses a 40-page report to one page with the numbers that matter | Copilot in Word; Gemini in Docs; Claude for long documents | Dropped caveats. Ask for "what did you leave out" as a second prompt. |
| Policy Q&A assistant | Answers staff questions from HR, IT and finance policy documents | Copilot agent over SharePoint; Claude Project; Gemini Gem | Out-of-date policy version. Assign an owner to refresh the source files. |
| Recruitment screening notes | Summarises a CV against the job description into a structured note | ChatGPT or Claude with the JD and scoring rubric | Bias and legal exposure. Notes inform a person; they never rank or reject. |
| Supplier document extraction | Pulls fields (dates, amounts, terms, renewal clauses) from PDFs into a table | Claude or ChatGPT with file upload; Copilot in Word | Misread figures on scanned documents. Spot-check a sample every batch. |
| Weekly management pack | Assembles the weekly numbers, commentary and exceptions from three or four sources | Copilot across Excel, Teams and Outlook; Gemini in Workspace | Commentary that sounds confident and is wrong. Numbers come from the source, not the model. |
Two things are worth noticing. None of these requires a developer. And every one has a person at the end, because the risk column is never empty.
The most common mistake is to start from what AI can do and look for somewhere to apply it. The teams that get results start from what people do and score it.
Run the audit first (a shared spreadsheet, one row per task, filled in by the people who do the work). Then score each row on five criteria, one to three each.
| Criterion | Score 1 | Score 2 | Score 3 |
|---|---|---|---|
| Frequency | Monthly or less | Weekly | Daily or many times a day |
| Time per instance | Under 5 minutes | 5 to 30 minutes | Over 30 minutes |
| Structure of the input | Unpredictable, varies each time | Loosely similar | Same shape each time (form, template, thread) |
| Risk if wrong | Customer, legal, financial or HR consequence | Internal rework | Caught and fixed in seconds |
| Data sensitivity | Personal, confidential or regulated data | Internal but not sensitive | Public or anonymised |
Add the scores. A task scoring 13 to 15 is a first-week candidate. A task scoring 8 to 12 is a good second wave once the team has habits and guardrails. Anything under 8 is either too rare to bother with or too risky to start with, and both are fine answers.
A worked example. A finance team lists "chase overdue invoices by email". Daily (3), ten minutes each (2), always the same shape: invoice number, amount, days overdue (3), an error is embarrassing but recoverable (2), the data is customer names and amounts, so internal but not regulated (2). Total 12. It goes in the second wave with a rule that every chaser is read before it goes out. "Summarise board papers" scores 1 (monthly), 3, 2, 2, 1 (confidential). Total 9. Worth doing, but only inside a tenant with the right data controls, and not in a free consumer tool.
The scoring stops the loudest idea in the room winning, and it makes the data-sensitivity conversation happen before someone pastes a customer list into a chatbot. The gov.uk "Skills for AI: what works" employer guide makes a similar point from the training side: the skills that stick are tied to a specific task the employee already owns.
Most teams need less than they think. There are three levels, and each one is enough for a different kind of task.
A person opens Copilot, ChatGPT, Claude or Gemini and asks for what they need, with the context pasted in. This is enough when the task is occasional, the input changes each time, and the person is going to read the output anyway. Meeting summaries, one-off report condensing, a first draft of a difficult email.
The improvement here is not software, it is habit and prompt quality. A team that saves its ten best prompts in a shared document has automated more than most teams with a licence for an automation platform.
These are the same models with instructions, files and a tone guide attached in advance. You build one in an afternoon with no code. Everyone on the team then opens "Proposal drafter" or "Policy assistant" and gets the same standard of answer without writing the setup prompt each time.
This is the right level when the same kind of task recurs, the source documents are stable (policies, templates, examples of good work), and the output needs to be consistent across the team. Seven of the ten workflows in the table above sit here.
The difference between the products is mostly where your data lives. Copilot agents read SharePoint with the user's existing permissions; Claude Projects and Custom GPTs take uploaded files inside their own workspace controls; Gemini Gems sit inside Google Workspace. Pick the one that matches where the documents already are and what IT has approved.
An automation platform runs without a person pressing a button. A trigger (an email arrives, a form is submitted, a file lands in a folder) starts a flow, one step of which calls a model to read, classify or draft, and the rest of which moves the result somewhere: a Teams post, a row in a sheet, a ticket in a system.
You need this level when the volume is high enough that a person opening a chat window is the bottleneck, and when the input arrives in a predictable place. Inbox triage at hundreds of emails a day, supplier document extraction across a shared mailbox, the assembly stage of a weekly pack.
Power Automate is the natural choice inside Microsoft 365 and is often already licensed. Zapier is the fastest to learn and connects to the widest set of SaaS tools. n8n is open source and can be self-hosted, which suits teams that want control over where data goes. A capable business user can build the first version of any of them. A developer becomes useful when the flow needs error handling, retries and audit logs that a business owner should not maintain alone.
| Prompting | Custom assistant | Automation platform | |
|---|---|---|---|
| Who triggers it | A person | A person | An event |
| Set-up time | Minutes | An afternoon | A day or two |
| Best for | Varied, occasional tasks | Recurring tasks with stable sources | High-volume, predictable inputs |
| Where the human sits | Throughout | Reads the output | Approval step in the flow |
| Typical examples | Report summary, difficult email | Proposal drafter, policy Q&A | Inbox triage, document extraction |
Go up a level only when the level below is visibly the bottleneck. Many teams that buy an automation platform never build a flow, because they skipped the audit that would have told them what to automate.
Guardrails are not paperwork. They are the reason the automation survives its first mistake.
None of these needs a committee. They need one page and one owner.
Most AI training is a tour of features. Workflow automation training should end with something running.
Day Seven's workflow automation course is built around the process in this article. Before the session, each participant lists the tasks they do repeatedly. On the day, the group scores them with the five-criteria table, picks one each, and builds it in the tool they already have: a prompt library, a Copilot agent, a Claude Project or Custom GPT, or a first Power Automate or Zapier flow. Sessions are lab-style, with minimal slides. People build with their own tools, on their own examples, and leave with the thing they built and a one-page guardrail note for it. The course is available as a full-day workshop on-site anywhere in the UK or live online, for teams of ten or more, in groups of around sixteen.
For teams that want to go further, an AI hackathon takes one real internal problem and works it through to a functioning build over one day to one week. The Day Seven Sprint is the seven-day version: a cross-functional group, a problem the business actually has, and a working automation with an owner and guardrails at the end. Hackathons are the "Prove" stage of our four-stage method (Align, Enable, Prove, Embed), and they are where a team finds out whether an automation earns its place.
We train on Microsoft 365 Copilot, ChatGPT, Claude and Google Gemini, so the session uses whichever the team has licensed rather than a tool it will never see again. Cost depends on group size and format; get in touch for a proposal.
Start with the audit and scoring table above, then build at level one or two using the tools you already pay for (Copilot, ChatGPT, Claude or Gemini). Most small businesses get their first useful automation from a shared prompt library and one custom assistant, with no new software and no developer.
The one your data already lives in. Copilot if you are a Microsoft 365 organisation, Gemini if you are on Google Workspace, and Claude or ChatGPT for document-heavy drafting and analysis in either. For flows that run without a person, Power Automate, Zapier or n8n sit on top of any of them.
Not to begin with. You need an automation platform only when the volume is high and the input arrives in a predictable place. Many teams never need one; a custom assistant that everyone opens covers most recurring work.
Both are a model with your instructions and files attached in advance so the team gets consistent output. A Custom GPT lives in ChatGPT and can be shared within a ChatGPT Team or Enterprise workspace; a Claude Project lives in Claude and is shared within a Claude Team or Enterprise organisation. The choice normally follows which licence and data agreement your organisation already has.
Copilot can draft, summarise and answer inside Outlook, Teams, Word and Excel, and Copilot agents can be built to answer from SharePoint content. To run something without a person pressing a button, you pair it with Power Automate, which is part of the same platform.
Ask the people who do the work to list their repeated tasks, then score each on frequency, time per instance, structure, risk and data sensitivity. High scorers go first. This produces better candidates than a brainstorm and surfaces the data-protection questions early.
It is safe to draft them with AI and send them after a person reads them. Fully automatic sending is a separate decision that depends on the risk of a wrong reply and your data-protection position. Most teams keep the person in the loop indefinitely for anything customer-facing.
Wrong outputs that look confident, sensitive data going to a tool that was not approved for it, source documents going stale, and nobody owning the automation after the person who built it moves on. The guardrails section covers how to handle each.
A prompt takes minutes. A custom assistant takes an afternoon. A simple Power Automate or Zapier flow with an AI step takes a day or two including testing. What takes longer is the audit and the habit-building, which is why training that skips them tends to produce nothing.
Yes. The workflow automation course covers all three levels: prompting, custom assistants (Copilot agents, Claude Projects, Custom GPTs, Gemini Gems) and automation platforms (Power Automate, Zapier, n8n), with each participant building at the level their chosen task needs.
Tell us what your team needs and what tools you have. We'll get back to you within one working day.