Website Project Checklist: What to Prepare Before Kickoff

TL;DR: Prepare these 10 items before a website project starts:

1. Written goals and 1 primary metric
2. 1 empowered decision-maker
3. Near-final copy for every page
4. Brand assets in source formats
5. 3 to 5 reference websites
6. Domain, DNS and account access
7. A content inventory and redirect list
8. Your integrations list
9. Legal pages
10. A budget range and a real deadline

As a Webflow lead developer I ask every client for these 10 things before kickoff. Stalled projects are almost never stuck on design or development. They are stuck waiting on one of these 10 items.

Why does preparation decide your timeline?

Build time is the predictable part of a website project. When I scope a Webflow build I can estimate design implementation, CMS setup and QA within about 20%, and a standard marketing site runs 2 to 4 weeks of development.

Waiting time is the real variable

What I cannot estimate is how long it takes to receive final copy or track down whoever controls the DNS. Waiting time, not work time, is what pushes launches back, and it routinely adds 2 to 6 weeks to an otherwise clean project.

The website project checklist: 10 things to prepare

The checklist below is ordered the way I ask for it: decisions first, content second, technical access last. You do not need all 10 items perfect on day one, but you should know who owns each one.

1. Written goals and one primary metric

Write down what the site must achieve in 1 or 2 sentences, then pick 1 primary metric. When a design decision gets debated in week 3, the goal settles the argument. Sites built to "look modern" get redesigned; sites built to hit a metric get measured and improved.

2. One empowered decision-maker

Feedback can come from a group, but approval has to come from 1 person. What I see go wrong most often is committee sign-off: 4 or 5 stakeholders, 5 opinions, and a homepage reworked 3 times in revisions. Name the approver before the project starts.

3. Near-final copy for every page

Copy is the single most common cause of delay across both agency and direct client projects. Design without real copy is guesswork, because headline length, section order and page structure all depend on the actual words. Each page needs real headlines and real paragraphs, not "content goes here".

4. Brand assets in source formats

Collect your logo as an SVG or another vector format, not a screenshot pulled from the old site. Add your exact brand colors as hex values plus the names and licenses of your fonts. A 1-page summary of colors, fonts and logo rules is enough if no full brand guide exists.

5. Three to five reference websites

Pick 3 to 5 sites and note what specifically you like about each one. "Make it like Apple" is not a brief. "I like how this site explains a technical product in plain language" is a brief, and it often saves a full revision round worth several days.

6. Domain, DNS and account access

Find out where your domain is registered and who can log in, weeks before launch. In my projects the DNS login is the item clients most often cannot locate, because it was set up years ago by someone who has since left.

Ownership of the build matters just as much. Webflow's Agency or Freelancer guest role lets your Workspace invite up to 2 guest teams free, or 10 on Enterprise, so the site can live in your account from day 1 (Webflow Help Center).

7. A content inventory and redirect list

If you are replacing an existing site, list every page and mark what to keep, merge or drop. Note which pages bring search traffic so they get proper 301 redirects, because unredirected URLs are the fastest way to lose rankings at launch.

Your inventory also shapes the CMS. Webflow allows 40 Collection lists per page, 10 nested lists and 100 items per list without pagination (Webflow Help Center), so a 500-item archive needs planning rather than improvisation. I covered the approach in Webflow CMS architecture basics.

8. Your integrations list

Write down every tool the site must talk to. Integrations are cheap to plan and expensive to retrofit, and a form that needs to reach your CRM changes how that form gets built. The 5 categories worth listing:

1. CRM: HubSpot, Pipedrive, Salesforce or similar
2. Email marketing: whichever platform owns your lists
3. Analytics: GA4 plus any product analytics tool
4. Booking or scheduling: Calendly, Cal.com or an embedded tool
5. Payments: Stripe or a full ecommerce platform

9. Legal pages

Privacy policy, terms and cookie consent requirements depend on where your customers are, not where you are. Have the text ready or assign an owner. These 3 pages are small, but when compliance is a requirement they block launch as effectively as a missing homepage.

10. A budget range and a real deadline

Share both, even when they are uncomfortable. A developer who knows the budget can tell you what fits inside it instead of quoting blind, and a custom Webflow marketing site typically lands between $3,000 and $25,000.

Budget the platform separately from the build. Webflow's Basic Site plan is $15 per month billed yearly with 300 static pages, and Premium is $25 billed yearly with 20,000 CMS items and 40 Collections (Webflow).

What happens if you skip the preparation?

The project still starts, and that is the trap. Kickoff feels fine, design begins against placeholder text, and the first 2 weeks feel productive.

The three failures that follow

1. Real copy arrives and does not fit the layouts. Sections get rebuilt, costing a revision round.
2. The missing DNS login surfaces during launch week. A 10-minute task becomes a 3-day hunt.
3. An unmentioned stakeholder appears in final review. Approved work reopens with days left.

None of those 3 outcomes are rare events. They are the default result of skipping the checklist, and each costs more to fix than preparation would have cost.

What should your developer take over from here?

Your developer should own everything beyond the 10 items above: sitemap proposals, design direction, CMS architecture, performance, SEO fundamentals and the launch process.

The standard to hold them to

Performance is measurable, so agree a target. Google's "good" Core Web Vitals thresholds are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, and Cumulative Layout Shift at 0.1 or less, at the 75th percentile of real visits (web.dev).

If you are still choosing who to work with, my guide on how to hire a Webflow developer covers vetting and rates. And if you have a project coming up and want a developer who runs this process by default, reach me through developmentrocha.com. Send the checklist items you already have and I will tell you honestly what is missing.