"We need a website. Something modern. Maybe 5 pages? Budget is flexible. Can you start Monday?"
If you've freelanced for more than a week, you've received this exact message. The client isn't being difficult, they genuinely don't know what they need. They know they have a problem (no website), but they can't articulate the solution.
Your job isn't to build what they described. Your job is to figure out what they actually need, before any number leaves your mouth. Here's the framework, plus three ready-to-send reply scripts matched to how vague the request actually is.
Why Clients Are Vague (It's Not Their Fault)
Most clients aren't designers, developers, or project managers. They don't think in wireframes, user stories, or sprint cycles. They think in feelings:
- "I want it to feel premium"
- "Something like Apple but for our industry"
- "Clean and modern, you know?"
These aren't requirements. They're vibes. And vibes don't ship.
The gap between what a client says and what they mean is where most project failures happen. Underquoting lives in that gap too: every unknown you didn't surface becomes unpaid work after you've committed to a price. Your job is to close the gap before any work, or any quote, begins.
The 5-Question Framework
When you receive a vague request, don't reply with a quote. Reply with questions. Here are the 5 that matter most:
1. "What's the business goal?"
Not "what pages do you want", what RESULT do you need?
- "We need more leads from our website" → lead generation focus
- "Customers can't find our products easily" → navigation/search problem
- "We look outdated compared to competitors" → redesign/branding
The answer to this question determines everything else.
2. "Who is your target audience?"
A website for enterprise B2B buyers looks completely different from one targeting Gen Z consumers. You need to know:
- Age range and demographics
- Technical sophistication
- What device they primarily use
- What problem they're trying to solve
3. "What does success look like in 3 months?"
This forces the client to think about measurable outcomes:
- "50% more contact form submissions"
- "Customers can find products in under 2 clicks"
- "We rank on the first page for 'dog grooming Austin'"
Now you have KPIs to design against.
4. "What do you NOT want?"
This question is gold. Clients often know exactly what they don't like:
- "Not like our competitor's site, too cluttered"
- "No pop-ups, I hate pop-ups"
- "Don't want a blog, we won't maintain it"
Anti-requirements narrow scope faster than requirements, and they feed directly into the Out of Scope section of your project brief.
5. "What's your real budget and deadline?"
"Budget is flexible" means "I have a number in my head but I'm not telling you." Press gently:
"To give you an accurate proposal, I need a budget range. Are we talking $1,000-$3,000, $3,000-$10,000, or $10,000+?"
Ranges feel safer for clients than exact numbers.
Three Reply Scripts, by Vagueness Level
Level 1: Vibes only ("We want something cool and modern")
There's nothing to extract yet. Don't pretend otherwise.
Hi [name], thanks for reaching out, I'd love to help. Before I can talk scope or price I need a picture of the business side. Three quick ones: (1) What should this project achieve for you, in plain terms? (2) Who's the main audience? (3) So I propose something realistic: is the budget closer to $1,000-$3,000, $3,000-$10,000, or above? Answer those and I'll come back with a concrete direction and next steps.
Why it works: three questions, not fifteen. A vague client faced with a long questionnaire disappears. Faced with three, they answer.
Level 2: Partial info ("5-page site for our clinic, need it in 6 weeks")
There's real substance, but the money-critical slots are still empty. Acknowledge what you have, ask only for what's missing.
Hi [name], this is a solid starting point: a 5-page site with booking, live in 6 weeks, is very doable. To scope it properly I'm missing four things: (1) Who's writing the page copy, you or me? (2) Any existing brand assets, or does design start from zero? (3) Which booking system do you use today, if any? (4) What budget range should I design the proposal around? Once I have these I'll send a full brief for your sign-off before we talk contracts.
Why it works: it never re-asks what they already told you. Clients notice when you read carefully, and it builds the trust that makes the budget question answerable.
Level 3: Detailed but contradictory ("Simple landing page, with a members area, CRM sync, and payments. Small budget.")
The dangerous kind. Everything sounds specified, but the pieces don't fit: "simple" and "members area + CRM + payments" cannot both be true. Name the contradiction, kindly.
Hi [name], thanks for the detail, this helps a lot. One thing I want to flag before quoting: the feature list (member accounts, CRM sync, payments) is a full web application, not a simple landing page, and those are very different budgets. Two honest options: (A) start with the landing page now and phase the app features in later, or (B) scope the full application properly, which starts around $[X]. Which direction fits your situation better?
Why it works: you surfaced the contradiction before it became your problem at the original price. Whichever option they pick, the scope and the money now match.
The Vague Budget Problem, Specifically
Budget vagueness deserves its own treatment because it's the one that costs you directly. Four patterns and what they usually mean:
| What they say | What it usually means | Your move | |---|---|---| | "Budget is flexible" | There is a number, you have to surface it | Offer three ranges | | "What would something like this cost?" | Genuinely no idea, fishing for education | Give a wide honest range with what moves it | | "We don't have much, but there's more work later" | Discount request with unenforceable promise | Price this project on its own merits | | Silence on the topic entirely | Hoping you'll be cheap | Don't quote until it's answered |
The range technique works because it converts a scary open question into a multiple-choice one. And if their range is a third of what the described scope costs, you found that out in email two, not in week three. That's the underquote you didn't take; if you want to check your history on this, run the underquoting audit.
When Vagueness Is a Red Flag (and When It's Normal)
Normal: fuzzy language, missing technical details, unclear on their own requirements, "not sure what's possible."
Red flags are behavioral, not verbal:
- Refuses to answer discovery questions ("just give me a price")
- Pressure to start immediately, before scope is written
- "We'll figure out the details as we go"
- Won't name a decision-maker
- Reacts to the budget range question with offense
One of these, proceed carefully. Two or more, walk. The full catalogue with response scripts lives in red flags in client briefs.
What if they refuse to answer at all?
One polite retry, then a boundary:
Totally understand you're busy. To be straight with you: without these answers any price I give would be a guess, and guessed prices are how projects go wrong for both sides. Happy to jump on a 20-minute call instead if that's easier than writing.
If neither the questions nor the call happens, decline. A client who won't invest 20 minutes in defining their project will not invest patience when invoices arrive.
From Vague to Actionable: A Real Example
Client's original message: "Hey, we need a website for our new coffee shop. Something cool and modern. We're opening in 6 weeks. What would that cost?"
After asking the 5 questions:
| Question | Answer | |----------|--------| | Business goal | Drive foot traffic + enable online ordering | | Target audience | Local residents, 25-45, mobile-first | | Success in 3 months | 100 online orders/week | | Don't want | No blog, no loyalty program yet | | Budget | $3,000-$5,000 |
Now you can write a brief:
- 4-page responsive site (Home, Menu, Order Online, Contact)
- Mobile-first design for local foot traffic
- Online ordering integration (Square/Toast)
- Google Maps + hours prominently displayed
- SEO for "coffee shop [neighborhood]"
- Timeline: 4 weeks (1 week buffer before opening)
- Budget: $4,200
That's a project. That's a brief. That's scope protection.
The Key Takeaway
Vague requests aren't red flags. They're opportunities to demonstrate professionalism. The freelancer who responds with "here's what I need to know before I can help you" will always win over the one who responds with "sure, I can do that for $2,000."
Ask better questions. Get better projects.
Try the free tool
This article walks through the problem; the free tool turns the answer into a copy-pasteable output in 30 seconds. No account, no signup. Paste the vague message and see exactly which requirements are missing before you reply.
→ Use the Client Brief Checker
Want this across every project?
Briefance saves every brief, scope check, change order, and revision counter against the client and project. Free plan: 3 briefs/month.