H Product Studio
H Product Studio · Website redesign services

Website redesign and relaunch for B2B companies.

Bring your content, design, CMS and inquiry flow into one maintainable website. Plan the move from the start — including the pages and business connections that already matter.

Website redesign · Existing businesses

Your next website starts with the one you already have.

Your offer has changed. The site still describes the old one. Services are scattered across pages, edits depend on a developer, and a good prospect has to piece together why your company is the right fit.

Our website redesign services connect the commercial story to the system behind it: content, page structure, visual design, CMS and inquiry handling. We work with B2B companies, service businesses and SaaS teams that need an established website to support the next stage of the business.

01  ·  Delivery scope

A new website your team can keep moving.

The brief identifies what earns its place in the next version, what changes and who will maintain it.

  • 01Content and service architecture: connect the questions buyers ask to clear service pages, relevant proof and the right next step.
  • 02Responsive UX and visual design: a coherent system for navigation, service pages, cases and contact, shaped around your existing or refreshed brand.
  • 03CMS and editing model: reusable content types, controlled page building, previews and a publishing workflow your team can actually use.
  • 04Frontend and integrations: implement the agreed design and connect the forms, booking tools, CRM or business systems that belong in the scope.
  • 05Content and URL migration: inventory the old site, carry across useful material, map changed addresses and test the search controls before release.
  • 06Relaunch and handover: verify customer journeys, record the release and rollback path, and hand over access, editing guidance and the next priorities.
02  ·  Choose the size of the change

Refresh, redesign or replatform?

The visible symptom does not always tell you which layer needs work. We make that distinction before committing to a build.

01

Refresh the presentation

Keep a sound structure and CMS. Improve the message, typography, imagery and priority pages when the foundation already supports the job. The first task is to identify the pages and decisions that need attention.

02

Redesign the experience

Rework navigation, service architecture, copy and page templates when the business has outgrown its current story. Reuse useful content and brand assets while giving visitors a clearer route from understanding to inquiry.

03

Rebuild the foundation

Consider CMS migration or a new frontend when publishing limits, maintenance or integrations prevent the required change. Choose the stack around the content model, editors and business workflows, then plan what must move with it.

03  ·  From review to relaunch

Each phase leaves a decision you can inspect.

  1. Step 01

    Map the current site

    Review the offer, pages, available search and analytics data, editing needs and integrations. Output: an agreed problem statement, ownership map and retain/change/retire decisions.

  2. Step 02

    Prove the direction

    Develop the content hierarchy and representative desktop/mobile pages together. Output: approved copy, design direction and template scope before the whole site is built.

  3. Step 03

    Build and rehearse

    Implement the templates and CMS, migrate content and exercise the important journeys in staging. Output: reviewed pages, tested URL mappings and a launch checklist with named responsibilities.

  4. Step 04

    Release and follow through

    Run the agreed cutover, check public pages and inquiry delivery, then review errors and search discovery. Output: a release record, ownership handover and a defined post-launch review.

04  ·  Budget and dependencies

What sets the cost of your redesign?

We scope the work around the site's actual shape. Page count alone hides the parts that carry the effort.

Selected client work

An established business. A new digital chapter.

WunderDerm needed its brand, service information, publishing and booking paths to move forward together. The project carried a recognizable business into a new website system.

WunderDerm case cover: the redesigned website hero with its blue and pink visual identity
WunderDerm · Augsburg, Germany · Client project

From a WordPress-era site to a connected service experience.

  • Brand refresh that retained the recognizable wordmark and established a reusable visual system.
  • Service architecture covering treatments, zones, pricing and booking handoffs.
  • Next.js frontend and Sanity content models, with previews and controlled publishing.
  • SEO migration work including metadata, sitemap support and redirects for former WordPress URLs.
Explore the WunderDerm redesign →
Forschungsmittel public B2B website and platform
Related B2B work · New platform build

When the public website connects to the business behind it.

Forschungsmittel brings a public advisory website, client dashboard, team workspace and document workflows into one system. It shows the engineering context for a website that has more to do than publish pages.

See the Forschungsmittel platform →
Scope for your next website

Start with the work your site has to do.

A service website, a SaaS marketing site and a site connected to a customer portal need different content and technical boundaries. We define those boundaries together so the redesign brief reflects the business you run.

For an existing application or internal workflow that needs staged replacement, explore our application modernization work. For a supplier change with an inherited codebase, use the software takeover path.

Application modernization →Software takeover →
Relaunch acceptance

What must still work on launch day?

A redesign changes the surface and often the system underneath. We agree these checks before release, then verify the actual site and receiving systems.

01

A buyer can still find the right page.

Retained content has an owner and destination. Changed URLs redirect to the closest relevant page; retired pages have an explicit decision. Titles, canonical tags, robots rules and the sitemap are checked against the released version.

02

An editor can publish a real change.

The people who will run the site try the content model, preview, publish and correction flow. Their normal work should fit the CMS without breaking the design or requiring an engineer for every service update.

03

An inquiry reaches its destination.

Test the form through its backend and receiving system, including failure and retry. The visitor's success message must correspond to the agreed technical receipt. Qualification and replies remain visible responsibilities of your team.

04

The team can operate the released site.

Confirm domain, hosting, CMS and repository access; record the deployment, recovery options and support owner. Then compare post-launch errors, search discovery and recorded inquiries with the baseline, allowing for consent and data delays.

Search results can change as Google recrawls a relaunched site. A redirect map and launch checks manage the transition; they do not guarantee rankings, traffic or lead volume.

Website redesign FAQ

Questions before a website redesign.

  1. A refresh fits when the structure and CMS work but the presentation needs attention. A redesign changes the content hierarchy, navigation and experience. A rebuild or replatform is justified when the existing foundation limits the required result. We review the current site, publishing needs and integrations before recommending the scope; replacing the CMS is a decision to justify, not a starting assumption.

  2. The main drivers are the number of distinct templates, content that needs rewriting or migration, the CMS model, integrations and launch dependencies. Forty pages using two templates are a different project from twelve pages with twelve custom interfaces. The proposal separates discovery, content and design, implementation, migration, third-party costs and any ongoing work, so you can see what the budget covers.

  3. Yes. WunderDerm is a published example of a WordPress-era site rebuilt with Next.js and Sanity. We first review what the current platform supports and what your editors need. If a new CMS is appropriate, its content model, previews, publishing permissions, media and redirects are included in the migration scope. A modern stack alone is not a reason to discard a useful existing system.

  4. Keeping the domain and valuable URLs is often possible. We inventory the existing pages, agree which content stays, map changed URLs to relevant destinations, and check redirects, canonical tags, robots rules and the sitemap. Search visibility can fluctuate while Google recrawls a changed site; no redesign can guarantee unchanged rankings. The migration plan and post-launch checks are how we manage that transition.

  5. We inventory the inquiry path before the rebuild and agree the destination and owner of each form. Acceptance covers the response shown to the visitor, error and retry behavior, the destination receipt and consent-aware tracking. A button click is not counted as a lead. A successful technical receipt is kept separate from your team's qualification, reply or sale. Existing CRM and booking integrations are scoped individually.

  6. We set milestones after reviewing templates, content readiness, integrations and migration risk. A phased release can work when sections have clear boundaries and the shared navigation, URLs and CMS remain coherent. The plan identifies who supplies and approves content, what must be ready before launch, and how a delayed dependency changes the sequence. We do not attach one universal delivery window to every site.

  7. The editing model is part of discovery. We agree which content editors can change, what remains a designed component, and which changes require engineering. Where a CMS is included, the handover covers content types, previews, publishing and an editing walkthrough. Repository, hosting, domain and CMS ownership are recorded so the next change does not depend on remembering who originally built the site.

  8. We work remotely with U.S. teams. The proposal sets the communication rhythm, review contacts, timezone overlap and release responsibilities for the engagement. Post-launch review and ongoing maintenance are defined separately, including the period, scope and available capacity. A website redesign does not automatically include an unlimited support retainer or round-the-clock coverage.

Your next website

What does your website need to do next?

Send the current URL and the change your business needs. This gives us a useful starting point for reviewing the fit and defining the next step.

  • Current website and CMS, if known.
  • The service, audience or customer journey that needs to improve.
  • Any important integrations, URL changes or launch constraints.

Working with U.S. teams remotely. Communication, scope and release responsibilities are agreed for the project.

Website redesign · Project brief

Tell us about your current website.