Founders ask this before they sign anything, and they should. "It depends" is a true answer and also a useless one. Here's what actually happens, stage by stage, across the engagements I've run.
Week one: visibility, not results
Nothing looks different yet, and that's correct. Week one is the audit: what's actually on your calendar versus what should be, where decisions are currently getting lost, what a leadership meeting looks like today. The decision log and initiative tracker get built, and the decision-rights conversation happens: what I decide, what I draft for you, what I escalate. If someone promises visible wins in week one, they skipped this step, and it will cost you later.
Weeks two to four: the cadence starts running
This is where it either takes or it doesn't. The leadership meeting gets real structure: agenda pulled from the tracker, not from whoever emailed last. The follow-through sweep starts catching commitments before they quietly die, usually a day or two after they're made. By week four you should see the first item close that would have stalled before: a vendor decision that was circling for a month, an intro that finally happened, a report that used to take you an evening now taking fifteen minutes to review.
Month two: you stop having to ask
This is the real inflection point, and it's quieter than people expect. You stop asking "what's happening with X" in meetings, because the tracker already has the answer and you know to look. The Friday brief becomes something you actually read instead of skim, because it tells you what needs your decision instead of everything that happened. If you're still chasing status updates at month two, the system isn't running yet, and that's worth a direct conversation, not a wait-and-see.
Month three: the real test
By now, at least one full initiative should be closed end to end, not just tracked: a market-entry workstream landed, a systems migration finished, a partnership signed. Tracking motion isn't the same as closing something. If nothing has actually landed by month three, the engagement isn't working. That's not always the CoS's fault; sometimes it's access that was never fully granted, or decisions that keep getting made in side conversations instead of the logged ones. Either way, month three is when you'll know, and it's the right moment to either recommit with a clearer scope or end it cleanly.
What slows the timeline down
- Delayed access: if the CoS is still waiting on calendar, inbox, or tool access in week three, everything else is downstream of that.
- No decision-rights agreement: without it, the CoS either oversteps and gets pulled back, or under-delivers waiting for permission that was never going to be denied.
- Old habits routing around them: if the team keeps solving things in DMs instead of the logged cadence, the system never gets a chance to prove itself.
- Treating month one like month three: expecting a closed initiative before the cadence has even had four weeks to run.
The mechanics of what gets installed in that first stretch are covered in more depth in what a fractional chief of staff actually does. If you want to talk through where your week is actually leaking time before you commit to anything, book the free 30-minute call.