What AI can do for you right now

There is a particular kind of tiredness at the end of a week where you have done a lot of the same thing. Meeting notes formatted the same way for the third time. The slide that is really last quarter’s slide, updated. The weekly report that asks for the same information from the same four people and takes an afternoon to assemble.

These are not hard tasks. They are not the work anyone hired you to do. They are the wrapper around the work, and they expand to fill whatever time you give them.

Level 1 is about removing the wrapper, by handling the parts that were never worth your time in the first place, leaving the judgment that is actually yours untouched.

Level 1: the personal layer, and what makes a good use case

Level 1 is one person, one task, no handoff. You and Claude. The return is real and you feel it more than you count it.

Three weeks in, you will not be adding up the hours. You will notice that you walked into the 8 am meeting prepared instead of running the notes while listening. You will notice that the report that used to eat Tuesday afternoon went out before lunch. The return is confidence and reclaimed evenings, and it is worth far more than any productivity spreadsheet will capture.

Not every task is a good Level 1 use case, and picking badly is the reason people try it once, find it underwhelming, and stop.

Three questions before you decide:

Do you do this often enough to feel it? A task you run twice a year is a poor candidate. The setup cost does not pay back on low frequency. A task you do 3 to 5 times a week is worth the 15 minutes to build the prompt.
Is the input predictable? Claude works best when you can describe the input in advance. “Meeting notes in this format, produce a brief in this structure” is predictable. “Write something creative that surprises the client” is not, because the judgment is the whole product.
Would you know if the output was wrong? If you cannot evaluate the result without doing the work yourself, you are not saving time. You are creating a review loop you have to run anyway. The best Level 1 use cases are ones where you can read the output in 30 seconds and know whether it is right.

If a task passes all three, then it is a candidate.

Four Level 1 use cases worth starting with

Meeting prep. Drop the agenda, the attendee list, and any relevant background into Claude. Ask for a one-page brief: context, the decision to be made, the questions you should ask. Takes 3 minutes to set up, saves 40 minutes of reading.

Weekly report curation. Drop the raw inputs, status updates, data, news, and ask for a structured summary in your standard format. Your job becomes editing, not assembling.

Email drafts for repeating situations. A follow-up after a proposal. A response to a common objection. An update to your team after a decision. Write the prompt once, update the specifics each time. The first draft is yours in two minutes.

Presentation outline from notes. Drop your thinking, rough notes, and the slide structure you use most often. Ask for a draft outline, section by section. You start from something rather than from nothing.

But Claude can help you not only in your professional life. The next two use cases are good starting points to save your time in your personal domain.

Your personal finance dashboard. Turn your bank statements into a live financial overview and keep it updated in minutes per month.

Your life dashboard. Takes your calendar, your to-do list, and the mental load you carry into one honest weekly view. For people running a career, kids, a household, and a body that still needs training.

None of these require any technical setup. No API key, no code, just Claude in the browser and a clear prompt.

AI meeting prep briefs: walk into every meeting ready

Most people read the meeting invite 2 minutes before it starts. They show up without an agenda, without knowing who holds the decision, and without a clear goal. They leave without closing anything.

AI meeting prep flips this. The AI reads your calendar, researches the attendees, builds an agenda, and surfaces open items, automatically, before every meeting.

What is an AI meeting prep brief?

An automated brief delivered in two stages:

Stage 1, the evening before (8pm): Full preparation for every meeting the next day, including a search through your email history to reconstruct context, even for empty invites.

Stage 2, 45 minutes before: A compact reminder with your single most important goal and question for that meeting.

A full brief covers the meeting and duration, the attendees and who holds the decision, what the email history shows, what the meeting is probably about, a recommended goal, a suggested agenda with time per item, the key questions to ask, the open items to close, and what to watch out for.

The empty invite problem, solved

Corporate calendars are full of invites that say nothing: “Weekly Sync”, “Touch Base”, “Q3 Check-in”. No agenda, no purpose, no clue.

The AI handles this by searching your email history for the past 6 months, finding previous meetings with the same people, related email threads, and unresolved topics. A brief for an empty invite might look like:

“No description in invite. Found 11 emails with Jan Müller over 90 days covering: Phase 3 approval, Q3 budget, insect control market sizing. Previous ‘Weekly Sync’ with Jan consistently focused on pipeline status. Likely agenda: pipeline review + Phase 3 update.”

You walk in knowing what it’s actually about, even when nobody told you.

Benefits

Walks in prepared: You know who decides, what you want, and what to cover. No scrambling.
Surfaces what’s stuck: Open items from previous meetings don’t disappear, they get flagged until closed.
Improves meeting outcomes: A clear goal per meeting means fewer follow-ups, fewer “let’s circle back” situations.
Saves prep time: A brief that would take you 20 minutes to assemble takes the AI 10 seconds.
Works across meeting types: 1:1s, cross-functional reviews, external calls, interviews, the format adapts.

Risks

Wrong context: If the meeting invite has a vague title (”Sync”) and no description, the AI has little to work with. Mitigation: add a one-line purpose to your calendar invites.
Missing attendee data: If attendees aren’t listed in the invite, the AI can’t research them. Mitigation: always add attendees to calendar events, not just the meeting link.
Over-preparation: A brief is a tool, not a script. Don’t follow it rigidly, use it to anchor your thinking, then stay present in the conversation.
Calendar access: The AI reads your calendar to generate briefs. Ensure you trust the platform and that calendar data is not stored or used for training.

Activation, step by step

Option 1: Google Calendar (Gmail users). Full briefs for all calendar events with attendees, agenda suggestions, open item tracking. Open Claude Cowork, go to Settings then Connections, find Google Calendar and click Connect, sign in with your Google account and grant read access. Then tell Claude once:

Create a scheduled task that runs every evening at 8 pm to prepare briefs for tomorrow's meetings, and another that checks every hour on weekdays and alerts me 45 minutes before any meeting

The words scheduled, every evening, and every hour are what tell Claude to automate this permanently rather than just do it once. Claude creates two recurring tasks that run automatically from that point on. You never need to repeat this. Click Run now on each to pre-approve calendar access.

Limitation: Only sees meetings in your Google Calendar. If your work meetings live in Outlook, connect that separately.

Option 2: Outlook / Microsoft 365 Calendar (corporate users). Same full brief capability, and the best option if your work calendar is in Microsoft 365. Same steps, connecting Outlook or Microsoft 365 instead, signing in with your corporate Microsoft account and granting calendar read access. Your IT admin may need to approve this. If your company uses conditional access or MFA, the connection may require additional steps.

Tip: Connect both Google and Outlook if your life is split across both, personal meetings in Google, work meetings in Outlook. Claude will see both.

Option 3: other calendar systems. iCloud Calendar is not natively supported yet; the workaround is to share your iCloud calendar with a Google account and connect Google Calendar instead. Calendly sends confirmation emails to your inbox when meetings are booked, so if Gmail is connected, Claude can detect these and flag upcoming meetings from email. For other tools, check Settings, Connections for the latest available connectors, the list grows regularly.

Getting better briefs

The AI uses the meeting invite to generate the brief. Better invites mean better briefs. Three habits that help: add a one-line purpose to every invite you create, list attendees with roles rather than just names, and link to relevant documents in the invite description.

What AI meeting prep does not do

It does not accept or decline meeting invites on your behalf
It does not send meeting notes or summaries to attendees
It does not record or transcribe meetings
It does not modify your calendar

All write actions require your explicit approval.

Email triage in Claude, detailed setup

What you get: a short brief twice a day that tells you what in your inbox needs action, what is worth knowing, what is worth reading, and what to ignore. You read the brief instead of the inbox.

Time to set up: about 20 minutes. No coding.

Note on labels: these steps follow the Claude desktop app (Cowork). Exact menu names (”Connections” vs “Connectors”, “Run now”) can differ slightly by version. The action is what matters, not the precise wording on the button.

Before you start

The Claude desktop app installed and signed in.
A Gmail account (these steps use Gmail; Outlook is nearly identical, see the note at the end).
20 minutes.

Step 1, open the desktop app

Open Claude on your computer, the desktop app, not the browser tab. Scheduled tasks and inbox connectors live in the desktop app.

Step 2, connect your inbox, read-only

Go to Settings, then Connections. Find Gmail in the list and click Connect. A Google sign-in window opens. Sign in with the account you want triaged. When Google asks what to allow, choose read access only if the option is offered. Claude can then read and sort, never send or delete.

If your version does not show a read-only choice, connect normally. You lock the safety in with the instruction in Step 3, which tells Claude never to send or change anything.

Why read-only: it removes any chance of an email going out or being deleted by mistake. You give up automatic labeling, which a brief does not need.

Step 3, create the recurring task

This is the part that makes it run by itself, twice a day, instead of once. In a new chat, paste this:

Set up a recurring scheduled task. Twice every day, at 7 am and 6 pm, read my Gmail from the last 12 hours and sort every email into four groups:

1. Action required — needs a reply or a decision from me today
2. FYI — important to know, no action
3. Worth reading — newsletters or updates relevant to me
4. Ignore — everything else

For groups 1 to 3, give one line per email: sender, subject, and why it matters. For Ignore, list subjects only. Send it all to me as one short brief. Never send, delete, or modify any email.

Claude creates the scheduled task (or two, one per time) and confirms the schedule back to you.

Step 4, approve access on the first run

The first time a scheduled run starts, Claude asks permission to open your Gmail. Find the task and choose Run now, or wait for the first scheduled time. Approve the Gmail access prompt when it appears. Do this once. After that the task runs on its own at 7 am and 6 pm every day.

Step 5, check it actually worked

Confirm a brief arrived after the first run. Open it and check the Action group against your real inbox. Did it catch what matters? Did it bury anything important in Ignore?

For the first few days, skim the Ignore list once a day. That is how you learn to trust it, and how you catch anything it mis-sorts.

Step 6, tune it to you (optional, worth it)

Once, in the chat, give it your context so the sorting sharpens:

Context for triage: I am the owner of small bakery and I am building AI automation as a hobby. Treat anything about [your priorities — e.g. specific clients, AI tools, a sport, job opportunities] as high priority. Treat generic marketing as Ignore.

The more specific the context, the better the brief.

If something goes wrong

No brief arrived: open the desktop app and check the task still exists and is scheduled. A laptop fully asleep or shut at the scheduled time can miss a run.
It mis-sorts a lot: refine the context in Step 6 with one or two concrete examples of what you want where.
It asks for access every time: re-approve once and confirm in Settings that the connection did not drop.

Outlook / Microsoft 365

Same steps. In Step 2, connect Outlook or Microsoft 365 instead of Gmail. Corporate accounts with strict IT rules may need admin approval. If the connection fails, that is usually why.

This guide covers Claude Cowork as of June 2026. Connector availability and features may change.