Teams often start a website with a visual reference and a list of pages copied from a competitor. The site becomes difficult the moment someone needs to add a service, a location, or a news item that the template did not imagine.
Start with the actions
Write down what a visitor should be able to do: understand the offer, trust the company enough to enquire, or complete a purchase. Every page should serve one of those actions or help a person choose among them.
Name the content types
Services, locations, articles, and people are usually separate types. If they are all free-form pages, editors will invent a new layout each time. A small set of templates is easier to keep consistent.
Decide who edits
Before development, agree who may publish, who may only draft, and which areas require a developer. That decision becomes the permissions in the CMS.
Plan the address
URLs should survive a redesign. Agree the main paths early, and keep a redirect list if an older site is being replaced.
A plan of this kind is short. It is also the difference between a site your team can run and a site that needs a project for every paragraph.