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?
- Check accessConfirm what your assistant can actually read. Memory is not full access, and connections vary.
- Run the reviewAsk for the two lists with examples, checked against what you already have.
- Pick the lightest fitPrefer a saved prompt or project over a full automation when it does the job.
- 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)
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?
What counts as the simplest useful setup?
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
- 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.