What am I missing?
The gaps between what I've said I'm doing and what I'm actually doing.
The Chief of Staff check: five questions I ask Claude about my business every week, run over everything it knows about me. It finds the money I'm not collecting and the decisions that contradict each other. Rude. Useful.
An hour to set up the context once. About ten minutes a week after that.
You've also got an email on its way with links to all the free resources, so you can find them again.
Jump to the Chief of Staff check ↓They only work if Claude knows your business first. With your context loaded, these are the questions I'd ask a very good COO if I could afford one.
The gaps between what I've said I'm doing and what I'm actually doing.
Past enquiries never followed up. Clients with no next step. Offers with nothing after them.
The plan from three weeks ago that this week's decision undoes without anyone noticing.
Based on everything it knows: risk, overload, the thing I keep putting off.
The one that stings. It does the arithmetic I've been avoiding.
Boring. Load-bearing. The reason the answers are about your business and not a business.
01 runs the five questions. 02 schedules them. 03 is for before a big decision. 04 keeps the objectives honest.
Paste into a new task in your project.
With everything you know about my business, my objectives and what I've built recently, answer these five questions. Be specific, name the files or decisions you're drawing on, and don't soften it. 1. What am I missing? 2. Where's the money I'm not collecting? 3. What have I decided this month that contradicts something I decided earlier? 4. Based on everything you know, what should I be worried about? 5. Can the plans I've made for this year still be made with the time that's left? Show the arithmetic. Finish with the one action you'd take first if you were me.
Paste into a scheduled task for Fridays at 3pm.
Every Friday at 3pm, read my context documents, objectives.md, and anything added or changed in this project folder this week. Answer the five Chief of Staff questions: what am I missing; where's the money I'm not collecting; what have I decided that contradicts something earlier; what should I be worried about; can this year's plans still be made with the time left. Lead with anything that's changed since last Friday. One page. Save it to my Outputs folder as chief-of-staff-YYYY-MM-DD.html.
Run before you commit to something new.
I'm about to decide [decision]. Before I do, check it against everything you know: my objectives, my recent decisions, what I've promised people, and my capacity. Tell me what it conflicts with, what it would push out, and who I've already promised something to that this affects. Then tell me whether you'd still do it, and why.
Once a quarter, so the questions stay honest.
Read objectives.md and what's happened in this project over the last quarter. Tell me which objectives are on track, which have stalled, and which I should drop. Then interview me, one question at a time, to write next quarter's objectives. Stop at three. Save the new version as objectives.md and move the old one to my Archive folder.
Three ways to go further, depending on where you are.
Build your AI chief of staff in 30 days, live, with me and a small group of people running businesses. The next cohort opens when the waitlist is full. Join it and you get first access and the waitlist price.
Join the Challenge waitlist →Three live calls a month, at least four new skills a month, plugin updates. For people already using Claude daily who want to keep building. Cancel any time.
Join the membership →Four private sessions building the whole system around your actual week, or a workshop for your leadership team. Book a call and we'll work out which.
Book a call →