How fractional IT leaders influence without a permanent seat

Every fractional IT leader is, on paper, a third party. You have a contract, not an employment agreement. Yet some fractional leaders end up attending senior leadership meetings and being treated as part of the team, while other contractors in the same business are kept at arm’s length and handed instructions.

The contract is rarely what makes the difference. What matters is how the relationship is framed at the start. If a client sees you as someone who delivers what they are told, you will be managed like a supplier. If they see you as the person who owns technology decisions, you will be brought into the room where those decisions are made.

This matters because being a trusted partner is simply the most effective way to work. You see problems earlier, you hear the commercial context behind requests, and you can shape decisions rather than react to them.

Being external can even work in your favour. One attendee with a long background in financial services pointed out that in heavily regulated firms, outside advisers are sometimes trusted more than permanent staff. Their independence gives leadership teams a level of reassurance that internal voices can struggle to provide.

One experienced fractional at the table was clear about this. When a prospective client approaches him, being part of the management team is a condition of the engagement. He will not take a role where leadership makes its decisions and then tells him afterwards what they think he needs to know.

A useful way to frame this is the RACI model. For any piece of work, people are either Responsible for doing it, Accountable for the outcome, Consulted for their input or Informed of the result. A fractional IT leader who is only consulted or informed has an opinion, not influence. To lead technology in a business, you need to be responsible or accountable for the decisions that matter.

In practice, that means agreeing a few things before the engagement starts:

• Which decisions sit with you, such as technology strategy, supplier selection and new software purchases.
• Which leadership meetings you attend and how often.
• Who you report to, and who has the authority to back your decisions when they are challenged.
• How technology spend is approved, and whether anything can bypass you.

These are easy conversations to have at the proposal stage, when the client is still deciding whether to bring you in. They are much harder to have three months later, when habits have already formed.

Another attendee described what happens when those terms aren’t set early. Working as a fractional with a professional services business, they were struggling to get traction with the leadership team. A senior leader kept buying new products and starting small technology projects of their own. Each time one problem was dealt with, another appeared, and it began to feel like a game of whack-a-mole.

Eventually the fractional said it had to stop. IT strategy and governance needed to sit with them. They were happy to bring in partners and specialists, but every technology decision had to go through one governance route. They framed it around a specific business risk: with tools and data spread across products nobody was overseeing, the business was exposed to data leakage and had no consistent way of managing its information.

It took a firm conversation, but it worked. The point was accepted and the leader stepped back. Today, technology decisions are routed through the fractional, and the leadership team defers to them.

Two lessons stand out. First, the argument was won by talking about risk to the business, not about the fractional’s own role. A senior leader will rarely give up control because an adviser asks for it, but most will listen when the issue is the security of client data. Second, this conversation would almost certainly have been easier at the start. Before the engagement begins, agreeing that all technology purchases go through you is a reasonable condition. Months in, it can feel like a challenge to leadership’s authority. If you can, settle decision rights in the engagement terms, so you never need to win them back.

Setting terms gets you into the room. It doesn’t guarantee everyone in it wants you there. One fractional described a senior leadership team split down the middle, with half ready for change and half resisting it. You think you are making progress because one leader is fully behind the plan, then another blocks it. His response is that he is prepared to lose business rather than stay in an engagement where change can’t happen.

This is one of the hardest positions for a fractional IT leader. Without buy-in across the leadership team, a successful change is difficult to push through and it can feel like you aren’t getting anywhere. Resistance often comes from people who have been in their industry for 20 or 30 years. They have seen initiatives come and go and they have built the current way of working. That isn’t unreasonable, but it does mean they need a reason to trust you before they will back you.

In our experience, a few things help:

• Test the appetite for change before you start. Ask each member of the leadership team what they want technology to fix. If only some of them can answer, you have learned something important.
• Secure a sponsor with real authority. Influence is much easier when someone at board level owns the change alongside you.
• Find out what the sceptics care about. Resistance usually has a reason, such as workload, past failures or a fear of losing control. Frame the change around their pain points, not your plan.
• Start with low-hanging fruit. Quick, visible wins show your worth to the people who doubt it. Each one earns a little more trust for the next, larger change.
• Know your walk-away point. Decide in advance what conditions would make the engagement unworkable. If a key decisionmaker will never buy in, staying on costs you time and reputation.

Walking away is harder for a solo fractional than for a consultancy, especially if it is your only engagement. That is exactly why the conditions need to be clear before you begin. Qualifying a client properly at the outset is far easier than leaving one later.

Setting terms early also protects your intellectual property (IP). One attendee described writing several detailed scopes of work for a prospect, each time being asked for more, only to find the client had taken his structure and ideas to someone else. We have seen the same pattern ourselves, with clients who return every few months saying they are ready, take a day or two of free work and then go quiet again.

Some free work is a normal part of winning business. The aim is to make sure it demonstrates your value without handing over the solution. Our recommendations are:

• Share the what, not the how. In early conversations, explain the problems you can see and the outcomes you would aim for. Keep the detailed roadmap and method for paid work.
• Cap your free time. Decide in advance how much unpaid scoping a prospect gets, such as an initial meeting and one follow-up.
• Offer a paid discovery phase. A short, fixed-price diagnostic gives the client something useful and gives you a fair return for your thinking. It also tests whether they are serious.
• Notice repeat behaviour. A client who keeps asking for more detail without committing is telling you how they will treat you once engaged.

How a client handles the scoping stage is often a good guide of how they will work with you, or not, going forward.

As an IT leader who doesn’t sit on the board, influencing long-established leadership teams is one of the hardest parts of the job. There is no exact formula, and not every engagement will succeed. But the fractional IT leaders who have the most influence tend to do the same things.

They set their terms before they start. They agree to be responsible or accountable for technology decisions, not just consulted or informed, and they put decision rights and governance into the engagement from day one.

They read the room early, find out where the pain points and the resistance sit, and build a plan to win trust. They start with visible, achievable wins and use them to earn the right to lead bigger change. And they know in advance what would make them walk away.

Once trust is in place, implementing change becomes much easier. Our recommendation to any fractional IT leader starting a new engagement is simple. Before you sign, write down the decisions you need to own and the conditions you need to be effective, and agree them with the client. It is the single conversation most likely to decide whether you are treated as a leader or as a supplier.

At Fluid, we support fractional IT leaders with the delivery capacity to turn strategy into results, so you can focus on leading. If you’d like to talk about how we could support your next engagement, get in touch.