Website Discovery Call Checklist
A website discovery call checklist is a structured list of questions and topics to cover before or during a scoping call with a prospective client for a website project. Work through Sections 1–7 on the call. Complete Section 8 within 24 hours. Items marked ★ should be completed before the call.
The checklist
★ items should be completed before the call starts
Before the call — preparation
- ★Research the client's current website — note what's missing, broken, or outdated
- ★Research one or two competitors they may have mentioned in earlier contact
- ★Review any brief or intake form the client submitted before the call
- ★Know your current availability and earliest project start date
- ★Have your discovery deposit amount ready to quote (if you charge for discovery)
- ★Prepare screen share if you'll walk through references or their current site
Section 1 — Goals and success definition
What does the client actually need this website to do?
- What is the primary goal of the new site? (Generate leads / Sell products / Establish credibility / Replace an outdated site / Launch something new)
- How will they measure success? (Enquiries, sales, form completions, traffic — get a number if possible)
- Who is their target audience, and what does that audience do when they land on the site?
- Are there any secondary goals or "nice to haves" that should not drive the primary design?
- What is the single most important thing a visitor should do on the site?
Notes
Section 2 — Current site and context
- What's wrong with the current site (if there is one)?
- What has worked well on the current site — anything to keep or carry forward?
- Has the client tried to fix the current site before? What happened?
- Are there existing brand assets? (Logo, style guide, fonts, colours, photography)
- Are there existing copywriting assets or will copy need to be written or sourced?
Notes
Section 3 — Scope
- How many pages / sections are in scope? (List them if possible)
- Is there a CMS / blog / news section?
- Are there any special functionality requirements?
- E-commerce / product listings
- Booking / appointment scheduling
- Forms (contact, enquiry, application, intake)
- Member / client login area
- Integrations (CRM, email platform, payment gateway, booking tool)
- Other: _______________
- Is there content the client is responsible for providing? (Copy, images, video)
- What is the agreed deadline for content delivery — and what happens if it's late?
- Are there third parties involved? (Developer, copywriter, photographer, SEO consultant)
Notes
Section 4 — Timeline and urgency
- Is there a hard deadline? (Event, product launch, end of lease, etc.)
- What is the preferred launch date?
- Is there flexibility in the timeline if scope expands?
- Are there blackout periods where the client will be unavailable for approvals? (Holidays, events)
- How quickly can the client typically turn around feedback? (Same day / within a week / unknown)
Notes
Section 5 — Budget
- Has the client shared a budget range?
- If not: "Do you have a figure in mind, or a ceiling you're working to?"
- Is the budget for the website build only, or does it need to cover ongoing maintenance and hosting?
- Is the budget all at once or milestone-based? (Deposit / mid-project / final)
- Does the client understand that scope changes after sign-off are billed separately?
Budget indicator: _______________
Approach confirmed with client: Fixed fee / Hourly / TBD
Notes
Section 6 — Technical and hosting
- What platform / CMS is preferred, or is it open?
- Who currently manages the domain and hosting?
- Is the domain renewing soon? (Risk: expired domain mid-project)
- Will hosting be managed by the studio or transferred to the client on completion?
- Are there email accounts hosted on the domain that could be disrupted during a migration?
- Is there an existing email marketing platform that needs to integrate with the site?
- Any SEO or analytics accounts already in use? (Google Analytics, Search Console, etc.)
Notes
Section 7 — Decision and next steps
- Who is the decision-maker for this project? Is anyone else involved in sign-off?
- What does the client need from you to make a decision? (Quote, proposal, samples, reference call)
- Is the client talking to other studios?
- What would make them choose you?
- What would make them not proceed?
- What is the timeline for their decision?
Notes
Section 8 — Post-call follow-up (complete within 24 hours)
- Send a call summary email within 24 hours — confirm goals, scope discussed, and agreed next step
- Send a follow-up questionnaire (Ascend Form) for any items that need more detail
- Add the project to your client project database with status "Discovery"
- If proceeding: issue the discovery deposit invoice before starting detailed scoping
- If not a fit: send a brief, respectful decline with a referral if possible
Discovery call summary record (for your files)
| Field | Value |
|---|---|
| Client / prospect name | — |
| Call date | — |
| Conducted by | — |
| Primary goal | — |
| Estimated scope | — |
| Budget indicator | — |
| Preferred launch date | — |
| Hard deadline? | — |
| Decision-maker confirmed | — |
| Competitor sites mentioned | — |
| Platform / CMS preference | — |
| Agreed next step | — |
| Follow-up due date | — |
| Outcome | Proceeding / Follow-up required / Not a fit |
How to use this checklist
Work through Sections 1–7 on the call. Complete Section 8 within 24 hours. Build a companion Ascend Form for the detailed follow-up questionnaire, and book the discovery call itself through an Ascend booking page so the client self-schedules.
The call that sets up the whole project
Every problem that surfaces mid-project — scope disagreement, timeline slip, budget dispute, technical surprise — can usually be traced back to something that wasn't asked at discovery. A website discovery call checklist isn't a sales script. It's a structured conversation that surfaces the information you need to deliver the project without unexpected friction.
The call has two outputs: a decision (proceed or not) and a brief (the notes that become the scope). Both are cleaner when the call is structured.
What to ask about budget without making it awkward
The budget question is where many discovery calls stall. A direct approach works better than circling around it: "Do you have a figure in mind, or a ceiling you're working to?" If they've shared a brief, the budget question is expected. If they haven't, framing it as a ceiling — not a minimum — tends to get a real answer.
The more useful follow-up is distinguishing between build budget and total budget. A client who has $8,000 "for the website" may not have mentally accounted for ongoing hosting, maintenance, or a separate content writer. Understanding that early prevents the conversation about extras at invoice time.
The technical questions that save the project
The hosting and domain section of this website discovery call checklist is underrated. Two issues surface here repeatedly. The first: the domain is registered somewhere the client doesn't have access to (an old agency, a previous employee, a registrar under an email address they no longer use). Finding this out on the call means you can plan for it. Finding out two weeks before launch means the launch slips.
The second: email accounts are hosted on the domain and will break during a DNS migration if not handled carefully. One question — "are there email accounts on this domain?" — prevents a frantic call from the client on migration day.
Setting up for the deposit conversation
A website discovery call that ends with "I'll send you a quote" puts the deposit conversation a week away. A call that ends with "I'll send the discovery deposit invoice as the next step" is different — the project has a concrete next action and the deposit frames the project as a real engagement, not a speculative quote.
The checklist includes a discovery deposit item in the pre-call preparation section. Having the number ready means you can name it on the call rather than calculating it later.
After the call, the website project handoff checklist closes the cycle that discovery opens.
The questions about decision-making that studios skip
"Who else is involved in sign-off?" is one of the most skipped questions on a website discovery call. The reason it matters: if there's a stakeholder not on the call — a partner, a board member, a parent company — their feedback can arrive at the design stage and require revisiting decisions already approved. Knowing the full decision-making structure at discovery gives you the option to include the right people in the scoping sign-off, not just the first-call contact.
Related templates
Frequently asked questions
What should a website discovery call checklist cover?+
A website discovery call checklist should cover: client goals and success metrics, current site and brand assets, scope (pages, functionality, integrations), timeline and hard deadlines, budget, technical and hosting requirements, and the decision-making process and next steps. The call should end with a clear agreed action.
How long should a website discovery call be?+
Most discovery calls for a small-to-medium website project run 45–60 minutes. Longer calls are appropriate for complex builds with multiple stakeholders or technical requirements. Shorter than 30 minutes usually means scope or budget was not fully explored.
Should I charge for website discovery?+
Many studios charge a discovery deposit that covers the detailed scoping session — either applied to the project if it proceeds or kept if the client doesn't. Whether you charge for the initial discovery call itself varies. If your calls routinely run over 45 minutes and produce a detailed brief, charging is reasonable.
What questions should I ask about the client's budget?+
"Do you have a figure in mind, or a ceiling you're working to?" is a direct way to open the conversation. Follow up by distinguishing build budget from total budget — does it include ongoing maintenance, hosting, content, or photography?
What do I do if the client doesn't know what they want?+
Ask about goals first, not deliverables. "What do you need the site to do?" is a more productive question than "how many pages do you want?" Goals are concrete — and from goals, deliverables follow.
How does a discovery call connect to booking and onboarding?+
The discovery call is typically booked through a scheduling tool. After the call, a follow-up questionnaire collects detailed information. If the project proceeds, the discovery deposit invoice is issued and client onboarding starts. Ascend handles the booking, the form, and the invoice.
What should I send the client after a discovery call?+
Within 24 hours: a call summary email confirming goals, scope discussed, and the agreed next step. If a detailed brief is needed, send a follow-up questionnaire rather than relying on the client to write a brief from scratch. If proceeding, issue the discovery deposit invoice promptly.
Related checklist
Website Project Handoff Checklist
The checklist that closes the cycle — credentials, CMS training, post-launch scope, and final invoice before the project is marked complete.
Book the call, collect the brief, issue the deposit.
The discovery call is step one. Steps two and three — collecting the detailed brief and issuing the deposit invoice — are often where momentum drops. Ascend handles booking, forms, and invoicing. A client can book the discovery call, receive and complete the follow-up questionnaire, and receive the deposit invoice without leaving a single workflow. The free tier covers one client end to end.
Start with Ascend free