សញ្ញាគ្រោះថ្នាក់នៅក្នុងសំណើរបស់ Freelancer

You post a brief. Within the hour you have fourteen proposals. Nine of them open with the same sentence, three of them quote a number without saying what it buys, and one of them asks whether your existing content is staying or being rewritten — which is the only question in the whole pile that would actually change the price.

That last one is almost always the person to hire. Not because a good question guarantees good work, but because reading your brief properly is the cheapest possible test of whether someone will read anything else properly. Everything below is a way of applying that test faster.

Why the proposal is the best signal you get

A portfolio shows you someone’s best day, curated after the fact, possibly with a team behind it. A proposal shows you how they work when nobody is watching: how carefully they read, how they think about scope, how they handle uncertainty, and whether they are willing to say “I need to know X before I can price this”.

It is also the only artefact you get for free, before any money changes hands. So it is worth spending ten minutes on rather than two. The habit that helps most is to read the proposals with your own brief open beside them, and to ask one question of each: could this have been sent to somebody else without changing a word? If the answer is yes, you are looking at a template.

None of this is about catching people out. Most freelancers writing weak proposals are not dishonest — they are busy, or new, or applying at volume because that is what they were told to do. But you are not hiring effort. You are hiring judgement, and the proposal is where judgement first shows up. Our guide on writing a project brief that gets great proposals covers the other half of this: the better your brief, the more obvious the weak proposals become.

Red flag 1: it could have been sent to anyone

The copy-paste proposal is the most common problem and the easiest to spot. Tells include an opening paragraph about the freelancer rather than about your project, a list of services that goes far beyond what you asked for, your project referred to in general terms (“your website”, “your business”) when you named it, and a closing line that could end any message ever written.

A subtler version is the proposal that mentions one specific detail from your brief in the first line and then reverts to boilerplate for the remaining four hundred words. That is a template with a personalised opener, which is worse than an honest template because it is designed to pass the exact test you are running.

The reason this matters is not etiquette. Someone who did not read your brief before quoting has not priced your brief — they have priced an imagined average job. When the real job turns out to be different, you are the one who finds out, usually halfway through.

• Template tellOpens by describing the freelancer, not the project.
• Template tellLists services you did not ask for, in the order they appear on their profile.
• Template tellUses generic nouns where your brief used specific ones.
• Genuine signalReferences a constraint from your brief and explains what it changes.
• Genuine signalAsks a question whose answer would move the price.

Red flag 2: it does not answer the brief

This is different from the template problem. Here the freelancer has clearly read your brief and has decided to propose something else — usually something bigger, occasionally something smaller, and generally something they would rather sell.

Sometimes that is legitimate expertise. A specialist who says “you have asked for a redesign, but the problem you described is a content problem and a redesign will not fix it” is doing you a real favour, and that proposal deserves a reply. The difference is whether they explain the reasoning and still quote what you asked for. A proposal that substitutes a different, larger job without acknowledging the swap is a sales move, not a recommendation.

The scaled-down version is just as risky. If you asked for eight pages and the quote covers three, the number is not comparable to the others in your inbox, and you will discover that at the worst moment. Whenever a proposal changes the shape of the job, ask for the original scope priced as well, so you have something to compare.

Red flag 3: the price makes no sense

There are two failure modes here and they look nothing alike.

The number with nothing attached. A price on its own is not a quote; it is a guess you are being invited to accept. Without a list of what is included, a stated number of revisions and a definition of “done”, the figure cannot be compared to anything and cannot be held to later. This is the most common cause of a job going wrong, and it is entirely preventable by asking one follow-up question.

The number that is far below everything else. A quote at a fraction of the others is not automatically a scam, and it is not automatically a bargain either. Sometimes it reflects a genuinely lower cost base. More often it reflects a smaller job than the one you described, a plan to add charges later, or someone who has not understood the work. The way to find out is to ask what is excluded. A low quote with a confident, specific exclusions list is often fine. A low quote whose author cannot say what is excluded has not been scoped.

Market rates vary enormously by scope, complexity and experience, so treat any published range as a rough orientation rather than a rule. Two of our guides go into the numbers in detail: how much a website costs and what a logo design costs.

Red flag 4: no scope, no deliverables, no revisions

Scope is the part of a proposal that decides whether the job ever ends. A proposal that does not define it is not cheaper — it has simply moved the argument to later, when you have already paid and are less able to walk away.

Three specifics are worth insisting on before you accept anything:

• Deliverables, as a list of nouns. Not “a logo” but the file formats, colour variants and sizes you will receive. Not “a website” but the number of unique page templates.
• Revisions, as a number. “Unlimited revisions” sounds generous and is usually a warning sign: it either means the price carries padding, or it means revisions will quietly stop when the freelancer decides they have. A stated number is more honest than an unlimited promise.
• A definition of done. The condition under which the work is finished and payable. Without it, “finished” is whatever the more persistent party says it is.

None of this needs to be adversarial. Most freelancers welcome a buyer who wants scope pinned down, because scope creep costs them more than it costs you. If someone reacts badly to being asked what is included, that is itself the answer.

Red flag 5: a timeline that is a promise, not a plan

“I can have it done by Friday” is a promise. “First draft four working days after I have your copy and logo files, then two days for revisions” is a plan. The difference is that a plan names its dependencies, and dependencies are where projects actually slip.

Be sceptical of any timeline that does not mention what the freelancer needs from you. Almost every late project is late partly because the buyer supplied something a week after they meant to, and a freelancer who has never noticed that pattern has probably not run many projects.

Be equally sceptical of a turnaround that is dramatically faster than everyone else’s for the same brief. It usually means a smaller job is being quoted, or that your work will be squeezed between other commitments. Speed is a real and legitimate thing to buy — but you want it stated as capacity, not as enthusiasm.

One practical note on scheduling: freelancers on Zinn Hub work all over the world, so agree deadlines as calendar dates with a named time zone rather than as “end of day”, and check what the current local time actually is on both sides before you fix a call. Daylight-saving rules differ from country to country and change during the year, so an offset you worked out once will not stay correct.

Red flag 6: the move-this-off-platform ask

If a proposal suggests continuing the conversation somewhere else, or paying by bank transfer, gift card or cryptocurrency directly rather than through the platform, stop there. This is the one item on the list that is not a judgement call.

The reason is mechanical rather than moral. Every protection you have depends on there being an order: a record of what was agreed, a payment the platform can see, and a process to fall back on. Pay outside that and there is no order, no cancellation route, no dispute route and no refund route — you have a private transaction with a stranger, and you have given up the only leverage you had.

On Zinn Hub, taking payments outside the platform is a serious breach of our terms and conditions and grounds for immediate permanent removal. If someone asks, you can decline and report it. A freelancer who has been on the platform any length of time knows the rule perfectly well, which tells you something about anyone who asks anyway.

The same logic applies to a request to pay a deposit off-platform “to secure the slot”. There is no slot. There is a payment you cannot get back. Our guide to common scams when hiring freelancers online covers the variations in more detail.

Red flag 7: proof you cannot check

Proposals often arrive with evidence attached: portfolio links, screenshots, named clients, glowing testimonials. Evidence is good. Uncheckable evidence is not evidence.

The things worth verifying, in rough order of how often they turn out to be misleading:

• Portfolio piecesAsk which part they personally did. “I worked on this” can mean anything from art direction to one icon.
• ScreenshotsAsk for the live URL. A screenshot of a result is not a result.
• Named clientsAsk what the engagement actually was. A one-off $50 task and a year-long retainer look identical in a logo strip.
• Pasted testimonialsPraise quoted inside a message is unverifiable by definition. Prefer reviews attached to a real order.
• Metrics and resultsAsk over what period and against what baseline. A percentage with no denominator is decoration.

This is precisely why review provenance matters. Reviews on Zinn Hub require a confirmed purchase, so a rating is attached to an order that genuinely happened rather than to a screenshot. Across the platform that currently averages 4.9 from over 38,000 verified-purchase reviews. It is not a guarantee about any individual freelancer — nothing is — but it means the number you are reading came from somewhere you can trace.

Zinners on Zinn Hub are also verified with government-issued photo ID and evidence of their skills and past work before they can sell. That answers the question of who you are dealing with. It does not answer whether they are right for your job, which is what the proposal is for. Our guide on how to vet a freelancer properly covers the checks worth making once a proposal has passed.

Red flags in how they communicate

Some of the strongest signals are not in the content of the proposal at all.

Pressure. “This rate is only available today”, “I have another client waiting for this slot”, “I need a decision by tonight”. Real capacity constraints exist and get mentioned calmly, once. Manufactured urgency is designed to stop you comparing, which is exactly the thing you should be doing.

Volume without substance. A very long proposal that never gets specific is a form of hiding. So is a very short one that is all reassurance and no detail.

Defensiveness to a reasonable question. Ask what happens if the first draft misses the mark. The answer matters less than the tone. Someone who treats a normal risk question as an insult will treat a normal revision request the same way.

Refusing to write anything down. “Let’s just get on a call and sort it out” is fine as an addition and a warning sign as a substitute. Calls are useful; unrecorded agreements are not. Whatever you settle verbally, put it back in writing in the platform messages afterwards.

Inconsistency. A proposal written in a very different voice from the freelancer’s profile and messages is worth a second look. So is a quote that changes materially between the proposal and the order without the scope changing.

Four things that look like red flags and are not

It is just as expensive to reject good people for bad reasons, so it is worth naming the false positives.

A short proposal. Experienced freelancers are often brief because they know exactly what the job is. Length is not effort. Judge specificity, not word count.

Imperfect English. Zinn Hub is available in 45 site languages and you can be messaged in 57, and a great many excellent freelancers are writing to you in their second, third or fourth language. Grammar tells you about language background, not about skill. What matters is whether the meaning is precise. If the proposal shows they understood a subtle point in your brief, they understood it.

A price above your budget. A quote higher than you hoped is information, not an insult — particularly if two or three others land in the same place. It usually means the job is bigger than you thought. The productive response is to ask what a reduced scope would cost.

Asking a lot of questions. This reads as hesitancy and is almost always the opposite. Someone who wants to know your deadline, your existing assets and who signs off is someone who has been burned by not asking. Treat it as a green flag.

What a genuinely strong proposal looks like

Strip everything above back and a good proposal does five things.

• It proves the brief was read — by referencing a specific constraint and saying what it means for the work.
• It states scope in nouns — deliverables, formats, quantities, revision count, and what is excluded.
• It gives a plan, not a promise — stages, dependencies, and what the freelancer needs from you and when.
• It attaches the price to the scope — so the number means something and can be compared with the others.
• It surfaces a risk — the thing most likely to go wrong, named up front rather than discovered later.

That fifth point is what separates the best proposals from the merely competent ones. Anyone can promise success. Naming the likeliest failure mode, before being paid, takes both experience and confidence.

If two proposals both clear that bar, the tie-breaker is usually not price. It is whichever freelancer’s questions made you think hardest about your own project — and if you still cannot choose, a small paid test is a better decision-maker than another round of messages. Our guide on testing a freelancer before you commit sets out how to run one.