Consultation Request Form Template
Arrive at the first consultation already briefed — situation, goals, budget reality, and the contact channel your prospect prefers.
The first conversation is free and genuinely useful — no pitch scripts. The more context you give us here, the more of that hour we spend on answers instead of introductions.
A consultation request form has one job that most versions of it fumble: making the consultation itself better. Contact details get a meeting booked; context gets the meeting to start at minute zero instead of minute twenty. This template is weighted accordingly — light on identity, heavy on situation.
Why the situation field is the centerpiece. It is required, generously prompted, and placed before any budget talk. The placeholder asks for three things — where you stand, what you've tried, what solved looks like — because those three answers are the skeleton of any competent discovery call. Consultants who read a thoughtful situation paragraph before the call consistently report shorter sales cycles: the prospect experiences the first conversation as already understood, which is the feeling that closes advisory work.
Budget, handled like adults. The budget question is optional, bracketed, and includes the honest escape hatch "not sure yet — help me scope it." Ranges depolarize a question that exact numbers make adversarial, the option to skip prevents abandonment, and the scoping option converts uncertainty into an agenda item instead of a lie. You learn what you need for triage — which inquiries fit your minimum engagement — without interrogating anyone.
The phone field that knows when it's wanted. Contact preference is a required choice: video, phone, or email-first. A conditional logic rule reveals the phone-number field only when "phone call" is selected — video and email people are never asked for a number they'd rather not give, and phone people are asked at the exact moment the request makes obvious sense. It's a small courtesy with measurable effect: phone fields shown unconditionally are a known abandonment point on professional-services forms.
Why Document mode. Prospects composing a situation paragraph want the whole form visible — context above, questions below. The one-question-at-a-time rhythm that suits capture forms would fight the reflective writing this form is built to invite.
What we left out. Company-size brackets, industry dropdowns, "how did you hear about us" — all inferable from the email domain, the situation text, or a thirty-second conversation. Each removed field bought completion for the field that matters.
Who uses this. Independent consultants and boutique firms, fractional executives, financial advisors, legal and accounting practices offering an initial session, and agencies that lead with a strategy call.
Make it yours. Rename the practice-area options to your actual service lines, tune the budget brackets to your engagement sizes, and set email notifications so requests reach you while the prospect is still in a deciding mood. Read the situation paragraph before every call — the form kept its half of the bargain; that's yours.
Frequently asked questions
Why does the phone field only appear sometimes?
A logic rule shows it only when "Phone call" is the chosen contact method. People who prefer video or email are never asked for a number, which removes a classic drop-off point.
Is asking for budget on a first-touch form too aggressive?
Not when it's optional, bracketed, and includes a "help me scope it" option. You get triage data from those willing to share, and nobody is forced to invent a number.
How do I keep response time fast?
Enable email notifications in Settings so each request lands in your inbox immediately, or webhook requests into your team channel. The ending promises contact within two business days — beat it.
Can I route requests by practice area?
Yes — filter the responses view by the "what do you need help with" column, or branch on it in your webhook receiver so each service line's lead owner gets their own requests.