Client Intake Forms for Agencies: Questions, Logic and Kickoff Handoff

A client intake form for an agency collects everything you need before work starts: who the client is, what they want to achieve, the scope, budget, timeline, who approves the work, and the brand files your team will need. A good one also qualifies the lead (is this a project you should take?) and turns the answers into a brief your team can kick off from. Below is the question set we recommend for web, design and marketing agencies, the logic that keeps it short, and how to hand the result to your project tools.
Intake form, project brief or creative brief?
Agencies use these three names loosely, and it helps to separate them because they happen at different moments.
| Form | When it's sent | What it answers | Typical length |
|---|---|---|---|
| Inquiry or intake form | Before the first call | Who are you, what do you need, budget, timing, are we a fit? | 8-12 questions |
| Client onboarding questionnaire | After the contract is signed | Billing, contacts, access, assets, communication preferences | 10-15 questions |
| Project or creative brief | Before production starts | Goals, audience, message, deliverables, mandatories, examples, sign-off | 12-20 questions |
Many small agencies combine the first and third into one form and send onboarding details later. That works if you use logic so a prospect with a small budget or the wrong service doesn't have to answer 20 questions before you tell them you're not a fit.
The questions to ask
Group questions so the client moves from easy (who they are) to harder (goals and constraints). Ask one thing per question; "tell us about your project" invites a one-line answer.
1. Contact and company
- Your name, email, phone and company (one contact info block)
- Company website
- Industry or what the business does, in one or two sentences
- Your role, and are you the person who approves the work? If not, who is?
The decision-maker question matters more than it looks. Projects stall when the person filling in the brief isn't the person who signs off.
2. The project
- Which service do you need? (website, branding, marketing campaign, content, ongoing retainer, something else)
- Is this a new project or a redesign/refresh of something existing?
- What should this project achieve? What problem does it solve?
- How will you know it worked? (more leads, launch on time, a new look for a funding round, sales from a campaign)
- Who is it for? Describe your ideal customer.
3. Scope and deliverables
- What do you need us to deliver? (multiple choice, specific to the service)
- What is a must-have, and what is a nice-to-have?
- Who will provide content: copy, photos, product data?
- Are there constraints we should know about? (platform, legal review, brand rules, accessibility requirements, existing contracts)
Splitting must-haves from nice-to-haves is the cheapest defence against scope creep. When a "quick addition" shows up in week four, you can point to what was agreed.
4. Brand and examples
- Upload your logo, brand guidelines and any existing assets
- Websites, brands or campaigns you like, and why
- Competitors (names or links), and what you like or dislike about how they present themselves
- Three words you want people to use about your brand
"And why" is the useful part of the examples question. A link alone tells you nothing about whether they liked the colours, the layout or the copy.
5. Budget and timeline
- Budget range (multiple choice ranges, not an open box)
- Ideal start date and launch date
- Is the deadline fixed by something outside the project, such as a product launch, trade show or season?
Ranges get more honest answers than an empty number field, and they let you branch.
6. Working together
- How do you prefer to communicate? (email, calls, Slack, a project tool)
- Have you worked with an agency before? What worked, and what didn't?
- Anything else we should know?
7. Agreement (onboarding stage)
- Confirm you've read the terms of engagement (yes/no)
- Signature
If you collect a signature, use it to confirm the scope the client just described, not to replace your contract. Your proposal or statement of work is still the legal document.
Service-specific questions
A full-service agency shouldn't ask a branding client about CMS plugins. Branch on the "Which service do you need?" answer and ask only the relevant block.
| Service | Extra questions worth asking |
|---|---|
| Website | New site or redesign; current URL; pages needed; features (booking link, shop, blog, member area, forms); CMS preference; who hosts; who writes the copy; SEO or migration concerns |
| Branding | What the business does; why customers choose you; brand personality sliders (e.g. classic vs modern, playful vs serious); words to be known for; deliverables (logo, guidelines, stationery, social kit) |
| Marketing / campaign | Campaign goal; channels; target audience; offer; existing ad accounts; tracking in place; monthly media budget separate from fees |
| Content | Content types; volume per month; tone; who approves; subject matter experts available for interviews |
Brand personality sliders work well as opinion scale questions with labels on each end (for example 1 = classic, 5 = modern), and they give your designers more to work with than "modern but timeless".
Qualifying logic that saves your time
An intake form that only collects is half the job. The other half is deciding who gets a call. Some rules that work for most agencies:
- Budget below your minimum. Send them to an ending that thanks them, says plainly what your projects usually start at, and points to a cheaper option (a template, a freelancer directory, a workshop). No call booked, no awkward email.
- Service you don't offer. Route to an ending that says so, instead of letting them finish a 15-question brief.
- Unrealistic timeline. If the launch date is before your lead time, show a question asking whether the date is fixed, so you know before the call whether it's a dealbreaker.
- Not the decision-maker. Ask for the approver's name and email so you can include them in the first meeting.
- Good fit. Send them to an ending with next steps, and if you use a booking tool, link to it.
Keep qualifying questions early in the form. The worst outcome is a prospect who spends ten minutes on a brief and then hits "we're not a fit".
For more on scoring and routing leads, see our guide to lead qualification questions.
Collecting brand assets without chasing
Chasing a high-resolution logo for a week is a common way to lose the first sprint. A file upload question in the brief fixes most of it:
- Ask for files at the point they're relevant (logo with the brand questions, sitemap with the website questions), not in a dump at the end.
- Say exactly what you want: "SVG or PNG logo, brand guidelines PDF, any photos you own the rights to".
- Make the upload required only when you truly can't start without it. If the client doesn't have guidelines, a required field forces them to upload something random.
- For large asset libraries (video, raw photography), ask for a link to a shared folder in a website field instead. Upload limits on most form tools, ours included, are sized for documents and images, not gigabytes of footage.
Handing the brief to your kickoff
The intake form should end with your team ready to work, not with an email someone has to retype into a project tool.
- Notify the team. Post each new brief to a Slack channel so the account lead sees it immediately.
- Keep a running log. Send every response to a Google Sheet so you can see all briefs, budgets and sources in one place.
- Create the project. Send the response as JSON with a webhook to Zapier, Make or n8n, and have it create a project or task in Asana, Trello, ClickUp or your CRM with the answers in the description.
- Confirm to the client. Send a confirmation email with a summary of what they told you and what happens next.
- Book the call. Send good-fit leads straight to your calendar booking page when they finish.
Then use the brief to write the kickoff agenda: goals and success measures, must-haves vs nice-to-haves, open questions from the "constraints" answer, approvers, and dates. If an answer is vague, that's the first agenda item, not something to guess at.
Our website design intake form guide goes deeper on the web-project version of this.
Common mistakes
- Asking for everything up front. Billing address and tax IDs belong in onboarding, after they've said yes.
- One generic form for every service. Branch, or keep separate forms per service.
- Open-ended budget fields. You get "depends" or nothing.
- No "why" on examples. You get links without meaning.
- No ending that sets expectations. Tell them when you'll reply and what the next step is, or they'll email you to ask.
- Making it look like a tax form. The brief is part of your pitch. If it's clumsy, the client notices.
How to do this in FlowyForm
FlowyForm shows one question at a time, which suits briefs: long text questions feel less daunting when they arrive one by one, and logic hides the blocks a client doesn't need.
- Start from a template. Use the client intake form template for onboarding (contact and billing details, goals, communication preferences, documents, terms and signature), the client requirements gathering form for a general project brief, the website questionnaire for web projects, or the branding questionnaire for identity work.
- Add branching. On the service question, add rules such as "if answer is Branding, go to question X". Budget ranges can route to different endings, and you can have more than one ending.
- Use answer recall. Insert their first name or company into later questions ("What should the new site do for Acme?") so it reads like a conversation.
- Track where leads come from. Add hidden fields to the link, for example
?source=referralor?source=linkedin, and they're stored with each response. You can also use them in logic. - Collect files and a signature. Add file upload questions for brand assets (10 MB upload limit on the free plan, 100 MB on Premium) and a signature question for the scope confirmation.
- Connect the handoff. Slack, Google Sheets and webhooks are included on the free plan. FlowyForm has no native Asana, Trello or HubSpot integration; webhooks through Zapier, Make or n8n get the data there.
- Brand it and share it. Match your agency's colours, fonts and logo, then embed the form on your site or send the link. Premium adds your own domain, removes FlowyForm branding, sends respondent confirmation emails and can redirect good-fit leads to your booking page when they finish.
What FlowyForm doesn't do: it has no price calculator, so it can't quote a project from the answers, and it doesn't book calls itself. Use budget ranges and logic to set expectations, and an ending redirect to your booking tool. See the agency client intake page for an overview.
FAQ
What should be included in a client intake form for an agency?
Contact and company details, the decision-maker, the service needed, project goals and how success is measured, audience, deliverables split into must-haves and nice-to-haves, constraints, brand assets and examples with reasons, budget range, timeline, and communication preferences. Add terms and a signature at the onboarding stage.
How long should an agency intake form be?
An inquiry form should take a few minutes: around 8-12 questions. A full project brief can run 15-20 questions if logic hides the ones that don't apply and the client knows up front that it takes 10 minutes or so.
Should I ask for budget on the intake form?
Yes, as ranges. Clients who won't pick a range are rare, and the answer lets you route small budgets to a polite ending before anyone books a call.
What's the difference between a client intake form and a creative brief?
The intake form decides whether and how you work together (fit, budget, timing, contacts). The creative brief describes a specific piece of work (objective, audience, message, deliverables, mandatories, approvals). Many agencies combine them for smaller projects.
Can clients upload logos and brand guidelines through the form?
Yes, with a file upload question. For very large files such as video or raw photo libraries, ask for a shared folder link instead.
How do I get intake answers into my project management tool?
Send the response by webhook to an automation tool like Zapier, Make or n8n and have it create the project or task, or log every response to a Google Sheet and work from there.