How to read a job post before you write a word
A four-step way to pull the real ask out of a hurried job post, so your proposal answers what the client meant.
Most freelancers treat a job post as a title and a budget. They skim, recognise the tool they know, and start typing. The proposal that follows is about the freelancer, because the freelancer did not learn enough about the client to write anything else.
A job post is a person describing a problem badly, in a hurry. Reading it well takes about ten minutes, and it is the most valuable ten minutes in the whole process. Here is a four-step way to do it.
1. Find the result, not the task
Clients list deliverables: a logo, ten reels, a checkout fix. Ask what they want to be true when the job is over. A café owner who needs a logo wants a signboard up before opening day. Write that sentence down. Your opening line will come from it.
2. Mark the evidence of pain
Read again and underline any phrase with feeling in it: as soon as possible, our last developer disappeared, launching on the 15th. These tell you what you will be judged on. A client who was abandoned by a past freelancer is hiring for reliability first and skill second, and your proposal should say how they will hear from you.
3. Check the alarm bells
You are also reading to protect yourself. Look for:
- a scope far larger than the budget could cover;
- a request for new, unpaid work specific to their project;
- pressure to talk or pay outside the platform before a contract;
- any request for your login, identity documents or a fee.
One mild concern is ordinary. Two serious ones together are a pattern, and no proposal fixes a pattern.
4. Decide
Now choose one of three: bid, bid with a clarifying question, or skip. Skipping is not laziness. Every post you decline gives time back to the ones that fit.
Do not miss the bottom of the post
The last paragraph is where clients put instructions to applicants: start your reply with a word, attach two samples, answer these three questions. Many applicants miss them. Following them is the easiest way to show you read the post, and ignoring them is the easiest way to be filtered out.
What you should have after ten minutes
- One sentence stating the result.
- One quoted phrase showing pain, or a note that there is none.
- A list of risks, even if it is empty.
- A decision.
- Any instructions to applicants.
With those five things in front of you, the proposal nearly writes itself: their problem in their words, one matching proof, a first step and one question. Without them, you are decorating a template.
The Bidcraft vault has a chapter of ten prompts that does this reading with you, one post at a time.