How to Analyze an Upwork Job Before You Write the Proposal

Do not write until you can explain the job in one sentence

If you cannot describe the work without looking at the post, you are not ready to bid. Analysis is not a formality. It is how you avoid spending Connects on jobs you cannot deliver, and how you pick a hook that is true.

Pass 1: product and outcome

Ignore skills for a moment. Write one sentence: “They want ___ so that ___.”

Examples:

• “They want a mobile app that stores workouts offline so trainers can run sessions with bad gym wifi.”
• “They want the WooCommerce checkout to stop double-charging so they can reopen the store.”

If you cannot fill those blanks, the post is vague. You can still bid, but your letter should ask the missing product question instead of pretending you already know the build.

Pass 2: must-have vs nice-to-have

Make two lists from the post:

Must-have — languages, platforms, credentials, location, “only people who have done X,” tools they already pay for.

Nice-to-have — “plus if you know Figma,” “bonus for AI experience,” extra integrations.

Bid when you honestly cover the must-haves. Nice-to-haves can appear as a single extra line, not as a claim that you are an expert in all of them.

Pass 3: risks and red flags

You are allowed to skip a job. Common reasons:

• Scope is a full product, budget is a small fixed price, and they want it this week
• They ask you to start work or share personal contact details before a contract
• They want a clone of a well-known product with no legal clarity
• The only requirement is “expert in everything”

Skipping is cheaper than a bad contract. If you still bid, name the risk in a question: “The post lists a mobile app, admin, and AI recommendations at this budget — which of those is the actual first release?”

Pass 4: match to your proof

Look at your own projects. Score them roughly:

• Close: same product and same stack
• Adjacent: same product, different stack you can map
• Weak: impressive but unrelated

Only Close or Adjacent should appear in the letter. Weak proof belongs on your profile, not in the first screen.

ProposalAI’s [job analysis](/help/how-to-use-client-requirements) can highlight skill overlap and suggest portfolio matches after you paste the post. Treat the score as a prompt to think, not as a reason to ignore a must-have you do not have.

Pass 5: decide the angle

Pick one angle for the proposal:

• Repair: you will isolate and fix a named bug
• Ship: you will deliver a defined first milestone
• Advise: the post is unclear, so you will propose a short discovery

Mixing all three makes the letter muddy. One angle keeps the hook honest.

Then write

Only after those five passes should you open a template or the [generator](/signup). The analysis note you already wrote is the personalization. The letter is just that note, cleaned up for the client.

A worked version of this process for a marketplace MVP is in the [full-stack example](/examples/full-stack-development).