The Short Version
The list of things a web designer genuinely needs from you is shorter than most onboarding packets suggest. What matters is not the length of the list — it is that two or three items on it run on someone else's clock, and those are the ones that decide whether your site launches in two weeks or two months.
So this is grouped by urgency rather than by category. Five things block the build. Four things need to be started on day one because other people control them. And a handful of items you have probably been told to prepare are not needed at all.
Group One: The Five Things That Block a Build
Your business facts, exactly as you want them published. Trading name, phone number, the email address inquiries should land in, your service area or street address, and your hours. These sound trivial and they are not: they go into page copy, into the structured data search engines read, and into your Google Business Profile, and they need to match in all three. If your business name is one thing on your license and another on your sign, tell us which one is going on the website.
Access to the domain — not the domain name, the login. Knowing you own yourbusiness.com is not the same as being able to change where it points. More on this below, because it is the single item most likely to hold up a launch.
Your logo in its original file. What you want is the vector original: SVG, AI, EPS, or a PDF that was exported from design software. Those scale to any size without going fuzzy. A 400-pixel PNG lifted off your current site will look soft the moment it appears in a header on a large screen. If the original is genuinely gone, say so early rather than searching for three weeks — it is a solvable problem and a short conversation.
Photos of the real thing. Your work, your premises, your team, your vehicles. These do not need to be professional, and a clear phone photo of actual work beats a stock image of a stranger every time. Send the biggest versions you have, straight off the camera or phone if possible. Compressing an image later is easy; recovering detail from a compressed one is not.
What you do and who for, in your own words. Two paragraphs typed into an email is plenty. Not marketing copy — just the plain version, including the things you would say on the phone. This is the raw material for everything written on the site.
That is the blocking list. Everything else can be gathered while the build is already moving.
Group Two: Start These on Day One
These four are not difficult. They are slow, because each one depends on somebody who is not you or us.
Your domain registrar login. This is the one that bites. Domains are frequently registered years ago by a former employee, a cousin, or an agency that has since been fired, with the two-factor codes going to a phone number nobody has. Recovering an account like that is a support-ticket process measured in days. Find out today whether you can log in and change a DNS record. If you cannot, starting the recovery now costs you nothing and starting it on launch day costs you the launch.
DNS, including your email records. Pointing a domain at a new site means editing DNS, and the records that route your email usually live in the same place. Changing one without carrying the other across is how a company loses its email for an afternoon. This is routine work when it is planned and unpleasant when it is improvised, which is why it belongs in week one rather than at the end.
Your Google Business Profile. For a local business this is at least as valuable as the website, and ownership needs to be yours rather than a previous marketing company's. Verification sometimes involves a mailed postcard, so it cannot be rushed.
Analytics access. Search Console, Google Analytics and Bing Webmaster Tools each need read access granted by whoever administers them. We send you the exact accounts to add and where to click once your project starts — but if those accounts are currently controlled by a provider you are leaving, request the handover early.
If you do nothing else after reading this page, check whether you can log into your registrar.
Group Three: What You Do Not Need to Prepare
Testimonials. Where a business has public Google reviews, we pull the real ones through the Google Places API during research and use them as written, with the reviewer's name and a link back to the source. A review someone can click and verify carries more weight with a reader than a quote a business supplies about itself. Don't go collecting praise before a build.
Finished copy for every page. This is the single most common way a website project stalls for months — the business decides it will write all twenty pages first, and then it has a day job. Send us the raw version described above instead. Turning that into pages that also target the right search terms is a separate craft, and it is work we do rather than homework we set. Nor does a site need to arrive complete: pages get added after launch as part of the monthly SEO content updates, which is what website automation means in practice, and that is the normal shape of a site that grows.
A new logo. If yours is dated, that is a worthwhile project and it is not this project. A website build can use the logo you have, and a rebrand done in parallel tends to delay both.
Wireframes, sitemaps or a page-by-page spec. If you have strong opinions about structure, send them. If you do not, planning the page structure around what people actually search for is the job you are hiring for.
Stock photography. We would rather have six honest photos than sixty polished ones of other people's businesses.
Sending Files: The Boring Details That Save Time
Our client portal takes images (JPG, PNG, WebP, AVIF, SVG, GIF, BMP, TIFF), documents (PDF, DOC/DOCX, XLS/XLSX, PPT/PPTX), plain text and Markdown, and video (MP4, MOV, WebM, AVI), up to 300MB per file and 300 files per client. Uploads get labeled as you go — Logo, Brand Guidelines, Content, Photos, Media, Documents, Inspiration, Screenshots or Social Media — which is more useful than it sounds when forty files arrive in one afternoon.
Three habits that make the difference:
- Originals, not copies. Not a screenshot of a photo, not an image pasted into a Word document, not a logo exported at the size your old site happened to use.
- One batch beats a trickle. Assets arriving over three weeks means three rounds of rework.
- Anything you hate is as useful as anything you like. A link to a competitor's site with "not this" attached saves a whole revision round. That is what the Inspiration label is for.
The Thing That Actually Delays Projects
It is usually not the assets. Our builds take one to two weeks on our side, and when a project runs longer, the cause is nearly always either an access problem from group two or a decision nobody has made.
Decisions are the quieter one. A project where three people all need to approve the homepage moves at the pace of the slowest calendar. Naming one person who can give a final yes does more for your timeline than any amount of file gathering. Our guide to how long a website takes goes through the rest of the timeline arithmetic, and the launch checklist covers what gets verified at the other end of the project.
If You Are Replacing an Existing Site
Three extra things, and one piece of good news.
The good news: the images and video on your current site can usually be pulled down and reused, so you do not have to re-source your own photos. Tell us at the start if you would like that done.
The three extra things. First, a list of your current pages, especially any deep ones that people link to or that rank — every one of those URLs needs either an equivalent on the new site or a redirect, which is the step that protects the rankings you already have. Our website migration checklist covers how that is handled. Second, access to the old site or at least its hosting, even if you never intend to touch it again. Third, clarity on who owns what — if a previous provider holds the domain, the content or the hosting account, sort that out before anything is built. We have written up who actually owns your website and how to move to a new developer for exactly that situation.
The Checklist, in Order
- Today: confirm you can log into your domain registrar. Start recovery if you cannot.
- Today: confirm you control your Google Business Profile, and start verification if not.
- Week one: request analytics access handover from any provider you are leaving.
- Week one: send business facts — name, phone, inquiry email, service area or address, hours.
- Week one: send the logo original and your real photos, in one batch, at full size.
- Week one: type two paragraphs on what you do and who for, plus the questions customers actually ask.
- Replacing a site: send the page list and flag anything that currently ranks.
- Throughout: name one decision-maker.
Six of those eight are quick. The two that are not are items one and two, which is why they are at the top.
If you would rather talk through what applies to your situation before gathering anything, that is what a free consultation is for.