Web Design Intake Form Template
Scopes a website design the way studios actually work — goal, pages, taste, and content readiness — and only asks for a URL when a live site exists.
The more we know before wireframes, the fewer revisions after them. Ten minutes here routinely saves a week of back-and-forth.
Website projects die in the gap between what clients imagine and what they can articulate. This intake closes that gap with questions a non-technical founder can answer honestly — and it opens with the one branch every web designer needs: whether a site exists today. Answer yes and a URL field appears; answer no and the form stays out of your way. That is a show rule from the Logic panel doing quiet UX work — nobody types "we don't have one" into a website field again.
Goal before pages. The single-select goal question forces a hierarchy most site briefs dodge: a portfolio that must win enquiries is a different design problem from a site that must explain a complicated service. Only after the goal does the form ask which pages exist in the client's head. That multi-select is your sitemap seed, and the gap between the stated goal and the page list is where your expertise enters the first call.
The content question is the schedule. Ask any studio what delays launches and the answer is never design — it is copy and photography that "will be ready next week" for eleven straight weeks. The content-readiness select surfaces this before contracts are signed: "please create it for us" changes scope, price, and timeline, and learning it on day one is worth more than any wireframe. The taste question stays open-ended because references communicate what adjectives cannot; budget bands and the launch date bound the possibility space.
Deliberately absent. Hosting, platform, and tech-stack questions — founders answer those with guesses, and guesses harden into requirements. Builds with accounts, integrations, or migrations belong on the web project intake template, which asks stakeholder-grade questions instead. Also missing: "describe your ideal website in detail", the question that yields either three words or three pages, both useless.
Who uses it. Freelance designers link it from the contact button on their portfolio. Studios send it ahead of discovery calls and read the answers aloud at kickoff. Site builders embed it on their services page — the inline embed sits flush inside an existing layout, with iframe and popup variants when those suit the page better.
Tuning it. Rewrite the budget bands around your floor; the bottom band should be your minimum engagement, so mismatched leads self-select out kindly. Swap page options for your specialty — e-commerce work adds Collections and Product templates. Turn on email notifications for new briefs, and if leads live in a CRM, the webhook pushes each submission across in real time, signed so your automation can trust the payload. Keep the two-page shape: contact details land on page one, so a half-finished brief still leaves a partial response worth a friendly follow-up.
Frequently asked questions
Why does the URL question only appear sometimes?
A conditional rule shows it only when the respondent says a site is live. You can see and edit the rule in the Logic panel — or delete it to always show the field.
Can this form sit directly on my studio site?
Yes — three embed options are on the Share page: inline for a seamless section, iframe for maximum compatibility, and popup for a button-triggered overlay.
What if a prospect abandons halfway?
Everything typed up to that point is stored as a partial response. Since contact details are on page one, you usually still get a reachable lead.
Can I reorder or delete questions I don't need?
The editor treats the form as a block document — drag blocks to reorder, delete what you don't need, and add new question types anywhere.