Skip to main content Scroll Top

Build Week: What the Business Is Asked to Provide, and When

Throughout our Build Week series, one theme keeps returning: the business’s part of the work. Website projects rarely slow down because of design or code. They slow down while waiting for content, access or decisions. Knowing in advance what you will be asked for, and roughly when, makes it far easier to keep a project on schedule.

Before kickoff

Even before the first meeting, a little preparation helps:

  • A short list of goals for the website, in your own words.
  • Notes on what you like and dislike about your current site.
  • A few example websites you admire, with a sentence on why.
  • The name of the person who will coordinate feedback and approvals.
  • Any important dates, such as a busy season or event.

During discovery and planning

In the early weeks, the team typically needs access and background:

Advertisement
  • Account access. Domain registrar or DNS provider, current hosting, the existing website, analytics and connected tools. Ideally, add the team as users rather than sharing your own passwords.
  • Brand materials. Logo files in high quality, preferably vector formats, plus any color, font or style guidance.
  • Business details. Services or products, service areas, hours, staff and anything that makes the business distinctive.
  • Customer questions. The questions you hear most often. These shape page content.

During design and development

Once the structure is approved, content becomes the priority. This is the stretch where preparation pays off most.

  • Written content. Text for each page, or raw notes if a writer is part of the project.
  • Photos. Images you own or have permission to use, such as your team, location, work and products. Original photos usually serve a business better than generic stock.
  • Product or service data. For stores, a spreadsheet with names, prices, variations, SKUs, weights and descriptions.
  • Policies. Privacy policy, terms and store policies, reviewed by your lawyer as appropriate.
  • Third-party details. Booking systems, payment providers and email marketing accounts that need connecting.
  • Timely feedback. Consolidated comments on sitemaps, wireframes and designs within the agreed review windows.

Before and after launch

In the final stretch, the business is asked to:

  • Review every page and approve the final content.
  • Test key tasks on real phones and report issues clearly.
  • Confirm a launch date and be available that day for questions.
  • Attend training and decide who will update the site going forward.
  • Confirm ownership of every account and file the documentation.

A simple way to stay ahead

Create one shared folder for the project at the start, with subfolders for brand files, photos, page content and policies. Add to it as you go. When the team asks for something, it is often already there. That single habit can shorten a project by weeks and makes the finished website more truly yours.

A Shared Folder Structure You Can Copy

A project folder works best when everyone knows where things go. A simple structure might look like this:

  • 01 Admin: the project summary, agreement, timeline and a list of account access granted.
  • 02 Brand: logo files in every format you have, color and font notes and any style guide.
  • 03 Photos: subfolders for team, location, work or products and events, plus a note on where each set came from and who holds the rights.
  • 04 Content: one document per page, named to match the sitemap.
  • 05 Products or services: the product spreadsheet or service descriptions.
  • 06 Policies: current privacy, terms, returns and accessibility pages, with notes on legal review.
  • 07 Feedback: consolidated comments for each review round.

Numbering the folders keeps them in a sensible order. Naming page documents to match the sitemap makes it obvious at a glance which pages still need content.

Advertisement

Tips for Gathering Each Item Well

Logos

Look for the original files from whoever designed your logo. Vector formats scale cleanly to any size. If you only have a small image pulled from an old website, mention it early, because recreating a logo takes time.

Photos

Choose the largest, sharpest version of each image you have. Phone photos can work well when they are well lit and in focus. Avoid images taken from other websites or social media accounts unless you have clear permission to use them.

Written content

Write the way you talk to customers. Start with the questions people ask and answer them plainly. If writing is hard, record yourself explaining a service and have it transcribed. The rough version can be shaped later.

Product data

Use one row per product or variation, with consistent column names. Check that every item has a unique SKU and an accurate price and weight. Clean data now prevents shipping and inventory problems later.

Common Reasons Projects Wait on the Business

  • Content assigned to someone already overloaded. If the person writing page content also runs the front desk, it will slip. Protect a little time on their calendar each week.
  • Waiting for everything to be perfect. Send drafts as they are ready. Content can be refined during review.
  • Feedback scattered across email, texts and calls. One place for feedback keeps nothing lost.
  • Decisions without a decider. When nobody is sure who approves, approvals stall. Name that person at kickoff.
  • Access requests left for later. Account access often takes longer than expected. Grant it early.

A Quick Readiness Check

Before each new stage, ask yourself:

  1. Has the team received everything it asked for at the last stage?
  2. Do we know what will be asked of us next, and when?
  3. Is the person responsible for each item aware and available?
  4. Are there any upcoming busy periods that will slow our responses, and has the team been told?

Questions Owners Ask

What if we cannot provide some content on time?

Tell your web team as early as possible. Often a page can be simplified, a placeholder approved or the item scheduled shortly after launch. Surprises late in the project are much harder to work around.

Can the web team write our content?

Some projects include writing and some do not. Ask at the start. Even with a writer, the business still provides the facts, details and review, because nobody knows your work better than you do.

Who should be our main point of contact?

Choose someone who knows the business well, can gather input from others and has enough time to respond within the agreed review windows. That person does not need technical skills. They need the authority to make decisions or quick access to whoever does.

Latest stories

View all
Our clients