How to hire and onboard your first contractor with AI

I hired my first contractor about a year later than I should have, and then did it badly. I handed over the task I hated most, which was the one I’d never systematised, and spent more time explaining and correcting than I’d have spent doing it. Six weeks later we parted ways and I concluded that delegation didn’t work for me.

It worked fine the second time, because I handed over something boring that I understood completely.

The task to delegate first

The instinct is to offload whatever you dread. That’s the wrong first handoff, for a reason that only becomes obvious in hindsight: you dread it partly because you’ve never made it repeatable, and you can’t judge someone else’s work at something you’re vague about yourself.

The right first task is repetitive, well-understood, and has a clear definition of done. Video editing to a template. Formatting and scheduling posts. Research with a specified output. Inbox triage against rules you can state.

You want to be able to look at the result and say immediately whether it’s right. That’s only possible on work you’ve done a hundred times.

Write the process before you hire

The step people skip, and skipping it is why first hires fail.

The fear is that documenting takes days. It doesn’t, if you do it while working rather than trying to write it from memory.

Record yourself doing the task once. Screen recording, talking through what you’re doing and why. Fifteen minutes, no editing, no preparation.

Get the transcript and hand it to AI. Ask for a step-by-step procedure document from the transcript, with decision points made explicit, plus a list of anything ambiguous that needs clarifying.

That last part is the valuable bit. The ambiguity list surfaces the judgement calls you make unconsciously, which are precisely the things a new contractor will get wrong. In my own recording, the model flagged four decisions I’d made without commenting on them at all.

Fill the gaps, then stop. Two pages is plenty. Don’t polish.

I keep these in Notion alongside everything else, one page per process, linked from the task they belong to. My Notion AI review covers the AI features, and if you’re recording those walkthroughs anyway, AI meeting notes tools that actually save you the follow-up covers getting clean transcripts.

Writing the job post

Most freelance job posts are vague, which is why they attract vague applicants.

What actually filters well:

• The specific task, described concretely. Not “video editing help” but “editing 3 talking-head videos per week to an existing template, 8-12 minutes each”.
• The tools. Name them. It filters instantly.
• Volume and schedule. Hours per week, turnaround expected.
• The budget range. Omitting it wastes everyone’s time and attracts the wrong end of the market.
• A specific instruction in the post. Ask applicants to start their reply with a particular word, or answer one question about the work. Removes every mass-applier immediately.

AI drafts this well from your process document, because the document already contains the specifics. Ask it for a job post based on the procedure, and edit the tone.

The paid trial task

Never hire from an interview alone. Interviews test how well someone interviews.

Pay for a small real task, four hours or so, at their normal rate. Give them the process document and no help beyond it. What you learn:

• Can they follow written instructions without a conversation? This is the single best predictor of whether the arrangement will work.
• Do they ask good questions, or do they guess and get it wrong?
• What’s the quality at their normal pace, not their showing-off pace?
• How do they communicate when something is unclear?

Pay for it regardless of the outcome. Unpaid trials attract the desperate and repel the good, and the four hours is the cheapest information you’ll buy all year.

Onboarding in a day

If the process document exists, this is short.

Access first. Everything they need, granted before day one, with permissions scoped to the work. Don’t share your main password on anything, use proper delegated access.

Walk through one instance together. They do it, you watch, you say nothing unless they’re stuck. Resist correcting style, correct only outcomes.

Agree the feedback loop. How work gets submitted, when you review, how corrections come back. Vagueness here creates the resentment that ends arrangements.

Have them update the document. This is the trick that makes documentation good. The person learning the process is the best person to spot what the instructions failed to explain, and by week three it’s genuinely usable by anyone.

What to keep yourself

Worth deciding explicitly, because drift happens.

Keep anything requiring your judgement about the business, anything client-facing where the relationship matters, and anything that is your actual differentiator. Hand off execution, keep direction.

The failure mode I’ve watched several people hit is delegating the thing that made them good, keeping the admin, and ending up as a manager of their own former craft. If you got here because you’re good at something, that something is usually the last thing to hand over.

For what to automate rather than delegate, the AI stack that replaces your first virtual assistant is the relevant piece, and a fair amount of what people hire for is better solved with a workflow than a person.

My take

Hire when a task is repeatable and documented, not when you’re overwhelmed. Overwhelm makes you hand over chaos, and chaos with an invoice attached is worse than chaos.

The genuine unlock here is that AI removed the excuse. Documenting a process used to be a day of writing nobody ever did. Now it’s a fifteen-minute screen recording and a prompt, and the output is better than what most people would have written, because the model asks about the decisions you’d have forgotten to mention.

Start with something boring you understand completely. Pay for a trial task. Have them improve your documentation as they learn it. And keep the work that only you can do, because the point of hiring isn’t to do less, it’s to do less of the wrong things.