Hand off the recurring, rule-based work first, not the work that scares you most.
Delegate the tasks that eat hours every week, follow a repeatable process, and won't sink anything if they go slightly wrong. That's inbox triage, calendar wrangling, data entry, travel booking, invoice chasing, and the small repetitive admin you keep re-doing. The instinct is to offload whatever you hate most, and that's usually the wrong first move, because the thing you hate is often the thing that needs your judgment or has no written process yet. Start with the boring, frequent, low-stakes stuff instead. It's the fastest to hand over, the easiest to check, and it buys back the most time in the first two weeks, which is exactly what you need to trust the arrangement enough to hand over anything bigger.
A task is ready to delegate when it clears four plain checks.
Run anything on your plate through these before you hand it over. If it clears all four, it goes to the top of the list. If it fails one, it's either not ready yet or it's yours to keep.
- It recurs. It happens every day or every week, not once a quarter. Frequent tasks are worth the setup cost of explaining them because that cost gets amortized fast. A once-a-year task rarely does.
- It follows a process. You could write down how to do it in a short list of steps, or record yourself doing it once. If there's a repeatable method, someone else can learn it. If the "method" lives only in your head and changes every time, write it down first, then delegate.
- It's genuinely eating your time. Be honest about the hours. Email alone runs two to three hours a day for a lot of operators. If a task is quietly costing you a morning a week, it belongs on the list even if each instance feels small.
- A mistake is recoverable. A miscategorized email or a rescheduled meeting is a shrug. Wiring the wrong amount to a vendor or firing off a message to your biggest client in your voice is not. Start where the blast radius of an error is small, and expand as trust builds.
The work that clears the test almost every time.
These are the categories that show up on nearly every "what to delegate" list for a reason: they're high-frequency, teachable, and low-risk. Most operators can hand off some version of all of them.
Inbox triage and calendar
Sorting and labeling mail, drafting replies to routine messages from your templates, unsubscribing you from noise, flagging the few things that actually need you. On the calendar: booking, confirming, and rescheduling meetings, protecting your focus blocks, and handling the back-and-forth of finding a time. You still decide what deserves your hours. Someone else runs the logistics of it.
Data entry and CRM upkeep
Updating contact records, logging call notes, cleaning up spreadsheets, moving information between tools, keeping your pipeline current. It's tedious, it's rule-based, and it's exactly the kind of below-your-pay-grade work that quietly piles up until the data is too messy to trust. A good first delegation because the process is obvious and the errors are easy to spot.
Travel and logistics
Flights, hotels, ground transport, itineraries, confirmations, the reschedule when a flight moves. Travel planning is detailed and time-sensitive but requires coordination, not strategy, which makes it one of the cleanest handoffs there is. You say where and when and your budget. The hours of comparison-shopping and booking aren't yours anymore.
Research and list-building
Market and competitor scans, sourcing suppliers or venues, pulling contact details, gathering the ten links you'd otherwise open twenty tabs to find. You define the question and the format you want the answer in. Someone else does the digging and hands you a tidy summary instead of a browser full of tabs.
Invoicing and repetitive admin
Sending invoices, chasing late payment, formatting documents, transcribing audio, prepping meeting agendas and circulating the notes after. None of it needs your judgment once the format is set, and all of it is the kind of small recurring drag that never feels urgent enough to fix but adds up to a full day a week.
Publishing and scheduling
Loading blog posts into the CMS, scheduling social content from a calendar you approved, resizing images, posting the things you've already decided to post. This is execution, not strategy. You still own the message and the plan. The clicking, formatting, and scheduling that turn a draft into a published thing can go.
The goal isn't to offload what you dislike. It's to offload what doesn't need you, so the work that does need you finally gets your full attention.
Some things belong on your desk, at least for now.
The mirror image of the four-part test is just as useful. Hold on to the decisions that shape the business: strategy, pricing, hiring, which clients you take, where the company is going. Hold on to the high-stakes relationships, the conversation with your biggest account or the negotiation that decides the quarter, until an assistant has enough context to represent you well, which takes months, not days. And hold on to anything that has no written process yet, not because it can't be delegated, but because delegating chaos just produces chaos faster. Document it first, then hand it over.
There's a softer trap here too. A lot of operators try to delegate the one task they most dread, decide the handoff "didn't work," and give up on delegation entirely. Usually the task they picked was a bad first candidate: too tied to their own judgment, too undocumented, too high-stakes for a first week. Pick the boring wins first. Prove the arrangement works on low-risk, high-frequency work, and the harder handoffs get much easier because you already trust the person and the system.
Your delegation list rarely stays in one lane.
Write out everything you'd love off your plate and look at the spread. It's almost never just admin.
The list starts with inbox and calendar. Then you remember the landing page that's been half-built for three months, the blog that hasn't been touched, the invoices piling up, the deck that needs designing before Thursday. That's the moment a single generalist virtual assistant hits a wall. One person is genuinely great at admin, or at design, or at writing, rarely all three, and the honest ones will tell you so. So you either accept that half your list stays undone, or you go hire a second freelancer, and a third, and now you're the project manager coordinating three contractors, which is its own part-time job you didn't sign up for.
That's the specific gap a flexible-team model is built for. With Lil Assistance, you submit tasks to a project manager who routes each one to the right specialist, an admin person, a web developer, a designer, a content writer, so a mixed list gets handled without you brokering between three different freelancers. Your hours flex across those functions week to week: a heavy design week and a heavy admin week draw from the same allocation instead of paying a fixed role to sit idle. You offload the coordination, not just the tasks. Here's the honest tradeoff, laid out plainly.
A single freelance VA
Best when your list is one narrow, recurring task.
- ✓ Lowest price for one well-defined job, and a direct one-to-one relationship
- ✓ Simple to start for pure admin or a single specialty
- × One skill set: admin help can't build your site or design your deck
- × You do the managing, and the work stops if they're sick or disappear
A flexible team with a PM
Best when your list spans several kinds of work.
- ✓ Specialists across admin, web, design, content, and video under one engagement
- ✓ A project manager absorbs the delegation and quality-checking overhead
- ✓ Hours reallocate by priority; the work continues when one person is out
- × A recurring commitment with a one-time setup fee per worker, not the cheapest route for a single tiny task
For context on the commitment: Lil Assistance publishes plans at $340 a week for 20 hours and $600 a week for 40 hours, plus a one-time $250 setup fee per remote worker, with no long-term contract. Every plan includes a project manager who coordinates your team and handles the delegation, so you get a single point of contact on either tier. Just know that manager isn't assigned to you alone; a PM typically handles up to around seven clients, depending on project size and staffing. If your whole need is one recurring admin task and nothing else, a solo freelancer is honestly the leaner choice. The team model earns its keep the moment your list refuses to stay in one lane.
The handoff is a few weeks of work, not a day.
Whatever you delegate and whoever you delegate to, the arrangement takes work off your plate over weeks, not on day one, and skipping the setup is how people conclude delegation "doesn't work." Do it in a short ramp. Week one, hand over the two highest-frequency tasks, inbox triage and calendar, because you'll see the results within days and the feedback loop is tight. Document each task once as you go, a short checklist or a screen recording, so you're building a library of processes instead of re-explaining the same thing every week. Review outcomes weekly, not every task in real time, and when something goes sideways, fix the instructions rather than taking the task back. Add the next tasks only once the first ones run without you. By week four you've usually offloaded a genuine chunk of the week, and you've built the trust and the documentation to keep going.
What should I delegate to a virtual assistant first?
Start with recurring, rule-based, low-risk work: inbox triage, calendar management, data entry and CRM updates, travel booking, and invoice chasing. These are high-frequency, easy to document, and quick to check, so you recover real hours in the first week or two and build the trust to hand off bigger things later. Avoid opening with the task you dread most, since that's often the one that still needs your judgment or has no written process yet.
What should you not delegate to a virtual assistant?
Keep the decisions that shape the business: strategy, pricing, hiring, and which clients you take. Keep high-stakes relationships and negotiations until an assistant has months of context on how you operate. And hold back anything with no documented process, not forever, but until you've written down how it's done. Delegating an undocumented, high-judgment task in week one is the single most common way delegation gets abandoned.
How do I know a task is ready to hand off?
Run it through four checks. Does it recur weekly or daily? Could you write the process down or record it? Is it genuinely costing you meaningful time? Is a mistake recoverable rather than catastrophic? Clear all four and it's a strong first candidate. Fail one and it's either not ready, needs documenting first, or should stay with you for now.
Can a virtual assistant handle design or website work too, or just admin?
A single generalist VA is usually strong in one area, admin or design or writing, rarely all three. If your list spans several kinds of work, you either hire multiple freelancers and manage them yourself, or use a team-based service where a project manager routes tasks to different specialists under one engagement. Match the model to the spread of your list: one narrow task suits a solo freelancer, a mixed list suits a coordinated team.
How many hours do I need to start?
Less than you'd think. Most operators can offload a meaningful slice of the week with part-time support focused on the highest-frequency tasks. Start small and scoped to the first two or three delegations, then scale the hours once the process is documented and running without you. Committing to a large block before you've proven the handoff just puts pressure on an arrangement that needs a few weeks to settle.
Start with the boring wins, then keep going.
Pick two recurring, low-stakes tasks off your plate this week. If your list already spans admin, design, and content, it's worth seeing how the hours work across a team behind one point of contact.