Should a second product get its own website?

Usually not at an early stage. If the same buyer is likely to use both products, keep them on one domain with one brand, and give each product its own page on that site. A separate website means separate content, separate search work and a second brand to maintain. That only pays off when the second product serves a clearly different buyer.

Should we sub-brand our second product?

Sub-brand it only if it serves a different buyer from your first product. A sub-brand gets its own name and some visual room while staying under the parent company. If the same person buys both, a sub-brand adds a name to remember and little else. When in doubt, launch it as a sibling under your main brand and split it out later if needed.

What should the homepage say when you have two products?

Lead with what the two products have in common. Name who they are both for and the job they both help with, in plain words. Then give each product a short block under the hero with its name, one sentence and a link to its own page.

How should the navigation change for a second product?

Add a Products menu that shows both products with a name and a one line description each. Move feature links off the top level, because with two products it is not clear whose features they are. Keep Pricing, customers and docs as top level links. If each product has its own sign in or docs, label them clearly so visitors reach the right place.

Should pricing be separate or bundled for two products?

It depends on how people buy. If most customers use only one product, give each product its own tab or switch on the pricing page. If many customers use both, show a bundle as a real plan and list each product's own price nearby so the value is easy to see.

Is launching a second product a reason to rebrand?

Not by itself. If the company still sells to the same buyers and makes the same core promise, the name and look can stay, and the site only needs new structure. A rebrand makes sense when the second product changes who you sell to or what you claim to be. In that case, settle the positioning first and let the design follow it.

Website for a Second Product: What to Change

When you ship a second product, your website has to stop describing one product and start describing a company that makes two. That comes down to four changes. The homepage states what both products share, the navigation gains a Products menu, each product gets its own page with its own proof, and pricing either splits by product or joins into one plan. For most teams under 50 people, the right setup is one brand and one domain, with the second product treated as a sibling rather than a new company.

The hard part is not the design. It is deciding how the two products relate, because every page depends on that answer. Below is how to make that call, then what happens to the homepage, the navigation and the pricing page, in the order we would tackle them.

What breaks when the second product lands

A site built for one product has that product in every part of it. The headline describes it. The nav links to its features. The pricing page lists its plans. The sign up button drops people straight into it. That was the right site for the company you were.

Then the second product ships, and it usually gets bolted on. A new nav link, a homepage banner, and a page that looks a little different from the rest. Visitors now land on a homepage that talks about product one and hints at product two. They cannot tell if you are one company with two tools, or two companies sharing a logo.

First, decide how the two products relate

Before anyone opens a design file, answer one question. Does the second product serve the same buyer as the first?

If the same person buys both, the products belong under one brand. They share a name, a look and a sign in. The second product is a sibling. This is the simpler case, and it fits teams whose second product grew out of what their first product's users kept asking for.

If the second product serves a different buyer, a sub-brand can make sense. It gets its own name and a little visual room, but it still sits under the parent company. A fully separate brand is rarely worth it at this size. Every brand needs its own site and content, and a small team struggles to feed even one.

If you are unsure, start as a sibling. Splitting a product out later is much easier than merging two brands back together.

What happens to the single-product homepage

Your homepage headline was written about one product. Now it has to describe the company. The trap is to go vague, with a line about empowering teams or the future of work. That line fits both products because it says nothing about either one.

A better move is to find what the two products have in common and say it plainly. Who are they both for, and what job do they both help with? Put that in the headline. Then give each product its own short block under the hero, with a name, one sentence and a link. Within one scroll, a visitor should know there are two things here and which one is meant for them.

Keep the proof you already have, but label it honestly. Logos, quotes and results from product one still count. Just do not let them sit next to product two as if they belong to both.

The nav is where visitors check what you sell. With one product, links like Features and Integrations made sense. With two, they raise a question. Features of what?

A Products menu solves this. It opens to show both products, each with its name and a one line description. Pricing, customers and docs stay as top level links. If each product has its own docs or its own sign in, say so in the menu, so people do not end up in the wrong app.

Each product also needs its own page, at an address like yoursite.com/product-name. That page gets its own hero, its own screenshots, its own proof and its own call to action.

How the pricing page changes

Pricing is where the relationship between the products becomes real, because it shows whether people buy one thing or two.

If each product is sold on its own, use tabs or a simple switch, one per product. Do not stack two full plan tables on one long page. People read the first table, stop scrolling, and assume it is the only one.

If you sell a bundle, show it as a plan, not a footnote. Say what each product includes inside the bundle, and show each product's own price nearby so the value of buying both is easy to see.

The order to do it in

Start with the relationship decision, since everything else depends on it. Next, rewrite the homepage headline and add the two product blocks. Then build the product pages. The nav and pricing come after, and they go quickly once the rest exists. Last, test the sign up path, so someone who clicks Start on product two's page does not land inside product one.

None of this is a rebrand. The name, the look and the company stay the same. If the second product changes who you sell to or what you claim, that is a bigger job, and rebrand or refresh explains how to tell the difference.

Where to go next

If you want outside help, our shortlist of design agencies for companies launching a second product compares ten studios side by side. For the pricing page on its own, see design agencies for pricing page design. If the new homepage headline is where you are stuck, SaaS hero section design covers how to write a hero that names what you sell. And before you change a live page, work through the SaaS website redesign checklist.

Studio Maydit designs websites and products for AI founders in the US, UK, and Europe. We build in Framer, Webflow, and custom code, and the work continues into product design. Recent clients include Wave, PixelFlow, Mi-VAD and 15 other AI and SaaS teams, and projects run to a fixed scope of three to four weeks. If product two has shipped and your site still only talks about product one, book a 30 minute call.