Brand Strategy
B2B rebrand and website redesign: write one brief before hiring
·5 min read
If you are commissioning a B2B rebrand and a new website, brief them together. Define what buyers need to understand, which evidence supports the new positioning, and who owns the decisions from identity through launch. Then decide whether one studio or several specialists should deliver the work.
One supplier can simplify coordination. It does not remove the need to agree on content, implementation and acceptance. Two suppliers can collaborate well when those responsibilities are explicit. The useful question is: who carries each decision into the working site, and who checks that it survived?
Start with a buyer question, not a list of deliverables
“New logo, guidelines and ten website pages” describes outputs. It does not explain what the new identity should help the business communicate.
Consider a hypothetical security company that has expanded from one developer tool into a platform. Its website still describes the original tool, while its sales team presents the broader offer. A fresh visual identity alone will not reconcile those stories.
A more useful brief might say: “Help a security leader understand which problems the platform addresses, find credible product evidence, and choose the right conversation with our team.” That gives writers, designers and developers a shared decision to work toward. It is a proposed objective, not a promise of conversion growth.
Bring current sales material, product descriptions and approved customer evidence into the brief. Identify statements that are outdated, unsupported or still awaiting approval. A design team should know which claims it can use before it builds a page around them.
Ask for one complete page before approving the whole system
A logo presentation and a homepage mood board can both look convincing while leaving important questions unanswered. Before extending the design across the site, review a representative page with real content.
Choose a page that has to explain something difficult: a product use case, an integration or a customer story. Ask the proposed team to show how the identity works in the heading hierarchy, illustration, supporting evidence and next action. Include the narrow-screen version and a realistic long title.
This review can expose decisions that a polished hero image conceals. Does the new typeface work for technical explanations? Can a customer quote retain its context? Does the call to action describe what happens next? Can the visual language support a second product without inventing another brand?
Our brand guidelines versus design systems guide explains the distinction between identity decisions and reusable interface behavior. They should inform each other; they need not live in one document.
Put the handoffs in the proposal
Use a short responsibility table when comparing proposals. The roles below are a starting point to adapt, not a required agency structure.
Swipe sideways to view every column.
| Decision | Evidence to request | Owner to name |
|---|---|---|
| What the business promises | Approved positioning and supported claims | Client decision-maker and strategy lead |
| How the promise becomes a page | A representative page using real copy and assets | Brand, content and web design leads |
| What editors can change | A demonstration of routine edits in the CMS | Implementation lead and client editor |
| What happens to existing links | URL inventory and a migration plan where needed | Developer and search owner |
| What makes the release acceptable | Tested journeys, unresolved issues and release decision | Client approver and delivery lead |
Ask who supplies the writing, checks factual claims, obtains permission for client logos, migrates content and maintains the site afterward. “Website included” is too vague to answer those questions. If your internal team owns a task, reserve time for it in the schedule.
A new identity does not require new URLs
Separate visual changes from decisions about the domain, page addresses and CMS. Retain useful URLs when they still describe the content. If addresses must change, budget for migration work alongside design.
Google's site-move guidance recommends separating major changes where possible, mapping old URLs to their replacements and using permanent server-side redirects. It also calls for updating internal links and monitoring the move. Ranking fluctuations can occur during a migration; a new design is not a guarantee that visibility will improve.
For the hypothetical security company, a renamed product page might need a relevant replacement URL. An old campaign download could need a different decision. Review those cases individually rather than treating every old address as a route to the new homepage.
Define acceptance around actions people can complete
Before launch, give the team concrete tasks to demonstrate: find a relevant product page, inspect supporting evidence, submit an enquiry through an agreed test process, and make a routine content edit. Record who checks each task and how problems will be resolved.
Include keyboard navigation, focus visibility, headings, form labels and narrow-screen layouts in the review. W3C's Easy Checks provides an initial accessibility review; it explicitly does not establish comprehensive accessibility. Agree separately on the depth of accessibility evaluation your project requires.
Keep a record of the existing site's relevant search and enquiry data before changing it, if that data is available and reliable. After launch, compare equivalent periods and account for changes in campaigns, audience and tracking. A rise or fall in enquiries alone does not isolate the effect of the rebrand.
Choose the team against the brief
Ask each candidate to explain a completed project from positioning to implementation: what it owned, how decisions crossed disciplines, and what the client had to supply. Look for work that demonstrates the kind of explanation your business needs, not only an industry label in a portfolio.
At Studio Melamed, branding and UX/UI services connect identity with digital product and website design. You can explore the Spectral project as a visual example of our work. To discuss a rebrand, bring the current site, the business change behind the request and the people who will approve the result.
The retainer versus project guide can help you separate a bounded launch from ongoing design work. Define that boundary before comparing prices: it makes proposals easier to assess and gives both sides a clearer commitment.
Sources and editorial context
This article was prompted by a Reddit question about commissioning a B2B rebrand and website together, accessed October 4, 2026. The discussion is a source of buyer questions, not verified evidence about any named agency. Technical recommendations refer to the Google and W3C guidance linked above. The security-company example is hypothetical; the brief and responsibility table are the studio's editorial recommendations.