Getting a client to say yes is not the finish line. It is the starting gun for a different kind of problem.
Most beginner freelancers lose money, time, or the client entirely in the gap between “they said yes” and “work begins.” They skip the scope summary email because they do not want to seem slow. They skip the contract because they do not want to seem difficult. They start work on a handshake and a payment promise, and then wonder what went wrong when the project turns into a five-revision, zero-deposit mess.
This post covers the exact steps you take between close and kickoff: the scope email, the contract, the payment terms, the kickoff setup, and how to frame the project so scope creep becomes a conversation instead of a freebie.
Do these right once and you will do them right every time.
What should I send a client right after they say yes?
Send a scope summary email within 24 hours of the verbal agreement. This is not a contract. It is a written record of what you both agreed to, giving the client a chance to confirm before work or contracts begin.
A lot of beginner freelancers skip this step because they are excited and want to get moving. That is understandable, but it is also the reason so many projects end with “but I thought you were going to include…” This email locks in shared expectations before anyone signs anything.
Here is what goes in it:
Scope Summary Email Template
Subject: Quick summary of what we discussed — [Project Name]
Hi [Name],
Thanks for the conversation. I wanted to send a quick written summary of what we covered so we are both on the same page before we move forward.
Project: [One-line description of what you are doing]
Deliverables: [List each item — e.g., 3 blog posts of 1,000 words each, 1 round of revisions included]
Timeline: [Start date and final delivery date, or milestone dates if the project is longer]
Rate: [Your total fee or rate per deliverable] — [Payment method and terms — e.g., “50% upfront, 50% on delivery via PayPal or bank transfer”]
Revision policy: [Number of revision rounds included — e.g., “One round of revisions is included. Additional rounds are billed at $X/hour.”]
Let me know if anything looks off or if you want to adjust before we proceed. Once you confirm, I will send the contract.
[Your name]
Keep it simple. This is not a legal document. It is a conversation in writing. The contract comes next.
Do I really need a freelance contract, and what if the client pushes back?
Yes, you need a contract. Every time. No exceptions. A signed contract protects both you and your client, and that framing matters when you present it.
Here is the honest truth about why contracts matter: most freelance relationships do not fall apart over the quality of the work. They fall apart over missed updates, slow replies, and unclear expectations about what was actually agreed to. A contract makes those expectations explicit before either party is frustrated.
For beginners, two free tools cover the basics well:
- Bonsai — free freelance contract templates, plus a platform to send and sign them digitally. The templates are practical and straightforward.
- AND.CO by Fiverr — similar contract and invoice tools with a clean interface. Free tier works well for most solo freelancers starting out.
You do not need a lawyer to get started. You need a document that names the client, names the deliverables, states the payment terms, and includes a basic revision policy. That is it.
If a client pushes back on signing: this is a red flag, but it is also a conversation. The right frame is not “my lawyer says so.” It is “this protects you as much as it protects me. If I deliver something that does not match what we agreed on, you have documentation to hold me accountable.” Clients who understand that framing almost always sign. Clients who still refuse after that explanation are telling you something important about what working with them will be like.
Rule to print and tape to your monitor: Never start work without a signed contract and a confirmed payment method. Not even “just the first part.” Not even for a client you know personally. If the project cannot move forward with basic documentation, the project is not safe to start.
How should I handle payment as a beginner freelancer?
Start with a 50% deposit upfront, 50% on delivery. This is the simplest structure for a beginner, and it protects you without asking the client to pay for something they have not received yet.
Here is how the three main options compare:
- 50% deposit, 50% on delivery — Best for small-to-medium projects under $1,000. Simple to manage and explain. You have skin in the game, and so does the client.
- Milestone payments — Better for longer projects. Break the project into phases (research, draft, final) and invoice at each milestone. Reduces financial risk on both sides if the project stalls.
- Full payment on delivery — Avoid this as a beginner. If a client does not pay after delivery, you have no leverage and no recourse. Some experienced freelancers use this for trusted long-term clients, but it is not a beginner model.
A few practical notes: always confirm the payment method before the project starts. Not “I’ll send a PayPal link later” — confirm it in writing during onboarding. Payment disputes almost always come from a payment method that was never actually set up. Also, payment apps vary by country. If your client is international, clarify whether you accept Wise, PayPal, bank transfer, or another method that works across borders.
According to research from AND.CO and Freshbooks, late or non-payment is the number one challenge freelancers report across skill levels. A deposit and a confirmed payment method at the start of the project eliminates most of that risk before the work begins.
How do I set up the project so scope creep does not happen?
Scope creep almost never starts as a deliberate attempt to get free work. It starts with a vague scope and verbal agreements that get forgotten. Your job in onboarding is to make the scope specific and put communication in writing from day one.
Two things kill this at the start:
The kickoff message. Whether you do a video call or work async, send a written kickoff message before anything else. Cover:
- What you are starting with (the first deliverable or phase)
- What you need from the client before you can begin (logins, briefs, reference materials, feedback on the scope email)
- How you will communicate: which platform (email, Slack, a project tool), how often you will send updates, and your response time
- What “feedback” means in this project: specific revision requests, not ongoing direction changes
The scope frame. In the kickoff or the contract, name what is out of scope as clearly as what is in scope. If a client asks for something that falls outside the original agreement, you say: “That sounds like a good addition. That would be outside the original scope, so I would quote it as a separate task.” That is not adversarial. That is professional. A client who feels informed and respected will accept that framing. A client left in the dark about what they are getting will feel like every boundary is an argument.
You can see this pattern play out in the research: a survey by Upwork found that scope creep affects the majority of freelance projects, and most of it traces back to unclear initial agreements rather than bad-faith clients. The fix is not a longer contract. It is a clearer scope and a written communication habit from the first day.
For a deeper look at how this connects to finding and closing clients in the first place, check out the parent guide: How to Start Freelancing: The Beginner’s Complete Guide.
FAQ
What if I do not have a formal contract template yet?
Start with Bonsai or AND.CO — both have free contract templates you can adapt immediately. You do not need a custom contract drafted by a lawyer to work with your first few clients. A simple document that names the project, deliverables, payment terms, and revision policy covers the basics. Upgrade to a more detailed contract as your projects grow in size.
Can I skip the deposit if I trust the client?
You can, but most experienced freelancers advise against it, especially at the start. Trust is not a payment method. A client who genuinely trusts you back will not object to a 50% deposit, because they understand it is how professional services work. If a client resists the deposit on principle, that is worth paying attention to.
What if the client wants to start right away and skips the onboarding steps?
Hold the line. You can be warm and accommodating while also being clear: “I want to get started quickly, too. Let me send you a quick scope email today and the contract by end of week so we can kick off properly.” Rushing the onboarding to please an impatient client almost always creates bigger delays later when the scope becomes unclear or payment becomes a problem.
How do I handle a client who keeps adding things mid-project?
Name it directly and without blame: “This is a great addition. It falls outside our original scope, so I would add it as a separate line item. Want me to send a quick quote for it?” This keeps the relationship intact and keeps the project profitable. The first time you do this is uncomfortable. The second time is professional. After that, it becomes the standard.
Close
The period between a client saying yes and work actually starting is where most beginner freelancer problems are born, not during the project itself. A scope email, a signed contract, a confirmed deposit, and a clear kickoff message fix almost all of it before it becomes a problem.
Grab the free 30-Day Freelancer Starter Checklist to track every step of your first client journey, including the onboarding steps covered here: renziebaluyutonline.com/freelancer-starter-checklist
For the full picture on starting freelancing from scratch, including how to find your niche, set your rates, and land that first client, read the complete guide: How to Start Freelancing: The Beginner’s Complete Guide
