Starting aWebsite Project

Start with a straightforward explanation of what you do. It does not need to sound like finished website copy.

• How your business works
• What makes the business different
• Why the website project is happening now

Decide what the website needs to help the business achieve.

Here are some examples:

• Generate better or more relevant enquiries
• Explain a complex offer more clearly
• Build credibility with a new audience
• Support sales, recruitment or growth
• Make content easier for your team to manage

Describe the people who need to use the site, what brings them there and what they need to understand before they can take the next step.

• Primary and secondary audience groups
• The questions they are likely to arrive with
• Any objections or concerns the site should answer
• The action you want each audience to take

A rough list is enough at this stage. I’ll help turn it into a clear site structure and identify anything that is missing or unnecessary.

• Pages you know the site will need
• Important services, projects, people or resources to feature
• Forms, booking tools, downloads or other interactions
• Content that needs different access or permissions

If possible, share a few relevant examples of websites that stand out for you.

• Competitors or comparable organisations
• Visual references that feel appropriate
• Patterns or conventions your audience will expect

Gather the current assets in their best available formats. If the brand needs to change, it is better to identify that before website design begins.

• Logo files, preferably in vector format
• Brand guidelines, colours and typography
• Licensed font files and usage information
• Existing templates or materials that show the brand in use

You do not need perfect copy. A useful draft with the right information is enough to begin shaping the content.

I’ll help organise, edit and refine the essential copy included in the project scope. Substantial new writing can be scoped separately when needed.

• Key messages and page headings
• Service, project or product information
• About, team and credibility content
• Calls to action and contact information

Review the current site before carrying everything forward. A new website is a good opportunity to remove weak, outdated or duplicated material.

• Content that must be retained
• Pages or files that can be retired
• Posts, projects or records that need migrating

Provide original, high-resolution files wherever possible. Avoid sending images copied from a website, presentation or social-media post.

• Photography and image libraries
• Illustration, diagrams, video or animation
• Captions, credits and alternative text where relevant

If possible, provide website analytics data from your existing website.

A simple shared folder saves time (Google Drive, Dropbox or similar). Group files by page or subject, use clear filenames and remove obsolete versions before handover.

• One agreed location for project files
• Clear folders for copy, brand assets and media
• Descriptive filenames rather than camera-generated names
• A clear indication of approved and working material

Nominate one person with responsibility for day-to-day communication, gathering internal input and confirming decisions.

• Coordinates access to people and information
• Consolidates comments from the wider team
• Confirms priorities and final decisions
• Keeps internal stakeholders aware of the schedule

Feedback works best when it is collected, discussed internally and delivered as one clear response at the agreed stage.

• Identify who needs to review each stage
• Allow time for internal discussion
• Combine comments before sending them
• Keep feedback tied to the agreed goals and audience

Some access may only be needed near launch, but identifying the correct account owners early avoids last-minute delays.

• Domain registrar and DNS access
• Current website and hosting access
• Analytics, Search Console and tag-management accounts
• Accounts for any services that connect to the website

Share fixed launch dates, events, holidays and periods when decision-makers will be unavailable. The project plan can then account for them from the beginning.

Work is scheduled once the project agreement is signed and the initial 50% payment has been received.

The remaining 50% is paid when the website is approved and ready to launch.