The signed proposal is the end of the sales process and the beginning of the client relationship. What happens in the days between signing and starting work shapes how the project feels for the next several weeks. A clear onboarding process makes the transition smooth and signals to the client that they made the right choice.
Most freelancers don’t have a formal onboarding process — they sign a contract, collect a deposit, and start working. The gaps that creates (missed information, unclear expectations, no established communication rhythm) are often what causes projects to go sideways in the first two weeks.
Here’s what a solid onboarding process looks like, step by step.
Step 1: Send a welcome email within 24 hours of signing
The window between signing and hearing next steps should be short. A welcome email sent within 24 hours of the proposal being accepted accomplishes three things: it confirms the relationship, sets expectations for what happens next, and maintains the momentum that closing the deal created.
The welcome email should cover:
- Confirmation that you’ve received the signed agreement
- Payment instructions for the deposit (or a link to the invoice)
- What you’ll need from them and when
- The proposed date for the kickoff meeting
- How you’ll communicate going forward (email, Slack, a project management tool)
Keep it short. This isn’t the place for detailed project discussion — it’s orientation.
Step 2: Collect the deposit before starting any work
This is non-negotiable for project work. The deposit (typically 25–50% of the project total) confirms the client’s commitment and covers your time if the project is cancelled early. Don’t schedule the kickoff meeting or begin any prep work until the deposit is received.
If you’re using a proposal and invoicing tool like Waco3, the deposit invoice can be sent directly from the accepted proposal — the client who just signed sees the invoice immediately, while the project is still fresh in their mind.
Step 3: Send an intake questionnaire or brief
Before the kickoff meeting, send an intake form that collects the information you need to prepare:
- Brand assets (logos, fonts, color codes)
- Existing documents relevant to the project
- Access credentials needed (website login, social media accounts, analytics)
- Specific preferences or examples of work they like
- Any constraints, deadlines, or dependencies
Getting this information in writing before the kickoff has two advantages: you arrive at the kickoff prepared, and you have a written record of what the client told you at the start of the engagement. If a client later says “I already told you X,” you have the intake form to refer to.
Step 4: Schedule the kickoff meeting
The kickoff meeting is a 30–60 minute call where you confirm the scope, establish working preferences, and answer any remaining questions on either side. It’s the first project-specific conversation after the contract is signed.
Schedule it for 3–5 days after signing — long enough to collect the intake questionnaire responses and deposit, short enough that the client still feels the momentum of starting.
Send an agenda in advance. Even a brief one (3–4 bullet points covering what you’ll discuss) signals that you’re organized and helps the client prepare.
Step 5: Send a written summary after the kickoff
After the kickoff meeting, send a written summary covering:
- Key decisions and confirmations made in the meeting
- Project timeline with milestones
- Any clarifications that came up
- Next steps and who’s responsible for each
This email creates a written record of the shared understanding at the start of the project. It’s a reference point if questions arise later, and it gives the client a chance to flag any misunderstandings before work begins.
The post-kickoff summary is the most useful document you’ll send in the entire project, and it takes 15 minutes to write. Make it a standard part of your process.
Step 6: Set up communication and project management tools
Within the first few days, establish the tools and cadence that will govern the project:
- Where will files be shared? (Google Drive, Dropbox, a project management tool)
- How should the client send feedback? (Email, a shared document, a commenting tool)
- How often will you provide updates? (Weekly status email, a standing call, milestone check-ins)
- What’s the best way to reach you for urgent questions?
The client doesn’t need to use sophisticated tools — but both parties should agree on a single channel for communication and a predictable update rhythm. Unclear communication channels are one of the most common sources of client frustration.
Step 7: Confirm the timeline and milestones in writing
Send a brief timeline document or include it in the post-kickoff summary. List the major milestones, the dates for client feedback windows, and the expected completion date. If there are dependencies (e.g., “this milestone requires you to deliver X by [date]”), call those out explicitly.
A shared written timeline does three things: it keeps the project on track, it gives you a basis for flagging delays, and it makes the client’s responsibilities visible — so when a delay happens on their end, it’s clear who owns it.
The entire onboarding process — welcome email through confirmed timeline — should take no more than a week. By the end of it, the client should feel confident about what’s happening, when, and how to reach you. That confidence is the foundation the rest of the project runs on.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
