Client Discovery Questionnaire Template

The discovery phase sets the foundation for everything that follows. A thorough discovery process prevents misaligned expectations, scope creep, and failed projects. A weak discovery process is why many projects struggle.

This questionnaire covers the essential areas you need to understand before you start any significant project. Customize it based on your service type.

Business and Goals

Start with understanding the client's business and what they're trying to achieve.

What does your company do?
What's your target customer?
What's the biggest challenge your business faces right now?
What are you hoping to achieve with this project?
How will we measure success? What metrics matter?
What's the business impact if this project succeeds?
What's the business impact if it fails?
What does success look like six months after launch?

Current State

Understanding where they are now helps you understand what needs to change.

What's your current solution or process?
What's working well about the current approach?
What's not working?
How many people use the current solution?
What's the adoption or usage rate?
Have you tried solving this problem before? What happened?

Project Scope

Get clear on what you're actually building or solving.

What specifically are we building/solving?
What's included in this project and what's not?
Are there any parts of the project that depend on external teams or factors?
Are there hard constraints (budget, timeline, technical) we need to know?
What's the primary use case you want to solve?
Are there secondary use cases?
Who are the primary users?

Timeline and Budget

You need to know when and what they can spend.

When do you need this completed?
Is that deadline flexible?
What happens if we're not done by that date?
What's your budget for this project?
Is that budget flexible?
Are there phases we could do sequentially to spread budget?

Stakeholders

Understand who's involved in the project and has influence.

Who's the primary contact for this project?
Who else needs to approve decisions? (Budget holder, executive sponsor, etc.)
Who will be the users of the final product?
Are there any stakeholders who might resist this change?
Who do we need to keep informed?
What's the escalation path if there's a problem?

Technical and Constraints

For technical projects, understand the environment and limitations.

What's your current tech stack?
Are there systems this needs to integrate with?
What are the technical constraints or must-haves?
Who's your IT/technical person we need to coordinate with?
What's your security and compliance requirements?
Are there any accessibility requirements?

Competition and Reference

Understanding what they see in the market helps you understand their expectations.

Is there a competitor doing something similar you like?
Are there any examples or references you can show us?
What do you like about those examples?
What would you do differently?

Communication and Logistics

Understand how the project will actually operate.

How often do you want to check in?
What format works best for updates? (Weekly calls, Slack updates, email)
Who owns communication on your side?
Are there team members or departments we need to coordinate with?
What's the approval process for deliverables?

Success Metrics and Measurement

Define how you'll know this project succeeded.

How will you measure the success of this project?
What would count as a failure?
How long after launch until we can assess whether it worked?
What metrics will you track?
Do you have baseline metrics we should understand?

Anything Else

Always end with open-ended room for them to share what matters.

Is there anything we haven't discussed that's important for us to know?
What are your biggest concerns about this project?
What are you most excited about?
Is there anything that's kept you up at night about this?

How to Use This Questionnaire

Send Before the Call - Give them the questions in advance. It helps them think and come prepared.

Interview Style - Don't just read questions. Have a conversation. Listen more than you talk. Follow threads that matter.

Document Everything - Take notes. Record the call if they agree. You'll reference this later.

Summarize - After discovery, summarize what you learned. Send it to them. "Here's what I understand about your project..." They'll correct misunderstandings while everything's fresh.

Use as Scope Reference - This discovery becomes your scope document. When there's later disagreement about what was included, you reference what was discovered.

Customization by Service Type

Design Projects - Add questions about brand guidelines, aesthetic preferences, and design constraints.

Development Projects - Add technical questions about integrations, third-party services, and technical requirements.

Marketing Projects - Add questions about marketing goals, audience, and existing marketing efforts.

Consulting Projects - Add questions about the current situation more deeply and what outcomes they're hoping for.

FAQ

How long should discovery take? Depends on project complexity. Small projects: one call, 60 minutes. Medium projects: 2-3 calls, few hours total. Complex projects: multiple workshops, weeks.

Should we charge for discovery? For large projects, yes. For small projects, you often include it. If it's a paid discovery project, be transparent about what's included and what happens after.

What if clients don't want to answer all these questions? That's a red flag. They're either not ready or they don't care about getting this right. Either way, you'll have problems later if you don't do discovery.

Who should we interview in discovery? The primary decision-maker, the end user, and the person who'll manage the project on their side. You might need multiple interviews.

Can we do discovery remotely? Yes, absolutely. A call with good notes works as well as in-person. Sometimes better because you're not distracted.

What if they give answers that conflict with each other? Ask clarifying questions. "You said success is more conversions, but you also said we shouldn't add features. How do we balance that?" Resolving conflicts early prevents problems later.