← Back to library

Find the AI setups hiding in your last six weeks of work

In a public LinkedIn post, consultant Matteo Bacchin-Bertling describes asking AI to review about six weeks of his own work to find repeated requests and chores, then suggest the lightest fitting setup for each. His prompt sat in a comment, so this page links to the post and offers our own version.

  • OutcomeHave an assistant look back over recent email, calendar and notes, split what others keep asking you for from what you keep doing by hand, and propose the three simplest setups worth building, each with test cases and risks.
  • SetupMinutes
  • LevelStarter
  • CreditMatteo Bacchin-Bertling
View original
Works with
ClaudeChatGPTMicrosoft Copilot

Published Oct 26, 2026Updated Oct 26, 2026AI dry run on sample input: passed Oct 26, 2026Source verified Oct 26, 2026

When should you use it?

  • You use AI daily but have not built any repeatable setups yet
  • You suspect the same requests reach you every week
  • Your assistant can already read your mail, calendar or notes

Not for: Tools without access to your recent work (paste a sample instead); Sending AI output to clients unchecked; Building ten automations at once; start with one

What do you need, and what do you get?

You need

  • Assistant access to roughly six weeks of email, calendar and meeting notes, or a pasted sample
  • A note on what you have already automated or saved

You get

  • Two lists: recurring requests from clients and partners, and tasks you keep doing yourself
  • Two or three real examples behind every pattern
  • The lightest fitting setup for each: saved prompt, project, skill or scheduled task
  • For the top three: inputs, draft instructions, two tests from recent work, and the main risk of sending its output to a client unreviewed

How does it work, step by step?

  1. Check accessConfirm what your assistant can actually read. Memory is not full access, and connections vary.
  2. Run the reviewAsk for the two lists with examples, checked against what you already have.
  3. Pick the lightest fitPrefer a saved prompt or project over a full automation when it does the job.
  4. Test one ideaTake the top suggestion, run its two tests on recent work, and keep the risk note in view.

The prompt

Our own prompt, inspired by Matteo Bacchin-Bertling and written to work in Claude, ChatGPT and Microsoft Copilot. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Review my recent work to spot tasks worth turning into AI setups.
Period: the last {weeks} weeks. Sources you may read: {sources}. Already built or saved: {existing_setups}. Tell me first which sources you cannot access.

1) Make two lists: things clients, colleagues or partners repeatedly ask me for, and chores I repeatedly do by hand. Back every item with two or three concrete instances, dated.
2) Drop anything I have already covered.
3) For each remaining item, suggest the lightest option that would work: a saved prompt, a project with standing context, a reusable skill, or a scheduled job.
4) For the best three, give the inputs it needs, draft instructions, two test cases taken from my recent work, and the main risk if its output reached a client without review.
Do not send, schedule or change anything.

Inspired by Matteo Bacchin-Bertling: LinkedIn post: a prompt to find AI use cases in your everyday work. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • An assistant with partial access will miss patterns; tell it what it cannot see.
  • Ideas without examples are guesses. Ask for real instances behind each one.
  • The risk note on client-facing output is the safeguard. Do not drop it.

Our take

Many people stall on AI at the same point: they know the tools can save time but cannot say which of their own tasks to hand over. Bacchin-Bertling's approach answers that with data you already have. Instead of brainstorming, have the assistant look back over several weeks of mail, meetings and notes and separate two things: what other people keep asking you for, and what you keep doing yourself. Two parts of his framing make this better than a generic ideas list. Every pattern needs real examples, which filters out wishful thinking, and each idea is matched to the lightest setup that fits, often just a saved prompt rather than a full automation. He also asks for a risk note on any client-facing output that skips review, which is the right reflex for consultants. The main limit is access: memory and connectors rarely cover everything, so tell the assistant what it cannot see. In our dry run on a fictional consultant's six-week sample (forty emails, twelve meetings, a notes file), the review found three recurring client asks and two self-made chores, suggested a saved prompt for weekly status notes as the top pick, and listed two tests and one client-facing risk for each of the top three.

Where the time goes back: It points your automation effort at work that already repeats, so the first setup you build pays back in weeks, not someday.

FAQ

Why is the original prompt not shown?
The author put it in a comment on his LinkedIn post, which we do not copy. The prompt on this page is our own version of the idea; the post is linked for credit.
What counts as the simplest useful setup?
Often just a saved prompt. A project helps when context carries over; a skill or scheduled task fits jobs with a clear output or a regular rhythm.

Source and credit

Inspired by Matteo Bacchin-Bertling. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
LinkedIn post: a prompt to find AI use cases in your everyday work
Creator
Matteo Bacchin-Bertling
Published on
LinkedIn
Original date
Oct 21, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Custom agent
AI dry run
Oct 26, 2026: passed. Dry-run tested by our AI test agent on sample input. Every pattern backed by examples; lightest setup chosen; risk note kept; no actions taken.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 26, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Check an AI answer or plan before you act on it

Paste in an AI-made plan and get a short verdict: what is backed by evidence, what is contradicted, what is only a risk, and what to check next.

Credit: u/softdeveloper23 on r/PromptEngineering

Minutes
Operations & AdminPrompt✓ AI dry run

Connect mail and calendar to an assistant with outbound locks

Use an agent on calendar and email for drafts and flags, while blocking send, decline and invite until you approve — after learning what goes wrong without locks.

Credit: u/sidds_inbox on r/ChatGPT

Minutes
Operations & AdminWorkflow✓ AI dry run

Build in-house real estate tools with a coding agent

Small, team-specific tools for offers, property reports and deal tracking, built with a coding agent instead of bought.

Credit: u/Clevelander87 on r/AiForSmallBusiness

An afternoon+
Operations & AdminPrompt✓ AI dry run

Fill forms from a source packet, then proof every one

Given a packet of facts and many similar forms, have an assistant fill each form and produce a checklist so you proof every submission before it goes out.

Credit: u/Remote_Tangerine_718 on r/ClaudeAI

Under an hour
Operations & AdminPrompt✓ AI dry run

Plan an n8n workflow with AI, then build it yourself

Talk a new automation through with a chat model before opening n8n: describe the job in plain terms, ask separately what can go wrong, get a readable list of named steps, then connect the nodes yourself and check every field path against real data, using the model only for small code and transform pieces.

Credit: Amin_Mahmodi

Minutes