Skip to content
SoloWOS
Start your free trial

Winning clients

What to ask on a freelance inquiry form (before the first call)

By SoloWOS teamPublished

IN SHORT

A freelance inquiry form should ask for name, email, the service needed, a short project description, timeline and budget range. Offer budget as ranges rather than an open box, keep the form under 10 fields with 4 or 5 required, and save contracts, logins and detailed briefs for onboarding after the client signs.

Prices and limits as of .

Key takeaways

  • Ask only what changes your next step before the call: whether to reply, which call to offer and which price range to quote.
  • Make 5 fields required (name, email, service, goal and a budget range with a "Not sure yet" option) and leave the rest optional.
  • Budget ranges whose lowest band ends at your minimum price tell you about fit and can route people to the right call; an open text box can't.
  • Conditional questions keep one form short for every service: a website lead sees page-count questions that a branding lead never sees.
  • Give every field a visible label tied to it in the code, and say "required" in words, as the W3C's forms tutorial recommends.

An inquiry form sits on your website or link in bio and settles one thing before anyone books your time: is this worth a call? It isn't the place for a full brief. Ask too little and the first call goes on basics; ask too much and people leave halfway. This post is part of the winning clients hub.

Which fields to include, and which to make required

Each field should change what you do next: reply or not, which call to offer, which price range to quote. If an answer wouldn't change anything before the first call, it belongs on the onboarding form you send after the client signs.

Inquiry form fields, in order
FieldTypeRequired?Why it's there
NameShort textRequiredTo address your reply and create the contact
EmailEmailRequiredWhere your reply goes, and what stops the same person showing up twice in your contacts
What do you need help with?Single choiceRequiredSorts the inquiry by service and drives the conditional questions
What should this project achieve?Long textRequiredThe one answer you can't guess; two or three sentences are enough
Budget rangeSingle choiceRequired, with "Not sure yet"Tells you about fit before the call and can send people to the right call
Deadline or ideal start dateDateOptionalShows urgency and whether your calendar can take the project
Company and websiteShort textOptionalContext for business clients, and something to look at before you reply
How did you hear about me?Single choiceOptionalShows which channel actually brings clients
PhonePhoneOptionalOnly worth asking if you call people back
Anything else? Links welcomeLong textOptionalRoom for examples, a brief or a shared folder

That's 10 fields with 5 required. If you sell one service, drop the service question and the phone field and you're at 8. The "How did you hear about me?" answer is worth keeping even when it's optional: it's the only way to tie a paying client to a post or a referral, as explained in tracking which post brought a client.

What to leave for the onboarding form

  • Billing address, tax details and who pays the invoices.
  • Logins and access to their tools. Never collect passwords in a form; ask for an invite to their account instead.
  • Brand files, photos and existing content. Ask for a link to a shared folder.
  • Detailed scope (every page, every deliverable). The discovery call and the proposal settle that.
  • Anything that belongs in the contract, such as payment terms or usage rights.

Example inquiry form for a web designer

Project inquiry
PROJECT INQUIRY
Tell me about your project and I'll reply within one business day. Fields marked (required) need an answer; the rest are optional.

1. Your name (required)
2. Email (required)
3. Company and website
4. What do you need help with? (required, choose one)
   ( ) New website
   ( ) Redesign of an existing site
   ( ) Landing page
   ( ) Updates and support
   ( ) Something else
5. How many pages do you expect? (shown for New website or Redesign)
   ( ) 1 to 5   ( ) 6 to 15   ( ) More than 15   ( ) Not sure
6. Address of your current site (shown for Redesign)
7. What should this project achieve? (required)
   Two or three sentences: who it's for and what should change.
8. Budget range (required, choose one)
   ( ) Under $2,000
   ( ) $2,000 to $5,000
   ( ) $5,000 to $10,000
   ( ) $10,000 or more
   ( ) Not sure yet
9. When do you need it live? (date)
10. How did you hear about me?
   ( ) Referral   ( ) Search   ( ) Social media   ( ) Other

Thank-you message:
Thanks! I've got your details and I'll reply by email within one business day.

How to word the budget question

Budget is the field freelancers hesitate over most, and the wording decides whether you get an answer you can use. Here are four ways to ask, from least to most useful for a one-person business.

Four budget question wordings compared
WordingWhat you get backThe problem
"What's your budget?" (open text box)"Flexible", "Depends", a blank, or an exact figureHard to compare across inquiries, and a form can't route on free text
"Estimated budget (USD)" (number field)A number, often a cautious guessIn SoloWOS, conditions compare answers as text, so a number can't send larger budgets to a longer call
Ranges, with the lowest ending at your minimum priceA band you can act onThe bands you choose steer people toward them, which is fine when they match your real prices
One line of context, then ranges: "Most sites like this run $4,000 to $9,000."A band, from someone who now knows your pricesFewer inquiries from small budgets, which is usually the point

Use ranges, end the first one at your minimum project price, and add "Not sure yet" so nobody has to invent a number to submit the form. Someone who picks the lowest band hasn't wasted your time: you can reply with a smaller package or a useful resource instead of a call. Once you're talking, the discovery call questions cover how to ask about budget out loud.

Conditional questions: one form, several paths

Conditional logic shows a question only when an earlier answer calls for it, so one form can serve every service without making people scroll past questions that don't apply to them. Base conditions on choice questions, where answers are exact, and keep each path to one or two extra questions.

WORKED EXAMPLE

Conditional paths in the web designer's form

Question 5 (page count) appears when the service is New website or Redesign. Question 6 (current site) appears only for Redesign. A landing page lead sees 8 questions, a new website lead sees 9 and a redesign lead sees all 10. After submitting, two routing rules run in order: budget is Under $2,000, or budget is Not sure yet, sends the person to a 15-minute intro call. Everyone else lands on a 45-minute discovery call, with their name and email already filled in.

Accessibility basics for labels and required fields

An inquiry form that a screen reader user can't finish is a lead you never see. The W3C's Web Accessibility Initiative sets out the basics in its forms tutorial, and none of them take extra time once you know them.

  • Give every field a visible label tied to the field in the code. The W3C's labeling tutorial recommends a label element whose for attribute matches the field's id.
  • Don't use placeholder text as the label. It disappears once someone starts typing, and screen readers don't treat it as a label (W3C form instructions).
  • Say which fields are required in words, for example "(required)" in the label. If you use an asterisk, explain it at the top of the form, as W3C technique H90 advises, and don't mark required fields by color alone (W3C Easy Checks).
  • Group choice questions. A set of radio buttons or checkboxes belongs in a fieldset with the question as its legend, so the question is read along with the options (W3C grouping controls).
  • Write error messages that say what went wrong and how to fix it, next to the field (W3C user notification). "Enter an email address like [email protected]" helps; "Invalid input" doesn't.

Build and test the form in six steps

  1. Write down your services and your minimum project price. They become the service options and the lowest budget band.
  2. Add the five required fields, then only the optional ones you'll actually read.
  3. Add one or two conditional questions per service, each based on the service answer.
  4. Decide what happens after submitting: a thank-you message with your reply time, or a booking page chosen by budget.
  5. Fill the form out on your phone, then again using only the keyboard (Tab to move between fields, arrow keys or Space to choose an option).
  6. Submit it once with a required field empty and check that the error message names the field and says how to fix it.

Build the inquiry form in SoloWOS

In SoloWOS you can build client intake forms from the Project inquiry template or a blank form, with text, email, phone, number, date and choice fields, each required or optional. A question can appear only when earlier answers match (is, is not, contains, is answered, is empty), with all or any of up to 10 conditions, and a hidden question is never required. Routing rules then send people to one of your meeting types with name and email filled in. Each response can email you and create or update a contact in your freelance client pipeline. Every label is tied to its field and screen readers announce required fields, which appear on screen with an asterisk, so add "Fields marked * are required" to the form's description. There's no file upload field; ask for a shared folder link. Solo includes 10 forms and 1,000 responses a month. To copy the questions into any tool, use the client intake form template.

Questions

How many questions should a freelance inquiry form have?

Between 6 and 10 visible questions covers what you need before a first call: contact details, service, goal, budget range and timing. Conditional questions let you add service-specific ones without showing them to everyone. If a question wouldn't change your reply, move it to the onboarding form you send after the client signs.

Should the budget question be required?

Yes, if it offers ranges and a "Not sure yet" option. A required open text box pushes people to type "flexible" or give up, while a required choice with an honest way out gets you a usable answer without forcing anyone to invent a number. If you sell one fixed-price package, state the price on the form instead.

What's the difference between an inquiry form and a client intake form?

People use the names loosely; timing is what matters. The form before the first call qualifies the lead: who they are, what they need, budget and timing. The form after signing collects what you need to do the work, such as billing details, access and brand files. Our client intake form template is the before-the-call kind.

Should I ask for a phone number?

Only if you'll actually call. Make it optional and say why you ask, for example "Only if you'd rather talk than email." If you reply by email first, a phone number you never use is just more personal data to protect, and one more field between the visitor and the submit button.

Where should I put my inquiry form?

On your contact page, at the end of each service page and in your link in bio, all pointing to the same form so every inquiry lands in one place. In SoloWOS you can add any published form to your Link in Bio page in one click and share its link anywhere else.

Sources

Facts checked against these sources on October 19, 2026. Rules and amounts change, so confirm them at the source before you file or sign.

  1. W3C WAI Forms Tutorial: Labeling controls
  2. W3C WAI: Form instructions tutorial
  3. W3C WCAG 2.2 Technique H90: Indicating required form controls using label or legend
  4. W3C WAI: Easy Checks, required fields
  5. W3C WAI Forms Tutorial: Grouping controls
  6. W3C WAI Forms Tutorial: User notification

Last reviewed:

SoloWOS tools mentioned here

Run your client work from one account

14 days free, no card needed · Then Basic for $2/month.

Start your free trial