This is the first piece in our Build Week series, which walks through what generally happens during a small business website project, one stage at a time. Every project is different, and timelines stretch or shrink depending on size and scope. But the order of the work tends to be similar, and knowing what is coming makes the whole process easier for everyone involved.
Why the first week has no design
Business owners are sometimes surprised that the first week of a website project produces no mockups at all. That is intentional. Design choices made before the goals are clear tend to get redone later. The first week is about understanding the business well enough that every later decision has a reason behind it.
The kickoff conversation
Most projects begin with a kickoff meeting. It usually covers questions like these:
- What should the website help the business accomplish? More calls, bookings, sales, applications or fewer repetitive questions?
- Who are the main audiences, and what do they need to find quickly?
- What is working on the current site, and what is frustrating about it?
- Are there websites, in any industry, whose approach you admire, and why?
- Who will make decisions and give feedback, and how quickly can they respond?
- Are there dates that matter, such as a season, event or product launch?
The answers shape the scope. They also reveal early whether expectations about timeline and budget are aligned.
Gathering access
The other major task of week one is administrative: getting access to the accounts the project will touch. That typically includes the domain registrar or DNS provider, current hosting, the existing website, analytics and any tools the site connects to, such as booking, email or payment services.
The best practice is for the business to keep ownership of each account and add the web team as a user, rather than sharing a single password or letting the web team create accounts in its own name. This is a good moment to discover any accounts that are in a former employee’s or vendor’s name, because fixing that can take time.
Reviewing what already exists
If there is an existing website, the team usually reviews it closely. Which pages get the most visits? Which content is current and which is outdated? Are there pages that other websites link to, which should keep their addresses or be redirected? Are there forms, integrations or quirks that need to carry over? This review prevents losses during the transition.
What the business can do this week
- Gather logins and invite the team to the relevant accounts.
- Collect brand materials: logo files, colors, fonts and any style guidance.
- Start a folder of photos you own or have permission to use.
- Write down the questions customers ask most often. They often become the backbone of the new site’s content.
- Choose one main point of contact for feedback.
By the end of the first week, the team should have a clear written summary of goals, audiences, scope and timeline. Everything that follows builds on it. Next in the series, Build Week 2 turns these goals into a sitemap and content plan.
Preparing for the Kickoff Meeting
The kickoff goes further when the business arrives having thought through a few things in advance. None of this needs to be polished. Rough notes are fine, and honest answers are more useful than impressive ones.
- Write one sentence about what success looks like. For example: A year from now, most new customers book online instead of calling during our busiest hours. A single concrete sentence helps everyone make tradeoffs later.
- List your top three customer types. For each, note what they usually want to know first and what they do next.
- Bring examples. Collect a handful of websites you like and a few you do not. Note one specific thing about each, such as how easy the menu was or how clearly prices were explained.
- Know your constraints. Budget range, dates that cannot move, staff time available for content and any tools you are committed to keeping.
- Bring the people who decide. If an owner or partner will have the final say, they should be part of the first conversation, not only the last.
Common Week-One Mistakes
- Starting with the look. It is natural to want to talk about colors and photos first. Holding that conversation until goals are clear saves rework.
- Too many decision makers. When five people each give separate approvals, projects stall. Agree on one main contact and a small group whose input is gathered before feedback is sent.
- Underestimating access problems. A domain registered under a former vendor’s account can take days or longer to sort out. Raising it in week one keeps it from delaying launch.
- Assuming the old site has nothing worth keeping. Even a dated website often has pages that bring in visitors from search or other sites. Reviewing the numbers before deciding what to drop protects that traffic.
- Vague goals. Saying the site should look more modern is a start, but it does not tell anyone what to measure. Tie the goal to something the business actually wants to happen.
What the Written Summary Should Contain
The week-one summary becomes the reference point for every later decision. When you receive it, read it carefully and check that it includes:
- The goals of the website in plain language, ideally with a way to tell whether each goal is being met.
- The main audiences and what each needs from the site.
- What is included in the project and, just as important, what is not.
- Key dates and the feedback turnaround expected from the business.
- A list of accounts, their owners and which access is still outstanding.
- Open questions that still need answers.
If something in the summary does not match your understanding, say so now. Correcting a misunderstanding on paper takes minutes. Correcting it after design or development can take weeks.
Questions Owners Ask in Week One
How much time will this project need from us?
It varies, but the business’s biggest time commitments usually come in reviewing structure, giving design feedback and providing content. Ask your web team for a rough schedule of when your input will be needed so you can plan around busy periods.
Should we keep our current site running during the project?
Usually, yes. The new site is built separately and replaces the old one at launch. Keep the current site updated and secure in the meantime, and avoid major changes to it unless they are necessary.
What if we do not know what we want yet?
That is what discovery is for. Good questions in week one help clarify priorities. You do not need to arrive with answers, only with a willingness to talk honestly about how your business works and what your customers need.




