How to Vet a Freelancer Before You Waste Three Months Finding Out They're Wrong for You

The First Red Flag Is Usually Visible Before You Even Talk to Them

Most people hire freelancers wrong.

They find someone on Upwork, or get a referral from a friend, or stumble across a website that looks nice — and they book a call. The call goes fine. The freelancer seems competent. They send a proposal. You sign off. And three months later you're either starting over or making peace with something mediocre.

The problem isn't that the freelancer was hiding something. Most of the time, the signs were there. You just didn't know what to look for.

Here's what to look for.

Their Portfolio Should Answer a Question, Not Just Look Good

A portfolio full of pretty screenshots is a marketing document. It doesn't tell you whether they can actually solve your problem.

When you look at someone's past work, ask yourself: does this project have anything in common with what I'm trying to do?

Not the industry — the type of problem. A developer who's built ten beautiful brochure sites isn't automatically a good fit for your Shopify migration. A marketer who writes for enterprise SaaS might not understand how a service business owner thinks or what their customers care about.

The portfolio should show evidence of your problem being solved. If it doesn't, that's not disqualifying — but it means you need to probe harder on the call.

Ask How They've Handled a Project That Went Sideways

Every freelancer with real experience has a story about a project that didn't go the way anyone planned. Scope creep, a client who went dark, a launch that broke something, a timeline that slipped.

How they talk about that experience tells you almost everything.

If they blame the client entirely — walk. If they say nothing ever goes wrong — don't believe it. If they tell you what happened, what they did, what they'd do differently — that's a person who's been tested and learned something.

I've had projects hit walls. A migration that surfaced data issues we didn't know were there. A build where the client changed direction mid-scope. The skill isn't avoiding those situations. It's what you do when they show up.

Asking this question also signals to the freelancer that you're serious and paying attention. Good ones appreciate that.

How They Communicate Is the Product

You're not just hiring a person for their technical skills. You're hiring a communication relationship for the duration of the project.

Some freelancers are talented but go quiet for two weeks at a time. Some check in constantly but never seem to move the work forward. Some will tell you what you want to hear rather than what's true.

Ask them directly: How do you typically communicate with clients during a project? What does a normal week look like?

Then pay attention to how they've already communicated with you. Did they respond to your initial inquiry the same day or after four days? Was their proposal clear and specific, or vague enough that it could mean anything?

The proposal is a sample of their work. If it's generic, that's probably what the project will feel like too.

Cheap Isn't a Bargain If It Takes Twice as Long

I'm not going to tell you to always hire the most expensive option. That's not the point.

But I've watched founders try to save money by hiring someone underqualified, spend three months managing confusion and revisions, and then come to me to redo the work anyway. At that point they've paid twice — plus the opportunity cost of the time they lost.

The number to evaluate isn't the rate. It's the total cost of a failed engagement.

When you're comparing proposals, ask yourself: if this goes badly, what does that cost me? Time to restart, lost revenue, burned goodwill with customers, missed season — put a number on it. Now the rate looks different.

A freelancer who charges more but communicates clearly, hits deadlines, and actually understands your business is almost always cheaper in real terms.

References Matter More Than Reviews

Five-star reviews on a freelancer profile are nearly useless. Most people don't leave bad reviews publicly. The real signal is in a direct conversation with a past client.

Ask for two or three references and actually call them. Ask what the project was, what the freelancer was good at, what was frustrating, and whether they'd hire them again for something different.

That last question is the one. People who wouldn't hire someone again usually can't bring themselves to say it outright — but they'll hesitate. They'll soften. Pay attention to that.

One More Thing: Red Flag Checklist

Before you move forward with anyone, run through this quickly:

• Do they ask more questions than you'd expect, or just send a number?
• Can they tell you what they won't do as clearly as what they will?
• Do they push back on anything, or just agree with everything?
• Is their contract or proposal clear about scope, timeline, and what changes cost?

A freelancer who only says yes is one who'll say yes when they shouldn't. You want someone who tells you the truth — even when the honest answer costs them the project.

If You're Thinking About Working with Me

I'm a solo consultant. Every project goes through me. You don't get handed off, and you don't get a junior version of whatever I sold you on.

I ask a lot of questions upfront. I push back when something doesn't make sense. And I'll tell you if I'm not the right fit before we ever get started.

If that sounds like what you've been looking for, book a call.