What to Prepare Before a Website Project

You do not need finished copy or a detailed design brief to start a website project. You do need enough information to decide what belongs on the site, who it is for, and who will approve the work.

Write down one main job for the website

“We need a better website” leaves too much open. Try a task a visitor should be able to complete: compare three services, browse a product catalog, or find the right person to request a quote.

For example, an equipment maintenance company might want visitors to find its service area, see which machines it handles, and send a service request. Those details help decide the pages and contact flow before anyone chooses a font.

If several goals compete, choose the one that matters for the first launch. Keep the others in a separate list so they do not quietly expand the scope.

Gather what already exists

A folder of useful source material is easier to work with than information scattered across chat messages. Start with:

• Business information: the name, a plain description of what you do, service locations, and public contact details.
• Products or services: current lists, specifications, brochures, and anything customers ask for before buying.
• Visual material: the logo, brand files, and photos you have permission to publish.
• The existing website: its URL, pages worth keeping, and things that are difficult to use or update.

Label outdated files and mark anything that cannot be published. If there are two price lists or conflicting product specifications, identify which one is current. Do not send passwords in the content folder; access can be arranged separately through the relevant service.

Bring references with a reason

Two or three reference sites are enough to start a conversation. Explain what you like about each: the navigation, how product information is arranged, or how little text appears on the homepage.

Also point out things you want to avoid. “I like the simple service list, but the animated introduction feels distracting” is more useful than “make it modern.” References guide the discussion; they do not supply copy or images to reuse.

Choose a person who can approve the content

Someone needs to confirm names, descriptions, photos, and priorities. If several people give feedback, collect their comments into one agreed response before sending it back.

Ask who will manage the site after launch as well. A team that needs to update product details every week may need a different setup from an owner who changes the contact number once a year. The CMS decision belongs in the scope discussion.

Agree on what launch includes

Before work starts, confirm the page list, who writes and checks the copy, revision rounds, domain and hosting responsibilities, and support after launch. Share a fixed deadline early, along with the reason for it.

If some material is missing, decide whether it blocks launch or can be added later. A missing service description may block a service page; a second set of team photos may not. That distinction keeps the first version achievable.

A short brief you can copy

Fill in the following before your first project discussion. “Not decided yet” is a useful answer when something needs to be worked out together.

• Business and audience: what you sell, who buys it, and which locations you serve.
• Main visitor action: request a quote, browse products, book a meeting, or another specific task.
• Pages for launch: list each page and the content already available for it.
• Content updates: what changes, who changes it, and how often.
• Approval: who checks business details and gives the final sign-off.
• Constraints: target launch date, budget range, and domain or hosting arrangements.

Send this with your existing website or reference links through the project contact page. It gives the scope discussion a concrete starting point.