How to Hire a Part-Time Assistant (or Use AI Instead)

I've hired three part-time assistants over the past four years, and I got the first one badly wrong. I posted a vague job ad, hired whoever interviewed best, and spent two months explaining tasks I could have finished myself in ten minutes.

The next two hires went completely differently because I flipped my approach: I wrote the work down first, hired off a paid test instead of a smooth interview, and locked down access before day one. If you want to hire a part-time assistant without burning a month on the wrong person, this is the method I now follow, step by step.

What does a part-time assistant do?

Part-time assistants handle inbox triage, scheduling, research, travel booking, and post-call follow-ups, typically working 5 to 20 hours per week.

Compared to a full-time hire, the scope is narrower, and the cost is lower. Unlike a task-based assistant service, a single person learns your tools and preferences over time rather than a rotating pool handling isolated requests.

What you'll need before you start hiring

The bad hires I've made started with skipping the prep. Before you post anything, get these four things in order:

• A written task list. This becomes your job post, your interview script, and your onboarding doc. Step 1 walks through how to build it.
• Hours and budget. On Upwork, the median rate for virtual assistants is $13 per hour, with many falling between $10 and $20. Managed services cost more, and I'll break those down in step 3.
• Tools and access. Set up a password manager and shared docs before day one. Handing over your raw inbox password is how security problems start.
• Time required. Budget 2 to 4 weeks from posting the job to having someone productive on day 1. Every time I've rushed this, I've paid for it in rework.

‍

{{templates}}

‍

How to hire a part-time assistant: Step by step

The same process works whether you're figuring out how to hire an executive assistant or a general admin. Only the task list and budget change.

Step 1: List the tasks you want off your plate

Track one full week of your work before you write anything. I keep a running note and log every task I handle more than twice; last time, this produced 26 items, 12 of which never needed my judgment.

Those 12 became the job description. Vague posts attract vague applicants, and a specific task list filters candidates before you ever read a proposal.

Pro tip: If a task takes longer to explain than to do, keep it. Start with the tasks that follow a repeatable pattern.

Step 2: Set your hours, budget, and working setup

Before you write a single word of the job post, nail down your weekly hours, your hourly budget, and whether remote works for you. I start every assistant at 10 hours per week because it's enough to cover a meaningful chunk of the workload without locking yourself into a bad fit. Ten hours gives you enough signal to know whether the relationship is working before you expand it.

Match the budget to the sourcing route you'll choose in the next step, since a freelancer and a managed service fall into different price bands.

While you're at it, pin down worker classification before you start. It's worth a quick check with an HR partner, because getting it wrong ends up costing more than the hourly rate ever would.

Pro tip: Write your budget as a monthly cap. Hours creep, and a cap forces the priority conversation early.

Step 3: Choose where to look for candidates

The choice comes down to how much vetting you want to handle yourself:

• Upwork puts the vetting on you. You'll review proposals, check work history, and interview on your own, at the rates I mentioned above. Best when budget matters more than your screening time.
• Time etc handles the matching for you. Time etc removes the screening work and folds the cost into the monthly plan, with their own pricing page listing $390 per month for 10 hours with a dedicated U.S. assistant. Whether that tradeoff makes sense depends on how you value your screening time.
• BELAY sits at the executive end of managed support. Go in with a clear number before booking the consultation, because BELAY's own FAQ puts U.S.-based part-time support at $1,200 to $3,000 per month. At that level of spend, the hire needs to absorb a significant executive workload to pay for itself.

Pro tip: If you need someone working within two weeks, skip the marketplace and pay the managed premium. Proposal review tends to take longer than you expect.

Step 4: Write a job post that filters for you

Paste your Step 1 task list into the post, then add the practical details: hours, tools, time zone, and rate range. I also bury one specific instruction in the middle, like asking applicants to open with the word "cadence", which removes everyone who never read the post.

Keep it short, because applicants skim, and the task list does more to predict fit than anything else in the post. Skip the personality wishlist entirely.

Pro tip: Ask one scenario question, such as how they'd handle a double-booked calendar with both parties traveling. The answer tells you more than any resume line.

Step 5: Screen applicants and run short interviews

Cut the pile in two passes. First, remove everyone who ignored your buried instruction, which in my last round dropped 31 applicants to 9. Then rank the rest against the task list alone. The cover letter polish doesn't tell you much.

Interview the top three for 20 minutes each, no more. I ask which tools they've run for past clients, one scenario from my actual workload, and how fast they turn things around. Twenty minutes is plenty to see how someone thinks, and dragging the call out longer mostly just rewards whoever interviews the smoothest.

Pro tip: Watch how they handle the scheduling of the interview itself. Someone who needs three emails to book a call will probably need three emails for most things.

Step 6: Assign a small paid test task

Don't skip this, and don't make it free. I give them two hours of work straight from my backlog, like cleaning a contact list or drafting replies to five pending emails, and I judge the result against what I would have produced.

The test surfaces things interviews miss. You'll see whether they follow instructions, ask when something's unclear, and meet a deadline without a nudge. A $40 test task has saved me from months of the wrong hire, which makes it the cheapest insurance in hiring.

Pro tip: Give deliberately incomplete instructions once. A good hire asks a clarifying question. Someone who's not a fit guesses and hands you back something confident and useless.

Step 7: Onboard with documented processes and access controls

Record yourself doing each recurring task once, with a short screen capture and voiceover, and store the videos in a shared folder. My onboarding doc is seven short videos and one page of preferences, and it got my second hire up to speed in a single week.

Handle access like it can go wrong, because eventually something will. Share credentials through a password manager, grant the minimum each task needs, and schedule a 30-day review to adjust access from there.

Pro tip: Set a daily async check-in for the first two weeks, one message with done, doing, and blocked. Drop it to weekly once trust is earned.

Common mistakes to avoid

• Trusting a strong interview over the paid test. Charm is a skill, and interviews reward it. It happens because someone who interviews well feels like someone who'll work well, so make the paid test the tiebreaker every single time.
• Delegating chaos. If a workflow lives only in your head, your assistant inherits your confusion at an hourly rate. Write it down before you hand it off, even when that feels slower than just delegating.
• Handing over full access on day one. New hires get raw inbox passwords because it's convenient. It's also how security incidents start, and I've seen it go wrong fast. Scoped access through a password manager costs ten minutes to set up and removes the risk entirely.
• Keeping a wrong fit too long. Sunk-cost training time makes you rationalize weak work, and I held on to my first bad hire for two months after the evidence. Set a 30-day decision date before they start, then honor it.

When to use an AI assistant instead

Before my third hire, I went back through my task list with a different question in mind. I sorted it into two buckets: decisions that needed my judgment, and work that was just passing things along. Inbox to calendar, calendar to apps, apps back to inbox.

The second bucket was bigger. Most of what I wanted to hand off was scheduling, triage, and notes, work that doesn't need a person. An AI assistant covers all of it now, for less than I'd pay a human assistant for a single week.

Go human when the work involves:

• Judgment calls, like vendor negotiations
• Relationships, like sensitive client conversations
• Anything in person. A tool that drafts your emails won't show up to the client dinner

Try AI first when your list skews toward:

• Inbox and scheduling
• Meeting notes and reminders
• Passing information between apps

The same logic scales up. Teams that hire assistants for several executives at once can end up paying human rates for admin overflow that software would handle, so run the same split on your list before hiring more people.

If your list is mostly the second group, try an AI assistant for a week before committing to a hire. 

‍

{{cta}}

‍

Lindy handles the work you’d delegate first

Lindy is an AI assistant you text. It handles your inbox, meetings, and calendar, and connects to hundreds of integrations, including Gmail, Outlook, Slack, HubSpot, and Salesforce.

That admin pile, the scheduling, triage, and notes, is what it was built for.

In practice, it covers the tasks most people hand off first:

• Ask from your phone: Text Lindy, and it pulls what you need from your calendar, email, and connected apps.
• Inbox triaged for you: Lindy sorts and prioritizes your email and drafts replies you can review and edit. Nothing goes out without your approval.
• Meetings covered end-to-end: Lindy preps you before the call, takes notes during it, and sends follow-ups afterward, all without you having to ask twice.

You can also set Lindy to text you updates on the things you've asked it to watch, so nothing sits in a queue waiting for you to check in.

Setup is quick, and the Lindy Academy walks you through your first tasks if you need a hand. There's a 7-day free trial with no credit card needed, and paid plans start at $49.99 per month.

Frequently asked questions

How long does it take to hire a part-time assistant?

Two to four weeks from job post to productive onboarding, in my experience. Managed services cut sourcing time to about a week, but documenting your processes and building trust still take up the remaining weeks.

What’s the hardest part of hiring a part-time assistant?

Documenting your own processes. A lot of people discover their "simple" tasks live entirely in their heads, and writing them down is slower and more humbling than any interview.

How much does a part-time assistant cost?

It depends on the route. Marketplaces cost the least, managed U.S. services run several times as much, and a part-time executive assistant through a managed service like BELAY sits at the top, at $1,200 to $3,000 per month.

Can Lindy replace a part-time assistant?

Lindy handles the coordination side well, like email, scheduling, and meeting notes. Anything that requires judgment, relationships, or in-person presence still needs a human. Sort your list into those two categories, and where Lindy fits will be clear.

What if the hire doesn’t work out?

Honor the 30-day decision date you set before they started. On managed services, ask for a rematch. On marketplaces, end the contract and repost with a sharper job description.