Every new client has a subtext. The concern they didn’t raise in the proposal call because it seemed minor. The bad experience with a previous freelancer that made them hesitant to hire again. The internal politics that make success harder than the project brief suggests. The boss whose expectations are materially different from theirs.
If that subtext stays hidden, it becomes a problem in weeks 3-6, when the client is frustrated by something that didn’t need to be frustrating, or disappointed by an outcome that would have been perfectly preventable if you’d known the real expectation.
The five-question onboarding survey is the tool that pulls the subtext to the surface. It’s sent on Day 3, takes 10 minutes to complete, and gives you a map of everything the client is thinking but hasn’t said. What you do with that map determines whether this project goes well or goes sideways.
Question 1: “What worries you most about this project?”
This is the permission question. It tells the client it’s safe to say something negative, and most of them have been waiting for that permission since the proposal stage.
What you’ll hear:
- “I’m worried the timeline is too aggressive.”
- “I’ve had freelancers start strong and then go quiet, that’s my biggest fear.”
- “I’m worried we don’t have everything internally organized enough to give you what you need.”
- “I’m concerned my team is going to keep changing the direction and you’ll get frustrated.”
Every one of those answers is a gift. Each worry tells you exactly where to invest in reassurance and process.
Your response protocol: For every worry expressed, send a direct acknowledgment within 24 hours:
“You mentioned your biggest worry is [X]. Here’s how I address that: [specific process, guarantee, or commitment that directly addresses the concern]. If at any point during the project you feel like [X] is becoming a problem, tell me immediately, I’d rather hear about it early.”
You don’t need to solve the worry on the spot. Acknowledging it specifically, showing that you’ve heard it, and naming your approach to it usually does 80% of the work.
Question 2: “What would make this a 10/10 engagement for you?”
This question surfaces the gap between the stated deliverables and the actual expectations. The contract says “brand identity system.” But a 10/10 for the client might mean something much more specific:
- “We get a final presentation I can use to pitch the new brand internally.”
- “The process doesn’t require me to attend a lot of meetings.”
- “The work gets done before our conference in September.”
- “You explain your decisions so I understand why the design choices were made.”
None of those may be in the contract. All of them are adjustable if you know about them in week 1.
The 10/10 question also surfaces aspirational expectations, the thing the client secretly hopes for but hasn’t voiced because it seems like too much to ask. When you know what it is, you have three options: (a) it’s already in scope and you can confirm that, which delights them; (b) it’s out of scope but easy to add, and adding it creates genuine goodwill; or (c) it’s out of scope and unrealistic, in which case you address the gap now instead of at delivery.
Question 3: “What’s gone wrong in similar projects in the past?”
This is the diagnostic question. Every client who’s hired a freelancer or agency before has a war story. A project that overran. A deliverable that missed the mark. A communication breakdown that made the relationship frustrating. A contractor who promised one thing and delivered another.
The patterns in their answer tell you where to focus your process:
- “The last agency we hired didn’t communicate proactively, we had no idea what they were working on.” → Invest in your check-in cadence. Send status updates before they ask.
- “The project went 3 months over schedule.” → Commit to explicit timeline tracking and early delay warnings.
- “We got deliverables that were technically correct but completely missed the tone.” → Invest in the Day 7 alignment session before executing at scale.
- “The freelancer was great creatively but terrible at managing feedback, things got lost.” → Clarify your revision process explicitly.
Each answer is a signal about where the client’s threshold for frustration lies. Their previous bad experience is the thing most likely to trigger a negative reaction in this engagement, even if you’re doing nothing wrong.
Question 4: “What does success look like to your boss (or other stakeholders)?”
The person who hired you is rarely the only person who will evaluate the work. The boss, the board, the marketing committee, the investor, they have expectations that may be entirely different from the person who’s managing the day-to-day project.
This question surfaces that gap before it becomes a crisis.
Common answers:
- “My boss wants to see the rebrand finished before our funding round in Q3.”
- “The CEO mainly cares about whether the new website moves the needle on leads.”
- “The committee will evaluate this on whether it matches our competitor’s quality.”
- “My boss thinks I’m spending too much on this, I need to prove it was worth it.”
The last one is particularly important. If the client needs to justify the spend internally, your deliverables need to produce evidence that supports that justification. That may mean a case study, a metrics summary, a before/after comparison, or just an explicit report at the end of the project. If you know about this need in week 1, you can build it into your process. If you find out at the final presentation, it’s too late.
The person who hired you will often defend you internally if things get difficult, but only if you’ve built enough trust and delivered enough visible value for them to stake their reputation on it. Question 4 tells you what they need to be able to say to their boss when the project is done. That’s the case you need to make with your work.
Question 5: “Is there anything I should know that you haven’t told me?”
This is the catch-all, and it often produces the most important answers of all five.
What surfaces in this question:
- Internal political context: “There’s a team member who’s been resistant to this project from the start.”
- Budget pressure you didn’t know about: “We had a difficult quarter and there may be pressure to cut this project early.”
- A hidden dependency: “The timeline depends on our CTO being available and she’s going on leave next month.”
- An opportunity you didn’t know about: “If this goes well, there’s a phase 2 we’ve been planning that’s 3x bigger.”
- A specific sensitivity: “Our founder is very protective of the original brand, run anything significant by me before presenting it to her.”
This question gives the client permission to tell you something they’ve been sitting on. Not every client will answer it. But the ones who do will tell you something that changes how you approach the project.
Building and Sending the Survey
Format: A Google Form with 5 open-ended short-answer fields. Title: “[Project Name], Quick Check-In Survey.” Add an introductory note:
“These 5 questions take about 10 minutes and help me serve you better from day one. There are no wrong answers, honest responses (including concerns or frustrations) are the most useful. I’ll address everything you share within 24 hours.”
That framing, “there are no wrong answers”, is the key to getting real responses. Without it, most clients give you the answers they think you want.
Send on Day 3: Include the survey link in the Day 3 kickoff recap email:
“One quick addition to today’s recap, I’d love for you to take 10 minutes on this short survey before our next meeting: [link]. It helps me understand your expectations and anything you want to flag early. I’ll respond to your answers personally within 24 hours.”
Response time: 24 hours. Not a mass response, a personal email to the client that addresses each of their answers specifically.
The Response Protocol
For each answer, your reply should be 1-3 sentences:
- Acknowledge what they said
- State how you’re addressing it
- Invite further conversation if they want it
Example for a “previous bad experience” answer:
“You mentioned that a previous freelancer went quiet halfway through a project. My approach: I send a brief status update every Monday morning, even if there’s nothing urgent to report. If I’m going to be unavailable for more than a day, you’ll hear about it before the gap happens, not after. If the cadence I’ve proposed ever feels insufficient, tell me and I’ll increase the frequency.”
Example for a “boss expectations” answer:
“You mentioned your CEO is primarily focused on lead generation results. I’ll structure the final deliverable report to include [specific metrics] and build in a ‘what happened after’ framework so you can follow up with data in 90 days. Let me know if there are specific metrics she’ll want to see, I want to make sure you have what you need to tell that story.”
The survey takes 30 minutes of your time (10 to build the form, 10 for the client to complete it, 20 to write your response). That 30 minutes regularly converts early-engagement anxiety into confidence, and occasional disaster into an avoidable misalignment.
Send it on Day 3. Every client, every project. No exceptions.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
