What changes the cost of a roofing website?

Two quotes for a roofing website can cover very different jobs. One may be a small site built around your existing copy and photos. Another may include new service pages, a move from your old website and connections to your CRM.

Before comparing the totals, compare the work. A useful proposal tells you what will be planned, written, built and tested, what you need to supply, and what you'll keep paying for after launch.

Here are the main factors behind that scope. The examples below are starting points for comparison, not fixed Goliath packages or price estimates. Pricing depends on an agreed brief.

Compare three kinds of roofing website project

A focused lead-generation site

You need clear service information, coverage, genuine proof and working call and estimate paths. You already have suitable photography and approved copy, and the office has a straightforward way to handle new leads.

The main work is organising that content, designing and building the pages, setting up forms and testing the experience. Even a small site needs mobile checks, useful error messages and a confirmed destination for each lead.

A site with deeper service and project content

You need to explain several roofing services, different property types or a substantial body of completed work. The existing content may be thin, out of date or scattered across documents.

The extra work includes interviews, writing, selecting and preparing photographs, organising project pages and making future updates manageable. Page count is part of the picture. So is the amount of original work each page needs.

A site connected to business systems

You want website requests to enter a CRM or field-service system, reach an assigned person and trigger an appropriate acknowledgement or follow-up task.

That adds work: checking platform capabilities, mapping information, handling duplicates, testing failures and agreeing who maintains the connection. Ask to see what happens when something goes wrong as well as how the successful demonstration works.

1. The number and purpose of the pages

Ask for a page list with a purpose beside each item. “Ten pages” tells you little if one proposal includes ten original service explanations and another includes the homepage plus several short supporting pages.

Think about the decisions visitors need help with. Repairs and full replacements may need different explanations. Residential and commercial buyers may need different proof. Avoid adding pages just to repeat the same copy with another place name.

Separate launch essentials from later additions. A smaller site with useful content is easier to get ready than a large one waiting for information nobody has agreed to supply.

2. Copy, photographs and project evidence

“Content included” can mean formatting your existing text or researching and writing every page. Find out who interviews your team, drafts the copy, checks technical details and approves the finished wording.

Give photography an owner too. Are you supplying project images, arranging a shoot or licensing supporting images? Who confirms permission to show customer properties and feedback?

Tell the agency what's ready and what still needs work. A folder of unlabelled roof photographs is different from a set of approved project stories with captions. Content preparation belongs in the scope and schedule, even when you do it yourself.

3. Design, editing and review rounds

Find out how the design will be developed and which parts can be reused. A tailored layout, a modified template and a site with many unique page types involve different work. Ask to see what's being proposed rather than relying on a label such as “custom”.

Agree how feedback works: who makes the final decision on your side, when you review the work and what happens if the brief changes. A new service section requested near launch can affect writing, design, development and testing together.

Check what your team can edit afterwards. If you plan to publish project updates yourself, include any training and instructions you'll need in the quote.

4. Moving an existing website

A rebuild should start with an inventory of useful existing pages, content and contact paths. Which page addresses will stay the same? What happens to pages that move or disappear?

For URL changes, Google's site-move guidance covers mapping old URLs to new ones, redirects, updated links and post-move checks. It also notes that search visibility can fluctuate during a move.

Make sure the proposal says who handles those tasks, who checks them after launch and what will be monitored. A fresh design doesn't automatically preserve everything useful about the old site, and a migration shouldn't come with a ranking guarantee.

5. Forms and lead-handling connections

Write down the path a lead should take. For example: estimate request, saved contact record, office notification, assigned employee and an accurate acknowledgement.

A form that emails one inbox takes different work from a connection that updates customer records and coordinates follow-up. Check the actual software, account plan and supported features before accepting an integration promise.

The proposal should name the setup work, usage charges, test cases and responsibility for failures. Decide who will respond to new leads before paying for a complicated workflow to collect them.

6. Hosting, maintenance and ongoing charges

Separate the build cost from the running costs. Depending on the setup, these may include hosting, domain renewal, software subscriptions, messaging usage, maintenance or ongoing content work. Check which are included in the quote and which are separate.

Find out who pays each provider, which charges can vary and what happens if you stop an optional service. Does support cover a broken form, routine content edits, new features or only certain technical issues?

Keep launch SEO work separate from ongoing marketing too. Titles, page structure and migration checks are a different scope from continuing research, content development or campaign management.

7. Ownership and the handover

Before signing, ask who controls the domain, website account, analytics and connected tools. Find out what access you receive, what can be transferred or exported, and which assets depend on third-party licences.

Ask how a handover would work if you later changed providers, including any charges or restrictions. Ownership and portability vary by platform and agreement, so get the details in writing.

Our questions to ask a marketing agency cover the wider checks around reporting, fees, access and ending an engagement.

Bring the same brief to every proposal

You don't need a long document. Start with:

• The roofing services and areas you want to promote.
• The pages and project examples needed for launch.
• Copy and photographs you can supply, plus any gaps.
• Existing pages and tools that need to be retained or connected.
• The person who receives leads and the next step they take.
• The editing, support and handover arrangements you need.
• One-time and ongoing costs, with the billing currency and any taxes clearly stated in the quote.

Use the roofing website checklist to find problems in your current site before deciding what to replace.

If you're planning a new site or a rebuild, take a look at our roofing website design. For a project that covers several services or business types, explore our custom website design service. Start with the leads you want and the work your team needs the site to do. That's the brief to compare proposals against.