Rebrand rollout: your website, materials and launch plan

A rebrand rollout should be scoped around the places where customers encounter your business, not just a replacement logo. Before commissioning the work, decide what stays, where the new identity will appear, who updates each channel and how the completed rollout will be accepted. That gives suppliers a real implementation brief rather than a request for a presentation of a new mark.

Not every refresh needs a new name, domain or website platform. If your offer and audience remain the same but your materials are inconsistent, a more coherent visual system may be enough. If your positioning or target customers have changed, different colours alone may not address the problem.

Define the change before requesting proposals

Describe a situation that someone can investigate. “We want to look modern” does not explain what the work must improve. “Prospects do not realise that we also serve business customers” provides a starting point for the message, service hierarchy and supporting examples.

Separate three decisions:

• Visual refresh: keeping the existing direction while improving consistency and applications.
• Messaging change: explaining your offer, specialism and customer benefits differently.
• Name or brand structure change: planning a transition between identities and channels as well.

These can belong in one project, but they should not automatically become one package. Specify what you want to preserve, such as a recognisable symbol, an established name or the way a core service is presented. Keeping something useful is a design decision, not a failure to commit to change.

Inventory customer touchpoints before pricing

Follow the customer's actual journey from finding your business to receiving a proposal. The logo in your website header is only one touchpoint. An old identity may survive in an attachment sent after an enquiry or a document a salesperson uses every day.

Your inventory should cover:

• The homepage, service pages, forms and confirmation messages.
• Photography, graphics, the favicon and link preview images.
• Presentations, PDF proposals, document templates and email signatures.
• Social profiles, advertising and your Google Business Profile.
• Signage, printed items and customer handouts.

For each item, record its owner, file location, required access and update process. Distinguish active materials from archives. You do not necessarily need to redesign every historical post, but decide which older assets still direct customers towards your current offer.

Your website needs a system, not a new header

Appearance and readability

The new palette must work across buttons, links, forms and messages, not just on a brand presentation slide. Check contrast, text readability and whether interface states remain distinguishable. A logo colour does not have to become the colour of small text or every button.

Ask to see the direction applied to real content. A long service name, a team photograph and a detailed form expose constraints that short slogans can hide. The separate guide to logo design deliverables covers the files and variants you should receive.

Content and functionality

If the rebrand reflects new positioning, include headings, service descriptions, supporting arguments and calls to action in the scope. A new visual layer should not conceal an outdated offer. The supplier needs approved business information, not an instruction to make the words fit the design.

Preserve working enquiry routes. After implementation, test forms, notifications, telephone links and downloads. If you are also considering a platform rebuild, use the guide to improving or rebuilding an existing website to keep that decision separate from the identity work.

A new logo does not require a new domain

A visual refresh can retain existing URLs. Changing domain is a separate decision with its own technical plan, not a cosmetic addition to the identity project.

If URLs must change, allow for an old-to-new URL map, redirects, updated internal links and indexing checks. Google recommends sequencing changes to the domain, CMS and layout rather than doing everything at once. Its guidance also warns that search visibility can fluctuate while a move is processed.

Agree the sequence with whoever manages the website. Planning does not guarantee unchanged rankings. Also account for email, addresses printed in materials and continued access to necessary old resources instead of switching them off on launch day.

Explain the transition to existing customers

Tell customers what the change means and what remains the same. If the team, service arrangements and contact channels genuinely continue unchanged, say so clearly. Do not promise continuity the business cannot substantiate.

Consider a hypothetical local contractor expanding from residential work into projects for commercial clients. The business keeps its name and domain but changes its service structure, project presentation and proposal template. Explaining the expanded specialism is more useful than simply announcing a new logo.

Your Business Profile name should reflect the real-world name used by your business, according to Google's representation guidelines. For a name change, check rebranding eligibility before editing an existing profile. Do not assume every change can follow the same process.

Plan the rollout and assign responsibility

Not everything has to change on the same day. However, the transition needs coordination so an advertisement does not lead to a website presenting a different business and a current proposal does not include an inactive address.

1. Approve the message and visual direction on the most important applications.
2. Prepare the website, templates and materials needed for launch.
3. Agree the publication sequence and identify who has access to each channel.
4. Test the journey from an advertisement or profile to an enquiry and proposal.
5. Retire active old templates and give the team one current asset collection.
6. Check public materials after launch and record outstanding corrections.

Name an approver for each task. “Client responsibility” is not enough when marketing approves the artwork but another supplier controls the website. Decide who can postpone a particular update if a required asset is not ready.

What should a rebrand rollout proposal include?

Compare proposals against the same applications. Separate identity development, asset production and publication costs. Ask about template quantities, language versions, content, licences and work requiring additional approval. “Website implementation” should identify actual views and components, not leave their extent open to interpretation.

Agree acceptance criteria: correct files, consistent active materials, working forms, assigned account access and practical team instructions. Approval need not end with “it looks good”. After launch, review customer questions and any difficulty finding the business. Do not automatically attribute a rise in enquiries to the rebrand alone.

Prepare your current website link, the reason for the change and an inventory of materials. Explore AMCompany's website services and portfolio, then describe your planned change. That provides a basis for separating design from implementation and identifying which existing elements are worth keeping.