- Seven ways to use AI before you hire a freelancer, none of them "have AI do the job instead."
- The money you waste on freelancers is almost never spent on the wrong person. It's spent on the wrong description of the work.
- Don't ask AI to write your brief. Ask it to interview you the way a sharp freelancer would on day one, then answer the questions.
- An hour building the crudest possible version yourself tells you what the job costs better than any rate guide.
- The build item turns the notes already scattered across your inbox into a brief someone can quote against, every time you hire.
Using AI before you hire a freelancer sounds like a setup for the obvious punchline, which is that you don't hire one. That's not this list. Skilled freelancers now make up 38% of US knowledge workers, up from 28% a year earlier, according to Upwork's Future Workforce Index 2026. More people are hiring them, not fewer. The question is what happens in the two weeks before you post the job.
Here's the part most advice skips. When a freelance engagement goes badly, the postmortem usually blames the freelancer, and the evidence rarely supports it. The Project Management Institute found that 47% of unsuccessful projects miss their goals because of inaccurate requirements management, which is a formal way of saying nobody wrote down what "done" meant. You can fix that side of the ledger for free, in an afternoon, before a single dollar moves.
Every idea below is new to this column, and each one ends with something you can start today.
1. Get Interviewed Before You Write the Job Post
The instinct is to ask AI to write the brief. Wrong direction. You know things about this project that no model does, and they're stuck in your head in a form nobody can quote against. What you need is extraction, not generation.
So flip the roles. Tell it to act as an experienced freelancer in that field who has just been handed your one-paragraph request, and to ask you every question it would need answered before quoting. Then sit there and answer them. The questions are the product. They surface the assumptions you didn't know you were making: who signs off, what happens to the old version, whether the deliverable has to work on a phone, which of your three stakeholders gets the final word.
Expect the first ten questions to be easy and questions eleven through twenty to be uncomfortable. The uncomfortable ones are the ones that would have surfaced in week three, at three times the cost. If you want the longer version of this discipline, writing a proper spec follows the same logic.
Start today: Write your request in one paragraph, then prompt: "You're an experienced [role] who just received this request. Ask me every question you'd need answered before you could give me a fixed quote. Ask them one at a time."
2. Build the Worst Possible Version Yourself First
Ade runs a three-truck landscaping crew outside Sacramento and needed an online booking page. He'd budgeted four thousand dollars and had no idea whether that was generous or insulting, because he had never made a booking page and couldn't picture what was hard about it. So he spent an hour with an AI assistant making the ugliest working version he could. Two forms, no design, a calendar that half worked.
He learned three things that hour. The booking form was trivial. The calendar sync was the entire job. And what he really wanted, which he had never written down anywhere, was for the customer's address to auto-fill the route sheet his crew already used. That last one was the actual project. It never would have made it into the brief.
This is scouting, not building. You're not trying to keep what you make. You're trying to find the wall you hit, because the wall is what you're paying for. Spend an hour, get to something broken, and pay attention to which part broke first.
Start today: Give yourself sixty minutes and a timer. Ask AI for the crudest working version of the thing you want to hire out, then note the exact moment you get stuck. Write that sentence down. It goes at the top of your brief.
3. Split the Job Into Judgment Work and Throughput Work
Most requests are two jobs wearing one coat. There's the part that needs taste, context, and someone's professional neck on the line. And there's the part that's volume: resizing ninety images, moving records between two systems, formatting the same document forty times. People hire one person for both and then feel vaguely ripped off when a skilled professional bills expert rates for an afternoon of copy and paste.
Describe the whole job and ask for it to be sorted into two columns: work that requires human judgment and would be risky to automate, and work that's repetitive and rule-based. Push back on the sorting, because the first pass is usually too generous to the judgment column. Then hire for column one and handle column two some other way, often by automating the repetitive half once.
Upwork's data points at the same split from the freelancer's side. Freelancers doing complex, judgment-heavy work with AI saw earnings rise 45% year over year, while lower-complexity generative production grew in volume and fell 13% in earnings per contract. The market is already pricing these two things differently. Your brief should too.
Start today: List every step of the job, then prompt: "Sort these into work that needs human judgment and work that's repetitive and rule-based. For anything you put in the judgment column, tell me specifically what the judgment is."
4. Turn Your Scattered Notes Into a Brief Someone Can Quote Against
The brief already exists. It's in six places. Three Slack threads, a voice memo, two screenshots of things you liked, an email where you explained the whole idea to a friend, and the answers you just gave in idea one. Nobody sits down to write a brief from nothing. They sit down to avoid the twenty minutes of digging, which is why so many job posts are four vague sentences.
Hand over the raw pile and ask for the standard shape: goal, background, scope, explicit non-goals, constraints, deliverable format, definition of done, and a list of decisions still open. That last section is the one nobody includes and every freelancer needs. And if you hire more than twice a year, this stops being a task you do by hand. Set up a document workflow that assembles the brief from your own notes and the next hire starts from a draft instead of a blank page.
Read it before you send it. The model will confidently fill gaps you left, and a fabricated constraint is worse than a missing one.
Start today: Dump every note, thread, and screenshot about the project into one place. Ask for it back as goal, scope, non-goals, constraints, deliverables, definition of done, and open questions. Then describe that process once and hand it off.
5. Price the Shape of the Deal, Not the Hourly Rate
Everyone googles the rate. Almost nobody thinks about the structure, and the structure is where the money moves. Hourly, fixed price, retainer, milestone, and day rate are five different bets about who absorbs the surprises. Fixed price sounds safe and quietly punishes you for every change you ask for. Hourly sounds risky and is often kinder when the scope is genuinely fuzzy.
Ask for the comparison directly. Describe your project, then ask which engagement structures fit it, what each one shifts onto you, and what each one shifts onto them. Ask specifically what goes wrong under each structure when the scope changes in week three, because it will. You'll walk into the conversation able to say "I'd rather do milestones for this, here's why," which lands very differently from asking what they usually charge.
Start today: Prompt: "For a project like this, compare hourly, fixed price, milestone, and retainer. For each one, tell me what risk I'm taking on, what risk they're taking on, and what happens if the scope changes halfway through."
6. Write the Test Task and Its Grading Rubric Before Anyone Applies
Tomas needed a copywriter for a regional HVAC supplier's product pages. He posted the job, got thirty-one applicants, and made the mistake everybody makes: he read the samples first and formed opinions, then built his criteria backward from the sample he liked. He hired someone excellent at witty brand voice for a job that needed patient, searchable, specification-heavy writing. Three weeks lost.
The fix is pre-registering your judgment. Before you see a single applicant, design a small paid test task that mirrors the real work, and write down what a great submission, an adequate one, and a bad one look like on three or four specific dimensions. Do it with AI, because it will push you to name dimensions you'd otherwise leave as a feeling.
Two rules keep this honest. Pay for the test task, always, and keep it under two hours. Unpaid spec work is how the industry gets a bad name, and the good freelancers already know to decline it.
Start today: Prompt: "Design a paid test task under two hours that mirrors this real work. Then write me a rubric describing what excellent, adequate, and poor look like on the three dimensions that matter most for this job."
7. Decide Now What You Need to Still Own on the Day They Leave
The engagement ends. The files sit in someone else's Figma. The domain is registered to their email. The one person who knew why the discount logic works that way is on to their next client. None of this is malice. It's the default, and the default has to be overridden in writing, up front, by you.
Ask what typically goes missing when a contractor finishes this specific kind of project, and you'll get a checklist you'd never assemble from memory: source files rather than exports, credentials transferred rather than shared, a plain-language note on every non-obvious decision, admin access moved to an account you control. Then put the checklist in the agreement instead of discovering it in month four.
One item deserves naming outright. In the US, the freelancer owns the copyright to what they create for you by default, even after you've paid in full. The U.S. Copyright Office explains the narrow conditions under which commissioned work counts as work made for hire, and a signed written agreement is one of them. AI can flag that this clause is missing. It can't write the clause for you, and for anything with real money attached, a lawyer should.
Start today: Prompt: "I'm hiring a freelancer for [project]. List everything I should require in writing so that I can maintain, change, or hand off this work after they're gone. Include file formats, access, credentials, and documentation."
Pick One
Seven is a list, not a plan. If you're hiring in the next month, do the interview in idea one tonight; it takes twenty minutes and changes the job post more than anything else here. If you're hiring in the next quarter, spend the hour on idea two instead, because knowing where the wall is will save you a five-figure misunderstanding.
On Sundays, All Things Agentic covers the week's news. On Wednesdays, The Loop takes one workflow apart and rebuilds it. Mondays are for ideas, and the agent workflow directory is where the ones you'll repeat stop depending on your memory.
Show up to the hire with the brief already written
Tell BYOBot how you gather project notes and what your briefs need to contain. You get back an agent that assembles the next one from the mess you already have.
Frequently Asked Questions
- Sometimes, and you'll know within an hour. If a rough attempt gets you something you can live with, keep it and save the money. Far more often the rough attempt shows you exactly how much craft the real version takes, and you hire with a clearer head and a smaller, better defined job. Both outcomes are worth the hour.
- No. Freelancers complain about vague clients, not prepared ones. A brief that states the goal, the constraints, the format, and the definition of done is the single kindest thing you can send. Say plainly that you drafted it with AI and that every decision in it is yours, then invite them to challenge any part of it. If you hire regularly, the same prep work scales well for a small business running lean.
- Three things. Whether a specific person is trustworthy, since a model has no evidence about them and will produce confident-sounding guesses anyway. The final wording of a contract, which is a job for a lawyer in your jurisdiction, though a review pass that flags what's missing is fair game. And the judgment call on taste, because if you can't tell good work from mediocre work in this field, a model's opinion won't rescue you.
- Detailed enough that two different freelancers would quote within range of each other. That means the outcome, the constraints you can't move, the file formats and access you need at the end, and one sentence describing what finished looks like. Anything past that is usually you designing the solution, which is the part you're paying someone else to do.
