What to Ask Before Starting a Freelance Project

Most project disasters are predictable from the first client call. Not because clients are difficult, but because the wrong questions get asked — or none at all. The work looks straightforward, both sides assume they understand the scope, and everyone moves on. Three weeks later, you are fielding a fourth revision round on something you thought was finished.

A project kickoff is not a formality. It is where you find out whether the engagement will go well. Here is the full list of questions — organized by category — to work through before any freelance project starts.

Scope and deliverables

• What are the specific deliverables? Name them explicitly: a website, a 1,000-word article, a brand identity with logo, icons, and color palette. Vague scope is the root cause of most revision disputes.
• What is not included? Getting explicit about exclusions in the first conversation makes change orders defensible later.
• Are there existing assets, files, or brand guidelines I need to work within?
• Who is providing what — and by when? If the client needs to supply copy, images, or approvals, nail down responsibility before work starts.

Timeline and hard deadlines

• Is there a fixed deadline, or is the timeline flexible?
• What is driving the deadline? A product launch, an event, a board presentation. Understanding the reason tells you when slippage becomes genuinely serious.
• Are there dependencies — things you need from the client before you can begin or continue?
• Who approves the work, and what is their typical turnaround time on feedback?

Feedback and revisions

• Who is the final approver? Is it the person you are talking to, or someone above them?
• How many stakeholders will be reviewing the work?
• What format should you expect feedback in — written notes, annotated PDFs, a call?
• My standard contract includes [X] revision rounds. Does that seem like enough for this project?

Budget and payment

• Has the budget been approved internally? Skipping this question leads to a common trap: three weeks into the work, a stakeholder above your contact decides the number is too high.
• What payment method works for your team — ACH, credit card, check?
• Are there purchase order or invoice processing requirements I should plan for?
• My standard terms are net 15 with a 50 percent deposit at signing. Does that work for you, or are there constraints I should know about?

Context and expectations

• Has your team worked with freelancers on this type of project before? The answer tells you how much process communication you will need to do.
• What does success look like at the end of this engagement?
• What has been tried before that did not work?
• Is there a brand guide, style document, or previous work I should review before I start?

The one follow-up that prevents most problems

After the call, send the client a short written summary: here is what I understood we are building, here is the timeline, here are the things I need from you before I can start. Not a formal contract — a one-page confirmation that takes five minutes to write.

If the client corrects your summary, that is a good outcome. It means you found the misalignment before it became a revision dispute or a missed deadline. The questions are not overhead. They are the project.