What to Prepare Before Starting a Small-Business Website

Start With the Business Goal

“We need a website” describes the project, but it does not explain what success should look like.

Choose the most important job the site should do. That might be helping customers call, visit a location, request an estimate, book an appointment, order food, buy a product, submit an application, or understand a service before making contact.

A website can support several actions, but they should not all compete for equal attention. Name one primary action and one or two supporting actions. For example, a service business may want visitors to request an appointment first, call with questions second, and read about each service before choosing either path.

This decision gives the homepage, navigation, and calls to action a clear direction.

Describe the Customers and Their Questions

You do not need a complicated customer profile. Write down who usually contacts the business and what they need to know before taking the next step.

A parent comparing childcare programs may ask about ages, schedules, meals, transportation, and enrollment. A restaurant customer may want the menu, pickup hours, location, and ordering instructions. Someone hiring a contractor may need to understand the service area, types of work, estimate process, and how to share project details.

These are practical website questions. Collect them from phone calls, direct messages, emails, and conversations at the counter. The questions that repeat most often usually deserve clear answers on the site.

List Services and Products in Customer Language

Make a working list of what the business sells or provides. Use the terms customers recognize, even if the business uses different language internally.

For each important service or product category, gather the basics:

• what it is
• who it is for
• what is included
• the price or starting price, when it can be shared
• the service area, schedule, or availability
• the next step a customer should take

This list does not have to include every variation on the first day. Prioritize what customers ask for now. A long catalog, detailed menu, or specialized service can be organized in phases when the full scope would delay the most useful version of the site.

Outline the Pages Around Real Decisions

Most small-business websites begin with a few familiar areas: a homepage, services or products, an about page, and a way to contact the business. Some need a menu, online store, booking page, application, project gallery, FAQ, or separate location pages.

Do not choose pages only because another website has them. Connect each page to a customer question or business action. If two pages would repeat the same information, they may work better as one. If a service has several steps, prices, or requirements, it may deserve its own page.

The page list can change during the project. A useful outline simply gives everyone something concrete to discuss.

Gather Accurate Business Details

Small details become highly visible once a website is public. Before design begins, collect the information that should remain consistent across the website and other business profiles:

• official business name and preferred public name
• address, service area, phone number, and customer email
• current hours and holiday or seasonal differences
• team names and titles that may appear publicly
• accepted payment methods or appointment requirements
• return, cancellation, shipping, privacy, or other customer-facing policies that apply
• professional licenses, certifications, or affiliations only when they are current and may be stated publicly

Mark anything that is not confirmed. It is better to label a detail as pending than to publish a guess that customers may rely on.

Collect the Best Materials You Already Have

Send the original logo files if they are available, not only a screenshot copied from social media. Gather current photographs of the storefront, interior, team, products, food, projects, or services that accurately represent the business. Confirm that the business has permission to publish each image.

Also collect any existing brochure, menu, price list, application, service description, review, or social post that contains useful source material. These items do not have to become website copy word for word. They help the provider understand what the business already says and where information may conflict.

Organize files with plain names such as `storefront`, `owner-name`, or `signature-service` instead of leaving dozens of files named with camera numbers. A short note explaining what each image shows can prevent the wrong photo or caption from being used.

Know Who Controls the Technical Accounts

A website project may involve a domain name, business email, hosting, analytics, a Google Business Profile, social accounts, payment tools, or an existing website platform.

Write down which accounts exist, who owns them, and which email address receives access or renewal notices. Do not place passwords in a shared planning document or ordinary email. When access is needed, use a secure transfer method or invite the provider through the platform's user or collaborator settings.

Confirming ownership early matters most for the domain. A finished website cannot use the intended address if nobody can reach the account that controls it.

Decide Who Reviews the Work

Projects slow down when feedback arrives from several people with no clear decision maker. Choose one person who can approve the structure, wording, images, and final launch. Other team members can contribute, but someone should be responsible for resolving conflicting suggestions.

It also helps to decide who will supply missing content and when. If the owner is gathering photos, a manager is confirming services, and an accountant is reviewing a policy, write that down. The website provider can then plan around real dependencies instead of waiting without knowing what is missing.

Bring Questions for the Website Provider

Preparation works both ways. The provider should be able to explain the process clearly.

Ask what the quoted scope includes, who writes or revises the content, how many review rounds are planned, and what could change the price or timeline. Confirm how the site will work on phones, how accessibility and search basics are handled, who owns the domain and finished materials, and what hosting, maintenance, updates, and support look like after launch.

If the answers depend on the project, they should still be documented before work begins.

Start With What Is Confirmed

Waiting for perfect content can keep a useful website from moving forward. Start with what the business knows today and separate it into three groups: confirmed, needs review, and not ready yet.

That makes uncertainty visible without turning it into an obstacle. The first version of a website can focus on the services, information, and customer actions that matter now. New pages, photographs, or features can be planned when the material is ready and the business has a reason to add them.

A good first conversation should help organize the remaining questions. You are preparing the business context, not doing the provider's entire job before asking for help.