How to evaluate a freelance project before you apply

A promising title is not enough to decide whether a project is a good fit. Before spending time on a proposal, work out what the client expects, what you can actually deliver and which unanswered questions could change the price. Use this checklist on a small website build, a design assignment or another fixed-scope freelance project.

1. Name the result, not just the activity

“Help with our website” describes an activity. “Deliver a responsive five-page site using approved copy and an existing brand kit” describes a result you can estimate. Look for an audience, a problem and a concrete deliverable. If they are missing, ask for clarification rather than assuming the smallest possible scope.

• What will the client receive: files, a working release, a report or a prototype?
• How many pages, screens, assets or workflows are included?
• What does approval depend on, and who makes that decision?

2. Check the whole budget

Read whether the amount is a fixed project budget, an hourly rate or a range. Confirm the currency and whether the figure covers the entire assignment. Include discovery, communication, revisions, testing and handover in your estimate, not only production time. Hosting, paid assets, research participants and third-party subscriptions may need a separate agreement.

There is no universal “good” budget. Compare the stated amount with your own estimated effort and costs. A low advertised amount may mean a small first milestone, or it may mean an unrealistic brief; ask which before quoting. Do not present a rough estimate as a guaranteed final price when the scope is still open.

3. Separate your work from client dependencies

A deadline is meaningful only if required inputs will arrive in time. List what the client must provide: access, content, brand assets, technical documentation or someone who can answer questions. Agree when feedback is due and what happens if an input is late. Do not promise a launch date that depends on access you have not received.

4. Agree boundaries before the first milestone

• Included work and explicit exclusions.
• Review rounds and what counts as a new requirement.
• Delivery format, source files and handover.
• Payment timing, milestones and the process for approving work.
• Any support expected after delivery.

Put these points into a written agreement appropriate to the project. This checklist is practical preparation, not legal advice or a substitute for reviewing the terms you accept.

A worked example

Brief: “Redesign our checkout, urgently.” Before quoting, ask which steps and devices are included, whether research exists, who supplies copy and whether the job is design-only or includes implementation. A narrower first milestone could be an agreed checkout flow and wireframes. Visual design, testing and development can then be priced explicitly instead of silently added to the same fee.

Apply, clarify or pass

Apply when the result and your fit are clear. Clarify when one or two missing facts change the estimate. Pass when the assignment requires skills you cannot provide, asks you to pay to obtain work or pressures you to expose credentials. A marketplace listing is not a guarantee of a client's identity, payment or continued availability.

On Vibe Work, native tasks and external opportunities have different response paths. A native task has an on-site response action; an external listing sends you to its original source. Review that source's current brief and terms before applying. Browsing is available without an account.