Series: AI × Supply Chain build breakdown
Stack: Claude Code (scheduled) · Gmail · Calendar · Slack · the spreadsheet brain
The problem
My inboxes and the day’s priorities were getting away from me. I wanted to walk in already knowing what mattered, not burn the first hour triaging three apps to find out.
How it’s changed
v1, the summary. Email and calendar in one place each morning. Useful, but I still had to do all the thinking.
v2, triage. It started flagging what needs action first, surfacing the threads waiting on me that I’d lost, and drafting the easy replies so I just review and send.
v3, plugged into the business. It reads the same brain everything else feeds, so now it carries the ops picture too (stock to watch, anything that looks off), not just my inbox. It knows where we are in the production cycle, and it links to a digest of what the overnight skills actually did, so nothing autonomous runs unseen.
Where it failed
The early versions kept getting the date logic wrong and drifting, the briefing would think it was the wrong day. The boring scheduling and state plumbing was where it broke, not the “AI” part. That’s been the pattern on nearly every build I’ve shipped.
And a briefing that’s too long gets skimmed, which defeats the point. The discipline is ruthless: lead with the one thing that matters and trust me to ask for the rest.
Leverage rating: 4 / 10
Runs itself every morning, and it genuinely changed how I start the day. A small thing that happens daily beats a big thing that happens once.
Related: the briefing sits on the same data layer the Shopify Ops Starter installs. Email me for how it’s wired.