What to never delegate to a VA, and what founders always get wrong.

Here is what I have learned about the two things you should never delegate, and the mistake almost every founder makes that has nothing to do with the task list.

What should a founder never delegate to a VA?

Two categories, and they are not the ones most lists give you. The usual advice says keep the “strategic” work and offload everything else. That is too vague to be useful. Here are the two lines I have actually seen get crossed, each with a real cost.

The first is anything that carries your authority as the leader. A client of mine went away and handed off sending the leadership message to his community group, plus following up on whether members had hit their KPIs and chasing billing and payments. The tasks got done. Nothing technically broke. But the community felt it immediately: why is an assistant sending this, when it should come from the leader? The message needed his voice and his relationship with those people, and a delegated version, however well written, quietly cost him standing. That is the test the best delegation filters use. If a task needs your judgment, your relationships, or your voice, it stays with you. Leadership communication needs all three.

The second is anything that requires you, specifically, to prove you are you. Another client handed off changing the security system on his house, and separately, reviewing his energy, health, and auto insurance. Reasonable admin to delegate, on paper. Except when my VA called, every provider required the actual account holder to verify their identity. They would not authenticate a third party acting on his behalf, and rightly so. We had to get the client on the line to verify before anything could move. Identity cannot be delegated. Anything gated behind personal verification, banking, insurance changes, account security, will stall the moment it leaves your hands, so it belongs with you from the start.

Then what can you actually delegate?

Almost everything else, and this is where founders leave the most time on the table. The research is consistent that 60 to 75 percent of a founder's weekly work is delegatable, and my own client hours bear that out.

The reliable list is long: entering and organising leads in the CRM, lead management, sending the daily, weekly, and monthly emails and follow-ups, building the monthly report, research, sourcing contacts and getting quotes over chat or email, design, posting, and scheduling. None of that needs your voice or your judgment. It needs a clear brief and someone reliable to own it. A founder who keeps doing these by hand is not protecting the business, they are working in it instead of on it, on tasks worth a fraction of their time.

Delegate the work that only needs to get done. Keep the work that needs to be you.

Why does delegation to a VA fail, then?

Here is the part that matters most, and it is the thing founders always get wrong. The problem is almost never what they delegate. It is how.

I have seen the same failures again and again, and none of them are about picking the wrong task. Founders delegate without clarity, handing over a task without saying what outcome they actually want or what they will still own, so the VA guesses and the output comes back wrong. The research calls this out bluntly: a task handed off without its context is not delegation, it is deferral with extra steps, and it lands right back on your desk the first time reality shifts. Clarity is where most delegation breaks, not competence.

Founders also delegate everything and then lose the thread, until they hit a moment of “I am not even sure, I would have to ask my VA,” which means they have stopped seeing their own business. Delegation is not disappearance. You hand off the work, not your awareness of it. Then there is the founder who bombards a VA with a pile of last-minute tasks and expects it all magically absorbed, with no task system and no reporting. A good VA is not a buffer for your lack of planning. Give the work early, know your VA's real capacity, and if you have more than one, run them as one team, not separate silos.

And there is the access mistake, which is really a protection issue. Founders either hand over full control of everything, banking, the entire CRM, every document, or they lock down so hard the VA cannot function. The right answer is scoped access: enough to do the job, not the keys to the whole business. A professional VA setup will actually ask you to limit sensitive access, because scoped permissions protect both sides.

The myth that breaks the most founders

There is one belief underneath all of these, and it is the most expensive one. The fantasy that a VA means your life is now set, that you can travel, drop to a few hours a day, and let someone else run it.

Here is the truth I tell every founder. A VA can take 70 to 80 percent of the manual work you were doing by hand off your plate. That is real, and it is a lot. But that remaining slice is not more admin. It is the leadership, the decisions, the relationships, the voice, the things the two scars above were about. Delegation done well gives you your hours back so you can do what a leader does. It does not give you permission to stop leading. The founders it blows up on are the ones who confused handing off the work with handing off the responsibility.

So before you delegate anything this week, do one thing. Take your recurring tasks and run each one through a single question: does this need my judgment, my relationships, or my voice? The “no” pile is your delegation list, and you should hand it off without guilt. The “yes” pile is yours, and no VA, however good, should be holding it. Get that sort right, brief the “no” pile clearly, and delegation stops being a risk and starts being the thing that finally gives you your time back.

If you want a team that already knows where that line sits, that is the kind of VA support we build: people who take the 70 to 80 percent that should leave your plate, and who will tell you plainly when something should stay with you.