Before you compare a fractional leader’s fee with the return they’re promising, ask them to show you the calculation. You should be able to follow it, challenge the assumptions and explain what would have to change for the engagement to pay for itself.

While advising a manufacturing operator, we role-played a business with a rework problem. He began with useful technical questions: where was the process breaking, and were people or equipment responsible?

I pulled the conversation back to a simpler question: “how much is this actually costing you?”

We were building a hypothetical business case, not reporting a client result. That distinction belongs in a real proposal too. An estimate can help you decide without pretending the savings have already happened.

Start with what is happening now

Ask what the business is losing, how often it happens and what evidence supports the number. A bad week repeated across twelve months can make an impressive annual figure. First establish whether that week was typical.

Then separate the kinds of value being counted. Recovered revenue is not all profit. Hours freed up do not automatically reduce payroll. They may still be valuable because your team can serve more customers or stop working late, but that is a different benefit.

Watch for the same improvement counted twice. If recovered capacity lets you deliver more orders, the proposal should explain how that connects to additional profit rather than adding every possible benefit together.

Agree on what would count as progress

I’d want the proposal to identify the part of the problem the operator can influence, the costs of making the change, their fee and the work required from our team. Compare the expected benefit with that whole cost, over the same period.

What is the starting point? Who will check whether the improvement lasts? What would make us revise the estimate?

A useful fractional leader should be comfortable working through those questions with you. If the answer depends on information nobody has, make finding it part of a bounded first phase before committing to a bigger engagement.

That is where experienced judgment earns its fee: turning a costly problem into a plan you can evaluate and act on. The outcome can be uncertain while the business case stays understandable. Ask the operator to show you how it works.

Consider the recommendation if the candidate can show how the work would get done with less of their time. Ask for a written plan before changing your hiring decision. A preference for part-time work, by itself, doesn't establish that it fits your business.

I recorded some feedback about this exact conversation. Someone was concerned about applying for a full-time role and then suggesting a shorter engagement.

The important part of my advice was that the operator has to know enough about the business and the position to make an honest recommendation. You can't arrive with the answer before you've understood the work.

The wording I suggested was: “After learning about what you guys need, I have to tell you, I don't think you should hire me for this full time.”

That's a recommendation to examine. It isn't a reason to skip the examination.

Ask what changed their view

You've advertised a role because something needs attention. A strong candidate may see a narrower assignment than the job description suggests. Ask them to explain the difference.

Which responsibilities require their experience? Which need daily execution? Who would handle that execution? What would still come back to you?

The answers matter because a smaller commitment to the candidate can leave a bigger commitment for your team. If the proposal only works because you silently take over the remaining responsibilities, you haven't established that it solves your problem.

I'd also ask what they've learned that supports their recommendation, and what they still need to check. Experience can inform the plan. It shouldn't become an excuse to leave the plan unexplained.

Put the alternative on paper

In the same feedback, I suggested the next step: “Let me put pen to paper and let you know what I would do to get this outcome for you.” Then walk through it together.

Use that discussion to connect the outcome, responsibilities and available time. Be explicit about the work left with your team. Compare the full cost of each arrangement, including any execution help the fractional proposal requires.

If the work needs dedicated daily leadership, keep that requirement. If the plan shows that experienced ownership of a narrower assignment is enough, fractional may be worth considering.

You don't have to defend the original job description. You do need a credible answer to who will do the work.

Hire a fractional leader when you need someone to work out what should change and own that work. Buy a fixed service package when you already know what needs doing and the package actually covers it.

I was reviewing a conversation with an experienced operator who was questioning his business model. He'd been doing custom fractional engagements. Now he was wondering whether he should offer a more defined menu of services instead.

My advice was to “continue on the bespoke path.” His problem was finding new business. Replacing the work he knew how to do with a different service model wouldn't automatically solve that.

For a business owner choosing help, there's a useful question on the other side of that conversation: are you buying the thing you need, or the thing that's easiest to put on a menu?

Decide how much of the problem you've actually solved

In the recording, I used setting up sales automation as an example of a discrete service. That's a specific thing someone can deliver.

If you've established who you want to reach, what to say and how follow-up should work, hiring someone to build the automation may be a sensible next step.

But suppose you haven't established any of that. You can finish the setup and still have nobody responsible for deciding whether you're pursuing the right business. The deliverable is complete. The commercial question is still open.

That's a hypothetical distinction, not a claim that automation is the wrong purchase. The point is to find out which decisions still need making before you buy implementation.

Make custom work specific

“Bespoke” shouldn't mean an open-ended promise to help with everything.

Ask the operator what they think is getting in the way, what they've solved before that's relevant, and what they would take responsibility for here. Have them explain where a fixed deliverable would be enough and where judgment needs to continue after delivery.

You may discover that you only need the package. Good. You may need an experienced person to make and carry through a series of connected decisions, without enough work for a full-time role.

That's where fractional can fit. Buy the responsibility your business is missing. Don't reshape the problem just to make it fit someone's menu.

Consider it if you know what you want an acquisition to do for your business, but haven't tested whether the company in front of you is the best fit. Comparing targets and helping structure one deal are different jobs. Decide which one you're buying.

An operator told me about a business considering an acquisition. At first, he thought the work would include a wider look at the market. The buyers clarified that they wanted help with one target they'd already chosen.

That changed the scope.

He also described a question he'd asked business leaders in earlier roles when they wanted to buy a company: “What do you want to get from it?”

That's the question I'd want answered before narrowing the assignment.

Separate the goal from the company

There may be a good reason to pursue this particular target. But write down what you're trying to gain without using its name.

What would the business be able to do after the deal that it can't do now? Why does owning this company look like the right way to get there?

Those answers give an adviser something to test. Without them, it's easy to spend the whole engagement working out how to buy a company without checking why it should be that company.

On our call, I asked whether knowing about other players could give the buyers more leverage. That was a question to explore, not a claim that another target was available or that a better deal had been secured.

Be clear about what you're leaving out

If you've already compared the options and made your choice, you may not need to pay for another broad search. A focused engagement around the chosen deal can make sense.

But if that comparison hasn't happened, make the gap visible. Ask the adviser what they'd need to check before they could support the choice. Then decide whether that work belongs in the engagement.

A narrower fee doesn't answer a question you've removed from the scope.

Fractional fits when you need experienced help around a specific buying decision, rather than a permanent person looking for acquisitions. Match the adviser's experience to that work. Finding targets, testing the fit and structuring a deal aren't interchangeable skills.

The useful outcome is a clearer decision. Know whether you're hiring someone to help choose the company or to help buy the one you've chosen.

Yes. But the first job needs to fit what you actually know. A fractional leader should help you find the information needed for the next decision, not make you clean up the whole business before they can help.

I was talking with an operator who was looking at a possible engagement with a service business. He'd asked for financial and operating information. Some had arrived. Some was still missing. He'd already told the business which items mattered most.

My response was, “Your instinct was totally right. Like, let me help you prioritize this.”

Then we talked about what to do if the information still didn't come back.

Make the first ask smaller

If the numbers were scattered, I suggested narrowing the request again: “I need to know this number and this number.”

The point wasn't to pretend rough numbers were verified. It was to find a useful starting point without turning the owner into the operator's research assistant.

As I said on the call, “We want them to feel like you're removing work from them.”

That's something I'd look for when hiring. Can this person explain which question needs answering first? Can they tell you what they can work out from the records you already have? If a report doesn't exist, can they explain how they'll help build it?

A long request list leaves you with another job. A clear first question gives you a way forward.

Keep the promise inside the evidence

I also told the operator he needed enough information to make a proposal “and know that it's defensible.” We were still discussing a possible engagement, not a completed turnaround.

That distinction matters. An estimate may help decide what to investigate. It doesn't prove where the problem is or what fixing it will achieve.

I'd scope the first work around closing that gap: check the key numbers, explain what's missing and establish what the next step should be. If gathering the information is part of the job, put it in the scope. Don't leave it as homework for the owner.

Fractional fits when you need experienced judgment to get through this problem, but haven't established a need for a full-time leader. You can separate what you know from what still needs investigating.

You don't need perfect reports to start a conversation. You do need someone who can move it forward without promising more than the facts support.

Consider fractional procurement help when a supplier disruption could stop your business and nobody owns the work of preparing an alternative. Start by finding out where you're exposed. A lower price alone won't answer that question.

I was talking with a procurement operator about the kinds of problems he could own for a smaller manufacturer. I used an illustrative situation: a business relies on a few suppliers, hasn't revisited the relationships in years, and would be in trouble if one couldn't deliver.

My point on the call was simple: “You need somebody owning this.”

Find out what you can actually replace

If you're the owner, I'd start with a specific question: what happens if this supplier can't deliver the next order?

Ask someone to trace the answer through the business. What can't you make or deliver? How long can you keep working with what you have? Is the alternative a supplier you can actually use, or just a name somebody found?

A backup on a spreadsheet isn't much help if nobody has established whether it can meet the requirement. That doesn't mean you should immediately replace a reliable supplier or spread every purchase across several vendors. It means the decision should follow the work of checking your options.

Give the work an owner

In the example, I talked about someone renegotiating with existing vendors and finding new ones. Those are possible parts of the assignment. The right scope depends on what the review finds.

I'd want to know which suppliers we depend on, what alternatives we have and what it would take to use them. I'd also want to know who will keep it current. If the review ends with recommendations nobody has time to act on, you still have the same exposure.

This is where fractional can fit. You may have purchasing handled day to day, but need an experienced person to lead a defined review and follow through on the important changes. That doesn't automatically require building a new department.

Don't measure this work only by whether the next invoice gets cheaper. Ask what your business will be able to do if the next delivery doesn't arrive. A useful engagement should leave you with a more credible answer.

Ask how the fractional leader will make room for the beginning of your engagement, not just how many hours they'll give you each month. If they can't explain what happens between signing and doing useful work, get that clear before agreeing to a start date.

I've made this mistake myself. My fractional practice was primarily sales and marketing, and I was focused on growing it fast. I'd onboard a client, then two days later another client, then two days later another.

As I explained on a recent call, “things are starting to fall apart.” I hadn't given each client the attention they needed.

The missing attention was in the first few weeks. I hadn't given each relationship enough time to establish why I was worth paying on a retained basis.

That's something I'd want to understand as the buyer.

Ask what starting actually means

On that same call, we had to clarify what I meant by onboarding. I wasn't talking about waiting for paperwork. I meant “start doing work for them and make them receive value.”

Use that distinction when you discuss availability. A signed contract and a kickoff meeting can happen without the substantive work moving very far.

Ask the person to walk you through the beginning. What do they need to understand about your business? Which people do they need time with? What decision or piece of work will they take ownership of first? What do they need from you to get there?

Then ask whether their calendar actually allows for it. You don't need private details about their other clients. You do need a credible explanation of how they'll handle the start you've agreed to.

Agree on a start they can support

I wouldn't turn my experience into a rule that someone can only start one client a month. If two clients are ready to start, I'm not going to make one wait four weeks just to space them out. The question is whether we can do the work and give both a good early experience.

For your business, an honest later start may be more useful than an immediate start followed by silence. If the work can't wait, find out who can give it the attention it needs now.

Fractional lets you bring in experienced help without making every engagement a full-time role. But the initial work still needs room on someone's calendar. Agree on what will happen, who will do it and when you'll see the first useful progress.

Consider a fractional industry expert when entering a new market means relying on people whose day-to-day work you don't understand. Have them walk through what happens after the sale, including who answers questions and where the customer goes when something is unclear.

I was discussing a potential engagement with an operator who knew veterinary operations. A financing business was considering entering that market. She'd spoken with its founder about the training and support the offering would need.

One concern she raised was very practical: a pet owner signs up, then calls the hospital's front desk with financing questions. The person answering is also trying to run the front desk.

That was a scenario she wanted the business to plan for, not a failure we'd established had already happened.

Look at the work your product leaves behind

My question on the call was, “What do they actually need?”

A business entering a market may initially look for introductions or advice on its pitch. This operator was looking at the work the offering would create inside the customer's business.

That's a useful reason to bring in someone who's worked in the industry. They can help you test your plan against the working day of the people expected to use it. Ask how their experience fits that specific work.

Before launch, walk through one ordinary customer journey. Someone has agreed to buy. They don't understand the next step. Who do they contact? Does that person have the information and authority to help? If not, where does the question go?

Those answers should shape the training, support materials and division of responsibility. A product can be straightforward to explain in a sales meeting and still leave the frontline team with work nobody planned for.

Make the engagement produce decisions

I'd want the expert to identify those handoffs with the people who'll actually use them. Then get specific about what needs to change before launch and who will own it. If the arrangement depends on your customer's staff providing support, make that expectation visible rather than leaving them to discover it later.

Also establish whether the market entry is actually moving. On this call, I said, “We don't know how serious he is about actually entering.” We still needed to clarify the opportunity.

Fractional fits when you have an active expansion to prepare for and need industry experience around a defined set of decisions. You don't necessarily need a permanent hire. You do need a workable answer to what happens after somebody says yes.

Consider a fractional operations leader when the same backlog keeps coming back and you haven't established what's creating it. Before adding people to process more work, find out whether some of that work needs to exist at all.

An operator told me about a team overwhelmed by returned mail. The proposed solution was to move the processing to another group with more people.

She started asking about the beginning of the process. The addresses were wrong. Was anyone checking them before the mail went out? In the situation she described, they weren't.

My response was, “We call that root cause problem solving.”

Moving the work would have relieved one team. It would have left the business processing the same returns somewhere else. Her question changed the assignment from handling the pile to understanding why the pile existed.

Find the point where the work is created

For an owner, that's a useful way to evaluate fractional help. Ask the operator to trace a real item backward through the process. Where did it first go wrong? Who had the information needed to catch it? What would have to change there?

Don't assume every backlog has a simple fix. You may genuinely need more capacity. But establish that before making a permanent hire around work you could prevent.

The existing backlog still needs handling. A sensible scope should address both jobs: what happens to today's pile, and what changes so fewer avoidable items arrive tomorrow. Measure those separately. Clearing old work doesn't show that you've stopped creating new work.

Buy ownership across the handoff

The team receiving a problem may not control the step that causes it. That's where the engagement needs to go beyond a recommendation. Who will work with the upstream team, put the change in place and check whether it actually reduces the problem?

In the same conversation, I asked, “How do you want this solved?” We were talking about the choice between reallocating the business's existing resources and having the operator handle the work.

Fractional can fit when you need experienced ownership of that correction, but not another permanent layer of management. Ask for a specific change and a way to check it. If the proposal just moves the backlog to a different desk, keep asking where the work starts.

A fixed fee can make sense when you’re confident in the opportunity and want to keep more of the upside. A results-based fee can make sense when you want payment tied to an agreed outcome. Compare what you’d pay if the work succeeds, not just what’s due upfront.

I recently talked this through with a fractional finance operator. He was considering charging a share of the money he helped a company save instead of a monthly retainer.

The attraction is obvious: the company pays when value shows up. But I pointed out something that’s easy to miss. A business can like the opportunity so much that it doesn’t want to give away a percentage of it.

As I put it on the call: “They know what the upside is.”

The cheaper start can become the bigger fee

Think about a company hiring someone to improve margins. If the owner believes the operator can unlock a meaningful improvement, a fixed fee may be an attractive trade. The company takes the risk of paying for the work and keeps the improvement beyond that fee.

Under a performance arrangement, the operator may take on more risk of doing work without getting paid. In exchange, their fee can grow with the result. That can be a fair deal. It still deserves a look at the total cost.

Work through the same three cases under both proposals: little improvement, the result you reasonably expect, and a much better result. What would you owe in each case? What would the company keep?

Agree on what counts

Before choosing, get specific about the starting point, what improvement counts, how you’ll measure it and when the fee is earned. Separate a saving someone identified from a saving the business actually achieved. Decide who has to implement the change.

A mixed approach is possible too. In that conversation, I discussed a smaller retainer plus a performance fee, with the retainer credited against the later fee. That’s an option to discuss, not a standard every operator offers.

First make sure you’re comparing the same work. Reducing the scope is a different decision from changing how you pay for it.

My advice on the call was, “Don’t go in with a preconceived plan.” Start with the problem and the upside. Then choose a payment structure that makes sense for both sides.