The onboarding period for a chief of staff in a consulting or professional services firm is one of the most important investments a CEO can make in the success of the role. A poorly structured onboarding leads to months of slow ramp, missed opportunities, and sometimes a failed hire. A well-designed onboarding accelerates effectiveness, builds organizational credibility, and establishes the working relationship that makes the chief of staff genuinely useful.
This guide covers how to structure the first 90 days for a chief of staff in a consulting firm, what knowledge they need to build quickly, and how to set them up for lasting success.
Why Consulting Firm Onboarding Is Distinctive
Onboarding a chief of staff in consulting requires attention to several dynamics that are unique to the professional services environment:
Client confidentiality from day one: The chief of staff will be exposed to sensitive client information almost immediately. Confidentiality protocols, NDA requirements, and data handling practices need to be established before the first client document is shared.
Partner relationship sensitivity: The chief of staff will need to build trust with partners who have significant authority and often some skepticism about a new “CEO’s person.” Managing these first impressions carefully matters.
Technical knowledge gap: If the chief of staff does not have a consulting background, they need to quickly understand the economics of consulting: billable utilization, project portfolio management, proposal win rates, and engagement economics.
Immediate operational demands: Unlike many new hires who have a true 90-day grace period, a chief of staff often walks into immediate operational needs: a board meeting in three weeks, a leadership offsite being planned, a strategic initiative that has been stalled. Managing these demands while also onboarding requires careful expectation setting.
Phase 1: The First Two Weeks - Foundation Building
Day 1 to 3: Orientation and Logistics
The first days should focus on practical orientation:
- Office and system access: CRM (Salesforce), project management tools, time-tracking systems, communication platforms
- Introduction to the EA and establishing initial working protocols
- Review of the firm’s organizational structure, practice areas, and key leadership contacts
- Initial review of current strategic priorities and outstanding initiatives
The CEO should plan to spend significant time with the chief of staff in the first week, not to hand off work, but to begin establishing the working relationship and transferring context.
Day 3 to 14: Deep Context Building
The chief of staff needs to build a rapid, deep understanding of the firm’s current state:
Financial and performance context:
- Current revenue and growth trajectory
- Utilization rates by practice area and overall
- Key financial ratios and targets
- Recent financial trends
Client portfolio context:
- Top ten to fifteen clients by revenue, their relationship history, and current engagement status
- Any at-risk client relationships
- The proposal pipeline and recent win/loss trends
Operational context:
- Active strategic initiatives and their current status
- Key operational challenges the CEO has been managing
- Technology systems and how they are used
People context:
- Key partners and their domains, preferences, and any current tensions
- Practice leads and their performance
- Critical talent: who is performing well, who is at risk, who is in transition
Schedule individual meetings with each practice lead and key functional leaders during this period. The goal is to understand their perspective on the firm’s current situation and to begin building trust.
Phase 2: Weeks 3 to 6 - Structured Observation and Early Contribution
Attending the Full Range of Meetings
During weeks three through six, the chief of staff should attend most of the CEO’s significant meetings, including leadership team meetings, practice reviews, client calls (where appropriate), and board or investor meetings. The goal is observation and context-building, not yet taking over facilitation or coordination.
This observation period is essential. The chief of staff learns how decisions are made, how the leadership team functions, which partners are collaborative and which are territorial, and what the CEO’s communication style and priorities really look like in practice.
Beginning to Take Over Coordination Functions
By the end of week six, the chief of staff should begin taking ownership of the operating rhythms they will manage long-term: preparing leadership team meeting agendas, beginning to maintain the performance dashboard, and coordinating preparation for upcoming governance meetings.
This gradual takeover should be communicated clearly to practice leads and other stakeholders: “Starting this month, [Name] will be coordinating the leadership team meeting agenda and follow-up. Please direct agenda items and updates to them.”
Phase 3: Weeks 7 to 12 - Full Operational Ownership
By the end of 90 days, the chief of staff should be operating with full ownership of their core responsibilities:
- Running the weekly leadership team meeting with minimal CEO preparation
- Maintaining the performance dashboard and delivering weekly CEO briefings
- Managing the business development pipeline in Salesforce
- Owning at least one active strategic initiative end-to-end
- Managing the preparation process for any board or partner meetings
The CEO should be clearly experiencing time liberation by this point: specific activities that previously required CEO involvement should now be owned by the chief of staff.
First 90-Day Review
At the 90-day mark, the CEO and chief of staff should conduct a structured review:
- What has been working well?
- What has been harder than expected?
- What adjustments are needed to the scope or operating model?
- What are the priorities for the next quarter?
This review creates explicit alignment and gives both parties an opportunity to course-correct before patterns are entrenched.
Harvard Business Review research on the chief of staff role emphasizes that the chief of staff’s effectiveness depends heavily on the quality of the working relationship with the CEO, and the first 90 days are when that relationship is most foundationally shaped.
Key Knowledge Areas to Develop Quickly
For a chief of staff without a consulting background, there are several knowledge areas that need to be developed rapidly:
Consulting economics: How consulting firms make money; the relationship between headcount, utilization, billing rates, and revenue; engagement economics.
Proposal process: How consulting proposals are developed, priced, and submitted; what drives win rates; the typical timeline from opportunity identification to contract.
Client relationship management: How consulting client relationships are structured; the role of account management in professional services; how client satisfaction is measured and managed.
Project management in consulting: How consulting engagements are planned and staffed; the role of project managers and engagement managers; how projects are monitored and controlled.
Professional services compliance: Professional licensing requirements relevant to the firm; NDA and confidentiality practices; conflict-of-interest policies; professional liability insurance.
Building Credibility with Partners and Practice Leads
One of the chief of staff’s most important early tasks is building credibility with the firm’s partners and practice leads. These are often strong-willed individuals who may be skeptical of a new role that sits between them and the CEO.
Effective approaches include:
- Listen more than you talk in early interactions
- Demonstrate genuine interest in understanding their practice and challenges
- Deliver on small commitments quickly and reliably
- Be transparent about your role and how you can be helpful
- Avoid positioning yourself as the CEO’s enforcer
Building trust takes time in consulting firms, where partner relationships are built on years of demonstrated competence and judgment. A new chief of staff who tries to move too fast will encounter resistance.
For more on how to structure the chief of staff role for long-term success, see this chief of staff hiring guide covering role design and onboarding best practices.
Common Onboarding Mistakes to Avoid
Moving too fast to restructure things: The chief of staff who arrives and immediately starts redesigning processes before they understand why things are done the way they are will alienate the team.
Taking on too much too fast: The chief of staff who tries to own everything from day one spreads themselves too thin and delivers poorly on all of it. Build scope gradually.
Failing to establish the working relationship with the CEO: The chief of staff who does not invest in explicit conversations with the CEO about working style, decision rights, and communication preferences will operate in ambiguity.
Underinvesting in partner relationships: The chief of staff who focuses only on the CEO’s world and neglects the partners and practice leads will struggle to be effective at coordination.
For comprehensive guidance on this role, see the chief of staff guide.
Conclusion
A well-designed onboarding plan for a chief of staff in a consulting firm is not a luxury. It is a strategic investment in the effectiveness of one of the most important roles in the firm. By building context quickly, establishing operating rhythms thoughtfully, and investing in the relationships that the role depends on, a new chief of staff can be genuinely contributing within 90 days and operating at full effectiveness within six months. The CEO who invests in this onboarding process gets a higher return on their investment significantly faster.
Related Reading
For further context, explore Chief of Staff Compensation Benchmarks in Automotive and Chief of Staff Compensation Benchmarks in Construction & Architecture.