Client Intake Form Examples for Agencies and Consultants

A client intake form should reduce the first meeting, not repeat it. Collect the facts needed to prepare, route, price, or reject the work. Leave discovery questions that benefit from conversation for the call.

The best intake form is shorter than the team’s internal wish list. Every extra field raises abandonment and gives you another answer nobody reads.

General client intake form

Use this structure for consulting, design, marketing, development, and professional services:

Contact and organization

• Full name
• Work email
• Organization
• Website
• Role in the project
• Other decision-makers

Project

• What are you trying to change?
• What is happening now?
• What would a successful result look like?
• Which services are you considering?
• Target start date
• Fixed deadline and reason
• Budget range

Existing setup

• Current platform or software
• Tools that must remain
• Previous supplier or internal owner
• Links to relevant files
• Known technical or legal constraints

Next step

• Preferred meeting times
• Who should attend?
• Permission to contact
• Terms and privacy acknowledgement

Core Forms’ field types cover text, email, URL, date, select, radio, checkbox, textarea, and file inputs. Start with the simplest control that produces an unambiguous answer.

Agency website project example

A website intake form needs enough detail to estimate risk:

• Is this a new site, redesign, migration, or repair?
• Which CMS and hosting provider are in use?
• How many page types exist?
• Does the site handle payments, memberships, or personal data?
• Who owns copy, images, analytics, DNS, and hosting access?
• Are there fixed launch, campaign, or contract dates?
• Which current feature cannot break?

Do not ask clients to paste passwords into the form. Collect the service name and account owner, then move credentials through a password manager after the project is accepted.

Use conditional logic to reveal migration questions only when “Redesign or migration” is selected. A simple lead should not scroll past 20 fields meant for a WooCommerce rebuild.

Consultant discovery example

A consultant often needs context more than files:

• What decision are you trying to make?
• What has already been tried?
• What evidence is available?
• Who owns the final decision?
• What happens if the problem is not solved this quarter?
• What would make this engagement a bad fit?

That last question saves time. A client who expects a guaranteed ranking, legal outcome, or revenue number should say so before the proposal.

File uploads without chaos

Use uploads for briefs, screenshots, reports, and sample data. Set accepted file types, individual size limits, total size, and file count.

The Core Forms file upload documentation covers restrictions and stored-file handling. Ask for the smallest useful file. A screenshot is safer than a database backup, and a redacted report is safer than a full customer export.

When a client has large or sensitive files, ask for a secure storage link instead of uploading through WordPress.

Route the intake automatically

An intake form becomes useful after submission:

1. Store the request in the submissions inbox.
2. Send an Email action with the summary and stable submission ID.
3. Send an Autoresponder with response time and next step.
4. Push qualified requests to HubSpot, Airtable, Notion, or another connected system.
5. Route by service, budget, country, or urgency using conditional action rules.

The forms for agencies workflow shows how to keep WordPress as the recovery record while clients work from the CRM or team workspace.

Use multi-step forms only when the sections are real

Multi-step presentation helps when each step represents a clear mental task: contact, project, current setup, files, review.

Do not split six fields across five screens to imitate Typeform. Every Next button is another commitment and another place to quit. Core Forms’ multi-step forms support progress, validation, and one-question-at-a-time layouts, but the content still needs to justify the steps.

Check the result with field drop-off analysis. If half the qualified prospects leave at the budget question, decide whether the range is wrong, the wording is hostile, or the question belongs later.

FAQ

What is a client intake form?

It collects the facts needed to prepare for, qualify, route, or price a new client request before the first meeting.

How many fields should an intake form contain?

Use the minimum needed for the next decision. A simple consultation may need 8 to 12 fields. A technical migration can justify more when conditional logic hides irrelevant sections.

Should a client intake form ask for budget?

Yes when budget changes the service or qualification decision. Use ranges and explain what the range affects.

Should clients upload passwords or API keys?

No. Ask which systems need access, then exchange credentials through a password manager after the engagement is accepted.

Can Core Forms send intake data to a CRM?

Yes. Core Forms includes direct integrations and generic webhooks, with conditional actions for routing different requests to different destinations.