The first 30 days of a fractional engagement set the tone for everything that follows. Clients form strong impressions quickly — about your professionalism, your judgment, and whether bringing you in was the right decision. The fractional executives who consistently build strong, long-term client relationships approach every new engagement with a structured onboarding plan. Those who wing it often spend the first 90 days in a low-level credibility hole they never fully climb out of.
This checklist covers what to do in the first 30 days of any fractional engagement, regardless of function. For more on this topic, see our guide on building a fractional practice.
Before Day 1: Setup and Logistics
The administrative work that should be complete before you show up:
- Signed agreement with clear scope of work. Don’t start work without a signed engagement agreement. Even for clients you trust completely, this protects both parties. See the engagement terms guide for what should be in it.
- First invoice sent. Invoice the first month’s retainer before or on day one, not at the end of the first month.
- Access requests submitted. Send a list of all systems, tools, and documents you’ll need access to: shared drives, project management tools, financial systems, communication channels, relevant data repositories.
- Calendar shared. Share your availability and working schedule. Set expectations about response time for non-urgent requests.
- Kickoff meeting scheduled. A structured kickoff meeting in the first week with relevant stakeholders.
Week 1: Listen, Don’t Prescribe
The most common mistake new fractional executives make is arriving with solutions before they understand the problem. Your job in week one is to listen, observe, and ask good questions. For more on this topic, see our guide on managing multiple clients.
Conduct stakeholder interviews. One-on-ones with everyone who will be affected by your work: the CEO or primary sponsor, the team you’ll work with directly, and any adjacent stakeholders. Ask each person: What’s working well? What’s not working? What does success look like in six months? What should I know that I haven’t asked about?
Review all relevant documentation. Strategic plans, financial models, org charts, previous reports, existing roadmaps, past post-mortems. Don’t rely on what people tell you — triangulate against what’s actually documented. For more on this topic, see our guide on client retention strategies.
Map the informal structure. Every organization has a formal structure and a real one. In week one, identify who the informal decision-makers are, where the real power sits, and which relationships will matter most for your ability to get things done.
Identify the quick wins. Look for two or three things you could address in the first 30 days that would be visibly valuable and buildconfidence. Quick wins aren’t about doing easy things — they’re about demonstrating that you can identify and act on what matters. For more on this topic, see our guide on pricing your services.
Week 2: Synthesize and Prioritize
Write an initial diagnosis memo. A 1–2 page written summary of your initial observations, structured as: what’s working, what’s not working, the three to five most important problems or opportunities, and your proposed focus for the first 90 days. Share this with your primary sponsor and get alignment before you start executing.
Establish your working cadence. How often will you meet with your primary sponsor? With the team? What’s the communication channel for urgent issues vs. routine updates? Getting this agreed explicitly in week two prevents friction later.
Identify your dependencies. What do you need from the organization to do your job well — data access, team bandwidth, budget authority, decision-making involvement? Surface these dependencies early, before they become blockers.
Week 3: Deliver Something Visible
By week three, deliver your first tangible output. Not a finished product — a visible signal that work is happening and progressing. This could be a preliminary analysis, a draft framework, a structured problem statement, or a set of prioritized recommendations.
The point isn’t to have fully solved anything yet. The point is to demonstrate your working style, show that you’re making progress, and give the client something concrete to react to. Early reactions tell you whether you’re calibrated correctly on what they need.
Week 4: Establish the 90-Day Plan
Agree on 90-day outcomes. What specific, measurable outcomes should this engagement produce in the first 90 days? Write them down. Get explicit sign-off from your primary sponsor. These outcomes become the basis for your first formal review and the anchor for renewal conversations.
Set up your reporting rhythm. Whether it’s a weekly email summary, a monthly report, or a shared dashboard, establish how you’ll make your work visible to stakeholders who aren’t directly involved day-to-day. Visibility is not optional — it’s how you prevent the “is this engagement worth it?” conversation from happening by default.
Build your internal network. Make sure you’ve had substantive conversations with everyone who will be important to your success over the next six months. Not just your primary sponsor — the operational people, the team members, the finance or HR partners who will be in your path.
Frequently Asked Questions
What if I’m brought in to fix an urgent crisis rather than for a planned engagement?
Compress the timeline but don’t skip the steps. Even in a crisis, spending the first two days listening and diagnosing rather than immediately prescribing produces better outcomes. The most common crisis mistake is acting on the presenting problem rather than the root cause — good diagnosis even under pressure prevents that.
How should I handle it if I discover in week one that the real problem is different from what I was hired to address?
Have the conversation directly and early. “Based on my first week, I think the most important issue is X rather than Y — I want to discuss whether that changes how we should structure this engagement.” Clients appreciate early course corrections much more than discovering six months in that you’ve been working on the wrong problem.