Twenty proposals and not one you can compare? The problem is usually upstream, in the brief. Here are the six things every project brief must state — outcome, scope boundary, what you supply, budget range, timeline and how you will judge “done” — plus the same job posted badly and posted well.
A brief is not paperwork you complete before the real hiring starts. It is the hiring. Whatever you write determines who bothers to read it, who can price it, and who quietly skips it because the effort of guessing your requirements is not worth a bid. If you have ever opened twenty proposals and found nothing you could compare, the fault almost certainly sits in the thirty lines you posted, not in the people who replied. This guide covers the six things a brief must state, how to phrase a budget and a scope boundary, and what to do in the first day after you post.
Why a vague brief attracts vague bids
Imagine two people read your posting. The first is a specialist who is busy, charges accordingly, and has three other briefs open in other tabs. The second is a generalist with a free afternoon and a saved template. A brief that says “need a website for my business, quote your best price” is unpriceable — so the specialist closes it, because guessing wrong costs them either the project or their margin. The generalist bids anyway, because their template costs them nothing to send.
So a vague brief does not get you a wide range of options. It systematically filters out the people you most want and filters in the people who bid on everything. Then it costs you a second time: without a stated scope, every quote you receive is priced against a different imagined project, so the numbers are not comparable. The lowest bid is not the cheapest option, it is the one whose author imagined the smallest job — and you will meet the rest of that job later, as a change request.
The six things every brief must state
You do not need a formal specification document. You need six answers, and a freelancer who reads them can price your work in ten minutes.
- The outcome. Not the task, the change. “Customers can book an appointment online and I get a WhatsApp alert” tells a freelancer far more than “build a booking page”, because it reveals what success looks like.
- The scope boundary. What is included, and explicitly what is not. This is the single highest-value paragraph in any brief, and it gets its own section below.
- What you supply. Logo files, product photos, copy, hosting, domain access, an existing codebase, a person who can answer questions. Anything you do not supply is either work the freelancer must do, or a dependency that will stall the project.
- A budget range. A range, not a figure. Hiding it does not get you lower prices; it gets you fewer usable bids.
- A timeline with a reason. “Two weeks” is a wish. “Live before our stall at a trade fair on the 20th” is a constraint a freelancer can plan against, and it tells them whether to say no.
- How you will judge “done”. The test you will actually run on delivery. If you cannot describe it, neither side knows what they are agreeing to.
Write a title a freelancer can filter on
Freelancers scan titles the way you scan a menu. On the projects listing your title competes with everything posted that hour, and the only job it has is to let the right person recognise their own work. Name the deliverable and the technology or discipline; leave the adjectives out. “Urgent!!” tells nobody anything, and “simple task” actively repels good bidders, because experienced people know that when a client calls something simple, it is not.
| Weak title | Why it fails | Stronger title |
|---|---|---|
| Need a website urgently | No discipline, no scope, no platform. Unfilterable. | 5-page WordPress site for a dental clinic, with online appointment booking |
| Simple Excel work | “Simple” hides the difficulty; “Excel work” could be ten different skills. | Automate a monthly sales report in Excel from three CSV exports |
| Looking for a designer | Which kind? Print, UI, brand, packaging? | Brand identity for a new filter-coffee brand: logo, colours, packaging labels |
| Fix my app | No platform, no symptom, no build access stated. | Android app crashes on launch after the latest release build — Flutter, source available |
Name a budget range without anchoring yourself too low
State the range and tie it to scope rather than to your willingness to pay: “Budget ₹25,000 to ₹40,000 for the scope below; if you think the scope needs more than that, tell me what you would cut to fit.” That phrasing invites a scope conversation instead of a discount conversation. Avoid a range so wide it carries no information — ₹5,000 to ₹5,00,000 is the same as naming none, and it reads as waiting to see who bids lowest. If you have no reference point for the range itself, work it out from the deliverables first: the method, and the full argument for posting a range at all, are in how to set a realistic budget for freelance work.
Scope exclusions: the paragraph that saves the project
Almost every freelance project that ends badly ends over something nobody wrote down. The client assumed content writing was included; the freelancer assumed the client would supply copy. Both were reasonable. Neither was stated.
So add a short “not included” list. It feels unfriendly for about one minute, and then it saves you a fortnight. You are not being difficult — you are making the quote you receive mean something, because a freelancer who knows exactly what they are pricing gives you a number you can compare against the next one.
Not included in this scope: writing the page copy (I will supply final text), product photography, ongoing maintenance after handover, and migration of the old blog posts. Happy to discuss any of these as separate work once the main build is agreed.
A brief rewritten: the same job, twice
Here is one real-world shape of brief in both its usual form and its useful form. The job, the budget and the deadline are identical; only the writing changes, and with it the quality of everything that comes back.
The first 24 hours after you post
Early proposals are disproportionately from people who were actively looking, which is usually a good sign. The window matters: freelancers know that a client who has not responded to anybody in three days is probably not hiring this week, so silence costs you the attention of the people still choosing where to spend their bids.
- Answer the questions that arrive inside the bids. A posting here has no public question thread, so a question only reaches you in someone's pitch or in a message — and one bidder's question was probably a gap for all of them.
- Write the answer once and send the same words to everyone who asks. A posting cannot be edited after it is live, so you cannot fix the brief in place; what you can do is make sure every bidder prices against one version of the truth, and get the missing sentence into the next brief you post.
- Reply to good proposals within a day, even if the reply is “this looks strong, I am reading everything until Friday and will come back to you.” Strong freelancers get booked while you deliberate.
- Close out the people you are not going to hire. A one-line no costs you ten seconds and is remembered the next time you post.
- Resist hiring in the first hour. The first proposal to arrive is the fastest bidder, not necessarily the best fit.
Mistakes that quietly cost you the good bidders
Four of these come up again and again, and each one filters out exactly the people you were hoping to attract.
- Asking for a quote with no scope. “How much for an app?” cannot be answered honestly, so you will only hear from people willing to answer it dishonestly.
- Calling complex work simple. “Simple integration with our accounting software” tells anyone who has done one that you have not, and that the estimate conversation will be painful.
- Requesting free sample work. A custom mockup, a sample chapter, a test page. Serious freelancers decline unpaid spec work, so you end up choosing from whoever had nothing better to do. If you need proof of ability, pay for a small first milestone instead.
- Posting the same job three times to “reach more people”. It reaches the same people, who now have to guess which posting is real.
- Describing a wish list as a requirement. Everything in the brief gets priced. If a feature is optional, mark it optional, and you will often get a quote with and without it.
Write the brief first, then post it. If you want to see how bidding, milestones and escrow fit together before you do, the sequence is laid out step by step in how it works.
Post your projectOne last check before you hit post
Read your brief as though you were a freelancer who has never met you, and ask one question: could I put a price on this without sending a single message? If the answer is no, find the missing sentence and add it. Then read it again as the freelancer you actually want — the busy specialist — and ask whether it is worth their afternoon.
It is also worth knowing what a good reply looks like, so you can recognise one in the pile. The structure that experienced freelancers use is set out in how to write winning freelance proposals; a proposal that restates your problem, names one relevant piece of proof and proposes a milestone plan is the shape you are hoping to receive. A brief that answers the six questions above is what makes that reply possible.
The takeaway: a brief is a filter, and a vague one filters in the wrong people. State the outcome, the scope boundary, what you supply, a budget range tied to scope, a timeline with a reason, and the test you will run on delivery. Add an explicit “not included” list, then answer questions in the first 24 hours. Do that and the bids that arrive will be comparable, which is the only way to actually choose.