How to Reduce Owner Dependency Before Selling Your IT Business

Could your IT business operate successfully without you?

It’s a simple question, but if you’re thinking about selling your business at some point in the future, it’s an important one.

Perhaps you have a good team, loyal customers and a profitable business.

But you’re still involved in many of the important decisions.

Key customers still call you.

You get involved when a significant sales opportunity comes along.

People come to you when there’s a problem.

You hold knowledge about products, customers, suppliers or the way the business operates that nobody else quite has.

None of this is particularly unusual.

When you’ve spent years building an IT business, it’s very easy to become central to how it operates.

But if a potential future exit is somewhere on your horizon, reducing that dependency can be worth starting much earlier than you might think.

And it’s not simply about working fewer hours.

It’s about building a business that is increasingly capable of operating successfully without your constant involvement.

What does owner dependency actually mean?

Being busy isn’t necessarily the same as having an owner-dependent business.

You could choose to work long hours and remain closely involved while still having a capable leadership team and people who can make decisions without you.

The better question might be:

What happens when you’re not there?

Do important decisions wait for you?

Do major customers expect to deal with you personally?

Are you still responsible for winning or closing significant sales opportunities?

Does important technical, product or commercial knowledge sit primarily with you?

When employees encounter a problem, do they solve it — or bring it to you?

Are there processes that work largely because you know how to make them work?

The more of those questions that lead back to you, the more owner dependency may exist within the business.

Why can owner dependency matter when you’re considering a future exit?

A potential buyer isn’t only interested in how your business performs while you’re there.

They’ll also want to understand what happens when you’re no longer there.

If important customer relationships, sales, knowledge, decisions and day-to-day operations depend heavily on the owner, it naturally raises questions about how the business will operate after that owner eventually leaves.

There’s also a very practical consideration for you.

If you ultimately decide to sell and much of the business still depends on your personal involvement, a buyer may want — or need — you to remain involved for longer to help with the transition.

As you move closer towards a potential transaction, the role of an M&A adviser becomes different from the earlier exit-readiness work involved in strengthening you and the business.

By contrast, if you’ve developed a capable team, transferred important relationships and knowledge, and built a business that can operate successfully without your constant involvement, you may have greater flexibility around what your own transition looks like.

That doesn’t mean reducing owner dependency guarantees you’ll be able to walk away immediately after a sale. Every transaction is different, and the eventual structure of a deal may involve a handover period or some continued involvement.

But if your personal objective is eventually to step away, it makes sense to start building a business that is increasingly capable of operating without you before you try to exit it.

And even if you ultimately decide not to sell, reducing owner dependency can still create something valuable:

More freedom while you continue to own the business.

Start by finding where the business depends on you

Before trying to reduce owner dependency, you need to understand where it exists.

One question I often use is:

If you stepped away from your business for a month tomorrow, what would be the first thing that started to wobble?

Think about:

Decisions
Which decisions still require your approval?

Customers
Which important customer relationships depend primarily on you?

Sales
Could the business continue generating and winning new opportunities without your involvement?

Knowledge
What do you know that other people in the business don’t?

People
Who regularly comes to you to solve problems or decide what to do next?

Processes
Which activities work because you’re there to make sure they happen?

You may discover that the business isn’t dependent on you everywhere.

The important thing is to identify where it is.

Every business is different

No two IT businesses are exactly the same, and neither are the owners who run them.

The areas where your business depends on you may be completely different from the areas where mine depended on me.

I’m also looking back at my own experience with the benefit of hindsight.

There are things we did that helped make the business less dependent on me, but there are also things I would do differently if I were preparing the business for sale today.

I would have started some of that work earlier. I would have created greater focus in certain areas, transferred some responsibilities sooner and thought more deliberately about what the business needed to look like without me at the centre of it.

I’ve tried to capture some of those lessons in this article — not because they’re a prescription for every IT business, but because they may help you ask better questions about your own.

I had to confront owner dependency in my own IT business

When I look back at the IT business I co-founded and eventually sold, I can see just how involved I had become across the organisation.

I was heavily involved in sales and significant projects.

I had relationships with major customers — although I also continued looking after some much smaller ones.

I was involved in supplier relationships, attending events, presenting at supplier events and completing training.

I was regularly pulled into discussions around software and product development.

I was involved in pricing and commercial decisions.

And for a long time, I had significant responsibility for updating, maintaining and developing our highly customised CRM system.

I was also one of the people employees came to when something needed solving.

Not everything depended on me. Other members of the team had substantial responsibility in areas such as finance and marketing.

But I was involved in far too many parts of the business.

I don’t think I deliberately created that dependency.

It developed gradually.

And I suspect that’s how it happens in many owner-led businesses.

You start the company. You learn how everything works. You build the relationships. You solve the problems.

And years later, everybody has become accustomed to you knowing the answer.

Including you.

Stop doing all the thinking

One of the biggest changes for me came when I changed my approach to leadership.

Around 2017, following my coach training, I started asking more questions rather than automatically providing answers.

Previously, if somebody came to me with a problem, I was very quick to start thinking about the solution.

In effect, I was taking on their thinking.

So I started responding differently.

“What do you think?”

“How would you resolve it?”

Initially, I remember getting a few raised eyebrows.

People weren’t necessarily doing anything wrong. I had simply spent years conditioning myself to be the person who came up with the answer.

Over time, something changed.

People increasingly started coming to me with a problem and a proposed solution.

And nine times out of ten, that solution was perfectly adequate.

Sometimes it was better than the answer I might have produced quickly myself.

That taught me something important about owner dependency.

Sometimes employees aren’t unwilling to take responsibility.

The owner may simply have become too accustomed to taking the responsibility back.

Transfer responsibility, not just tasks

Delegating more work doesn’t necessarily make your business less dependent on you.

You can delegate a task while still insisting that every important decision comes back to you.

If that happens, you’ve moved the work — but you haven’t necessarily moved the dependency.

People need the opportunity to develop their capability.

That may mean gradually giving them greater responsibility, appropriate authority and room to make decisions.

And inevitably, they won’t always do things exactly as you would.

That’s part of the process.

If you’ve spent years being the person who knows how everything should be done, resisting the temptation to step back in can be difficult.

But if everybody has to reproduce your exact answer before they’re trusted to make a decision, the business may struggle to become genuinely less dependent on you.

Look for unnecessary complexity

There’s another aspect of owner dependency that I think is easily overlooked.

Complexity can make the owner more necessary.

If a business has accumulated numerous products, services, suppliers, commercial arrangements and different ways of doing things, somebody has to understand how all those pieces fit together.

In an owner-led business, that person can easily become the owner.

In my own business, one of the things I would do differently with hindsight is create greater focus earlier.

We dealt with a large number of manufacturers and offered a broad range of products.

Looking back, I would probably have reduced the number of manufacturers considerably and concentrated more of our effort on the areas where we had decided we genuinely wanted to compete.

I would also have moved away from bespoke software development earlier and focused more on developing repeatable solutions and platforms.

And as the business developed, I became increasingly willing to decline meetings and opportunities that didn’t fit where we wanted to focus.

But that’s our example.

It doesn’t mean your IT business necessarily needs fewer suppliers, products or services.

Your source of complexity may be completely different.

The more useful questions are:

"What is creating unnecessary complexity in your business?"

And:

"How much of that complexity eventually finds its way back to you?"

Spread important relationships

Customer relationships can be another source of owner dependency.

It’s natural for founders and owners to develop strong relationships with important customers.

In the early stages of a business, that’s often an advantage.

But if a customer sees their relationship as being primarily with you, what happens when you’re no longer there?

Reducing that dependency doesn’t mean suddenly withdrawing from important customers.

It can mean gradually broadening the relationship.

Introduce other members of the team.

Allow them to lead meetings.

Let somebody else take responsibility for the account.

Make sure knowledge about the customer is shared rather than sitting with one individual.

The same principle can apply to important supplier and partner relationships.

The aim is for those relationships increasingly to belong to the business, rather than solely to its owner.

Get important knowledge out of your head

Knowledge can create dependency too.

In my case, one example was our CRM system, Commence.

It was an off-the-shelf product, but we had customised it considerably over the years, and for a long time I was heavily involved in updating, maintaining and developing it.

Eventually, that knowledge and responsibility needed to move away from me.

Your equivalent may be completely different.

It could be pricing.

Technical architecture.

A particular software platform.

How major projects are scoped.

Supplier knowledge.

Customer history.

Commercial processes.

Whatever it is, ask yourself:

What does the business need to know that currently lives primarily inside my head?

Documenting processes can help.

But documentation alone doesn’t remove owner dependency if everybody still comes back to you whenever they need to make a decision.

Knowledge needs to be transferred and used.

Test whether you’re actually becoming less necessary

One way of finding out whether you’re making progress is to step away.

I certainly wouldn’t claim that by the time we sold our business I could disappear indefinitely and never think about it.

That wasn’t my experience.

But I did notice progress.

By around 2018, I remember going on holiday and receiving considerably fewer interruptions than I had in earlier years.

Part of that came from changing my leadership approach.

Part of it came from preparing properly.

I would let key customers know I was going away.

Someone would take responsibility for my role while I was absent.

I would only expect to be contacted if something genuinely required my involvement.

Although, in truth, I would still normally check in once or twice myself to see how things were going.

Some habits take longer to change than others.

The important point wasn’t that the business suddenly stopped needing me.

It was that fewer things genuinely required my involvement.

You don’t necessarily need to start by disappearing for a month.

Take a day away.

Then perhaps several days.

Pay attention to what happens.

Which decisions wait for you?

Who gets stuck?

Which customers specifically ask for you?

What problems are sitting on your desk when you return?

Those are useful clues about where dependency still exists.

You may need to change how you measure your own value

There’s another side to reducing owner dependency that I didn’t fully appreciate at the time.

For many years, one of the ways I measured my own contribution was through sales.

How much business was I bringing in?

How many hundreds of thousands of pounds of sales had I generated that month?

As we moved closer towards eventually selling the business, my role changed.

I wasn’t handling as many individual sales opportunities.

At the same time, I was spending considerable amounts of time preparing the business, working through pre-due-diligence and due diligence, meeting with people, presenting to potential buyers and dealing with everything involved in preparing for a transaction.

My contribution had changed.

But for a while, my personal scoreboard hadn’t changed with it.

Looking back, that’s an important lesson.

If you’ve spent years being the person who solves the problems, wins the deals, knows the answers and makes the decisions, becoming less necessary can feel uncomfortable.

It can almost feel as though you’re contributing less.

But perhaps the measure needs to change.

Your value as an owner may increasingly come from building a business that needs less of you, rather than continually proving how much it still needs you.

Don’t try to remove yourself overnight

Reducing owner dependency isn’t about trying to make yourself irrelevant by next Friday.

It can take years.

And different areas of the business may move at different speeds.

Start by identifying where the greatest dependencies exist:

  • Choose an area.
  • Develop capability.
  • Transfer responsibility.
  • Give people appropriate authority.
  • Test what happens.
  • Learn from it.
  • Then move on.

Over time, the objective is not necessarily for you to do nothing.

It’s for your involvement to become increasingly a choice rather than a requirement.

Owner dependency is only one part of exit readiness

Owner dependency is important, but it doesn’t exist in isolation. Preparing an IT business for a potential future exit involves looking at the business more broadly

It connects with the strength of your leadership team.

Your ability to generate sales without the owner.

Customer relationships.

The predictability of revenue.

Systems and processes.

Financial visibility.

Positioning.

And the risks that may exist within the business.

And owner dependency may not be the most important issue in your business.

Every business is different, which is why I don’t believe there’s a single checklist of improvements that every owner should make before a potential sale.

The starting point is to understand your own business.

Where are you today?

Where does the business still depend on you?

What else may need strengthening?

And, importantly, what deserves your attention first?

That’s why I believe preparing for a potential future exit should begin by stepping back and assessing where the business is today — before deciding what needs to change.

Not sure where to start?

I’ve created the Exit Readiness Focus Framework specifically for IT business owners who are beginning to think about a potential future exit.

It helps you step back from the day-to-day, think about what you want personally, assess where your business is today and identify what deserves your attention first.

PAUSE → CLARIFY → PRIORITISE → COMMIT → PROTECT

The complete workbook is free to work through in your own time.

DOWNLOAD THE FREE EXIT READINESS FOCUS FRAMEWORK

Leave a Reply

Your email address will not be published. Required fields are marked *

This field is mandatory

This field is mandatory

This field is mandatory

There was an error submitting your message. Please try again.

Security Check

Invalid Captcha code. Try again.

Information icon

We need your consent to load the translations

We use a third-party service to translate the website content that may collect data about your activity. Please review the details in the privacy policy and accept the service to view the translations.