I Came Back From a Sick Day to 500 Emails. So I Built This.
You don't have to invent new workflows — you just have to borrow the right ones

Senior Full Stack Engineer with 8 years of industry experience. Happy to guide or mentor anyone, or to collaborate on any problems!
I took a sick day once.
Just one. I was genuinely unwell, so I closed my laptop and actually rested. No inbox-checking guilt. No Slack at bedtime. A proper sick day.
The next morning I opened my email to find over 500 messages waiting for me.
I'm a senior software engineer at PayPal, based in India. My team spans time zones — a significant chunk of my colleagues are in PST, which means by the time I wake up, they've already put in half a workday. While I slept, pull requests were reviewed, builds ran and failed and ran again, Jira tickets got updated, and threads I was CC'd on spiralled into long back-and-forths. GitHub alone sends a separate notification for every single step of a build pipeline — every success, every failure, every approval. On a busy overnight, I'd typically walk in to 100–200 emails. That one sick day more than doubled it.
The emails themselves weren't really the problem. The problem was not knowing whether something urgent was buried in there. Something with my name on it. Something that had been waiting since yesterday and was now quietly blocking someone else.
So I'd block out time — a solid 30 minutes, first thing — just to get through it all. Scan, skim, sort, prioritise. And here's what bothered me about that: the first 30 minutes of your workday are usually your sharpest. That's when you're freshest, before meetings and interruptions erode your focus. I was spending that window on triage — on sorting — rather than on the focused, heads-down work that actually moves things forward.
That had to change.
Stealing a Good Idea (and That's Fine)
I came across the concept of a "morning brief" through something someone else had shared — a way they'd set up an AI to read through their inboxes and surface what mattered before they started their day. Their specific setup wasn't a match for mine. But the idea was.
This is one of the most underrated things about AI tools right now. You don't have to be the one who invents the workflow. You just have to be willing to pick up what someone else figured out, hold it up against your own situation, and ask: could this work for me?
I took that concept, mapped it to my actual morning — Outlook email, Slack, Jira, Outlook Calendar — and built something that fit. It took some tinkering, but the starting point wasn't a blank page. It was someone else's half-finished idea that I finished for myself.
I'd encourage you to do the same thing here.
What the Morning Brief Actually Does
Think of it like this: imagine you had a diligent intern whose only job was to arrive at the office before you, read every message, scan every notification, check your task list and your calendar — and then hand you a single, clean briefing when you walked in the door.
That briefing tells you:
- What's on fire right now — urgent, needs your attention before anything else
- What's about to get warm — not critical yet, but will be if you don't move on it today
- Quick wins — tasks you could knock out in under 15 minutes to clear your plate early
- Good to know, but not urgent — the rest, summarised so you can decide later whether to act
That's my morning brief. Every morning, before I open a single email or Slack thread, I run it. Within 5–10 minutes, I have that briefing in front of me — and I know exactly what my morning looks like.
It doesn't replace reading my emails. I still get to all of it eventually. But it gives me a lay of the land first, so I can start the day with intention rather than anxiety. I can make an informed choice about what to open first, rather than just thrashing through whatever's at the top of the pile.
The Honest "How It Works" Section
I use Claude Desktop for mine, though Claude on the web works the same way.
The key piece you'll need is connectors — these are the integrations that let the AI actually read your tools. You configure them once, and after that they just work. For my setup, I needed connectors for:
- Outlook (email)
- Slack (team messages)
- Jira (tasks, stories, and bug queues)
- Outlook Calendar (what's on my plate today)
The connector setup is a one-time thing. It does require some patience — it's not quite as simple as clicking "install." If you're not confident doing it yourself, 20 minutes with a technical colleague is genuinely all it takes. Think of it as the cost of admission: you pay it once, and then the brief just works every morning after that.
Once your connectors are live, the rest is just a prompt — the instruction you give the AI before it reads everything. Here's the version I use, which you can copy and adapt directly:
📋 Morning Brief Prompt — Copy and Adapt
Good morning. Please review my Slack messages, emails, Jira board,
and Outlook Calendar for today, then give me a structured morning
brief with the following sections:
1. 🔴 URGENT — Things that need my attention right now. Flag anything
with my name on it, unresolved blockers, or anything time-sensitive.
2. 🟡 WATCH LIST — Things that aren't urgent yet but will become urgent
soon if I don't act today.
3. ✅ QUICK WINS — Tasks I can finish in under 15 minutes. I want to
knock these out early.
4. 📌 FYI — Everything else summarised briefly. I'll decide later
if I need to act.
Keep it concise. I want to be oriented and focused within 10 minutes
of reading this.
Swap in whatever tools you actually use. If you don't have Jira, remove it. If you use a different project tracker, name that instead. The prompt is yours to make your own.
A Couple of Honest Caveats
Your AI intern is fast and eager — but occasionally gets things wrong. A few things worth knowing upfront:
It can misread priority. An email thread that looks urgent based on the subject line might already be resolved. The brief is a starting point, not gospel. Give it a quick sanity check before you act on anything it flags as on fire.
The setup requires real effort. Connectors don't install themselves, and if you hit a snag, it can feel frustrating. But this is a one-time setup, not an ongoing tax.
Check your company's AI policy first — this one is non-negotiable. You're connecting real work tools containing real work data. That data may include confidential information, client details, or anything else that falls under your organisation's compliance obligations. Before you set anything up, speak to your IT team, your HR department, or whoever owns your company's AI usage policy. Don't assume it's fine just because the tool is popular.
This is especially important if you're considering a free AI tool. Free tiers often have different — and more permissive — data handling terms than paid or enterprise plans. If in doubt, use a paid or enterprise-grade tool with clear data privacy commitments, and still check with your policy team first. A five-minute conversation now is far better than a compliance issue later.
The Real Point
I'm not sharing this because mornings need to be optimised or because inbox zero is a worthy life goal. I'm sharing it because there's a real cost to spending your sharpest 30 minutes every morning on sorting rather than on doing — and most of us have just quietly accepted that cost.
You don't have to build this from scratch. Start with this prompt. Borrow the concept. Adapt it to your tools and your situation.
The goal isn't to read faster. It's to walk into your morning already knowing what needs you — and giving your best hour to the work that actually deserves it.
That's a good morning.



