All posts
Pricing & hiring

Website Requirements Checklist Before You Talk to Any Agency

A website requirements checklist to finish before you talk to any agency: goals, audience, pages, content, platform, budget and decisions, to cut discovery time.

By Mehdi Hassan7 min read

The short answer

A website requirements checklist covers what to prepare before hiring a web design agency: one clear goal, your audience, a page and template list, who writes the copy, brand assets, integrations, platform and editing needs, access to accounts, a budget range, a deadline and a named decision-maker. Preparing these cuts discovery time and makes quotes far more accurate.

Key takeaways

  • Agree requirements internally before any agency call, or you'll pay the agency to host your debate.
  • List templates and CMS collections, not just page names, so quotes can be compared.
  • Decide who writes the copy before asking for quotes. It's the biggest swing in price.
  • Gather logins for domain, DNS, analytics and CRM early. Missing access is a common, avoidable launch delay.
  • Name one decision-maker. Feedback by committee is a common cause of slipped schedules.

Part of Website Redesign RFP Template (Free, Startup-Friendly)

What do you need to prepare before hiring a web design agency?

Before hiring a web design agency, prepare answers on your goal, audience, pages, content, brand, integrations, platform, access, budget, timeline and decision-making. You don't need a perfect spec. You need the team to agree on the basics, so the agency can spend its time on how to build the site rather than on what the site is for.

This website requirements checklist is an internal prep list. It's not something you send as-is. Once it's done, turn the answers into a web design brief for one agency or a website redesign RFP for several. Either way, the agencies you talk to will quote faster and closer to the real number.

The website requirements checklist

Work through the list in order. Each item has a one-line test of whether you've really answered it.

  1. One main goal. Can you finish the sentence: the site succeeds if more [visitors] do [action]?
  2. Audience. Can you name the primary buyer's role and company type in one line?
  3. Traffic sources. Do you know roughly where visitors come from today and where you want them from?
  4. Current problems. Have you listed three to five specific issues, with evidence from analytics, sales or customers?
  5. Page list. Have you listed every page and marked each one must-have or nice-to-have?
  6. Templates and CMS. For repeating content (blog, case studies, careers), have you listed the template and a rough item count?
  7. Copy ownership. Have you decided who writes copy: you, the agency, or a mix?
  8. Existing content. Do you know what can be reused, what needs rewriting and what's missing?
  9. Brand assets. Do you have the logo files, colors, fonts and guidelines, and are they staying?
  10. Integrations. Have you listed forms, CRM, scheduler, analytics, chat and any product data?
  11. Platform and editing. Do you know who will edit the site after launch and how often?
  12. Accounts and access. Do you have logins for the domain registrar, DNS, hosting, analytics and CRM?
  13. Legal and compliance. Do you know your privacy, cookie and accessibility requirements?
  14. Budget range. Have you agreed a range you can actually spend?
  15. Deadline. Is there a fixed date, and what's the reason for it?
  16. Decision-maker. Is one person named as the final approver?

Which website requirements change the quote most?

The requirements that change a website quote most are copy ownership, the number of unique templates, CMS complexity and integrations. Get those four right and agency quotes will land much closer together.

Requirement

Why it moves the price

How to make it precise

Copy

Writing is a large share of the work, and some quotes exclude it

Say who writes each page

Unique templates

Each distinct layout is designed and built separately

Count layouts, not pages

CMS collections

Each collection needs fields, templates and editing setup

List collections and fields

Integrations

Each tool adds build and testing time

List tools and what data flows where

Migration

Moving old content and redirects is real work

Count items and URLs

Copy is usually the biggest single swing. Several landing-page cost sources note that two quotes can differ tenfold depending on whether strategy and writing are included. Our website statement of work template shows how to write copy into the scope as its own line item, so there's no doubt later.

How do you prepare content and copy before the project?

Prepare content by gathering raw material, not by writing final pages. Agencies that write copy work best from notes, recordings and customer language. Agencies that don't write copy need final text, and you'll need to plan time for that.

  1. Collect customer language

    Pull quotes from sales calls, reviews, support tickets and onboarding interviews. These are the best raw material for copy.

  2. List proof you can use

    Testimonials with permission, customer logos you're allowed to show, ratings and case studies.

  3. Audit existing pages

    Mark each current page keep, rewrite or delete, especially pages that rank in search.

  4. Gather visuals

    Product screenshots, team photos and any illustration or photography you own.

  5. Decide who writes

    If the agency writes, give them access to the material above. If you write, schedule the time now.

If the site is mostly one conversion page, use our landing page brief template. If a new identity is part of the project, prepare a brand design brief alongside this checklist.

How should you set budget and timeline requirements?

Set budget as a range you can actually spend and timeline as a target date with its reason. Both help an agency propose the right depth of work, and both are more useful than a single number with no context.

For context, typical agency project ranges we see quoted run from about $5k to $80k+ for Webflow builds, $3k to $28k for Framer builds and $20k to $120k for Next.js builds, and they vary widely with scope and whether copy is included. If you're working to a tight budget, our list of website agencies for early-stage startups under $10k is worth reading first.

For example, suppose your deadline is a product launch

Hypothetical example: a startup wants a new site live for a launch in eight weeks. The checklist shows copy isn't written, three integrations are needed and nobody has the DNS login.

The realistic options are to reduce scope for launch day, for example a strong homepage and pricing page first with the rest following, or to move the date. Knowing this before talking to agencies means you can ask each one how they'd phase it, rather than discovering the gap mid-project.

What happens after the website requirements checklist?

After the checklist, you write a brief or RFP, talk to a shortlist, compare proposals and sign a statement of work. Good preparation makes each step shorter. Our agency evaluation scorecard helps at the comparison stage, and the website launch checklist covers the other end of the project.

At Designify, a completed checklist means the intro call goes straight to the trade-offs: what the site must say first, which pages matter most and what to phase. Delivery timelines are scoped on that call. If you'd rather test the team before committing, our $1,000 trial week is one week of design and development on your real project.

Frequently asked questions

Do I need a full requirements document before talking to an agency?
No. A short checklist of agreed answers is enough for a startup site. Formal requirements documents suit large organizations with procurement processes. What agencies need is clarity on the goal, audience, scope, copy ownership, budget and decision-maker. A good agency will help you fill gaps, but only if the core decisions are already made internally.
Should I talk to agencies before deciding on a platform?
You can, as long as you know your editing needs. Explain who will update the site, how often and what they'll change, and let the agency recommend a platform. If you already have a strong reason to choose one, such as an existing team skill, state it as a requirement. Be wary of agencies that recommend the only platform they use without explaining why.
What if my team disagrees on the requirements?
Settle it before hiring, or name one person who decides. Disagreements about audience or goals don't go away once an agency is involved; they show up as conflicting feedback and extra rounds. A short internal meeting working through the checklist, with a named final approver, resolves most of them faster and cheaper than mid-project debates.
How much detail do agencies need about integrations?
Enough to know which tools are involved and what data moves between them. For example: the demo form sends leads to HubSpot and books a call in a scheduler. Agencies don't need API documentation up front, but they do need to know about anything unusual, such as pulling live product data or gating content behind a login, because that changes the build significantly.

· CEO & Design Director

Copywriter, designer and developer, and founder of Designify Studio. Over five years, 60+ projects across 14+ industries, for startups that have raised $300M+.

Want us to do this for you?

We take craft seriously over at Designify Studio. We do deep research and do what we do best - pay attention to the smallest details and make sure we speak to the right audience.

Schedule Call