The Vague Request Problem
"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.
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 90% of project failures happen. Your job is to close that gap, before any work 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.
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.
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.
How Briefance Handles This Automatically
The 5-question framework works. But it takes time, writing questions, waiting for answers, synthesizing responses into a brief.
Briefance does this in seconds. Paste the client's vague message, and the AI:
- Extracts every requirement it can find
- Identifies what's missing (budget? timeline? deliverables?)
- Generates smart follow-up questions you can send directly to the client
- Produces a structured brief once answers come back
From vague email to professional brief, without the back-and-forth overhead.
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.