The question I get most often from a founder who's seriously considering fractional leadership isn't about cost or credentials. It's some version of: what does this actually look like once it starts?
It's a fair question, and an important one. Bringing a senior operator into your business - even part-time - is a meaningful decision, and most founders want a realistic picture of the process before they commit to it. So here's an honest walkthrough of what the first 90 days of a fractional leadership engagement typically looks like.
The first 90 days of a fractional leadership engagement typically follow three phases: a focused diagnostic period in the first two to three weeks, an implementation phase where the fractional leader begins building and fixing what the diagnostic surfaced, and an early momentum phase by day 60–90 where initial systems are in place, and the function is starting to run with more structure and less founder dependency.
The first two weeks are about understanding, not fixing. A good fractional leader resists the urge to start changing things on day one and not because urgency doesn't matter, but because changing the wrong thing quickly is worse than changing the right thing two weeks later.
During this phase, expect:
Structured conversations with the team. The fractional leader meets individually with the people closest to the function - not to evaluate them, but to understand how work actually flows, where the friction lives, and what's been tried before.
A review of existing systems and documentation. Whatever processes, tools, or frameworks already exist, get reviewed honestly - what's working, what's half-built, and what exists on paper but isn't actually followed in practice.
Alignment with the founder on priorities and scope. This is where the engagement gets concretely defined: what does success look like in 90 days? What's the single highest-priority problem? What decisions does the fractional leader have authority over, and which ones still need founder sign-off?
By the end of this phase, you should have a clear, written picture of the current state, the priority problems, and a rough plan for the next 60 days. If a fractional leader skips this phase or rushes through it, that's a signal worth paying attention to, as diagnostics done quickly are usually diagnostics done poorly.
This is where the bulk of the visible work happens. With the diagnostic complete and priorities aligned, the fractional leader moves into building, fixing, and implementing.
What this looks like varies by function, but the pattern is consistent:
Quick wins get addressed early. Most diagnostics surface at least one or two problems that can be fixed quickly and meaningfully: a broken handoff, a missing piece of documentation, or a misconfigured tool. Addressing these early builds trust and momentum before the bigger structural work is complete.
The core systems work begins. This is the heavier lifting: building the process documentation, implementing the CRM, designing the team structure, developing the go-to-market plan, or whatever the engagement's primary scope requires. This work typically spans several weeks and involves regular collaboration with the team; it's not work done in isolation and handed over.
Regular check-ins keep the founder informed without requiring their involvement in every decision. A well-structured engagement includes a consistent cadence - weekly or biweekly - where the founder gets visibility into progress without being pulled into the operational details. This is often the point where founders start to feel the shift: decisions that used to require their input start to happen without them.
Early adjustments happen based on what's actually working. No build phase goes exactly according to the initial plan. Good fractional leaders adjust based on real feedback rather than rigidly executing a 60-day-old plan that new information has made partially obsolete.
By the final third of the first 90 days, the engagement should be showing visible signs of traction. This doesn't mean everything is finished - most meaningful organizational change takes longer than 90 days to fully mature - but it should mean the trajectory is clearly positive and the founder can see the shape of where things are headed.
Signs that an engagement is on track by day 90:
The function has documented processes that didn't exist before, even if they're still being refined. The team has more clarity about who owns what and how decisions get made. The founder has stopped being the default answer to questions in this function - at least for the categories of decisions that were explicitly handed off. There's a clear plan for the next 90 days, built on what's been learned rather than the original assumptions from day one.
What it doesn't mean: that the function is fully optimized, that every process is perfect, or that the fractional leader's work is done. Ninety days is enough time to establish direction and build real infrastructure, but it's rarely enough time to complete a full transformation, especially in operationally complex businesses.
One of the most common misconceptions about fractional leadership is that it requires no founder involvement. The opposite is true, especially in the first 90 days.
The founder's role shifts from doing the work to enabling the work: being available for the decisions that genuinely require their input, providing context the fractional leader needs to make good calls, and being honest during check-ins about what's working and what isn't. Founders who stay engaged during the first 90 days without micromanaging tend to get significantly more value from the engagement than those who disappear and expect to be handed a finished product.
A few things commonly extend or complicate the first 90 days, and are worth knowing in advance:
Unclear decision-making authority. If it's not clear who can approve what, even good work stalls waiting for sign-off.
Incomplete access to systems or information. A fractional leader can't fix a CRM they don't have admin access to, or redesign a process they can't see documented anywhere.
Competing priorities that shift mid-engagement. Some shifting is normal and healthy. Frequent, significant changes to scope make it difficult to build the momentum that 90 days is designed to create.
Team resistance that isn't addressed directly. Change is uncomfortable, and a new fractional leader stepping into a function often surfaces some discomfort. The engagements that go best are the ones where the founder actively supports the transition rather than leaving the fractional leader to navigate team dynamics alone.
When I start a new engagement, the first two to three weeks are intentionally diagnostic - understanding the team, the systems, and the real priorities before making changes. By day 60, the core build work is well underway. By day 90, the founder should see a function that looks meaningfully different than where it started, with a clear plan for what comes next.
If you're trying to picture what this would actually look like inside your business, a 30-minute conversation is a good place to start. We can talk through what the first 90 days would realistically involve for your specific situation.
The Learning Plan provides embedded fractional leadership across product, marketing, and operations for growing businesses in Ontario.