How to Write a SaaS Homepage When You Launch a Second Product

How do you rewrite a SaaS homepage when you launch a second product?

Start by deciding what the company is now, not what the new product does. A homepage for two products must explain the shared problem both solve, show the buyer which product fits them, and keep the flagship's proof intact. Most second-product homepages fail because they bolt the new product onto old copy.

I have seen this play out on several B2B software sites. The team launches a second product, adds a new section halfway down the page, changes the hero to something vague enough to cover both, and wonders why demo requests for the flagship dip. Nobody decided what the company stands for. They just made room.

This article is the process I use to rewrite a homepage when a company goes from one product to two. It is a positioning job first and a copywriting job second.

Why does a second product break the homepage you already have?

Because your current homepage was written to sell one thing to one buyer. Every line, from the hero to the proof section, points at a single outcome. Adding a second product forces a choice between a broader promise that may feel vague and a narrower one that hides the new product. Ignoring that choice sells neither well.

The symptoms are easy to spot. The hero headline becomes abstract, with words like platform, suite, or solutions doing the heavy lifting. Customer logos stay the same even though they only bought the first product. The navigation grows a Products menu that most visitors never open.

None of these are copy problems on their own. They are signs that the company has not answered the positioning question, so the homepage is trying to answer it by committee.

What are the three homepage structures for a two-product SaaS?

There are three workable structures: flagship-led, umbrella, and split. Flagship-led keeps the first product in the hero and introduces the second as an extension. Umbrella leads with the shared problem and presents both products as answers. Split sends visitors to two clear paths from the first screen. Each fits a different stage and buyer overlap.

Flagship-led works when the second product is new, small, and sold mostly to existing customers. The homepage keeps doing its job for new buyers, and the second product gets a strong section and its own page. This is the safest option and the one I recommend most often in the first year after launch.

Umbrella works when both products sell to the same buyer and solve parts of one bigger problem. The hero names that bigger problem in the buyer's words. The products then appear as two ways to solve it, with clear guidance on where to start.

Split works when the products serve different buyers, for example one for marketing teams and one for finance teams. The first screen asks the visitor to self-select. It is honest, but it weakens the brand story, so I only use it when the buyer overlap is genuinely small.

How do you choose between flagship-led, umbrella, and split?

Use two questions: how much do the buyers overlap, and how much revenue does each product carry today. High overlap and an established second product point to umbrella. Low overlap points to split. A young second product, whatever the overlap, usually points to flagship-led. Revenue reality should beat roadmap ambition.

The trap is choosing umbrella because it feels like where the company is going. If ninety percent of new pipeline still comes from the flagship, an umbrella homepage taxes your main revenue source to promote a product that has not earned the space. That trade only makes sense if leadership has decided to accept it on purpose.

I make this choice with the go-to-market plan open next to the homepage draft. If you have not planned the motion for the new product yet, start with my guide on how to plan go-to-market for a second product line. The homepage should follow that plan, not invent it.

What should the hero say on a two-product homepage?

The hero should name the outcome the buyer wants, in plain words, at the level that covers the products you are actually selling to that visitor. Avoid category words like platform or suite unless buyers use them. The subheadline then says which product helps with what, so nobody has to guess.

A good test is whether a buyer could repeat the hero to a colleague. "They help revenue teams stop losing leads between the website and the CRM" can be repeated. "The all-in-one growth platform" cannot. The first is specific enough to remember and broad enough to cover two related products.

I also check whether the hero leads with the problem or the product. For most B2B buyers arriving cold, the problem earns attention first. I explained my reasoning in whether a SaaS homepage should lead with the product or the problem, and a second product makes that decision more important, because the product name alone no longer tells the whole story.

How do you keep proof honest when only one product has customers?

Attach proof to the product it belongs to. Logos, case studies, and quotes from flagship customers should sit next to the flagship, not under a headline that implies they use both. For the new product, use early proof that is true: a pilot quote, a design partner, or a clear explanation of how it works.

Borrowed proof is the fastest way to lose trust with a careful buyer. If a prospect asks a reference customer about the new product and hears "we have never used it," the deal gets harder. It also confuses AI assistants that read your page and try to describe what each product does and who uses it.

When a new product has no customers yet, I would rather show a short, concrete walkthrough than a vague claim. Buyers forgive a young product. They do not forgive being misled about one.

How should navigation and product pages change?

Give each product its own page with its own hero, proof, and pricing path, and keep the homepage as the router. Navigation should name products by what they do, not only by brand names. If a visitor cannot tell which product page to click from the menu alone, the labels need work.

Product names are often the weakest part of a two-product site. Internal teams know them well, but a first-time visitor does not. I usually pair each name with a short descriptor in the navigation and in the product section, so the name gains meaning through repetition.

Product pages also need clean structure for search and AI engines. Each page should explain one product clearly, link back to the shared problem, and use consistent names everywhere. On Webflow, that usually means a dedicated page per product with matching Organization and Product schema markup kept in sync with the copy.

How do AI assistants read a homepage with two products?

They try to work out what the company does and which product does what, often from the homepage and the product pages together. If names are inconsistent or one product's proof bleeds into the other, assistants can blend them into one confused description. Clear, consistent language per product is the best defense.

This is where B2B SaaS positioning meets answer engine optimization. Buyers now ask ChatGPT, Gemini, Claude, or Perplexity to explain a vendor before they visit. If your homepage blurs two products, those answers may blur them too. I looked at this pattern in how AI assistants describe a company with two products.

The practical fix is the same one that helps human readers. One sentence per product that says what it is and who it is for, repeated exactly on the homepage, the product page, and the About page. Consistency is cheap and it compounds.

How do you test the new homepage before you commit?

Test the message before the design. Show the new hero and product sections to a handful of target buyers and ask them to explain what the company does and which product they would start with. Then watch real behavior after launch: product page clicks, demo requests by product, and search queries in Google Search Console.

Message testing tools like Wynter can help if you sell to a defined persona, and simple customer calls work just as well when you know your buyers personally. The question to answer is not "do you like it." It is "what would you tell a colleague this company does." If the answers differ wildly, the copy is not done.

After launch, I track demo requests split by product in GA4 or the CRM, and I watch scroll and click patterns in a tool like Hotjar or Microsoft Clarity. If the flagship's demo requests drop sharply, the new structure is costing more than it earns, and that is a signal to revisit the choice.

What should you do next?

Write one sentence that says what the company does now, then pick flagship-led, umbrella, or split based on buyer overlap and revenue. Rewrite the hero to match, move proof next to the product it belongs to, and test the message with real buyers before redesigning anything. The structure decision does most of the work.

I build B2B websites and the go-to-market systems behind them, and a second product launch is one of the moments where both have to move together. The homepage, the product pages, the CRM fields that track which product a lead wants, and the routing that sends them to the right rep all depend on the same positioning choice.

If you are about to launch a second product and want help deciding how the homepage should change, reach out through pravinkumar.co. Let's chat.