DEV Community

Alfred P
Alfred P

Posted on

5 Questions to Ask Before Taking Any Freelance Project

Not every project is worth taking.

This is a hard lesson because when you are building a freelance business, every project feels like one you cannot afford to say no to. But the wrong projects cost more than their invoice value: they consume time you could spend on better clients, create stress that damages your other work, and sometimes leave you with less money than you started with.

Five questions that help you decide before you commit.

1. Is the scope actually clear?

Not "can I build something for this client" but "can I describe the finished product in a single paragraph with enough specificity to build to?"

If you cannot describe the deliverable precisely, you cannot estimate it accurately. Vague scope leads to underquoting, scope creep, and a fixed-price project that bleeds money.

Ask yourself: if the client and I disagreed at the end, would the contract protect me? If the answer is no, the scope needs more definition before you start.

2. Can I talk to the actual decision-maker?

Projects run by committee or filtered through a middleman who then interprets to someone else are high-risk.

Find out early: who has final say on design decisions, on delivery acceptance, and on payment approval? If you cannot get in front of that person at least once before the project starts, you are going to spend a lot of time getting conflicting feedback from people who do not have authority to actually approve anything.

3. Does the timeline make any sense?

"We need this in two weeks" for a six-month project is a red flag, not a challenge.

Unrealistic timelines create one of two bad outcomes: you rush and deliver something below your standard, or you work unsustainable hours and resent the project by the end. Neither is good for your reputation or your wellbeing.

If the timeline does not work, say so and propose a realistic one. Clients who accept that are clients you can work with. Clients who insist on the impossible timeline are showing you how the rest of the project will go.

4. Do I actually want to work with this person?

This sounds unserious. It is not.

You will spend hours communicating with this person. Their communication style, their responsiveness, their tendency toward reasonable or unreasonable feedback will affect your daily experience for weeks or months.

The first interaction you have with a client is the best version of the working relationship. If it is already uncomfortable or frustrating in the sales stage, factor that in.

5. Is the rate actually right?

Not "is this a rate I would accept" but "is this a rate at which this project is profitable?"

Calculate: estimated hours times your target rate, plus a buffer for revision cycles and client communication. Compare that to the quoted price. If the math does not work at your target rate, you are either underquoting or taking a below-rate project.

Both are okay sometimes. They should be conscious decisions, not accidents.


Saying no to the wrong project creates space for the right one. The discipline to ask these questions consistently is one of the things that separates sustainable freelance businesses from ones that feel like they are always barely holding on.


The Solopreneur AI Toolkit includes prompts for evaluating projects and writing airtight proposals. EUR 12.

Top comments (0)