All articles

Reviewing proposals and choosing someone

How to read proposals quickly without missing the good ones, what the shortlist and interview stages are for, what the signals on a profile actually mean, and how to decline people properly so your reputation as a client holds up.

Proposals arrive on the job page. Reading them well is a skill, and the main mistake clients make is treating it as a procurement exercise — sorting by price and picking the cheapest that looks acceptable.

The funnel

A proposal moves through defined stages, and moving someone forward is not a commitment:

Submitted — it arrived and you have not acted on it.

Shortlisted — you are interested. The freelancer is notified, which is worth knowing: shortlisting tells someone they are in contention, and good freelancers prioritise accordingly.

Interviewing — you are talking. Shortlisting and interviewing open a conversation without committing you to anything.

Offer sent — you have sent a formal offer. Still not binding until accepted and funded.

Hired, or archived if not selected.

The funnel only moves forward. That is deliberate: it stops a proposal bouncing between states and leaves the freelancer with a clear picture of where they stand.

Reading a proposal in thirty seconds

You are looking for evidence the person read your post and understands the work.

Does it engage with your specifics? A proposal that names your stack, your constraint, your existing design, is from someone who read it. One that could have been sent to any job in your category was.

Do they ask a good question? The single strongest signal. Your brief has gaps — every brief does. Somebody who identifies the right gap and asks about it is thinking about the work. Somebody who promises to deliver everything with no questions has either not read it or will discover the gap later, expensively.

Is the approach plausible? You do not need to evaluate it deeply. You need to see that one exists.

Is the price explained? A number with reasoning is worth more than a lower number without.

Templates are not automatically bad — a good freelancer has a structure they adapt. What matters is whether it was adapted to you.

What the profile signals mean

Alongside the proposal you see signals on the freelancer. They are worth understanding rather than treating as one score.

Verification level tells you Open Lance has confirmed who they are. It says nothing about work quality, but an unverified account is an unknown in a way a verified one is not.

Talent Level is a composite of performance on the platform — completion, ratings, repeat hires and so on. High means a track record.

Ratings and reviews are from completed contracts, so they cannot be fabricated by someone who has never worked. Read the text rather than the number. A four-star review saying "excellent work, one deadline slipped" tells you more than a bare five.

Completion rate and repeat hires. Repeat hires are the one I would weight most heavily. Clients coming back is the strongest available signal that working with someone was good.

Portfolio. Look at whether it resembles your problem, not whether it is impressive in general.

A new account with no history is not a bad bet — everyone starts somewhere, and new freelancers often deliver excellent work for a good price to build a reputation. It is simply an unknown, so size the first commitment accordingly: a small first milestone tells you more than any amount of evaluation.

Talk before you commit

Shortlist three or four and message them. Ten minutes of conversation tells you more than any proposal.

What to look for: do they ask about the parts you left vague? Do they push back on anything unrealistic? A freelancer who agrees to everything, including the impossible deadline, is either not reading carefully or will renegotiate later.

Ask what they need from you. Most projects that go badly go badly because the client did not supply something on time. Someone who tells you what they need up front is someone who has done this before.

Timezone and availability are worth confirming explicitly, because "available" means different things to different people.

Choosing

Two failure modes, roughly equal in frequency.

Choosing on price alone. The cheapest proposal is cheapest for a reason, and the reason is sometimes that they have not understood the work. Rework costs far more than the difference.

Over-indexing on credentials. The most decorated freelancer is not automatically right for your job. Fit matters more than prestige.

The useful question is: who understood the problem best, and can I work with them? Then structure the engagement so being wrong is survivable — small first milestone, real output, then commit further.

Declining people

Do it, and do it promptly. It costs you nothing and it matters.

Freelancers spend something to apply. Leaving proposals in limbo for weeks is the most common complaint about clients on any marketplace. Archive the ones you are not taking as soon as you know, and they are notified and can move on.

You do not owe anyone detailed feedback. A prompt decline is enough. If someone was close and you would work with them another time, say so — it costs a sentence and people remember it.

When you close the job or hire someone, remaining proposals are archived automatically and their authors told, so nobody is left waiting indefinitely.

Your reputation as a client

Freelancers rate clients too, and they talk. A client who responds, decides, funds promptly and communicates gets better proposals over time — visibly so, in a market where good freelancers can choose.

The behaviours that build it are cheap: reply to proposals, decline promptly, fund quickly once agreed, and approve work you are happy with rather than sitting on it.

A workable process for a busy job

If a post has attracted thirty proposals, reading them all properly is not realistic. A process that works:

First pass, ten seconds each. Does it engage with the specifics of your post? Discard anything generic. This usually removes half.

Second pass, a minute each on what remains. Approach, relevant evidence, price with reasoning. Shortlist four or five.

Third pass, look at the profiles of your shortlist properly. Portfolio, reviews, repeat hires.

Then talk to three. The conversation decides it.

Do not try to rank thirty proposals against each other. Filter to a handful worth a conversation and decide from there.

Questions worth asking in the conversation

Three that consistently reveal the most:

"What would you need from me to make this go well?" Somebody who has done this before has a clear answer. Somebody who says "nothing, just leave it with me" usually has not.

"What is the part of this most likely to go wrong?" Tests whether they have thought about the actual work rather than the pitch.

"How would you approach the first week?" Reveals whether there is a method.

None of these are trick questions and all three are useful to you regardless of who you hire.

Deciding between two good candidates

When two are genuinely close, useful tiebreakers in rough order: who understood the problem better rather than who has the stronger CV; who asked the better questions; who will be easier to work with over several weeks; and only then, price.

If they are still level, hire the one with a smaller first milestone. You will learn more from a week of real work than from another round of evaluation.

Interviewing without wasting anyone's time

Once you have a shortlist, keep the conversation short and specific.

Tell them what you are trying to decide. Ask the two or three questions that would actually change your mind. Be honest about your timeline and about how many people you are talking to.

Twenty minutes is usually enough. An hour-long interview for a two-week project is a signal to a good freelancer that the engagement will be heavy on process and light on work.

If you are going to take a week to decide, say so. Silence after an interview is the thing freelancers complain about most, and the good ones will have taken other work by the time you come back.

Watch for these

A few patterns worth noticing at the proposal stage, because they predict problems.

Agreeing to everything, including a deadline that is not realistic. It reads as eagerness and usually means they have not thought it through.

No questions at all, on a brief that plainly has gaps.

A price far below everyone else, with no explanation.

A proposal that describes their process at length and your problem not at all.

None of these are disqualifying on their own. Two or more together usually are.

Common questions

Do I have to respond to every proposal? No, but archiving the ones you are not taking is a courtesy that costs one click.

Can I shortlist more than one person? Yes, as many as you like, and it commits you to nothing.

Can I ask for a sample? A small one, yes. A large unpaid sample is not reasonable and good freelancers will decline.

What if nobody is right? Close the job or improve it and repost. You are not obliged to hire.

Related

Did this answer your question?

Did this not answer it?

Open a ticket and a person will read it. You do not need an account.

Reviewing proposals and choosing someone · Open Lance