"You did the hard part. You found someone great. Congratulations — now comes the part where most founders completely blow it."
— A note to the reader
The first 90 days of a Chief of Staff engagement are make-or-break. Not in the vague, motivational-poster way that phrase usually gets thrown around. In a very literal, "this hire either becomes transformative or becomes a very expensive mistake" kind of way. The CoS role is uniquely fragile in its early days because it lacks the structural clarity that most roles come with.
Here's the thing: a bad first 90 days doesn't mean you hired the wrong person. It often means you onboarded them wrong. At Resonance Search, we specialize in placing Chiefs of Staff and senior operators at VC-backed companies — and the pattern is clear. What follows is a week-by-week framework based on direct feedback from our placed CoS candidates and the founders who hired them.
Chapter One
Days 1–30: Learn the Landscape
Listen first, act second
The biggest mistake a new Chief of Staff can make in their first month is trying to prove their value too quickly. Month one is about absorption, not action. Your CoS needs to understand the company the way you understand it — the politics, the priorities, the personalities, the things that keep you up at night.
Week 1: Immersion
The first week should feel almost uncomfortably slow for your CoS. Their job is to meet everyone and understand everything. Set up one-on-ones with every member of the leadership team, key ICs, and anyone who has institutional knowledge. Your CoS should be shadowing you — sitting in on your meetings, reading your emails, getting a raw, unfiltered view of how you spend your time.
Give them access to everything: board decks, financial models, strategy docs, OKRs, the Slack channels where real conversations happen. The goal is total context.
Week 2: Deep Dive into Priorities
By week two, shift from "meet everyone" to "understand everything." This means going deep on current priorities, the strategic plan, the org chart (the real one, not the one on the website), and the key metrics that drive the business.
This is also when they should start identifying quick wins. Not big strategic initiatives — small, visible improvements that signal competence.
Weeks 3–4: First Ownership
By end of month one, your CoS should be taking ownership of one or two small but meaningful projects. Think: running the weekly exec sync, owning board meeting prep, or getting a stalled cross-functional project unstuck.
Establish your communication rhythm now. Most successful CEO-CoS pairs land on a brief daily check-in plus a longer weekly deep-dive.
Key Milestone: End of Month 1
Your CoS should be able to clearly articulate the company's top five priorities and your biggest pain points as CEO. If they can't, you either haven't given them enough access or they haven't been asking the right questions.
Chapter Two
Days 31–60: Build Credibility
Earn your seat at the table
Month two is where the real work begins. Your CoS has the context. Now they need to use it. Your job as CEO is to give them the space and authority to go do it.
Own a Cross-Functional Initiative
By month two, your CoS should be taking point on at least one meaningful cross-functional project. Not assisting, not coordinating — owning. This is where they'll start to build or lose credibility with the broader leadership team.
Represent the CEO
Start sending your CoS to meetings in your place — the ones where your presence is more symbolic than substantive. This signals to the organization that the CoS has your trust. A CoS without the CEO's visible backing is just another person with opinions.
Build Leadership Relationships
A great Chief of Staff isn't just the CEO's proxy — they're a trusted partner to the entire leadership team. The goal is to become someone that leaders actually want to loop in. This is one of the key differences between a Chief of Staff and an Executive Assistant.
Identify Process Gaps
The best Chiefs of Staff develop a sixth sense for organizational friction. They can feel when a team is stuck, when a process is creating more work than it saves, or when a meeting is a waste of everyone's time.
Key Milestone: End of Month 2
There should be at least one visible, tangible win that the broader team can point to. Not a behind-the-scenes save — something the organization experienced. Visibility matters because it builds social capital.
Get Help Hiring Your Chief of Staff
Finding the right Chief of Staff is one of the highest-leverage hires you'll make. Don't leave it to chance.
Chapter Three
Days 61–90: Drive Impact
Operate independently, think strategically
Month three is when you should start feeling the difference. Not just in your CoS's output, but in your own life. You should notice that certain problems stop landing on your desk. That meetings run better even when you're not there. That strategic initiatives are actually moving.
Full Ownership of Strategic Initiatives
By now, your CoS should be fully owning two to three strategic initiatives. Not just managing logistics — shaping strategy, making judgment calls, and driving outcomes. Think: building the annual planning process from scratch, leading a cross-functional GTM fix, or owning fundraise preparation.
Operating Independently
The daily check-ins from month one should be evolving. You're not telling them what to do anymore — you're telling them what's on your mind, what's worrying you. They take that context and figure out where to focus. The best CEO-CoS relationships at this stage feel like a partnership, not a manager-report dynamic.
Building an Intelligence Network
The best Chiefs of Staff become the most connected people in the company. By month three, people should be voluntarily bringing them information, concerns, and ideas. This network gives you a second set of eyes and ears — and often, a more honest picture than you'd get on your own.
Key Milestone: End of Month 3
Clear, measurable evidence that the CEO is getting time back and strategic initiatives are moving faster. You should be able to point to specific hours reclaimed, specific projects that shipped because the CoS drove them, and specific problems caught before they escalated.
Red Flags in the First 90 Days
Not every CoS hire works out. Here are the warning signs — spot them early and course-correct.
They're still asking basic questions in month two. That suggests either a lack of intellectual curiosity or an inability to synthesize complex information quickly.
The leadership team avoids them. If your direct reports aren't engaging with your CoS, they haven't built credibility. Figure out why.
They wait for instructions. The CoS role requires extraordinary self-direction. If they're idle until you give them a task, they don't have the right disposition. Similar expectations apply to a COO, but at a different scale.
They can't handle ambiguity. If your CoS gets paralyzed when the plan changes, they're going to be miserable — and so are you.
You don't trust their judgment. By month three, you should trust your CoS to represent your thinking, make calls on your behalf, and handle sensitive information with discretion.
What NOT to Do as CEO During Onboarding
Many CoS failures aren't actually CoS failures — they're CEO failures. If you're prone to the common mistakes founders make, the onboarding phase is where they compound.
Hovering
If you're reviewing every email they send, sitting in on every meeting they take, or second-guessing every decision — you're not delegating, you're creating extra work for both of you. You have to tolerate some imperfection in the short term to get independence in the long term.
Dumping Too Much Too Fast
The opposite failure. You unload everything at once. Every project, every problem. Be ruthless about prioritization. Give them the most important things first and add scope gradually.
Not Making Introductions
A personal introduction from the CEO carries enormous weight. An email that says "hey everyone, meet our new Chief of Staff" carries almost none. Take the time to make warm, personal introductions.
Keeping Information Back
Your CoS can't help you with the hard stuff if they don't know about the hard stuff. Be radically transparent from day one. They should know everything you know.
Not Defining Success
"Help me with stuff" is not a job description, and it's not a success metric. Before your CoS starts, have a clear picture of what success looks like at 30, 60, and 90 days.
Setting Up for Long-Term Success
The first 90 days are the foundation, but they're not the finish line. After the 90-day mark, schedule a formal retrospective — a genuine two-way conversation about what's working and what isn't.
In our experience placing Chiefs of Staff, many eventually transition into operational leadership — VP of Operations, Head of Strategy, or even Chief Operating Officer. Across our searches, the strongest CoS candidates consistently come from VP, Senior Director, or C-suite backgrounds. Some stay in the CoS role for years. Either path can work, but your CoS needs to know there is a path.
If you're still navigating the search, Resonance Search works with startup founders on exactly these kinds of hires.