Web Design Intake Form Template
This intake scopes a website design the way studios work in practice, covering goal, pages, taste, and content readiness. It asks for a URL only 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 without bluffing, 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 show rule from the Logic panel does quiet UX work, so 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.
Content readiness is the calendar. 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, because "please create it for us" changes scope, price, and timeline, and learning it on day one beats any wireframe. The taste question stays open-ended, since references communicate what adjectives cannot, while budget bands and the launch date bound the possibility space.
The questions founders should not answer. Hosting, platform, and tech-stack questions come off, because founders answer them 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. So does "describe your ideal website in detail", the prompt that yields either three words or three pages, both useless.
On your site, tuned to your floor. 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, where the inline embed sits flush inside the layout and iframe or popup variants cover the pages that suit them better. Rewrite the budget bands around your floor, so the bottom band is your minimum engagement and mismatched leads self-select out kindly. Swap the page options for your specialty, since e-commerce work adds Collections and Product templates. Turn on email notifications for new briefs, and when 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 show the field for everyone.
Can this form sit directly on my studio site?
Three embed options wait 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.