You have a signed proposal and a start date. From here the work is the easy part to think about. The harder part is everything around it: who sends what, when, how feedback arrives, and what happens when the client asks for one more thing.
This page lays out the stages of a typical freelance project and what you owe the client at each one. Each stage has its own playbook with templates. Read this one first, then open the one you need today.
The stages at a glance
Stage | What you produce | Playbook |
|---|---|---|
Paperwork | Signed agreement, scope, first payment | |
Onboarding | Access, assets, billing details, welcome email | |
Kickoff | Agreed plan, owners, dates, follow-up email | |
The work | Weekly updates, decisions in writing | |
Feedback | Consolidated rounds, sign-off | |
New asks | Priced change requests | |
Handover | Files, notes, final invoice, testimonial ask |
A two-week logo job moves through all of these in a few days. A six-month website build spends most of its life in the middle rows. The order stays the same.
Before any work: the paperwork
The most common mistake is starting on a promise. The client is excited, you want the project, and the agreement "will come next week". Then the scope is whatever the client remembers, and payment arrives when their accounts team gets to it.
Three documents carry the whole project. A master services agreement covers the relationship: payment terms, ownership of the work, confidentiality, how either side can end it. A statement of work covers this one project: deliverables, what is out, revision rounds, dates. The deposit and payment terms decide when money moves.
For a small job, one email with all of that in it, and a reply saying "agreed", is a workable minimum. Start when the first payment lands, not before.
Onboarding: get what you need in one go
Between signing and the first real day of work, collect everything you will need: logins, brand files, the person who approves work, the GSTIN and billing address for invoices. Ask for it in one list, not over ten WhatsApp messages across two weeks.
You also send things: a welcome email with your working hours, how to reach you and what happens next. The client onboarding checklist has both lists and the email.
Kickoff: agree the plan out loud
The kickoff call is where the client hears your plan and you hear the things that were not in the brief: the launch date that cannot move, the director who will see the work at the end and have opinions, the festival week when nobody will reply.
Keep it under an hour, send the agenda the day before, and write it all up within a day. The remote kickoff meeting playbook has the agenda, a time zone table for overseas clients and the follow-up email.
During the work: a rhythm the client can rely on
Clients rarely complain that the work is slow. They complain that they did not know what was happening. A short written update on the same day every week fixes most of that, even when the update is "on track, nothing needed from you".
How often depends on the project and the client. A three-day job needs two messages; a retainer needs a weekly note and a monthly summary. Agree the channel too. Many Indian clients default to WhatsApp, which is fine for quick questions but a poor place for decisions. The client update cadence playbook covers the schedule, the update template and channel norms.
Keep one place for everything: a Notion page or Google Doc per client with the scope, decisions and updates in it. The Notion and Loom setup shows one way to do it.
Feedback: rounds, not drips
Feedback is where fixed-price projects lose money. It arrives in pieces from different people, some of it contradicts earlier feedback, and some of it is new work dressed as a change.
Agree the number of revision rounds in the SOW, ask for each round in one consolidated list from one person, and get a written sign-off at the end. Handling revisions has the contract wording and the replies to use.
New asks: say yes with a price
Clients will ask for more. That is usually good news; it means they like the work. The problem is only when extra work goes in without anyone agreeing what it costs or how it moves the date.
Run every new ask through a short change request: what is added, how long it takes, what it costs, what it does to the deadline. Stopping scope creep has the process, the scripts and the template.
When it goes wrong
Some projects turn: late payments, a new stakeholder who wants to start over, messages at 11 pm. Most of these are easier to handle when everything up to that point is in writing. Dealing with a difficult client covers what to say, when to pause work and what you can do about unpaid invoices.
Handover: finish properly
The last week decides whether the client comes back. Send the final files in an organised folder, a short note or video on how to use them, and the final invoice. Move any passwords you held to the client and remove your own access.
Then ask for two things while the client is happy: a testimonial and a referral. The client offboarding checklist lists everything to close off.
After the project
A client who has worked with you once is the cheapest new project you will ever win. Put a reminder in your calendar six to eight weeks after handover to check how the work is doing, and suggest the next piece when it makes sense. Turning one-time clients into repeat clients covers the follow-up, and retainers covers turning steady work into a monthly fee.
Set up on day one of every project
0 of 5 done
If you only do one thing from this page, write every decision down in the shared doc on the day it is made. Every later stage gets easier when you can point to it.
Common questions
What is the best way to manage freelance projects as a beginner?
Use one shared document per client that holds the scope, timeline, decisions and weekly updates, and one folder for files. Send a written update on a fixed day each week. Ask for feedback in one consolidated round per draft. Price anything new before you do it. That covers most of what goes wrong on a first project, and you can add tools later once you know what you are missing.
Do I need project management software as a freelancer?
Not at the start. A Notion page or a Google Doc per client, a shared Drive folder and a calendar are enough for two or three clients at a time. Move to a board tool such as Trello or ClickUp when you are juggling more projects than you can keep in your head, or when a client wants to see progress without asking you.
Is an email agreement enough for a small freelance project?
For a small job, an email that sets out the work, the price, the payment dates, the number of revisions and the deadline, with the client replying "agreed", is far better than nothing and is usually good enough as evidence of what was agreed. For anything you will run for more than a month, or with a company, use a proper agreement and a statement of work.
Should I charge for meetings with a client?
Build the kickoff and a set number of review calls into your quote. If the client wants a standing weekly call on top of that, either price it in or say how many calls the fee covers. Meetings that keep growing are a form of scope creep, and they eat the hours you meant for the work itself.
