Your product has moved on, but your website still shows an older version. Sales keeps explaining things that visitors should already understand from the homepage. Meanwhile, marketing waits for development support every time it needs a new campaign page.
A website relaunch makes sense when these problems share a common cause: your website no longer reflects your offer or the way you work with buyers. Positioning, copy and page structure need to work together. A new design alone will not make an unclear value proposition easier to understand.
This guide explains when a website relaunch is worth it, what budget and timeline to plan for, and how to define the scope. You will also find concrete budget ranges from our B2B SaaS projects and a process that runs from strategy through to handover.
What does a website relaunch include?
A website relaunch fundamentally updates an existing website so it can better serve buyers and marketing. A redesign focuses on visual design, while a migration moves content or technology to a different system. Both can be part of a relaunch.
For a strategic B2B SaaS relaunch, we establish which buyers the product is most relevant to and why they should choose it before starting design. This positioning becomes the foundation for the messaging. Page structure, website copy and product presentation all build on it.
The agreed scope then includes development and preserving important existing content. Enquiry journeys and tracking are tested before launch, followed by training for the marketing team. A new logo, domain or CMS is only needed if there is a concrete reason for the change.
When is a website relaunch worth it?
A website relaunch is worth considering when your company has outgrown its existing website. This often happens after expanding the product or entering new markets or customer segments. What matters is which information and capabilities the current website lacks.
| What you notice | What to clarify first |
|---|---|
You want to win larger companies, but the website still speaks to your previous customer base. | Which additional decision-makers, buying criteria and evidence do these customers need to see? |
You are launching a new product, but the website still explains only the existing offer. | Who is the new product for, which problem does it solve and how does it complement the existing offer? |
Your standalone tool has become a suite, but the website does not explain how the parts fit together. | When do buyers need individual products, when do they need the whole suite and what extra value does the combination offer? |
You are positioning yourself in a new category, but prospects still put you in the wrong one. | Which category does the target audience understand, and which alternatives should they compare your product with? |
Sales explains the offer differently from the website. | Which target audience, value proposition and evidence should both consistently communicate? |
Visitors arrive, but relevant demo requests do not follow. | Are you reaching the right buyers, do they understand the value and can they answer their key questions before making an enquiry? |
Campaign pages and product updates regularly wait for development capacity. | Which changes does marketing need to make independently, and which components, permissions or skills are missing? |
The age of your website alone tells you very little. If only one landing page is underperforming and the rest of the setup works, a focused update is often enough. If several important pages explain the wrong offer and are difficult to develop further, there is a stronger case for a website relaunch.
Website relaunch: all at once or in phases?
A phased website relaunch makes sense when you need a quick improvement or cannot commit a large project budget. That might be ahead of a product launch or when internal capacity is limited. A smaller initial scope can also be the better choice for a seed-funded company.
We usually start with the homepage and a few particularly important pages in the buyer journey. The homepage explains the offer independently and leads to a specific action, even if supporting pages are not ready yet. That means it can already serve as a landing page for an advertising campaign.
Responses to this page provide useful signals for the next phase. In the ad funnel, you can observe which visitors request a demo and which questions remain unanswered in the subsequent conversation. These signals help guide revisions, but do not prove the impact of an individual message on their own.
The remaining pages are built in parallel on the same foundation. Reusable components allow every new page to build on work already done. Whether the first version launches on the existing domain or temporarily on a subdomain depends on the project.
How much does a website relaunch cost?
B2B SaaS companies typically invest €40,000–€70,000 excluding VAT in a full relaunch with path digital, including strategy. Smaller projects start at €30,000 excluding VAT. These are our project and proposal ranges, not a general market benchmark.
The actual price depends on what needs to change and how much work the existing website creates. To get proposals you can compare, define the following:
- Which products and target audiences does the website need to explain?
- How many page types and languages are required?
- Which copy and product visuals need to be created?
- Which content, features and integrations need to be retained?
- What should marketing be able to do independently after launch?
What are you paying for in a website relaunch?
You are paying for experience and a guided process that turns your team's product knowledge into a convincing website. Positioning and messaging are documented clearly, bringing marketing, sales and leadership onto the same page. The website then shows what your product does today, who it is relevant to and why buyers should choose it.
If you manage a website relaunch in-house, you need to prepare these decisions and coordinate the whole project yourself. Working with several suppliers adds handovers between strategy, copy, design and development. A consistently managed process reduces this coordination work and keeps the agreed positioning intact through to the finished pages.
The investment also includes enabling marketing to keep developing the website independently. Clear copy, relevant customer evidence and straightforward enquiry journeys should help more visitors take the step towards a qualified enquiry. Reusable components allow your team to add new campaigns, products and use cases without setting up a new project each time.
How long does a website relaunch take?
A comprehensive website relaunch takes several months. The exact duration depends on whether positioning and messaging are already clear, how many pages need to be built and which content needs to be migrated. A timeline is only meaningful when you know which services it covers and when the clock starts.
Internal participation also affects the schedule. Product knowledge, reviewed content and consolidated feedback need to arrive on time so the next steps can begin. Named contacts and agreed approval dates help avoid delays between strategy, copy, design and implementation.
Our rule of thumb for a B2B SaaS website relaunch is no more than six months from project start to launch. If it takes longer, we see that as a signal to look more closely at priorities, responsibilities and firm decisions. The key question is whether the agreed scope explains the duration or whether the project keeps getting pushed aside by other work.
With an internal build or suppliers you coordinate yourself, there is a particular risk that nobody takes clear responsibility for overall progress. Without reserved capacity and clear decisions, handovers between copy, design and development stall. Meanwhile, the product and company keep evolving, so the new website can already be out of date when it launches.
If the desired deadline does not fit the full scope, a phased launch can make sense. The homepage and priority pages go live first while other areas are developed in parallel. The strategic foundation and plan for further development need to be in place beforehand.
Should you manage a website relaunch in-house or hire an agency?
An in-house relaunch makes sense if your team has the necessary skills and genuinely available time. An agency can help when important capabilities are missing, an external strategic perspective is needed or the project cannot be managed internally. You can also combine strategic support with in-house implementation.
| Situation | Suitable approach |
|---|---|
Strategy is clear and an experienced web team has capacity. | Build in-house and add specific specialist expertise where it is missing. |
Product knowledge is available, but positioning and messaging are unclear. | Develop the strategy together, then implement internally or externally. |
Marketing needs a relaunch but cannot manage the project alongside its other work. | An agency takes on the agreed delivery and project management, while your team provides input and makes decisions. |
When choosing a partner, look at the thinking behind the websites they show you. Ask them to explain which buyer questions the pages answer and how those questions informed the copy. Also establish whether your team will be able to create a new landing page independently after handover.
A proposal should make clear who is responsible for copy and which work on existing content and technology is included. The label “strategy” alone tells you very little about the service. What matters is whether the work produces clear positioning and a usable foundation for the website.
How to plan and deliver a website relaunch
The process starts with goals and the strategic foundation. Pages and their content follow before design and implementation begin. Each step needs a tangible outcome that supports the next decision.
1. Define goals and responsibilities
Start by defining which problem the website relaunch should solve and how you will recognise an improvement. “Looking more modern” is not a sufficient goal. A more concrete goal is helping buyers understand a new product or enabling marketing to publish campaign pages using existing templates.
Appoint someone in your company who owns the website relaunch and can make decisions. Involve marketing, sales, the product team and leadership early so product knowledge, customer questions and strategic goals come together. Define who provides input, who checks factual accuracy and who gives final approval.
Shared criteria protect the project from late discussions driven by personal taste. An incorrect product claim should be corrected. A founder's preference for a different typeface should be assessed against the agreed brand and communication goals.
2. Clarify positioning: where to play, how to win
Positioning defines which buyers your product is especially relevant to and why they should choose it over their alternatives. We also examine which category the market understands and which terms need more explanation. A long feature list does little to help if buyers cannot place the offer.
We document the answers in a shared canvas. It captures target buyers, alternatives and the distinctive value proposition, supported by relevant product evidence. This gives the whole team a clear view of the decisions behind the website copy.
3. Develop the messaging
Messaging translates positioning into statements buyers can understand and put into context. It defines which problem to address first and how to substantiate the value proposition. This shared foundation prevents every page from telling a different story.
Compare your homepage, sales presentation and product demo side by side. They can go into different levels of detail, but the same target buyers and benefits should be recognisable in each. Resolve conflicting promises before writing the website copy.
4. Develop the buyer journey, page structure and copy
The page structure follows the questions buyers need to answer before making a decision. A use-case page explains a specific application in everyday work. A feature page makes sense when buyers want to evaluate that particular capability.
Define the next step each important page should prepare buyers to take. Use that as the basis for the copy and supporting evidence. This prevents copywriting from becoming an exercise in filling the spaces left over after design.
A SaaS homepage should quickly show who the product is for and what value it delivers. Product views and a clear explanation of how it works then make the promise tangible. Relevant customer evidence addresses doubts before the page leads to a demo or another useful next step.
5. Develop the design and reusable components
The design makes the content hierarchy and product easy to understand. That is why we work with real copy and relevant product visuals. Generic illustrations do not help if visitors still cannot tell what the software does.
For ongoing development, marketing needs a reliable set of components and page templates. New landing pages should be built from them without introducing a separate set of design rules for every page. AI-generated drafts also need to fit this system so that greater speed does not create an increasing number of one-off solutions.
6. Migrate content and prepare for launch
Before launch, decide which content to keep, revise or remove. Changed URLs need appropriate redirects. Making these decisions early allows you to plan migration effort and risks more realistically.
When switching CMS, for example from WordPress to Webflow, custom content elements need particular attention. A shortcode might display a table in the old system but appear as plain text after a basic import. Have representative content checked in the new system before migrating everything.
If multiple language versions are planned, include their content and responsibilities in the same preparation. That also covers labelled product images and forms. Multilingual content only needs a dedicated main workstream if the project scope calls for it.
Website relaunch checklist: what needs to be checked before launch?
Before launch, you need to know that buyers can reach important content and that enquiries actually arrive. Preserving existing search traffic matters just as much. Assign clear owners to the checks and record verifiable results.
- Content: Check important pages on desktop and mobile, including migrated tables and embedded elements.
- Enquiry journeys: Complete a form submission or demo booking and confirm it arrives in the intended system.
- SEO: Map old URLs to new ones, test redirects and remove accidental indexing restrictions.
- Metadata: Check titles and descriptions against the new content and populate them throughout the site, including CMS templates. Required fields help prevent missing entries.
- Technology: Check loading speed, clear page structure and accessible text content. Relevant structured data must accurately describe the visible content.
- Languages: Check planned translations, language switching and localised enquiry journeys.
- Tracking and privacy: Test measurement under the relevant consent settings. Have the responsible privacy or legal contact review cookie settings and legal notices against the new setup.
- Access and rollback plan: Confirm access to the domain and DNS settings and define who will restore the previous website if problems arise.
- Launch timing: Choose a time window with low relevant usage and support available.
Mapping changed pages is particularly important for SEO. Permanent redirects should point to relevant replacement pages, as Google explains in its site move guidance. Even careful preparation cannot entirely rule out short-term ranking fluctuations.
A clear technical structure also helps make content discoverable. Google's existing SEO fundamentals apply to its AI search features, including accessible text content. This does not guarantee inclusion in AI-generated answers.
Publishing is only one part of the launch window. The domain connection, important pages and enquiry journeys need to be checked on the live website afterwards. Reserve a staffed time window with a buffer that also allows for a rollback if problems occur.
What happens after a website relaunch?
After the relaunch, marketing needs to be able to use the new foundation. Decide before launch which campaign or new page will be created first. Completing a real task during handover shows whether the team can work with the templates and components.
The company can then manage the website itself or bring in support for individual additions. What matters is that routine updates do not always depend on external availability.
Evaluate results against the goals agreed at the start. Look at confirmed demo bookings and relevant enquiries alongside feedback from sales. Bounce rate and time on page are diagnostic measures, not proof of success on their own.
