Consultation Request Form Template

Arrive at the first consultation already briefed: situation, goals, budget reality, and the contact channel your prospect prefers.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

The first conversation is free and useful, with 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, while context gets the meeting to start at minute zero instead of minute twenty. This template is weighted to match, light on identity and heavy on situation.

Why the situation field is the centerpiece. It is required, richly prompted, and placed before any budget talk. The placeholder asks for three things, where you stand, what you have tried, and 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 report shorter sales cycles, because 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 that lets someone say they are not sure yet and want help scoping it. Ranges take the edge off a question that exact numbers make adversarial, the option to skip prevents abandonment, and the scoping choice turns 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, so video and email people are never asked for a number they would rather not give, and phone people are asked at the moment the request makes obvious sense. It is a small courtesy with a measurable effect, since phone fields shown to everyone are a known abandonment point on professional-services forms.

Why the whole form shows at once. Prospects composing a situation paragraph want the whole form visible, context above and questions below. The one-question-at-a-time rhythm that suits capture forms would fight the reflective writing this form is built to invite.

Fields the email already answers. Company-size brackets, industry dropdowns, and "how did you hear about us" all stay off, since the email domain, the situation text, or a thirty-second conversation reveals each one. Every removed field bought completion for the field that matters.

Rename it to your service lines. Independent consultants and boutique firms use it, along with fractional executives, financial advisors, legal and accounting practices offering an initial session, and agencies that lead with a strategy call. Rename the practice-area options to your real 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, because the form kept its half of the bargain and the rest is 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 right away, or webhook requests into your team channel. The ending promises contact within two business days, so beat it.

Can I route requests by practice area?

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.