Intake Forms for Web Design Agencies: From Brief to Build

By Daniel Akselrod · July 2026

The most expensive sentence in web design is “that’s not what I had in mind.” It usually shows up at the first design review, after your team has spent 40 hours building something the client imagined differently. The gap between what the client said and what the client meant is where projects go sideways — and a thorough intake form is the best tool you have for closing that gap before the contract is signed.

Most web design agencies rely on a discovery call to gather project requirements. The call is important, but it is not sufficient. Clients say things in conversation that they would not write down, and they write things down on a form that they would not think to mention on a call. A structured intake form forces the client to articulate decisions they may not have consciously made yet — about scope, about technology, about what “done” actually looks like. That is not a formality. That is the foundation of a project that finishes on time and on budget.

Project scope: new build vs. redesign vs. migration

These are three fundamentally different projects with different timelines, different technical requirements, and different risk profiles. A new build starts from nothing. A redesign starts from an existing site that needs to be improved. A migration starts from an existing site on one platform that needs to move to a different platform. Your intake form needs to determine which one this is immediately, because the rest of the questions change based on the answer.

For redesigns, ask what specifically is wrong with the current site. Not “what do you want to change” — ask what is not working. Is the design outdated? Is the site slow? Is it not ranking in search? Is the content management system too difficult for their team to use? Are they losing leads because the site does not convert? Each of these problems points to a different solution, and a client who says “I want a redesign” may actually need a performance optimization, a CMS migration, or just a new homepage — not a full tear-down.

For migrations, ask what platform they are currently on, why they want to leave, and what data needs to move. Blog posts, product listings, customer accounts, order history, 301 redirects for SEO — migration scope balloons when these requirements surface after the project has started. Get them on the form.

Tech stack preferences and constraints

Some clients have opinions about technology. They want WordPress because their last site was WordPress and they know how to use it. They want Shopify because they are selling products. They want a custom React application because their CTO read an article about single-page apps. Others have no preference and are trusting you to recommend the right platform.

Your intake form should ask about existing technology stack (current CMS, hosting provider, domain registrar), any platform preferences or requirements, whether the client has internal development staff who will maintain the site after launch, and what third-party integrations are needed — CRM, email marketing, payment processing, booking systems, inventory management, analytics tools.

Integration requirements are the hidden scope bomb. A client who mentions Salesforce integration in passing on a call may not realize that the connector alone is a $5,000 line item. When it is a checkbox on a form, you can price it before the proposal goes out.

Content readiness: the project’s longest dependency

Content is the single most common cause of web design project delays. The client assumes content will be easy. It is not. Writing effective website copy, sourcing professional photography, organizing product descriptions, drafting an about page that does not read like a resume — these tasks take time, and clients consistently underestimate how much time they take.

Your intake form should ask directly: Do you have written copy ready for all pages? Do you have professional photography and graphics? Do you need copywriting services? Do you need photography or stock image sourcing? Who on your team is responsible for providing content, and by when can they have it ready?

If the answer to any of these is “not yet,” your project timeline just extended by however long the content takes — and that needs to be reflected in the proposal. A project quoted at eight weeks that waits three months for content is an 20-week project with an angry client on both ends wondering why it is taking so long.

Brand assets and design direction

Does the client have a logo? Do they have brand guidelines? Do they have a color palette, typography selections, or a brand standards document? If the answer is yes, ask them to provide those files with the intake form. If the answer is no, that is additional scope — either you are providing brand identity services or you are designing a website around a brand that does not exist yet, which is like furnishing a house before the walls are built.

For design direction, ask the client to provide three to five websites they admire and what specifically they like about each one. This is more useful than asking about style preferences in the abstract. A client who says they want something “clean and modern” might mean Apple.com or they might mean a minimalist personal blog — those are very different design briefs. Concrete examples close the interpretation gap.

Also ask about design constraints: Does the site need to match existing print materials or signage? Is there an existing brand color that must be preserved? Are there brand elements the client dislikes about their current visual identity? Knowing what they do not want is as useful as knowing what they do.

SEO goals and current search performance

If the client’s current site ranks well for important keywords, a redesign that ignores SEO can destroy that ranking overnight. If the client’s current site does not rank at all, the redesign is an opportunity to fix the technical foundation — but only if SEO is part of the scope.

Ask whether the client currently tracks search engine rankings. Ask what keywords or phrases they want to rank for. Ask whether they have a Google Business Profile, Google Search Console access, or Google Analytics installed. Ask whether they have ever done SEO work or hired an SEO consultant. And ask whether SEO services are something they expect to be included in this project or addressed separately.

This section does double duty. It sets expectations about what the project will and will not include from a search perspective, and it gives your team the baseline information needed to preserve existing rankings during the migration. A 301 redirect map is not glamorous, but a redesign that tanks a site from page one to page five costs the client real money.

Budget and timeline

Web design budgets vary by orders of magnitude. A small business owner expecting a $2,000 website and an enterprise client expecting a $200,000 web application are both “web design clients,” but they need completely different agencies, processes, and deliverables. Your intake form should ask for a budget range — not to hold the client to it, but to determine whether there is a fit before you spend time on a proposal.

For timeline, ask about the desired launch date and whether it is firm or flexible. A firm date tied to a product launch, a rebrand announcement, or a trade show is a real constraint. A “we’d like to launch in two months” from a client who does not have content ready is wishful thinking, and it is better to identify that at intake than at the midpoint review.

Ask about the approval process. Who signs off on designs? How many rounds of revisions are expected? Is there a committee that reviews the work? A project where one person has final say moves differently than a project where a five-person marketing team needs consensus on every page.

Post-launch: maintenance and ongoing expectations

This is the section that separates agencies with high client retention from agencies with constant churn. What happens after the site launches? Does the client expect you to host the site? Will they need ongoing content updates? Do they want a maintenance retainer for security patches, plugin updates, and performance monitoring? Do they expect phone support?

If you do not ask these questions at intake, the client will assume the answers — and their assumptions will probably be more generous than your standard offerings. Getting maintenance expectations on paper at intake lets you scope the post-launch relationship and price it into the proposal, or clearly communicate that post-launch support is a separate engagement.

The intake form as a qualification tool

A thorough web design intake form does more than collect project requirements. It qualifies the lead. A client who takes the time to fill out a detailed form, provides reference websites, knows their budget, and has content ready is a client who is serious about the project and ready to move forward. A client who leaves the form mostly blank, has no budget in mind, and wants a proposal by Friday is a client who has not done the thinking required to start a web project — and that is important information to have before you invest hours in a proposal.

The same principle applies in business consulting — the intake form measures how prepared the client is for the engagement, not just what the engagement is about. In both fields, client readiness is the strongest predictor of project success.