A discovery call goes sideways when the first twenty minutes are spent learning things a form could have asked: what the client is trying to change, what they already run, and who signs off. A project discovery form collects those facts before the call, so the call can be spent on the parts that need a conversation.
This post gives you a client discovery template you can copy, grouped by what each answer is for. It also covers which questions to leave optional, and a routing table that turns a submission into one of three next steps (book the call, send a short follow-up, or say it's not a fit) and sends it to the place your team already works.
It sits between two earlier guides. The web design client questionnaire covers the short inquiry and the full brief for website projects, and the agency lead qualification scorecard covers scoring. Here the job is narrower: make the discovery call useful, whatever service your agency sells.
Decide what the form is for
A discovery form earns its place if, after reading one submission, someone on your team can answer three questions:
- Should we talk, and what is the next step?
- What do we need to prepare or ask on the call?
- Who owns this inquiry now, and where is it recorded?
Every question below serves one of those. If a question doesn't change the next step or the call agenda, cut it. A longer form is fine when each question is plainly about the client's project; it's the generic ones that make people stop.
Copy the questions, grouped by purpose
The groups are for your team. On the form, the client sees plain questions in this order, ideally one group per screen. Required questions are marked; everything else can be skipped.
Goal and success measure
- What should this project change for your business? (required) Ask for the outcome, not the deliverable. "More booked demos from the site" tells you more than "a new homepage."
- How will you know it worked? Offer a few choices (more leads, faster sales cycle, fewer support requests, a launch that happens on time, something else) plus a short text box.
- What happens if you do nothing this quarter? This one separates a real problem from a nice-to-have, and the answer is often the best opening line for the call.
Scope
- Which of these do you need help with? (required) List your actual services as checkboxes, plus "Not sure yet."
- What is already done, and what is missing? For example: brand is done, copy is missing; the app exists, the onboarding flow doesn't.
- Is this a one-off project or ongoing work?
Budget range
- Which range fits what you have in mind? (required) Use your own ranges, start the lowest one at your real minimum, and include "Not sure yet" and "Prefer to discuss." Put a one-line note above the question saying what a typical engagement costs, if you're willing to publish that.
Ranges with a "Not sure yet" option are easier to answer than an open budget box, and the answer is easier to route. A blank free-text budget field tells you nothing; "Not sure yet" tells you the client needs a reference point, which is a follow-up you can send.
Timeline
- When would you like to start? Choices such as "this month," "next month," "this quarter," "later," and "no fixed date."
- Is there a fixed date this is tied to? A launch, an event, a funding round, the end of a contract. Ask what it is, not only whether it exists.
Decision process
- Who else is involved in choosing an agency? (required) Choices such as "just me," "me and a partner or manager," "a committee," "procurement is involved."
- Are you talking to other agencies or considering building it in-house? Optional, and worded neutrally. You're not screening them out; you're preparing for a comparison.
Existing stack
- Which tools does this need to work with? Checkboxes for the tools you see most (your common CMS, CRM, analytics, email, scheduling, payments) plus "Other."
- Who owns the accounts for those tools? This decides whether week one is spent building or waiting for access. Ask who, never for the login itself.
- Current website or product link. Optional; not every client has one ready.
Constraints
- Is there anything we should know before we suggest an approach? Brand rules, legal review, accessibility requirements, a platform you're locked into, an internal team that must approve technical choices.
- How do you prefer to work? Async updates, a weekly call, a shared Slack channel.
End the form with contact details (name, work email, company) and a confirmation screen that says what happens next and who will reply. Don't promise a response time unless someone owns it.
Leave these optional
Making the wrong question required costs you good inquiries. These are the ones to leave optional and what to do when they come back blank:
| Question | Why optional | If it's blank |
|---|---|---|
| What happens if you do nothing | Some clients haven't thought it through yet | Ask it on the call; it's a good opener |
| One-off or ongoing | Often decided after the proposal | Assume one-off and mention retainers later |
| Other agencies or in-house | Can feel intrusive on a first contact | Don't infer anything from silence |
| Account owners | The person filling the form may not know | Make it the first item on the call agenda |
| Website or product link | Early-stage clients may not have one | Ask for a deck or a competitor they admire |
| Constraints | People forget until something blocks them | Ask once more in the call recap |
| Working style | Low stakes before a proposal | Default to your usual cadence |
Keep the required set small: the goal, the services, the budget range, the decision process, and contact details. Everything else improves the call but shouldn't block the submission.
Route each submission
Routing means deciding the next step from the answers and putting the submission where the right person will see it. Start with three outcomes and one rule each. The table is an example for a small agency; replace the triggers with your own offer.
| Answers say | Next step | Where it lands |
|---|---|---|
| Service you sell, budget at or above your minimum, decision-maker involved | Book the call; send your scheduling link in the reply | Team channel for a fast reply, plus the CRM as a new deal |
| Service you sell, but budget is "Not sure yet" or timeline unclear | Send one short follow-up question before booking | Team channel, tagged for the owner of follow-ups |
| Budget below your minimum, or a service you don't offer | A polite no, with a referral or a smaller offer if you have one | Shared sheet only, so the record exists without pinging anyone |
| Fixed date you can't meet | Ask whether the date can move before saying no | Team channel, flagged for whoever plans capacity |
| Anything you can't classify | A person reads it today | Team channel |
Every submission should also land in one shared record, whatever its route. A Google Sheet works at small volume: one row per inquiry, with the answers, the route, the owner, and the status. Move to a CRM when follow-ups and handoffs start slipping through the sheet.
The follow-up for the middle row should be one question, the one that decides the route. For an unclear budget, that might be: "Thanks for the detail on the redesign. So we can suggest the right scope, does a starting range of [your minimum] work, or would a smaller first phase be better?"
Three fictional submissions, routed
These are made-up examples to show the table in use.
A. A clear yes. A two-founder software company wants a marketing site rebuilt before a launch they've dated. They pick two of your services, choose the range at your minimum, say both founders decide, and list their CMS and analytics. Route: book the call. The call agenda writes itself from the "what's missing" and "fixed date" answers.
B. Promising but unclear. A regional clinic group wants "help with patient inquiries," picks "Not sure yet" for budget, and says procurement is involved. Route: one follow-up asking about the budget range and the procurement timeline, then decide. Note that procurement usually adds steps, so the start date on the form is probably optimistic.
C. Not a fit today. A solo founder wants a full product build with a budget range below your minimum and a date three weeks out. Route: a polite no, with a smaller first phase if you offer one. The row stays in the sheet in case they come back after funding.
Build it in Dashform
Paste this into the Dashform form generator and edit the bracketed parts:
Create a project discovery form for [agency name], which offers
[your services]. Group the questions into: goal and success measure,
scope, budget range, timeline, decision process, existing stack,
and constraints. Required: the business outcome, services needed,
budget range, who is involved in the decision, name, work email,
company. Everything else optional.
Budget ranges: [your ranges, starting at your minimum], plus
"Not sure yet" and "Prefer to discuss".
Ask who owns the accounts for their tools, never for logins or passwords.
End with: "Thanks. [Name] will read this and reply with the next step."
Save as a draft for review.Review the draft before you publish: check the services list, the ranges, and that no question asks for credentials.
Then connect the destinations from the form's Connect tab. Dashform has native Slack (post a message to a channel), Google Sheets (append a row), and HubSpot (create or update a contact) destinations, and a Webhook destination for any other CRM or an automation tool such as n8n, Make, or Zapier. Each destination can have a routing condition built from the answers, for example "budget range equals Not sure yet" or "services contains Brand strategy," so the Slack message fires only for the rows of your table that need a person, while the sheet takes every submission. Conditions read the answers themselves; they are not driven by an AI lead score.
On the pricing page (checked November 18, 2026), native integrations, which include these destinations, are listed on the Pro and Business plans.
If you send submissions to your own endpoint, read our form webhook checklist before relying on it in production. It covers deduplicating retries, verifying signatures, and replaying a failed delivery.
Adjust the form after ten real calls
After a handful of calls, look at which answers changed what you did. If nobody read the "how do you prefer to work" answer, drop it. If the call kept stalling on account access, make that question required. If "Not sure yet" became the most common budget answer, publish a starting range next to the question.
The agency client intake process covers what happens after the call, from clarification to handoff. To start from a ready-made form instead of a prompt, the project estimate request template is the closest fit.







