How long does a rebrand take?

A B2B rebrand that includes the website takes three to six months from kickoff to launch when the decisions are closed before design starts, and six to twelve when they aren't. That's the honest answer, and the second half of it is the one most quotes leave out. Company size changes how much there is to roll out and how many people hold a veto; it doesn't change the thinking time. This article gives you the timeline phase by phase, the multiplier that explains why quotes and calendars disagree, a 90-day plan from a project with dates on it, and the two clocks no agency can compress.

Key takeaways

• The timeline is a multiplier, not a range. The same plan runs at ×1 when decisions are closed before design, ×1.5 to 2 when they're made during design, and ×2 to 3 when they're reopened after it.
• Decision readiness beats company size. Forty people or four hundred, the four decisions take two to four weeks with the owners in the room. Size scales the rollout and the approvals, not the thinking.
• Two clocks run on their own. Google needs weeks to process a site move and wants redirects kept for a year; a new name adds a trademark clock measured in months.

The timeline, phase by phase

Here is the rebrand timeline I'd defend, for a B2B company that is changing positioning, identity and website together. The ranges assume the people who own the decisions take part; every week they're absent gets added to the end.

Added up with the overlaps, that's three to six months from kickoff to launch, with rollout continuing after it. A refresh runs shorter, six to ten weeks, because the first two phases shrink to confirmation: positioning holds, the identity gets a better expression. Which one you need is the first timeline decision, and the 20% Test settles it in five questions before anyone quotes.

Why the quote and the calendar disagree

Everyone blames the execution: the design took too long, the developers missed deadlines, the agency moved slowly, or… the website became more complicated than expected. That's usually the story. But after being involved in enough rebrands, I've noticed something different:

• Most delays don't start in design
• Nor in development
• They start when nobody has actually decided where the company's going

At first, everything looks fine: the project kicks off, and the next meetings happen. Then ideas are shared, and mood boards get created. Design directions are explored, and people finally feel some progress. Then… some interesting questions happen:

• "Who are we actually trying to reach?"
• "What makes us different?"
• "What are we trying to become over the next few years?"
• "What problem is this rebrand supposed to solve?"

Suddenly, the conversation shifts, and not because the design is wrong, but because the direction was never clear. I've seen projects where execution moved smoothly for weeks before everything stalled. Many leadership teams assume speed comes from moving quickly into action. However, the opposite is often true because fast decisions create gaps in clarity, which don't magically disappear. They simply show up later as revisions, disagreements, and rework.

One example stands out… before moving into website design, we created mood boards to establish visual direction. They took roughly three hours, whereas the website pages took five days. The logical thing would have been to align on direction first. Instead, stakeholders wanted to jump ahead and see finished designs. The result was more feedback, revisions, time, and uncertainty. The expensive part wasn't creating the pages. It was avoiding the decision that should have happened before the pages were created.

The same thing happens when too many people become decision-makers. Everyone has an opinion and wants to contribute, but nobody wants to make the final call. I once worked with a leadership team where feedback was coming from so many directions that progress nearly stopped. Eventually, we reduced decision-making to a small group. The project immediately became easier to move forward. To be honest, most rebrands are not delayed by work but by uncertainty. Because leadership agrees that change is needed, but not on what the company actually is, where it's going, and what success looks like once the project is finished.

The Variance Map, the multiplier behind every overrun

Put those stories on a timeline and a pattern appears that I call the Variance Map. The length of a rebrand isn't a range you pick from; it's the plan multiplied by when the decisions get made.

• Decisions closed before design, ×1. The plan runs as quoted. Reviews check execution against a written direction, and revision rounds argue about craft, not identity.
• Decisions made during design, ×1.5 to 2. Every open question becomes a revision round at design prices, and design reviews turn into the leadership meeting the company never held. Sixteen planned weeks become twenty-four to thirty-two.
• Decisions reopened after design, ×2 to 3. A late stakeholder, a board member, a new sales leader reopens positioning at 80% built. Pages get rebuilt, the identity gets second-guessed, and sixteen weeks become thirty-two to forty-eight.

That is how a twelve-week quote lands at thirty. Nobody lied in the quote. It assumed ×1, and the company delivered the conditions for ×2.5. The multiplier is also the only part of the timeline you fully control: it's set by whether the decisions exist in writing on the day design starts.

What company size changes, and what it doesn't

Every guide to rebrand timelines sorts companies by size, and the bands are roughly right as a description of rollout. What they hide is where the time goes. A forty-person company and a four-hundred-person company take the same two to four weeks to close positioning, audience, message and structure, provided the people who own those answers are in the room. What grows with size is everything after that: the number of assets carrying the old brand, the number of markets and languages, and above all the number of people who can reopen a decision.

So a large company's rebrand isn't slower because thinking takes longer. It's slower because the rollout is bigger and the approval chain is longer, and the second factor is a choice. Deciding who actually decides before the first review, and keeping that group small, is worth more weeks than any amount of design capacity. A big company with three decision-makers moves like a small one. A small company with fifteen moves like an enterprise.

A realistic 90-day plan, with a dated record

When the direction is settled first, a mid-market B2B rebrand with a new website fits in roughly ninety days to launch. Here is the shape, with the overlaps that make it possible.

Weeks one to four close the decisions: diagnosis, ranked positioning options, the audience call, the message in full sentences, the site structure page by page, each decision with an owner and a date. Weeks five to ten run identity and website design in parallel against that brief. Weeks nine to thirteen build and migrate, with URL mapping treated as a deliverable of its own. Week thirteen launches. Rollout of decks, templates and listings continues for the weeks after, and nobody is surprised by it because it was on the plan from day one.

I can show the first phase on the record. Fiscallion, a fractional CFO firm, had its strategy and website architecture opened on 26 May and closed on 18 June 2025, three and a half weeks, ahead of wireframes, design and development on the same project board. The build then executed closed decisions, and the site went from one ranking keyword to 260 within fourteen months. The full sequence behind that board is the B2B website redesign process; whether your company is ready to start the clock is what the Readiness Ten scores in one session. If the date is set by a funding announcement, the decisions fit before it and the full rebuild belongs after.

The two clocks you can't compress

Two parts of a rebrand run on timetables nobody in the project controls, and both are missing from most quotes.

The first is search. If the rebrand changes URLs or the domain, Google treats it as a site move and processes it at its own pace: a small to medium-sized website can take a few weeks for most pages to move in its index, and larger sites take longer. The same documentation asks you to keep the redirects for at least a year, so the old URLs stay on the plan long after launch day. Rankings fluctuate during that window; a rebrand that launches a month before the quarter that matters has chosen the worst month.

The second is the trademark office, if the name changes. In the first half of its 2026 fiscal year the USPTO's average time to a first examination of a trademark application was 4.45 months, and total processing ran ten months. A rename filed when the new identity is approved will not be registered by launch. File the mark the day the name is chosen, in the decisions phase, and the clock runs alongside the design work instead of after it.

What changes when alignment comes first

When leadership aligns early, projects move surprisingly faster. Because people stop revisiting the same conversations. Everyone has a clear brief and understands the positioning. Stakeholders know what they're evaluating. So, the team spends less time debating and more time building. A rebrand will always take time… and it should. Because you're now redefining how a company presents itself to the market. The time worth defending is the thinking at the start; the time worth cutting is the rework in the middle. Running that first phase as a fixed three-week engagement, before any agency is briefed, is the work I do as a Website Strategy Consultant, separate from the build so the timeline has no reason to stretch.

Final thoughts

If your rebrand keeps dragging on, it's worth asking an uncomfortable question: Is the delay really happening in execution? Or is execution waiting for decisions that nobody wants to make? Because in most cases, that's where the real bottleneck lives: not in the design files, not in the website, not in the agency. It lives instead in the leadership conversations that should have happened before the work ever began. Put dates on those conversations and the rest of the calendar starts behaving.