Introduction
A discovery call is not a sales presentation disguised as a conversation.
Its purpose is to understand the client's problem well enough to decide whether and how you should solve it.
A strong discovery process produces a clearer scope, better proposal and fewer surprises later.
You do not need to ask every question in every call; follow the project.
Start With the Business
Ask what the company does, who it serves and what has changed recently.
Understand how the website fits into sales or operations.
This creates context before you discuss pages and colors.
A website is usually supporting a broader business process.
Ask Why the Project Exists Now
Find the trigger.
Maybe the existing site is outdated, a new service is launching or marketing is being expanded.
Urgency and motivation affect scope and timeline.
This question often reveals the real priority.
Understand the Audience
Ask who the primary visitors are and what they need from the site.
Different audiences may require different paths.
B2B buyers, consumers and job applicants do not evaluate a company in the same way.
Prioritize the audience tied to the project goal.
Review the Existing Site
If a site exists, ask what should be kept and what should change.
Discuss current traffic, SEO, content and integrations.
Do not assume a full rebuild is necessary.
Sometimes the right project is targeted improvement.
Discuss Content
Ask whether copy, images, products and brand assets are ready.
Identify who approves and supplies content.
Content gaps can alter both cost and timeline.
Clarify whether migration from the old site is required.
Discuss Functionality
Ask what users must be able to do.
Examples include purchase, book, log in, upload files, search, compare or submit complex forms.
Explore the workflow, not only the feature name.
This helps distinguish a plugin requirement from custom application work.
Ask About Integrations
Identify CRM, email, payments, inventory, analytics and other systems.
Ask whether accounts already exist.
Integrations can add hidden complexity.
Include them in the project scope early.
Clarify Timeline and Budget
Discuss realistic budget and deadline constraints.
Explain which requirements have the largest cost impact.
If budget and expectations do not align, explore scope options rather than pretending everything fits.
Honest constraints produce better projects.
Define Success
Ask how the client will judge whether the project worked.
Success could mean more qualified leads, easier editing, faster performance or better ecommerce operations.
A clear success definition guides decisions later.
Not every project needs a numerical conversion target.
Frequently Asked Questions
How long should a discovery call be? — Long enough to understand the project; many focused calls can be completed in 30–60 minutes.
Should I give a price during the call? — Only when the scope is standardized. Custom projects usually benefit from a written proposal afterward.
Should clients prepare anything? — Existing website access, brand materials, examples and a rough feature list can help.
Is discovery billable? — Basic sales discovery is often free, while deeper workshops or technical discovery may be paid.