A clear route from roofing knowledge to a finished website.

We begin with a direct conversation about the business as it operates today: the work you want, the services you provide, the areas you cover, how enquiries arrive and what a homeowner commonly needs to know before contacting you.

We also identify genuine proof that may be suitable for publication, the source and usage rights for supplied media, and any restrictions around customer details or project imagery. Mentioning or supplying an item does not guarantee publication: proof must be genuine, current where relevant, attributable and supportable.

Initial discovery topics

• Core and secondary roofing services.
• Customer and property types, service geography and company history.
• Current referral, phone, email, Facebook and directory journeys.
• Logo, existing brand assets and social profiles.
• Genuine job and before-and-after photographs, including permission or licence to use them.
• Real project details, customer reviews and testimonials approved for publication.
• Genuine memberships, trade-body affiliations, manufacturer relationships, accreditations, guarantees, warranties, insurance and business credentials.
• Owner or team information, if the business wants it shown.
• Contact details, opening/contact preferences and preferred enquiry routes.
• Common homeowner questions and genuine points of difference.
• Useful wording from the client’s own website, leaflets, Facebook material or other content.
• What the client likes, dislikes, wants included or wants approached differently.
• Practical constraints, priorities, decision-makers and the boundaries of the agreed scope.

Discovery should never ask for account passwords or private authentication credentials. If source material is incomplete, identify the gaps and plan accurate copy or new photography; do not fill them by inventing proof, history, projects or claims, or by copying a competitor.

I translate discovery into a focused sitemap and content plan. This establishes the main visitor journeys, how services are grouped, where project evidence belongs and how calls to action lead toward contact.

I organise first-pass website copy using your source information, then flag facts, permissions or technical details that only you can confirm. Pages are included because they serve the business and visitor—not to inflate the project.

Outputs

• Sitemap and navigation.
• Page purposes and section hierarchy.
• Content requirements and first-pass organisation.
• Asset and evidence checklist.
• Agreed conversion route.

You review the website at agreed points and provide consolidated feedback. Particular attention goes to factual accuracy, service scope, locations, contact details, project permissions and any claims that require evidence.

I refine the agreed work and resolve implementation issues within scope. Review is a working stage, not an invitation to publish unverified placeholders and correct them later.

Client review checklist

• Are the services and locations accurate?
• Is the working process represented fairly?
• Are project facts and images approved for use?
• Are credentials, reviews and business claims current and supportable?
• Do contact details reach the right place?
• Is anything confidential or misleading?

Before launch, key pages, links, responsive layouts and contact routes are checked within the agreed scope. Metadata and indexing settings are reviewed so previews remain non-indexable and the canonical production site is only made indexable through a deliberate launch decision.

Launch preparation and handover are included as part of the build. Any continuing care arrangement is discussed separately once the finished website and ongoing needs are known.