A no-code AI Morning Summary

3/24/26

I’ve been thinking a lot about how I start my workdays.

As a Customer Success and Account Manager at a B2B SaaS company, my mornings used to look something like this: open Gmail, scan for anything urgent. Switch to Google Calendar, figure out what’s on today. Check Slack for threads I missed overnight. Pop into HubSpot to see what tasks are due and whether any deals moved. Then mentally piece together a plan for the day — usually while sipping coffee and hoping I didn’t miss something important.

It’s not that any one of those steps is hard. It’s that doing them all, every single morning, across four or five different tools is a drain. Not on my skills — on my attention. By the time I’ve assembled the picture of “what’s going on today,” I’ve already burned through a chunk of my best morning energy.

So I decided to try something: what if I could have all of that waiting for me when I sit down?

The idea

I’d been experimenting with Claude — Anthropic’s AI assistant — for a while. Mostly for writing help, thinking through problems, that kind of thing. But when I started exploring Cowork mode (their desktop tool), I realized it could actually connect to the tools I use every day: Gmail, Google Calendar, HubSpot, Slack, and more.

That’s when the idea clicked: what if I could set up a recurring task that runs every weekday morning, checks all my work tools, and delivers me a ready-made briefing?

I’m not a developer. I don’t write code for a living. But I figured — why not try?

What it actually does

Every weekday at 7:30am, before I’ve even opened my laptop, Claude runs a scheduled task that does the following:

Email review. It scans my Gmail for everything sent and received in the last 24 hours, flags anything that looks like it needs a reply or follow-up, and checks for unread or starred messages that might have slipped through the cracks.

Calendar check. It pulls today’s meetings — who’s attending, what it’s about, any relevant context — and also looks back at yesterday’s meetings to piece together a recap of what happened and what outcomes might need follow-up.

Slack scan. It checks my workspace for mentions, active threads, and important team or customer updates. Anything that looks like it needs my attention gets surfaced.

HubSpot review. It looks at my open tasks, recent deal activity, and any contacts or companies that have been updated recently. So if a deal moved stages or a customer reached out, I know about it.

Then it compiles all of that into a structured morning briefing: what’s happening today, what needs my action, and a summary of yesterday’s key meetings and outcomes.

And the part I’m most proud of: it pushes the action items directly into Things 3 (my task manager), sorted into the right customer account projects with appropriate deadlines based on urgency. So by the time I sit down, my task list is already organized.

How I built it

Here’s the thing that surprised me most — the whole setup was basically a conversation.

I opened Claude’s Cowork mode on my Mac, and told it what I wanted. Something like: “Every weekday morning, check my Gmail, Calendar, Slack, and HubSpot, and give me a briefing. Then push the tasks into Things 3.”

Claude took it from there. It checked which tools were already connected (Gmail, Google Calendar, and HubSpot were good to go via MCP connectors — think of these as bridges between Claude and your apps). For Slack, it set up browser-based access as a fallback. For Things 3, it uses the app’s URL scheme to create tasks directly.

The whole thing runs as a “scheduled task” — essentially a saved set of instructions that Claude executes automatically on a cron schedule. I didn’t write a single line of code. I described what I wanted in plain English, refined it through a few back-and-forth messages (“can you make sure State Farm tasks go into the State Farm project?” / “add tags like ‘bug’ or ‘feature request’ to the right items”), and that was it.

The conversation felt less like programming and more like onboarding a very capable assistant.

What I’ve learned so far

A few reflections, now that I’ve been running this for a bit.

It’s not about replacing my judgment — it’s about saving my attention. The briefing doesn’t tell me what to think about my day. It gives me the raw materials so I can make better decisions faster. I still decide what’s actually urgent, what can wait, and what needs a different approach. But I’m making those decisions with everything in front of me, instead of context-switching across five tabs.

The setup is iterative, not one-shot. My first version was pretty basic. Over time, I’ve been refining it — adding smarter routing for Things 3 projects, better tagging logic, adjusting what gets surfaced and what doesn’t. It’s a living system, not a finished product. And because the instructions are in plain language, tweaking them is easy.

You don’t need to be technical to do this. I think there’s a misconception that leveraging AI tools like this requires coding skills. It doesn’t. What it requires is clarity about your workflow. If you can describe what you do every morning in plain sentences, you can automate a good chunk of it. The AI handles the technical wiring.

It’s changed how I think about my role. CS and Account Management are fundamentally human roles — they’re about relationships, empathy, understanding what your customer actually needs. But so much of our day gets eaten by information gathering. If I can reclaim even 30 minutes of that, that’s 30 minutes I can spend actually being there for my customers instead of hunting through inboxes.

For fellow CS/AM folks

If you’re in a similar role and curious about trying something like this, here’s what I’d suggest:

Start by mapping out your morning routine. Literally write down every tool you check and what you’re looking for. That description is your prompt. Then look into tools like Claude’s Cowork mode (or similar AI assistants that support integrations) and see which of your tools can be connected.

You don’t need to automate everything on day one. Start with one or two data sources — maybe just email and calendar — and see how it feels. Then layer on more as you get comfortable.

The hardest part isn’t the technology. It’s giving yourself permission to try.

This is part of my effort to share more about my work in Customer Success and Account Management. I’m not an expert on AI, but I am someone who’s figuring out how to use it in a way that makes my actual work better. If you have questions or want to swap notes, feel free to reach out.