A first virtual assistant hire tends to work when you hand over one specific, recurring task that you've already written down. It tends to fail when you hire "some help" and expect the person to work out what you need.
So the order is: pick the task, document it, post a short and specific job, pay a few candidates for a small trial, then onboard the best one with limited access to your accounts. Most of the effort sits in the first two steps, and you do those before you talk to anyone.
Decide what to hand over first
Log what you do for a week. A notes file with a line per task is enough. Then run each task through three checks:
- Recurring. It comes up weekly or more. One-off jobs cost more to explain than to do.
- Teachable. You can describe the steps and show what a finished version looks like.
- Low-risk. A mistake is cheap and easy to undo.
Tasks that pass all three are your shortlist. Typical ones are formatting and uploading posts, inbox triage, scheduling, updating a spreadsheet, resizing images and basic research against a checklist.
Leave out anything that needs your judgment about the business, anything you haven't done often enough to explain, and anything where an error costs money or reputation, such as refunds, publishing without review or replying to an upset customer. Those can move over later, once you trust each other.
Before you hire for a task, check whether software could do it. If it's the same data moving between the same two apps every time, a simple no-code automation is cheaper than a person and doesn't need managing.
Write the process down before you post the job
Pick one task from the shortlist and document it. I'd do this as a screen recording of you doing the task while talking through it, plus a short written checklist underneath. Include what you start with, the steps in order, what "done" looks like, and the two or three mistakes you'd expect a newcomer to make.
This does two jobs. It gives your VA something to follow, and it tells you whether the task is ready to hand over. If you can't write the steps, the task isn't ready yet.
Don't polish it. The first person to follow the document will find the gaps, and you fix them then. If the work is content-related, a repeatable writing workflow already gives you most of the document.
Where to look for a virtual assistant
There are three realistic routes:
- General freelance marketplaces such as Upwork. You post a job, freelancers apply, and you can see their profiles and past client feedback. The pool is large, so the screening is on you.
- Country-specific job boards such as OnlineJobs.ph, which describes itself as a marketplace for hiring remote workers in the Philippines directly, without an agency in the middle.
- Referrals and agencies. A recommendation from someone who has worked with a VA for months is the strongest signal you'll get. Agencies handle screening and replacement for you and charge a markup for it.
Fees, payment protection and contract features differ between platforms and change often, so read the current pricing page on the platform itself before you post.
A job post you can copy
Short and specific beats long and impressive. Name the task, the hours and the tools, and add one small instruction so you can see who reads carefully.
Title: Virtual assistant for [task], about [X] hours a week
About the work: I run a small [type of business]. I need help with [specific task], which comes up [how often]. You'll get a recorded walkthrough and a written checklist for it.
What you'll do: [Step or outcome 1]. [Step or outcome 2]. [Step or outcome 3].
Tools: [For example Google Sheets, WordPress, Canva]. Tell me which of these you've used.
Hours and communication: About [X] hours a week, on your own schedule, with work delivered by [day or time and time zone]. We'll communicate in writing through [channel].
Pay: [Your hourly rate or fixed price], paid [weekly or per milestone]. Shortlisted candidates get a paid trial task of about [one to two] hours.
To apply: Start your reply with the word "[any word]" and describe one similar task you've done, in two or three sentences.
Long job posts with a dozen "nice to have" skills attract generic applications. A narrow post gets fewer replies and better ones.
Run a paid trial task
Shortlist two or three people and give each the same small task, taken from the real work and built on your documentation. One to two hours is plenty. Pay everyone for it at the agreed rate, whether or not you hire them. Unpaid "test work" is unfair to candidates and puts off the experienced ones.
When the trials come back, look at more than the finished result. Check whether they followed the document, whether they asked a question when something was unclear instead of guessing, and whether they delivered when they said they would. Someone who makes a small mistake and communicates clearly is usually a better long-term bet than someone who gets it right in silence.
