One question came up during a recent discovery call, and it was one of those that lingers in the back of your mind long after the meeting ends.

“Should we outsource this role?”

Wrong question.

Ask whether you can afford not to.

By the time someone asks that question, the business has usually been feeling the pressure for a while.

More often, they’re trying to solve a real problem. They need capacity. They need specialist skills. They’re growing faster than they can hire, or they’ve reached a point where the way they’ve always built teams no longer fits where the business is heading.

What stood out to me wasn’t really the question itself. It was how little time we actually spent talking about outsourcing.

Instead, the conversation kept circling back to the role. What success would actually look like. Who this person would work with. How decisions would be made. What kind of ownership the position really needed.

By the end of the call, where the role would be based felt like one of the least interesting parts of the discussion.

The more I thought about it afterwards, the more I realized the conversation could have happened in almost any boardroom.

Every business arrives at the conversation from a different place.

Some have outgrown the way they’ve always hired. Others have reached the point where the cost of waiting is becoming harder to ignore.

What they all have in common is the same underlying question: what does this role actually need in order to succeed?

I’ve sat in conversations where two businesses were hiring for exactly the same position, yet the role couldn’t have been more different.

On paper, the job title was the same. The job description might even have looked similar.

Take an Operations Manager, for example.

In one business, the role existed to keep a proven system running efficiently. In another, there wasn’t really a system yet. They were hiring someone to build it. Same position. Completely different expectations.

That’s why these conversations rarely begin and end with a job title.

Sometimes a role changes long before the job description does. As businesses grow, responsibilities shift, priorities evolve and expectations change. The title stays the same, but what actually needs to be delivered by that role can look completely different.

By this point, answering whether the role should be outsourced had almost become secondary.

The discussion had shifted towards something far more useful: understanding what success in that role would actually look like.

How much autonomy would this person need?

Who would they be working with day to day?

Were they stepping into a business with established systems, or one that was still building them?

And twelve months from now, what would you hope this person had changed, improved or delivered?

One answer naturally led to another. The role itself became much clearer.

Coming back to, “Should we outsource this role?” felt like returning to a different question altogether.

The role hadn’t changed. The understanding of it had.

It had become much easier to see where the biggest risk actually was. It wasn’t in building the role through a global team. It was in leaving the business without the capacity it needed to keep growing.

Some roles benefit from being deeply embedded in the day-to-day workings of a business. Others can create just as much value from somewhere else, provided the role is clearly defined and the expectations are just as clear.

The strongest partnerships we’ve seen have one thing in common. At some point, “the outsourced team” simply becomes “our team.”

It happens because the business understood exactly what it needed before making the hiring decision.

I’ve had variations of this conversation more times than I can count. The question is usually familiar. The discussion never is.

Every business is working towards something different, and every role asks for something different in return.

Growth won’t wait.

Neither will the pressure on your team.

The question is: can you afford not to outsource?