Branch by service
A dropdown at the top routes each service to a section with only its questions. A retainer and a one-off project need almost nothing in common.
A client intake form is the difference between a project that starts and a project that starts twice. It collects scope, budget, timeline, decision-makers, and the assets and access you will need. Before the kickoff call rather than during the second week.
Not a stock template. Build it in a few minutes from a blank form, or describe it and let AI draft the questions on a paid plan.
The reason intake forms fail is that they get written for the agency, not the client. Nobody can answer "what are your KPIs?" cold. Ask what they want to happen, in their words, and translate it yourself.
A starting point, not a rulebook: every question below is a real Questionful question type, and all of them are editable once the form is in your account.
| Question | Question type |
|---|---|
| Which service are we starting? The branching question, each service needs different details | Dropdown |
| Company name and website | Short answer |
| Who is our main point of contact? | Short answer |
| Who signs things off? Not always the same person | Short answer |
| What does success look like in six months? | Paragraph |
| What is the deadline, and what drives it? | Date |
| Which of these do you already have? Brand assets, analytics access, copy, domain | Checkboxes |
| Upload anything relevant Paid plans, brand guidelines, existing contracts | File upload |
| How do you prefer to communicate? | Multiple choice |
A dropdown at the top routes each service to a section with only its questions. A retainer and a one-off project need almost nothing in common.
Checkboxes for the accounts and assets you need turn a vague "we will send those over" into a list you can chase against.
A file upload question collects brand guidelines and existing material inline, filed with the response rather than scattered across an inbox.
Email the project lead on submission, and let the Google Drive integration keep a PDF of the intake with the project folder.
Service, contacts including who signs off, the outcome in the client's own words, the deadline and what drives it, and a checklist of assets and access you need. Everything else can wait for the call.
Yes on paid plans, up to 25 MB per file. Uploads are stored on EU infrastructure and downloaded through signed links. The free plan does not accept respondent uploads.
Yes. A dropdown routes each service to its own section, so a retainer client never sees the one-off project questions.
Indirectly: every submission POSTs as JSON to Zapier, Make, or your own endpoint, and any of those can create the project, folder, or ticket.
Route each answer choice to its own section, so people only see what applies.
Feature19 types, including specialist ones most builders skip.
FeatureEvery response POSTed as JSON to any endpoint, signed if you want it.
TemplateAsk the budget, timeline, and fit questions before the first call.
TemplateStructured intake for internal or client work, routed by request type.
TemplateCollect everything a new starter needs to be set up on day one.
TemplateCollect scope, budget and deadline once, instead of across nine emails.
Use caseQualify enquiries while they are being filled in, and hand every submission straight to the tool your sales process already runs on.
Use caseTurn recurring internal requests (time off, IT tickets, purchase approvals) into structured forms with a real audit trail.
Unlimited forms and 100 responses a month, free. Paid plans from €19.
No credit card required.
Choose which cookies you allow. Strictly necessary cookies are always on because the site cannot function without them.
Required for core features such as security, load balancing and remembering this cookie choice. These set no tracking cookies.
Google Analytics, used to understand traffic and improve the site. Loaded only if you allow it.