How to Set Client Expectations on Day One
Your first conversation with a new client determines whether they'll be a dream or a nightmare to work with. The clarity you establish in those first hours shapes everything that follows - how responsive they'll be, how many change requests you'll field, and whether they'll hire you again.
The mistake most agencies make is jumping straight into work. Instead, invest one focused conversation into alignment before anything else.
The Four-Part First Meeting
Part 1: Scope Definition
Before you do anything, make sure you're solving the same problem they think they hired you to solve. Walk through their current state, desired state, and what success looks like in their words. Ask: "What does winning look like 30 days from now?"
Document everything they say. Not to be legal, but to catch misalignment early.
When you say back to them, "So you need X, Y, and Z before we launch," they'll either nod or correct you. That's the whole point.
Create a written scope document - even if it's just a bulleted email. "We'll deliver: homepage redesign, product pages, cart. We won't do: copywriting, SEO, ongoing support." Be as specific about what you're not doing as what you are.
Part 2: Timeline and Checkpoints
Tell them your start date, milestones, and launch date. Then add one critical layer: decision deadlines. "You'll need to approve homepage mockups by September 15 so we can refine by September 22." Clients who know the decision timeline tend to make decisions faster.
Frame waiting time as their cost, not yours. "If you take three weeks to get stakeholder approval, that pushes launch by three weeks" sounds obvious, but most clients don't think about it that way.
Part 3: Communication Protocol
This is where you prevent the 10 PM text messages. Tell them how they reach you, how fast you respond, and what's in scope for communication.
Say something like: "I'll respond to emails within 24 hours on weekdays. For urgent issues, text me.
We'll have weekly check-ins every Tuesday at 2 PM. Between those, status is in your project dashboard."
Set the expectation now that you're not available evenings and weekends. If you answer Slack at midnight once, they'll expect it every time.
Part 4: Deliverables and Format
Run through exactly what they're getting and in what format. "You'll get Figma prototypes, design assets as PNG and SVG, a CSS component library, and onboarding documentation." This prevents the surprise where they expected source files and you gave them a PDF.
Ask what tools they use to stay organized - Asana, Linear, ClickUp - and use that. When you work in their system instead of asking them to check yours, approval cycles shorten dramatically.
What to Put in Writing Immediately After
Send a recap email or brief document that lists:
- What you're building (with specifics)
- What you're not building
- Key dates and decision windows
- Who the decision maker is for approvals
- Weekly check-in schedule and format
- How to submit feedback and changes
- Communication response times
This becomes your reference document. When scope creep happens in week four, you point back: "That wasn't in our original scope here, but let's talk about adding it as phase two."
Red Flags to Address Now
If they can't articulate what success looks like, push back. "I want to make sure we get this right. Can you give me three specific things you want different after we launch?" If they struggle, they might be unclear on their own needs.
If the decision maker isn't in the room, pause and address it. "I want to make sure Sarah from marketing is aligned too, since she'll be using this daily. Can we do a quick call with her before we start?"
If they mention a budget but it's lower than you'd normally charge, say it now. "That budget suggests a simpler scope than what you described. Should we scale back, or do we need to revisit the number?" Not later.
The Result You're Aiming For
When you nail this first conversation, what changes:
- They approve work faster because they know the process
- Fewer scope creep requests because you clarified what's in
- Fewer communication friction points because you set the rhythm
- They don't ghost you because they know when to expect updates
- They refer you because they felt heard and managed well
The entire relationship compounds from this single conversation. Spend 90 minutes getting it right instead of 90 hours dealing with misalignment later.
FAQ
Q: Should I send a contract before this meeting or after?
Send it after the alignment call. You need to know what you're actually building before you lock down scope and timeline in legal language. Use the call to clarify what goes in the contract.
Q: What if the client says no to some of my boundaries?
That's valuable information. If they won't accept 24-hour response times, they're a high-touch client. You can adjust your pricing or decline them now before you're frustrated six weeks in.
Q: How detailed should the written scope be?
Detailed enough that someone unfamiliar with the project could read it and understand what you're building. Three to five pages is usually right.
Less than one page feels hand-wavy. More than ten pages creates scope creep risk because clients read different sections differently.
Q: How do I handle clients who want to "figure it out as we go"?
Warmly decline or adjust your pricing significantly up. Undefined scope is how projects end up 40% over timeline and budget.
Make that risk visible to them: "Without clear scope, this could take 8 weeks or 16 weeks depending on what we discover. I'd need to charge a retainer instead."