A Day in the Life of a Chief of Staff

It's 7:54am. Your phone buzzes on the kitchen counter while the coffee's still dripping. The CEO has forwarded an email from a Tier-1 customer who's threatening to churn over a billing change Finance pushed live last Friday. The forward says one word: "thoughts?"

Your day just started six minutes early.

This is the job. Not the version on the LinkedIn post when you got hired, where you wrote about "partnering with the CEO on strategic initiatives." Not the version your parents tell their friends about, where you're "basically the COO-in-training." The actual version, where Tuesday at 7:54am you're already on your laptop drafting three possible replies before standup, and by 9am one of them is going out under the CEO's name and the other two will become a Slack thread you'll mediate by lunch.

Most Chief of Staff guides describe the role as if it's mostly strategy work. It isn't. It's mostly judgment work in 15-minute increments. So instead of another framework post, here's what an actual Tuesday looks like for a CoS at a 250-person Series C SaaS company. Names changed, calendar real.

Why this job is different from anything else on the org chart

Before we walk through the day, the structural thing nobody warns you about: the CoS role has no fixed scope, no peer to compare yourself to, and success is measured by what didn't blow up.

Every other role on the leadership team has a function. The VP of Sales owns the number. The CFO owns the model. The CPO owns the roadmap. You own the gaps between them, plus whatever the CEO walked into your office worried about this week. There's no quarterly OKR for "kept the leadership team functional" or "caught the thing nobody else was watching."

That ambiguity is the job. If you need a clean job description and a known career ladder, this isn't it. If you can hold the chaos and translate it into action without needing your name on the deck, you're in the right seat.

The other thing: you're senior in influence, junior in title. You'll sit in rooms where you're the youngest person by ten years and the only one without a P&L. The role only works if you genuinely don't need the credit. The minute you start counting whose idea something was, you've lost.

8:00am — CEO email triage

By 8am you're at your desk with two monitors and four tabs open: Gmail, Slack, the CEO's calendar in Google Workspace, and the Notion page where you keep the running decision log.

The CEO has, on average, 47 unread overnight messages. Some are from VCs. Some are from customers. Some are from his mother. About six of them genuinely need his attention today. The rest are noise, and your job for the next 45 minutes is to sort them into four buckets:

CEO answers personally. Board chair, top three customers by ARR, anything from the General Counsel marked urgent, the one founder he's mentoring. About 6-8 emails. You leave these untouched and flag them in a Slack DM with a one-line summary so he can hit them between his 8:30 workout and the 9:30 standup.

You answer as the CEO. This is the bucket nobody outside the role understands. You have his blessing and his calendar to draft replies for the routine "great chatting yesterday" follow-ups, the calendar reschedule requests, the "loved your post" thank-yous, the introductions he agreed to make three weeks ago. About 15-20 emails. You write in his voice, send from his account, and log the send in a shared Google Sheet so he can scan it later. This took six months of trust-building to earn. Don't fake it before you've earned it.

Delegate. Anything operational that belongs to a function. Customer escalations go to the CSM team with context. Vendor contracts go to Finance. Recruiter outreach goes to the People team. About 12-15 emails. You write the handoff with enough context that the receiver doesn't need to ask three follow-up questions.

Kill. The cold pitches, the conference invites, the "I think we should chat about your AI strategy" from someone who clearly hasn't read the website. About 8-10. Archive without reply. Done.

By 8:50am, inbox sorted, three drafts in his outbox, one Slack DM with the day's "you specifically need to handle these six things" list. You join the standup at 9:25 with five minutes to refill coffee.

9:30am — Leadership team standup

Eight people on the call. CEO, CFO, CRO, CPO, VP Engineering, VP Marketing, VP People, you. Camera on. Twenty minutes hard stop.

Your job in this room is not to talk. It's to run the room.

You own the Notion doc that has the agenda, the decisions log, and the parking lot. You start the call by sharing the doc, calling out the three things you committed to land this week, and asking the CEO if anything new bumps the agenda. Then you shut up and listen.

Here's what you're actually doing while looking like you're just taking notes:

• Tracking what's getting decided versus what's getting deferred again. If the CRO has now punted the territory rebalance question for three Tuesdays running, that goes in your follow-up list. Not as a callout in the meeting — as a 1:1 with him at 2pm.
• Watching body language. The VP People crossed her arms when the CEO said "we need to move faster on the leveling project." That's a 3pm DM from you to her: "hey, that one looked like it landed weird, want to talk through it?"
• Catching the thing nobody wants to say out loud. This is the highest-leverage move you'll make all day. When the engineering velocity slide gets glossed over for the second week running, you say, calmly, "Are we on track for the Q2 release date or are we now looking at June?" The room exhales because you asked the question they were all waiting for.

By 9:50, the Notion doc has 11 decisions logged with owners, four parking-lot items, and two action items assigned to you because the room couldn't agree on an owner. That's normal. You'll figure those out by Thursday.

11:30am — The cross-functional escalation that wasn't on your calendar

This is the meeting you didn't schedule. It happens in Slack. The CRO DMs you: "Got a minute? Sales is saying Product committed to a feature for the Acme renewal and now Engineering says it's not on the roadmap. I need this resolved before the customer call at 2pm."

You read the thread. Sales did get a verbal "we should be able to do that" from a PM in February. Product never wrote it down. Engineering scoped it three weeks ago at 6 weeks of work and quietly de-prioritized it for the platform migration. Nobody told Sales. Sales told the customer it's coming in Q2.

Welcome to your real job.

You message the PM, the EM, and the AE separately, not in a group thread. Group threads in this kind of fight create defensive posturing. You ask each one for their version, then you call the AE first because the customer call is in two hours and that's the timer.

By 12:15 you have a position. The feature can ship in 4 weeks if Engineering swaps a lower-priority item out of the sprint. The PM agrees. The EM agrees if his manager signs off. The CPO signs off because you laid out the trade-off cleanly: "We move the integration work to Q3, we keep the Acme renewal worth $480K." The AE has talking points for the 2pm customer call by 12:50.

Nobody escalated this to the CEO. That's the win. The CEO will hear about it in the WBR on Friday as a one-line note: "Acme renewal saved, scope swap approved, cost is integration work pushed to Q3." That's how this role compounds. The fires the CEO never has to know about are the ones that prove your value.

1:00pm — Lunch (working)

You eat at your desk and use the 30 minutes to draft the slide the CEO will need at 4pm for the board prep. You also send three Slack messages you owe people, plus a 1:1 prep doc for your 2pm with the VP People in Lattice. Lattice is doing the thing where it surfaces the four agenda items she added this morning, two of which are about a performance issue with one of her direct reports, one of which is the leveling project from standup, and one of which is "I want to talk about my role." That last one matters and you flag it mentally.

2:00pm — 1:1 with a department head

The 1:1 with the VP People is half coaching, half intel-gathering, zero authority on paper.

You don't manage her. She doesn't report to you. The CEO doesn't ask you to manage her either. But you're the person she trusts to think out loud with, because when she talks to the CEO she has to bring solutions, and when she talks to her peers she has to bring confidence, and with you she can just bring the messy version.

The first 25 minutes are about the leveling project. You listen, you ask three questions, you push back gently on one assumption. You don't fix it. She doesn't need fixing. She needs a thinking partner who's read the same Pigment workforce model she's been staring at for two weeks.

The last 5 minutes are the "I want to talk about my role" thing, and now you're hearing the actual signal: she's been recruited by a competitor, she hasn't decided yet, she wanted to tell someone before she told the CEO. You don't promise anything. You don't try to retain her in the meeting. You say "thank you for telling me, I'd like to think about how to approach this with the CEO together, can we talk again Thursday?"

Then you spend 20 minutes after the call in your private notes file figuring out what this means for the org. If she leaves, the leveling project stalls, the performance review cycle is at risk, and the People team morale takes a hit because she's the glue. The CEO needs to hear this from you tomorrow morning, not Thursday. You shift your DM list.

4:00pm — Board prep / WBR

Two hours until the CEO's day ends and three deliverables on your plate: a redlined board slide, a WBR pre-read for tomorrow's 8am meeting, and a quick-turn financial cut.

You open Pigment. The CFO finalized the April actuals at 3:45pm, which means the revenue number on the board slide you drafted at lunch is now wrong by $140K. Pigment auto-syncs to your Google Slides template via the connector you built two months ago, so the chart updates itself, but the narrative bullets above the chart don't. Those are yours.

You rewrite the bullets. Net new ARR landed 4% under plan, which sounds bad but the gross retention number came in 200 basis points above plan, which is the actual story. You reframe the slide around retention as the leading indicator of the year. The CEO reviews at 5:15, redlines two phrases, approves it.

While that's rendering, you build the WBR pre-read in Notion. Standard format your team has used for 14 months: Wins, Losses, Asks, Numbers, Decisions Needed. Five sections, one page, every department contributes their two-bullet update by 4pm Tuesday. You stitch it together, flag the three items that need decisions tomorrow, and post it in the leadership Slack channel at 5:45pm.

Six minutes later the CRO replies "thx" with a thumbs-up. The CFO replies with a correction on the gross margin number. You fix it. The CEO replies "looks good, see you 8am." That's the close-out signal.

6:30pm — The stack you actually use

People ask what tools the CoS role runs on. The honest answer is fewer than you'd think, used harder than you'd expect.

• Notion. The decisions log, the operating cadence docs, the WBR pre-read template, the 30/60/90 plans for new execs, the running list of "things the CEO worried about this quarter." If it's a decision or a process, it lives in Notion. The discipline is writing it down within 24 hours of the meeting, or it's lost.
• Slack. Every diplomatic conversation. Every "hey can I get a read on this" message before the meeting. Every quiet 1:1 with a department head who needs to vent. The DM is your most-used tool. Channels are for operations; DMs are for politics.
• Google Workspace. Calendar warfare. You manage three calendars: the CEO's, the leadership team's shared calendar, and your own. The CEO's calendar is a strategic document. You protect his thinking time on Wednesday mornings, you push his 1:1s to 30 minutes when the week is overloaded, you cancel the meetings he shouldn't be in. Gmail is for triage and drafting in his voice.
• Lattice. 1:1 prep, performance signals, engagement survey results. You don't run People, but you read every survey breakdown by team because it's the leading indicator for which VP is about to lose a key person. Lattice flagged the People team's eNPS drop three weeks ago, which is part of why this morning's 1:1 didn't fully surprise you.
• Pigment or Adaptive. Whichever your CFO chose. This is the source of truth for every board number, every revenue cut, every headcount model. You don't build the models, but you read them well enough to spot when a number on a slide doesn't match the model and to push back before the CEO presents it.

That's it. Five tools. No CoS-specific software. The job runs on judgment, not tooling.

What nobody tells you

By 7pm you're closing the laptop. The CEO sends one more Slack: "Great day, thanks." It's the same message he sent yesterday. It will probably be the same message he sends tomorrow. That's the feedback loop.

A few things nobody puts in the job description:

You'll mediate at least one leadership conflict a week that nobody, including the people involved, will know you mediated. You'll save renewals, prevent resignations, and reframe board narratives, and most of those wins will go uncredited because the only way the work works is if the visible owner gets the credit.

You'll have weeks where you feel like an air traffic controller and weeks where you feel like a glorified executive assistant. Both are real. The role oscillates. If you're a year in and you can't tell whether you're doing strategy or admin, that's not a problem with you, that's the job.

You'll learn more about how a company actually runs in 18 months as CoS than in five years as a functional VP. That's the trade. You give up the clean ladder, the visible ownership, and the line on your resume that says "ran the X function." You get the seat next to the CEO, the political education of a lifetime, and the pattern recognition that lets you walk into any company and read the org chart in 30 minutes.

If you're considering this role, ask yourself one question: can you do hard work that makes other people look good, for two years, without resentment? If yes, this is the best seat in the company. If no, take a VP role somewhere instead.

The 7:54am email forward will keep coming either way. The only question is whether you want to be the person who answers it.

Learn More

• Companion JD: Business Operations Manager
• Your First 30/60/90 Days as a New Chief of Staff
• Operating Cadence: WBR and Quarterly OKRs
• Cross-Functional Brokering: Leadership Team Conflicts
• Chief of Staff Tools and Tech Stack