The First Week With a New Client Decides Everything

The client who scope-creeps you in month two was telegraphing it in week one. So was the client who paid late, the one who ignored your contract revisions limit, and the one whose 'quick question' emails turned into three-hour calls. Most freelance problems aren't surprises — they're consequences of a kickoff that didn't establish anything. How you set up the first week determines most of what happens after.

What the first week is actually for

It's not for impressing the client with a fast start. It's for calibrating expectations on both sides. A project kickoff isn't the beginning of work — it's the beginning of a working relationship. The patterns you establish now, intentionally or by default, are the patterns you'll live with for the rest of the engagement. A late reply to the kickoff email isn't just a delay; it's setting a norm about what your communication looks like. A meeting where you don't establish decision-making authority isn't just an oversight; it's opening the door to design-by-committee six weeks from now.

1. Send a kickoff summary within 24 hours. Before any work begins, put the agreed scope, timeline, and payment schedule in a short written summary. One document, no ambiguity. If the client sees the scope differently at this point, you want to know now — not after you've built something.
2. Establish who can approve changes. On any project with more than one stakeholder, find out explicitly who has final say. 'The team will review it' is how you end up with contradictory feedback from five people, none of whom feel responsible for signing off. One name, one decision-maker.
3. Set your communication channel and rhythm. Tell them how you prefer to be reached, when you're responsive, and what urgent means. 'I check email at 9am and 4pm' sounds restrictive. It's actually what a professional working relationship looks like.
4. Request everything you need before starting. Assets, credentials, brand guidelines, copy — front-load the list. Waiting on client materials mid-project stalls work and extends timelines through no fault of yours. Ask once, comprehensively, before the project clock starts.
5. Confirm the first milestone in writing. Not the whole timeline — just the next checkpoint. 'I'll have a first draft to you by Friday. I'd like your consolidated feedback within five business days.' Small written agreements build the habit of mutual accountability.
6. Send the deposit invoice on day one. Not after the kickoff call, not after you've started work — the same day the engagement begins. Waiting to invoice is just waiting to get paid. Starting work before the deposit clears is lending money to a client you've known for a week.

The signal to watch for

If a client responds to the kickoff summary with objections — not questions, but pushback on scope, timeline, or payment terms you both already agreed to in writing — that tells you something. A client who reframes the agreement at kickoff is not going to become easier to work with once the work is underway. You're not one good email away from resetting the relationship. You're at the moment of easiest exit, before any real work has been done.

A good first week doesn't look heroic. It looks organized. You send a clear summary, ask for everything you need, establish how you'll communicate, and collect the deposit. None of it is complicated. It's just uncommon enough that clients who've worked with less structured freelancers will notice — and the clients worth keeping will appreciate it.