Every client is different. Different industries, different team sizes, different ways of making decisions. But after a few years in this work, I’ve noticed that certain questions come up again and again. Not because people are unoriginal, but because the questions tend to point at the same underlying things.
Here are the ones I hear most. And what they usually mean beneath the surface.
“How do I know if I’m ready?”
This is the question I get asked before someone hires support, and sometimes even after they already have. It tends to arrive in a few forms. “Is it too soon?” “Am I busy enough to justify this?” “What if I’m not ready to let go of things yet?”
The readiness question is usually less about logistics and more about trust. Trust in the process, and sometimes trust in themselves. Business owners who’ve been holding everything together for years often don’t have a template for what it feels like to hand something over. So the question of readiness is really a question about what comes next.
My honest answer is usually this: if you’re asking whether you’re ready, you probably are. The people who aren’t ready don’t tend to ask.
“What should I hand over first?”
This one comes up in the first few weeks of working together, and it tells me a lot about how a client thinks.
Some people immediately want to hand over the things they least enjoy. Inbox management, scheduling, the admin that piles up. That’s completely understandable. But it’s not always where I can add the most value first.
The better question is: what’s the thing that keeps slipping? Not the task you dislike most, but the one that, when it doesn’t get done, has a ripple effect. That’s usually the place to start. Fix the quiet leak before you redecorate.
“How do you handle confidentiality?”
This one comes up often, especially with clients at an executive level or in industries where information is particularly sensitive. Legal, finance, healthcare-adjacent work.
The short answer is: the same way any trusted colleague would. With discretion, with clear agreements in place, and with the understanding that access to information is a privilege, not a default.
I’ve never found this to be a reason not to work with a VA. I’ve found it to be a reason to choose carefully, and to have the conversation upfront rather than assuming.
“How will I know if it’s working?”
This one is worth sitting with, because it reveals something about expectations.
Some clients measure it by tasks completed. Others by how they feel at the end of a week. Some want formal reporting. Others want to notice the absence of something; the inbox that no longer stresses them, the Friday that doesn’t bleed into the weekend.
There’s no single right answer, but I always encourage clients to decide what success looks like before the work begins, not after. Otherwise you’re evaluating something without a benchmark, and that tends to lead to vague dissatisfaction that’s hard to name and harder to fix.
“What happens when something goes wrong?”
This is my favourite question. Not because things go wrong often, but because the people who ask it are usually the people I work best with.
When someone asks this upfront, they’re not assuming failure. They’re thinking clearly about how a real working relationship functions. Things do go sideways sometimes. A miscommunication, a missed deadline, a task done differently than expected. The question isn’t whether it happens. It’s whether both sides can say so when it does.
My answer is always the same. When something goes wrong, we talk about it. Directly, and soon. Nothing festers if it gets named quickly.
The thread running through all of them
If I step back and look at these questions together, they’re all asking some version of the same thing: can I trust this?
Trust that the timing is right. Trust that the handover will go well. Trust that private information stays private. Trust that the work will be good. Trust that friction, when it comes, will be manageable.
That’s the work underneath the work. And it’s why the first few weeks of any partnership matter so much. Not because everything needs to be perfect, but because that’s when trust either starts to build or quietly doesn’t.
In my next post, I’ll take a wider view. The patterns I keep seeing across the different businesses I support, and what they might mean if you’re reading this and thinking about your own.