Client intake form questions for freelancers should help you answer one practical question: is this enquiry ready for a useful conversation, a proposal, or a polite no? A form that collects every detail about a business can still fail if it never clarifies the requested outcome, decision maker, or timing. A shorter form with a purpose for each field is easier to act on.
This guide separates pre-sales intake from the deeper information you collect after someone hires you. It includes twelve adaptable questions, a fictional worked example, a simple routing system, and the checks that keep the form from becoming another inbox.
Client Intake Form Questions for Freelancers Start With the Decision
Before writing a form, decide what happens after someone submits it. For most solo service businesses, the possibilities are limited: schedule a discovery conversation, request one missing detail, send an appropriate next step, or decline because the project is not a fit. The intake should give you enough evidence to choose among those paths, not demand a finished creative brief before you have agreed to work together.
| Stage | What you need to know | What can wait |
|---|---|---|
| Initial enquiry | What is requested, why it matters, contact, fit, broad timing | Detailed passwords, full brand libraries, every stakeholder preference |
| Discovery and proposal | Objectives, deliverables, dependencies, likely budget and approval path | All implementation access and the complete kickoff pack |
| Signed-project onboarding | Confirmed scope, owners, working files, permissions and first milestone | Inputs required only for much later phases |
If the engagement is already signed, use the more detailed client onboarding checklist instead of treating an enquiry form as the entire kickoff process. The distinction prevents the form from asking a prospective customer for access or documents they have no reason to share yet.
The 12 Questions I Would Put in a Small Freelance Client Intake Form
Use the first six as a starting point and add the others only when the answer changes your decision. The suggested response type is deliberate: short fields should not become essays, while genuine uncertainty needs somewhere to be explained.
| Question for the client | Response format | Why the answer matters |
|---|---|---|
| 1. What is your name, organization (if any), and best email for this enquiry? | Three short fields | Gives the reply a clear recipient. A telephone number is optional unless calls are genuinely necessary. |
| 2. Which service or type of project are you asking about? | Multiple choice plus “not sure” | Routes the enquiry without assuming the customer knows your service menu. |
| 3. In a sentence or two, what are you trying to achieve? | Short paragraph | Distinguishes the desired outcome from a shopping list of deliverables. |
| 4. What would you like to have in hand at the end? | Short paragraph or examples | Reveals whether they want advice, a document, a campaign, an implementation, or ongoing support. |
| 5. Is there a target date, and what makes that date important? | Date plus optional explanation | Separates a hard external deadline from a flexible preference. |
| 6. What is the best next step from your perspective? | Call / written estimate / ask a question / not sure | Respects how the customer wants to begin without promising an instant quote. |
| 7. Is there an indicative budget range or procurement limit we should work within? | Optional ranges / prefer to discuss | Helps avoid designing an option neither side can approve. Only ask if it affects the offer. |
| 8. Who will decide whether the project goes ahead? | Role or short text | Shows whether the respondent is the final approver or coordinating others. |
| 9. What is already in place that this work would need to use? | Website link or short text | Identifies existing material without requesting account credentials. |
| 10. What have you tried, and what is not working? | Optional short paragraph | Helps avoid proposing work the customer has already ruled out for a good reason. |
| 11. Are there important constraints we should know before discussing scope? | Optional checkboxes plus explanation | Surfaces approval steps, limited availability, required languages or technical restrictions. |
| 12. Is there a public link or example that shows the type of result you have in mind? | Optional URL | Supports a more productive conversation without collecting private files too early. |
You should not copy all twelve by default. A designer offering a fixed-price logo package may only need the service, objective, timeline, budget band and contact details. A consultant discussing an international launch may need decision authority, markets and procurement constraints earlier. Remove a field when you cannot explain how its answer changes the next action.
A Copyable Short Version for the Website Contact Page
For a first enquiry, I would publish the following wording rather than a survey that feels like a procurement portal. The final line sets the expectation that submitting is a request to discuss a project, not acceptance of an agreement.
Tell me a little about the project
What name and email should I reply to? What kind of help are you looking for? What outcome are you hoping for, and what would a useful finished result look like? Is there an important date or constraint I should know about? Is there a public example or website link that would give me context?
Please do not include passwords, payment-card details, confidential client documents, or sensitive personal information in this form. Sending an enquiry does not create a client relationship. I will use the information to consider and respond to your request.
The public-facing wording should link to your real privacy notice and state a realistic response window only if you can meet it. If you offer several services, a single service-selector question can reveal a few relevant follow-ups rather than showing everyone a long questionnaire.
Worked Example: Two Enquiries, Different Next Actions
Consider two fictional enquiries for a freelancer who builds small business websites. These are decision examples, not client results or conversion data.
Enquiry A: A small consulting firm says it needs one service page before an industry event. It explains the audience, has an existing website, and identifies the owner as approver. The likely next step is a focused scope conversation or a written request for the current page and required content. There is no reason yet to ask for hosting credentials.
Enquiry B: Someone checks “new website,” writes “as soon as possible,” and leaves the outcome blank. Rather than immediately booking an hour, the freelancer can ask: “What should the website allow a visitor to do, and is there a date tied to an actual launch or event?” That one clarification could reveal a simple brochure page, a full ecommerce project, or an idea not yet ready to quote.
Neither submission should be assigned an invented lead score or declared qualified solely because it filled in the form. The point is to make the next decision visible.
Turn Answers Into a Small Response Workflow
Intake fails when it becomes a new place where information disappears. Even without automation, record a submission date, contact, service, fit status, unanswered question, and next action. A shared spreadsheet is sufficient for modest volume. A basic Notion CRM for freelancers can hold this information if you already use it.
| Status | When it applies | What happens next |
|---|---|---|
| Needs clarification | Outcome or scope is unclear | Ask one targeted question; record the next check |
| Potential fit | Service, problem and initial context line up | Invite a discovery call or ask for the specific details needed for a proposal |
| Not a fit | Outside your services, capacity or other stated boundaries | Send a courteous decline without collecting more data |
| Confirmed client | Scope and commercial agreement have been accepted | Move to the signed-project onboarding process, not a second sales sequence |
Do not automate assumptions that require judgment. A form can save the contact, notify you and send an acknowledgement, but it should not promise project availability, a price or an agreed deadline that no person approved. Likewise, an enquiry is not automatic permission to add the person to a marketing newsletter.
Affiliate disclosure: This article contains an affiliate link. If you sign up through it, Anywhere Work Lab may earn a commission at no extra cost to you. Recommendations are based on editorial relevance, not commission.
If a growing volume of enquiries makes follow-ups difficult, EngageBay CRM is one dedicated system worth comparing for contact, pipeline and follow-up management. Evaluate the actual form-to-CRM handoff and current plan limits before committing; a simple spreadsheet is usually easier when submissions are infrequent. This is a research-based option, not a claim that it was personally tested for this article.
How to Set Up the Form Without Buying New Software
Google Forms is a practical starting point if you already work in Google Workspace. Its official setup guide documents creating a form, sharing it for responses and analyzing submissions; Google also explains sending responses into a Sheet. It is not a complete CRM or secure credential intake solution.
- Create the basic questions. Start with contact, service, intended outcome, deliverable, timing and preferred next step. Keep optional questions optional.
- Check the respondent settings. Decide whether an account sign-in is required and whether the form will reach people outside your Google organization. Confirm that the settings do not accidentally block prospective clients.
- Choose one response destination. Use a responses sheet or a designated inbox. Decide where the decision status and next action will live. Avoid forwarding every submission into several disconnected systems.
- Write one acknowledgement. Confirm receipt and describe what happens next without implying the project is booked. If you cannot promise a response time, do not invent one.
- Test as a client. Use a private browsing session and a mobile device if possible. Submit a fictional response and verify receipt, permissions, field validation, confirmation wording and the link to your privacy notice.
For a more advanced site, conditional questions, a branded form or a connected client portal may make sense. Add those only after the simple flow proves useful. The client portal guide describes what belongs in the project space after a client is accepted; it should not be confused with the public enquiry form.
Protect Privacy Before You Add Fields or Uploads
Collecting business contact information still creates responsibilities. A useful starting principle is data minimisation: ask for what serves a stated purpose, restrict access, and avoid keeping information indefinitely. The UK’s Information Commissioner’s Office guidance explains the necessity principle for personal data under the relevant regime. Applicable rules vary by country, service and relationship, so adapt your notice and retention practice rather than treating a generic form as legal compliance.
Do not request passwords, identity scans, payment card numbers, medical details or confidential business files simply because the form builder offers an upload field. Once a contract is signed, exchange required sensitive materials through an access-controlled channel appropriate to the work. Only people who need the submissions should receive them.
Separate the purpose of replying to a project enquiry from optional marketing communications. If you wish to offer a newsletter, give that its own clearly explained choice and follow the rules applicable to your recipients. An acknowledgement email about the enquiry is not a justification for an unrelated promotional sequence.
The Final Five-Minute Quality Check
- Can a stranger tell what the form is for before answering?
- Does every required field change a decision or a necessary reply?
- Is the requested outcome clearer than a generic service category?
- Can the respondent decline a budget answer when a budget is not essential?
- Does a test submission land in the one place you actually check?
- Are privacy information, access rules and acknowledgement accurate?
- Can you identify the next action for a vague submission without guessing?
Finally, compare the form against a real recent enquiry and ask what information would actually have helped. If the answer is “one question about decision authority,” add that. If five fields routinely go unused, remove them. The best client intake form questions for freelancers are the ones that make the first useful reply easier, not the ones that fill the longest spreadsheet.
