How to onboard a new freelance client

Same day the contract is signed (or the client says yes), send the kickoff email with the deposit invoice attached. State the next steps clearly: deposit clears → intake form → kickoff call. This converts the client's commitment into specific actions on a specific timeline. Most clients pay the deposit within 24 hours of receiving a clear, confident kickoff email; deposit lag past 48 hours is usually a sign the kickoff email lacked clarity.

Once the deposit clears, send a structured intake form rather than asking for materials in unstructured emails. The form pre-asks the questions you need answered: brand assets, target audience, examples of work they like, technical access requirements, success criteria. This is more respectful of the client's time (they answer once, in one place) and more useful for you (you have all the context you need before the kickoff call). For most engagements, a form with 8-15 questions is the right depth.

Once the intake form is back, confirm the kickoff call and send a short note acknowledging what they sent. 'Got the intake form — looking forward to digging into [specific thing they mentioned] on our call. I've blocked an hour to review your materials beforehand.' This signals you're treating their time and inputs seriously, and it gives them confidence the call will be useful, not 'so tell me about your business.'

Plan the call as: 5 minutes context, 25 minutes deep dive on the specific deliverables and concerns surfaced in intake, 10 minutes timeline and milestones, 5 minutes wrap and questions. End the call with explicit next steps and the date of the next deliverable. The kickoff call should feel like work, not introductions — by this point, both sides should already know each other's basics from the proposal and intake. Use the call to align on substance, not exchange pleasantries.

Within 24 hours of the kickoff call, send a written project plan: deliverables, milestones, dates, what's expected from the client at each milestone. This is not a long document — half a page is enough. The format that works: 'Phase 1 (Week 1-2): [deliverable]. Client reviews and provides feedback by [date]. Phase 2 (Week 3-4): [deliverable]. Client approves by [date]. Project completes [final date].' Putting this in writing prevents the 'I thought we said next week' confusion that derails projects in week three.

Give the client a single place where they can find everything related to the project: the contract, the project plan, deliverables, invoices, and any shared files. A client portal (built into your tools, or a shared folder if you don't have a portal) reduces the number of 'where's that thing you sent me?' emails by an order of magnitude. The first time a client looks for something and finds it themselves, they trust your operations measurably more.

Three traps. First, going silent — clients who don't hear from you in week one start to worry. Send a brief weekly status update even if there's nothing to report yet. Second, over-promising on timeline — pad your initial estimates 20-30% in case of unknowns; meeting your stated dates is more valuable than ambitious dates that slip. Third, accepting scope additions before kickoff is done — if a client surfaces a new request in week one ('oh, can we also add X?'), defer it: 'Let's discuss that as a separate scope question after we've kicked off — happy to write it up as a change order.'