client intake form template

Better proposals usually start with better intake.

A useful intake form does not just collect contact details. It captures scope, decision process, risks, constraints, assets, and approvals so the next handoff is less ambiguous.

Use the template See related tools
Search intent Freelancers, agencies, and service providers who need a reusable intake form before proposals, onboarding, or implementation.

This page is a practical guide, not a guarantee of leads, revenue, compliance, payment collection, or platform approval.

Core intake sections

A safe starting template.

Adapt this to the buyer's business, tools, consent rules, contracts, and platform policies before using it with real customers.

01
Business and contact details: name, email, company, role, time zone.Review manually before external use.
Step
02
Project goal: what changed, what is broken, what success would look like.Review manually before external use.
Step
03
Current tools: website, CRM, email, forms, calendar, payments, documents.Review manually before external use.
Step
04
Scope boundaries: what is included, excluded, pending, and blocked.Review manually before external use.
Step
05
Approval path: decision maker, review date, launch owner, support contact.Review manually before external use.
Step

Checklist

What to verify before using the workflow.

Ask for the business problem before asking for preferred tools.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Separate must-have requirements from nice-to-have requests.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Capture examples, screenshots, files, and source links early.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Add a change-request path before work begins.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Turn intake answers into a proposal outline and launch checklist.

Keep this visible before sending, publishing, collecting data, or handing the workflow to another person.

Avoid these mistakes

The page should reduce risk, not just increase clicks.

Asking broad questions that do not change the proposal.

Fix this before treating the workflow as production-ready.

Skipping approval roles and then waiting on the wrong person.

Fix this before treating the workflow as production-ready.

Mixing onboarding, discovery, and support into one messy form.

Fix this before treating the workflow as production-ready.

Starting work before missing assets and tool access are visible.

Fix this before treating the workflow as production-ready.