Becoming a Virtual Assistant With No Experience

Assistant work is a bundle of small jobs a business owner has stopped being able to hold, handed over in whatever order they fell apart.

That is why the job posts read like a software list. The software is incidental. Where those clients are found is a separate decision, settled in which freelance platforms are worth your time.

The six kinds of task clients hand over first

Inbox triage. Not answering everything — sorting. What needs the owner, what needs a standard reply, what needs deleting, and what has been sitting there for three weeks going quietly wrong.

Calendar. Booking, moving, confirming, and protecting blocks of time from being eaten. This is where you find out whether the client actually wants the meetings they say yes to.

Moving data between places. A form fills up and somebody has to put it in the system. Orders into a spreadsheet, contacts into a CRM, receipts into a folder with sane names.

Chasing. Suppliers who have not confirmed, customers who have not replied, an invoice nobody has paid. Polite, repeated, logged. Few people enjoy it, which is precisely why it gets delegated.

Research lists. Find twenty suppliers of this, with prices and contacts, in a sheet. Dull, well-defined, and easy to be visibly good at.

Documents and files. Formatting a proposal so it does not look homemade, converting things, renaming a folder full of IMG4471.jpg into something findable.

Inbox-heavy work that is really customer contact — refunds, complaints, a ticket queue — is a different service under different pressure, covered in remote customer support as a freelancer.

What you already have that counts

You have run a household, or a shift, or a group chat that organized something real. The transferable part is not enthusiasm. It is the habit of holding a list that lives outside your head, and of closing loops.

Concretely, these count: writing a message that gets a reply out of somebody who ignores messages; noticing that two documents say different things; keeping a promise to follow up on a day when nobody reminded you.

Software neither counts nor matters much. The tools in a VA job post are learnable in an evening each, and every one of them has free documentation and a free tier. What is not learnable in an evening is judgment about which of forty emails matters.

Day one: access, passwords and where the boundaries go

Do not accept a client's personal password if a delegated option exists. Every serious tool has one — a team seat, a shared mailbox, delegated access, a guest account. Ask for that by name. It protects them from you and you from them, and asking marks you as somebody who has thought about it.

Where a shared credential is genuinely the only route, put it in a password manager rather than a chat thread, a notes app or a screenshot. Chat threads stay searchable forever by whoever ends up with that account.

Ask three questions on day one and write the answers down. What am I not to touch? Who else has access to these accounts? When this ends, who removes my access, and how?

The last one sounds negative on day one. Ask it anyway; it produces a professional answer.

Then set your own boundary and say it once: you do not make payments, you do not accept legal or financial instructions on their behalf, and you do not run their business through your personal accounts.

Learning how they want it without asking forty questions

Ask for one example of the finished thing. One old proposal, one previous week's report, one email they were happy with. A lot of what you would have asked is already in it.

Then do a small batch and show it early. Three of whatever it is, not thirty. Send them with one line: this is the shape I am working to, tell me what to change. Correcting three items costs the client a minute. Correcting thirty costs them an afternoon, and costs you the client.

Keep a preferences file from day one. Two columns of plain notes: the thing, and how they want it. How they sign off emails. Which supplier they refuse to use. What time is protected. Who is allowed to book them. That file is the asset you are quietly building, and it is the reason replacing you gets expensive.

Batch your questions. One message at a fixed point in the day, numbered, each answerable in a sentence. A trickle of single questions across eight hours is how assistants get let go while doing good work.

Reporting so the client can see what they are getting

At the end of each agreed block — a day, a week, whatever you sold — send a short note in three parts: done, waiting on you, next. Five lines is plenty.

The middle part is the one that matters. Waiting on you is where the two decisions only they can make go, and it turns your silence into their queue rather than your failure.

Include the boring counts you actually observed: emails cleared, calls booked, rows entered, suppliers chased. Not estimates of value, not adjectives about how the week went. Counts of things you did, which are true and checkable.

The report is also your evidence later, when you want more hours or a different rate. Those conversations go better with a stack of these behind them, and pricing freelance work when you are new starts from what you can show.

Requests that are not assistant work

Bookkeeping is the frequent one. Categorizing receipts is admin. Reconciling accounts, filing returns, anything ending in a signature, is regulated work — and the client wants it done cheaply by you rather than properly by an accountant. Say no, and say why.

Being the named person on anything is not administration. A company registration, a tax account, a payment account, a domain: whoever is named carries the liability, and no hourly rate covers that.

Sales with a target attached is a different job at a different price. So is managing other contractors, which is supervision. So is running paid adverts with the client's money, where one mistake costs them real money in an afternoon.

Then there are requests that are assistant work but not the assistant work you sold: personal errands, a family calendar, a second business, weekends. These never arrive as a demand. They arrive as a favor, once, and stay. The first call is where a lot of this gets set — running a first client call without freezing — and the slow version afterwards is stopping freelance scope creep.

Refuse or reprice, and do it the first time. A repriced request is an ordinary business conversation. The fifth unpaid one is a resignation.