Use this kit before quoting a freelance project. It helps you collect project details, define scope boundaries, and confirm expectations before work starts.
Quick answer: what to collect before starting
Before starting a freelance project, collect the client’s goal, target audience, required deliverables, deadline, approval owner, budget range, revision expectations, file/access requirements, and what is explicitly out of scope. Then confirm those answers in a kickoff email before work begins.
This kit gives you:
- a client intake questionnaire
- a scope boundary checklist
- a revision policy note
- a kickoff email script
- an AI workflow prompt to turn intake answers into a project brief
This is general business information, not legal advice. Adapt it to your contracts, local rules, and client agreement.
1. Client intake questionnaire
Copy this before a discovery call or quote request.
Project basics
1. What is the main goal of this project?
2. What problem should this project solve?
3. Who is the target audience or end user?
4. What final deliverables do you expect?
5. What deadline or launch date matters?
Decision process
6. Who approves the final work?
7. Who gives feedback during the project?
8. Are there brand, legal, compliance, or stakeholder requirements?
9. What examples should I use as a reference?
10. What examples should I avoid?
Scope and constraints
11. What is included in this project?
12. What is definitely not included?
13. How many revision rounds do you expect?
14. What files, accounts, or access will I need?
15. What price range has been approved?
Success and handoff
16. How will you judge whether the project is successful?
17. What format should the final files be delivered in?
18. Who owns the next step after delivery?
19. Are there future phases that should be quoted separately?
20. Is there anything that could delay approval or payment?2. Scope boundary checklist
Use this checklist before sending a proposal.
Scope boundary checklist
[ ] Deliverables are named clearly.
[ ] Number of pages, screens, files, revisions, or sessions is defined.
[ ] Deadline and client response time are both clear.
[ ] Approval owner is named.
[ ] Feedback channel is defined.
[ ] Revision rounds are limited or priced separately.
[ ] Rush work is excluded or priced separately.
[ ] Extra meetings are excluded or priced separately.
[ ] Source files, exports, and handoff formats are defined.
[ ] Third-party costs are excluded or listed separately.
[ ] Out-of-scope requests require a new quote or change order.3. Simple revision policy note
Use neutral wording. Do not promise legal protection.
This project includes [NUMBER] revision round(s) based on the agreed scope above. A revision means a change to the agreed deliverable, not a new deliverable or a major change in direction. Requests outside the agreed scope can be quoted separately before work continues.Alternative softer version:
To keep the project on schedule, I include [NUMBER] focused revision round(s). If the project direction changes or new deliverables are added, I’ll pause and send a short updated estimate before continuing.4. Kickoff email script
Send this after the client agrees to proceed.
Subject: Project kickoff: [PROJECT NAME]
Hi [CLIENT NAME],
Thanks — I’m ready to start [PROJECT NAME]. Before I begin, here is the project summary I have on file:
Goal: [MAIN GOAL]
Deliverables: [DELIVERABLES]
Deadline: [DATE]
Approval owner: [NAME]
Revision rounds included: [NUMBER]
Out of scope: [ITEMS]
Files or access needed: [ITEMS]
Please reply with “Confirmed” if this looks correct. If anything needs to change, send the update before [DATE/TIME] so I can adjust the schedule or quote if needed.
Best,
[YOUR NAME]5. AI workflow companion
Use this prompt after the client answers the intake questions.
You are helping me prepare a freelance project brief.
Client intake answers:
[PASTE ANSWERS]
Create:
1. a one-paragraph project summary
2. agreed deliverables
3. out-of-scope items
4. open questions to ask before quoting
5. potential scope creep risks
6. kickoff email draft
7. simple task list for the first project phase
Keep the tone professional and concise. Do not add legal language or guarantees.6. Common scope creep signals
Watch for these phrases before you agree to a project:
- “It should be quick.”
- “We’ll know what we need when we see it.”
- “Can you just include a few extra versions?”
- “The deadline is flexible, but we need it soon.”
- “Several people will review it.”
- “We do not have examples yet.”
- “Budget depends on the final idea.”
These do not mean the client is bad. They mean the project needs clearer scope before you quote.
7. When to pause before quoting
Pause and ask follow-up questions if:
- no single approval owner exists
- deliverables are not countable
- timeline depends on other teams
- the client asks for unlimited revisions
- required access is not available
- the price range is unclear
- the client cannot define success
A short pause before quoting is usually cheaper than a long dispute after work starts.
8. FAQ
Is this a contract template?
No. This is an operational intake and scope checklist. It can help you organize project details, but it is not legal advice or a substitute for a contract.
How many revision rounds should freelancers include?
Many freelancers include one or two focused revision rounds. The right number depends on the project type, price, timeline, and client approval process.
Should I ask for budget before sending a proposal?
Yes, if possible. A price range helps you recommend the right scope instead of guessing. If the client will not share a range, define exactly what your quote includes.
What if the client changes direction midway?
Pause and summarize what changed. If the request adds new deliverables or changes the original goal, send an updated estimate or change order before continuing.
Can I use AI to create the project brief?
Yes, but review it manually. AI can summarize intake answers and flag risks, but you are responsible for the final scope, pricing, and client communication.
Next step: copy the intake questions, scope checklist, kickoff email, and AI prompt into your project workspace before sending your next proposal.
This is general business information, not legal advice. Adapt it to your contracts, local rules, and client agreement.