Hook

Video Poster Image

Key Takeaways:

  • Process Before Platform
    Map your customer journey first. Then choose the tools that support it. Automation without clarity just amplifies the chaos.
  • Build a Single Source of Truth
    Stop juggling multiple systems. Pick one core platform for data and integrate everything else into it.
  • Automate the Repetitive, Personalise the Rest
    Automate the predictable. Keep the personal moments human. That’s how you stay connected while scaling.
  • AI Should Be Your Teammate, Not Your CEO
    Use AI to assist, not decide. It should lighten your cognitive load — not replace your judgment.

If your business feels like it’s held together with spreadsheets and wishful thinking, this episode will show you how to scale without losing the soul of your brand.

Sub-Header 1

Sub-Header 2

Sub-Header 3

Sub-Header 4

Sub-Header 5

Sub-Header 6

Sub-Header 7

Sub-Header 8

Sub-Header 9

Sub-Header 10

How to hand over client work in your cybersecurity consultancy without taking it back: The SALE™️ Method

Aug 18, 2026
Text - sabotaging growth? Image Deirdre Martin on AI generated background

You handed the client over on Monday.

By Wednesday, you had the work back.

The client hadn't complained. Your team member hadn't made some spectacular mess of it. You simply started thinking ahead. What if the client notices the difference? What if the quality isn't quite right? What if they start wondering why they're paying for an entire company when they could have hired someone cheaper?

Before the client said a word, the work was back with you.

If you're running an established cybersecurity consultancy, this probably sounds familiar. And if it does, you're likely one of three founders.

You're Climbing Callum: revenue is growing, but so is your workload. Every new client adds another decision that has your name on it.

Or you're Stretched Stuart: you have a good team and they handle the day-to-day. But the serious conversations, the pricing calls, and the complicated client situations still find their way back to your desk.

Or you're Plateaued Peter: strong reputation, solid clients, good credibility. But the next stage of growth requires more of you, and there is not more of you to give.

Different situations. Same problem. The amount of work that can happen without the founder has not changed.

 

The ceiling that shows up in your diary first

There are only so many client calls you can attend in a week. So many reports you can personally write or review. So many difficult conversations where you can be the one in the room.

At some point, your consultancy hits the capacity of your calendar.

This is where it gets a bit sneaky. You tell yourself the client isn't ready for someone else. But in years of coaching cybersecurity founders through exactly this, I've found that most of the time, the client never said that. You said it for them.

Clients ask about your processes, your controls, your business continuity. They want to know how the service continues when key people aren't available. They want reassurance the business can run.

What they generally don't ask is: "Will you personally write every report for me?"

They don't ask that because they're buying from a company.

Which makes it slightly ironic when you're sitting there, convincing yourself they'll panic the moment someone else does any of the work.

 

Why the logical decision gets made emotionally

Here's the thing worth sitting with.

The decision to hand work over is usually made logically. You thought it through, identified the right person, briefed them properly. You had the Monday handover.

The decision to take it back is made emotionally.

A question from the client. An email where they copy you in. A half-second pause on a call. And suddenly the voice on your shoulder goes: There you are. I knew this would happen.

So you step back in. It's your business. You're the person who fixes things. In the moment, it feels like the responsible call.

But what actually happened? Your team member lost the chance to deal with it. The client learned to wait for you. And you're back doing the work that was handed over on Monday.

The handover hasn't failed. You felt uncomfortable. And when your name, your reputation, and a valuable client are all involved, discomfort can look an awful lot like evidence.

That is the distinction I want to draw your attention to: the decision to take back was made on a prediction, not on proof. Your prediction beat your decision.

 

Why your consultancy still feels small

A cybersecurity consultancy can look bigger on paper while staying just as dependent on the founder.

You've hired people. Payroll has gone up. There are more names in the team meeting.

But the important client work still finds its way back to you. The team might prepare it, you end up deciding it. They might draft it, you end up rewriting it. They join the call, you handle the awkward bit.

And then everyone wonders why the consultancy still feels small. Why it's not really growing.

It feels small because the amount of work that can happen without you hasn't changed.

That's the ceiling, and it shows up in your diary before it shows up in your revenue figures or your team headcount or anything else.

 

What the client is actually buying

There's a story you're telling yourself about the client.

You were probably on the original sales call. You were the person who built the relationship. You were likely the one who spotted the real problem when everyone else was looking in the wrong place. When something got difficult, you stepped in and sorted it.

So when you think "they hired me," you're not making it up entirely. There is truth in it.

But you've been filling in the rest of the story.

The client asks a question, and you think: they don't trust John. They copy you into an email, and you think: they want me involved. There's a pause on the call, and suddenly the story writes itself: see, I knew this would happen the moment I brought someone else in.

So you step back in.

Here's what I'd ask you to consider. When clients ask about your processes, your controls, your insurance, your business continuity planning, they're asking: is this company solid? Will the service continue if someone leaves? Do you have the right people and the right systems?

What they're generally not asking is whether you, specifically, will be writing every deliverable personally.

 

The SALE™ď¸Ź method: how to stop treating a prediction as proof

I use the SALE™ď¸Ź method when a founder has started treating a prediction as though it's already happened.

Each letter maps to a step. There are five of them.

S is for Story.

Name the story you're selling yourself in one sentence. Specific. Get it down.

"The client will lose confidence when John starts running the reporting cycle." That gives you something useful.

"I'm going to ruin the relationship by giving John the work" doesn't. That's so broad your brain could spend the rest of the week finding reasons to believe it. Go specific: what exactly do you think will happen? When? What will the client notice? What will they actually say?

A is for Audit. This isn't about arguing with yourself or pretending everything will be grand.

Start with the evidence that supports the concern. The client knows you, yes. They've asked for you personally before. Your team member is newer to the account. Fair enough.

Now ask: what else is true? Has your team member already done part of this work? Has he handled something without you in the room? Has he delivered well when you weren't on the call? And what don't you actually know yet? Often, the biggest unknown is what the client thinks, because nobody's thought to ask them.

I had a client once who came to every coaching call telling me she was rubbish at sales. So I asked her to go back through her last ten booked sales calls. How many people turned up? How many bought? Where did the calls come from?

She came back with an 83% conversion rate.

She was not bad at sales. The problem was that people were booking calls and not showing up. A completely different issue, and one that was much easier to fix. The audit stopped her solving the problem in her head and showed her the one that was actually there.

L is for Likelihood.

How likely is the outcome you're predicting?

Could your team member need a bit of correction? Yes, maybe. Could the client ask why things are changing? Of course. Could there be an awkward moment on a call? Quite possibly.

But across everyone I've coached through handing over delivery, not one founder has lost a client because someone else started doing the work. That's my coaching experience, not an industry-wide study. It's still worth something: it gives you solid ground to weigh against the story in your head.

There's research in psychology on affective forecasting that points to something useful here. We're consistently poor at predicting how bad a future event will actually feel, or how long the impact lasts. We're very good at imagining the worst. And we're poor at remembering that we'd actually handle it.

If the client hesitates for half a second, you've mentally lost the account, damaged your reputation, and worried about your cash flow for the next month, all before anyone has actually complained.

So ask yourself: what do I think will happen? What is the evidence it might? On a scale of one to 100, how likely is it? And what would I do if it did happen? Once you know what you'd do next, the risk usually stops feeling quite so enormous.

 

E is for Execute & Emerge.

This means you stop thinking about the story you were selling yourself, and you take action like handing over a client, and you actually hand one over.

Speak to the client before anything changes. Introduce your team member properly. Explain why you chose them, what they'll own, and how the review period will work.

Something like this:

"For the next two weeks, John will run the reporting cycle and the follow-up actions. I'll review everything before it goes to you. We'll have a catch-up at the end of the two weeks. And of course, if there's any issue during that period, you can raise it directly with John. After that, John will own the delivery. I'll still be involved in the relationship and any strategic decisions, and we'll catch up quarterly to assess how things are going."

That gives your client continuity. It gives your team member proper ownership. And it gives you a date when you're supposed to step back.

"I'll review it after two weeks" is a plan.

"I'll stay copied in for now" is how you end up reading a client email at 10:40 on a Sunday night, seven months later, telling yourself you're only keeping an eye on things.

Emerge.

This is the step most founders forget. Reflect on what you've realised and how you've changed as a result. Go back and look at what actually happened. Did the client lose confidence? Did they accept John? What did he handle well? What needed a bit of help? What can he take on next?

I had a client who'd hired a salesperson. The salesperson booked an introductory call with a prospect and then couldn't make it. My client had to take the call himself. He was expecting rejection before he'd even joined the call, because the warm introduction hadn't happened the way he was used to.

That conversation became a proposal. And the relationship has since opened up a much larger opportunity than the original call would have suggested.

He'd spent a lot of time worrying he wouldn't be accepted, but working through the SALE ™ď¸Ź method allowed him to let go of those stories before he got on the call. And... the result couldn't have been more different from the story.

That's why you have to go back and look at the evidence. Otherwise, you can get real proof that things went well and still carry the old story into your next decision.

 

The silent handover problem

One thing I'd avoid if you are passing over the relationship management of a client: the silent handover.

I saw plenty of these in my 20 years in retail banking. A client would discover they had a new relationship manager, and they'd be furious. And usually, they had no issue with the new person. They were furious because nobody had thought to tell them someone new was coming in.

They felt passed around. Often the whole thing could have been avoided with one brief conversation before anything changed. 

Tell the client before the emails or the calls start coming from someone different. Tell them who that person is. Explain why you trust them. Be clear about what you're still involved in.

And then follow through on stepping back when you said you would. A temporary safety net becomes the operating model when nobody decides it shouldn't be.

 

What happens when the handover actually works

Once delivery is genuinely in your team's hands, you get to choose what job you want.

You might want to step back from client work and run the business. You might love delivery and want to keep doing it. That's a real option. You could bring in a general manager to run operations and growth while you stay close to the technical work. But you have to let them run it.

Hiring someone to manage the business and then overruling their decisions every day is a very expensive way of staying in control of everything.

You can also do both. Stay in delivery and run the business. Nothing wrong with that. But it comes with a ceiling. Leadership takes time. Sales conversations, proposals, planning, admin, they all take their share. Whatever's left is the delivery you can personally do.

You can do both. You just can't do both while pretending the ceiling doesn't exist.

 

Questions worth sitting with this week

Which client relationships still depend on you being involved in every conversation?

Where have you decided what the client will think before they've said anything?

And where has a two-week review period somehow been running for eight months?

If your consultancy is already doing well but the delivery and difficult decisions keep coming back to you, that's the problem I work on with cybersecurity founders inside Millionize: The Built Beyond You System.

It's a 6-month advisory and implementation build where we develop a buyer-ready position, turn how you sell into a playbook your team can use, get your delivery standard out of your head and into the business, and put an operating rhythm around it so ownership is clear. One client went from roughly £95k to £385k in a financial year while cutting delivery time from 5 to 7 days down to around 2.

If that sounds like the direction you want to be heading, you can apply to work with me using the link below. We'll look at where the business still depends on you, what's keeping it there, and whether Millionize is the right next step.

The client handover survives the week when you stop treating the story you're selling yourself as proof.

Name the story. Audit what you actually know. Look at the likelihood. Execute a controlled handover. Then emerge with the evidence.

Learning to let go gives the client, your team, and yourself the chance to trust the business you've built.

 

[Apply to work with Deirdre →] https://www.deirdremartin.ie/book-a-call

Deirdre Martin is a Neuro-Strategic Business Coach and StoryBrand Certified Guide who helps cybersecurity consultancy founders build businesses that grow without everything running through them. She spent 20 years in banking and financial services before building her coaching practice from scratch, and now works with established founders who are ready to move from founder-dependent to founder-light.

Stay connected with episodes, news and behind-the-scenes updates!

We hate SPAM. And we will never sell your information, for any reason.

Frequently Asked Questions

Resources Mentioned

Recent Episodes

How to hand over client work in your cybersecurity consultancy with...

Delegation for cybersecurity founders: what to hand over, and what...

Why Marketing Money Disappears When Brand Strategy Comes Second