Reformat Labs

    AI action plan

    What's a Good 30-Day AI Plan for a Small Business?

    Week-by-week tasks, realistic time commitments, and clear outcomes for each stage.

    Book a discovery call
    4 weeksa structured plan you can complete alongside normal work - not a project that takes over
    2-3 hrsper week of additional time required, reducing to net time savings by week 4
    5+tangible, measurable outcomes you should be able to point to at day 30
    £0-20/mocost of the tools needed to run this plan - free tiers cover the audit, paid tiers from week 2

    What makes this different

    Most 30-day AI plans are written by people who want to sell you AI tools or training. This one is written for a business owner who has a full schedule, a degree of healthy scepticism, and wants to know if AI can genuinely help - not a theoretical case for why it should.

    The plan has four phases. Week 1 is entirely offline - it's a friction audit before you touch any tools. This is the step most people skip, and it's why most AI rollouts don't stick. You can't pick the right tool before you know which tasks you actually want help with.

    Week 2 is about getting wins from the tasks you identified, before building any process. Week 3 is about turning what worked into a repeatable workflow. Week 4 is about measuring the result honestly and deciding what to do with month 2.

    Each week has specific daily tasks, a realistic time estimate, a list of outcomes you should have by the end of it, and a 'watch out' note on the most common mistake at that stage. By day 30 you should have a clear, honest picture of what AI does and doesn't do for your specific business.

    Week 1 of 4

    Week 1 - Audit

    Understand where AI can actually help your specific business before touching any tools. Most AI rollouts fail because people pick tasks based on what seems interesting rather than what creates the most friction.

    Days 1-2

    Do the friction audit

    90 min

    Spend 90 minutes writing down everything you or your team does in a typical week. For each task, note: how long it takes, how often it happens, and whether it involves words, research, or data (the three things AI handles best). Don't edit or filter yet - just list.

    Days 3-4

    Score and rank your tasks

    30 min

    Go back through your list and score each task on two dimensions: time cost (how many hours per week total?) and AI suitability (is it repetitive? does it involve writing or research? is the quality bar achievable?). Your top 5 scores become your target list for the month.

    Days 5-6

    Research tools for your top use case only

    45 min

    Pick the single highest-scoring task from your list and find the right tool for it. Don't research tools for all five tasks yet - that leads to tool overwhelm and paralysis. Create accounts for 2-3 candidate tools and set them up (5 minutes each). Most have free trials.

    Day 7

    Write your day 30 target

    10 min

    One sentence. 'By day 30, I want to be saving [X hours per week] on [specific task], with output quality that is [good enough to use after a light review / good enough to send directly / better than what I was producing manually].' Pin it somewhere you'll see it. This is your measurement benchmark.

    By end of week 1 you should have

    A ranked list of your 5 highest-friction tasks
    Accounts created for 2-3 tools
    A written day 30 target
    A clear picture of where your time actually goes

    Watch out

    Don't try to pick the 'right' tool before completing the audit. Tool selection before task selection almost always leads to retrofitting tasks to the tool rather than the other way round.

    Week 2 of 4

    Week 2 - Quick wins

    Get 2-3 tangible wins before investing in deeper setup. The goal this week is building the habit of reaching for AI first - not optimising outputs, not building workflows, just using it consistently on real work.

    Days 8-9

    Do your single best task with AI five times

    As you work

    Take your top-ranked friction task and do it with AI every time it comes up this week. Don't wait for the 'right' prompt - write a reasonable brief and see what comes back. Your first prompts will be rough. That's expected and useful: you'll learn faster from five imperfect attempts than from one overthought one.

    Days 10-11

    Add email drafting as a second use case

    As you work

    If you're not already doing this: use ChatGPT or Claude to draft your next 10 emails. Not just the complex ones - all of them. The goal is to see whether AI drafts are faster to edit than writing from scratch. For most people, they are, even when the first draft needs significant editing. This becomes your second repeatable use case.

    Days 12-13

    Try one 'stretch' use case

    30 min experiment

    Pick a task you weren't sure AI could help with and try it. Good candidates: summarising a long document you received, generating a first draft of a proposal or case study, creating a standard response template for a common client question, or researching a topic before a client meeting. Low stakes, but potentially high reward.

    Day 14

    Honest review of week 2

    20 min

    Write 3-5 sentences: which tasks produced useful AI output? Which didn't? What made the difference? Jot down the 2 prompts that worked best. You'll formalise these into templates next week.

    By end of week 2 you should have

    5+ AI-assisted versions of your primary friction task done
    A sense of which prompts work and which don't
    At least one task where AI genuinely saved you time
    Notes on 2 prompts worth keeping

    Watch out

    Don't reject AI for a task after one attempt. AI output quality is highly sensitive to how the task is briefed. If the first result is poor, try a more specific brief before concluding the task isn't AI-suitable.

    Week 3 of 4

    Week 3 - Deeper rollout

    Move from ad hoc AI use to structured, repeatable workflows. By the end of this week you should have at least one prompt template you can reuse, persistent context set up in your primary tool, and - if you have a team - a clear shared starting point.

    Days 15-16

    Build your first prompt template

    45 min

    Take the prompt that worked best in week 2 and formalise it. Write it out in full with clear [placeholder] sections for the parts that change each time. Save it somewhere you'll find it: a pinned note, a Google Doc, your browser bookmarks. Test it three times with real tasks. Adjust the wording until it produces consistent output.

    Days 17-18

    Set up persistent context

    30 min

    If you're using ChatGPT: go to Settings and set up Custom Instructions. Write a short description of your business, your role, and your communication style - this context applies to every conversation. If you're using Claude: create a Project and add an instruction note. This step alone saves 5-10 minutes of re-briefing per session.

    Days 19-20

    Share with your team (or add a second use case if solo)

    30 min

    If you have a team: pick one tool and one use case, write a single paragraph of guidance on how to use it, and share it in a team meeting or brief message. Don't overcomplicate this - 'Here's how I've been using ChatGPT to draft client emails. Try it this week and tell me if it's useful' is enough. If you're solo: add one automation or integration (e.g. connect AI to your email client, or try a purpose-built tool for your sector).

    Day 21

    Address data and privacy questions proactively

    20 min

    Whether or not anyone has raised it, now is the right time to set clear guidelines on what can and can't go into AI tools. Write three sentences covering: which tools are approved, what data should never be inputted, and what review standard applies to AI outputs. Share this alongside your team rollout note. This prevents problems later.

    By end of week 3 you should have

    At least one reusable prompt template written and tested
    Persistent context set up in your primary tool
    Team aware of AI use with basic guidance (or second solo use case running)
    Short written data guidelines shared

    Watch out

    Don't try to automate everything at once. Automation is a week 4+ activity. In week 3 you're building reliable manual workflows first - you can only automate what you've already proven works.

    Week 4 of 4

    Week 4 - Measurement

    Measure what's changed, document what works, and use the results to plan month 2. This week is about making your AI use intentional and sustainable rather than trailing off after the initial enthusiasm.

    Days 22-24

    Measure time saved against your day 1 baseline

    45 min

    Go back to your week 1 friction list. For each task you've been using AI on: how long does it take now vs before? Be honest about this - count only real time saved, not theoretical efficiency. If a task now takes 20 minutes instead of 45, that's 25 minutes saved per occurrence. Multiply by weekly frequency to get a weekly hours figure.

    Days 25-26

    Quality and reliability check

    30 min

    For each AI use case: are you happy with output quality after your review process? How much editing is typically required? Have there been any errors or near-misses that reached clients? Are you using a consistent review process, or reviewing differently each time? The goal isn't zero editing - it's a reliable, repeatable standard you're comfortable with.

    Days 27-28

    Document what works

    45 min

    Write a short note (half a page is fine) covering: the tools you're using, the 2-3 use cases that produced the best results, your best prompt templates, and your data guidelines. This is the start of your AI workflow documentation. It's also what you'll show to new team members, clients who ask, or a consultant helping you go deeper.

    Days 29-30

    Plan month 2

    30 min

    Decide: which use cases will you continue and build on? Which tasks from your original friction list haven't you tackled yet? Are any of your current workflows ready to be automated? What training or support would help your team go further? Write 3 specific goals for month 2 and put them in your calendar.

    By end of week 4 you should have

    A concrete measurement of hours saved per week
    A quality and reliability assessment of each AI use case
    A short written AI workflow document
    Three specific goals for month 2

    Watch out

    If your measurement shows little or no time saved, don't conclude AI doesn't work for your business. Dig into why: were the tasks AI-suitable? Was the brief specific enough? Was too much editing required? Almost always there's a correctable root cause.

    After day 30

    What a successful month 1 looks like

    At day 30, a successful run of this plan typically looks like: 2-3 tasks you now do significantly faster, one or two prompt templates you use weekly, a short AI workflow document you could share with a new hire or client, and a clear idea of which tasks from your original friction list you haven't tackled yet.

    Month 2 is where the compounding starts. You build on what worked, automate one or two of the manual workflows, and start looking at sector-specific tools if they exist for your industry. Most businesses find that the hardest part of month 1 is building the habit of reaching for AI at all - by month 2, that habit is established and the efficiency gains start to accelerate.

    Continue and deepen

    The 2-3 use cases that produced the best results in month 1. Build more sophisticated prompt templates and tighten your review process.

    Automate one workflow

    Take a proven manual AI workflow and connect it to another tool via Zapier, Make, or a native integration. Start with the highest-frequency task.

    Add one new use case

    Pick one task from your original friction list that you didn't get to in month 1. Apply the same week 2 approach: do it five times before building any process.

    Want a structured start?

    We run AI workshops and consultancy sessions that compress this plan into a single day

    Our half-day and full-day AI workshops cover the friction audit, tool selection, prompt building, and team rollout - in a structured session with your actual business context. You leave with a working AI setup, not a plan to build one.

    Common questions

    FAQs

    Get in touch

    Book an AI discovery session

    No commitment. Response within one business day.