Launching a new product without rebuilding your site, the focus method

There's a reflex I see all the time when a brand drops something new. They want to redo everything. They think, hey, we've got a new product, so let's rebuild the bundles, rework the whole nav, slot the new product in everywhere, create new bundles. And three weeks later they're still debating the structure of the desktop menu while the product itself still isn't live.

Last week, in a meeting with a supplements brand (probiotics, digestive enzymes, that kind of thing), we had exactly this debate. They were launching a new product, "The Digestion Essential." And the real decision we made was simple. Do nothing to 80% of the site.

Before a launch, first ask yourself what you're NOT touching

The trap is wanting to integrate the new product into everything that already exists from day 1. This brand already had a whole range of bundles. Detox bundles, skincare bundles, bundles that sell well. The natural temptation was to rebuild all those bundles with the new product slotted in. A digestion + detox bundle, a digestion + skincare bundle, you get the idea.

We talked it through in the meeting. And honestly, I wasn't keen at all.

Because if you do that, you dilute your launch. Instead of having a clear message "here's our new product," you've got the product drowned among fifteen combinations. The customer who lands no longer understands what's new and what was already there. And on your end, you've got a massive project that delays everything.

So the decision was simple. Launch the product on its own, or on subscription, full stop. No bundle with the new product for now. The bundle rework, we're keeping that for phase 2. Once the product has been running, once we have sales data, once we know how people buy it, that's when we'll build the bundles. Not before.

What's left when you strip all that away is two pieces of work. The product page, and the home. That's it.

It all comes down to the product page

I say it often, in eCom, the photo sells more than the product itself. For a launch, it's even more true. The guy who lands on the product page doesn't know the product yet, so everything has to be there to convince him.

On this launch, we went all in on the product page. Several photos, trust elements clearly visible, copy that tells a bit of the product's origin story (why we created it, what it actually does). The idea is that someone who knows nothing about the brand can understand and buy while staying on that page.

Something that changes everything in the process is that we validate everything in a Figma mockup before developing anything. We build the product page in mobile first, we share it, and feedback comes directly as comments on the mobile view. No back-and-forth text by text, no "on line 3 replace this with that." You comment directly on the mockup, it's way more efficient. And above all you fix things before integration, not on a page that's already built where every change costs dev time.

If you generally struggle to convert on your product pages, go take a look at abandoned cart emails, because recovering a cart that's hesitating is often more profitable than going after fresh traffic.

The home, keep it almost untouched

Here's where we had the second real debate. Do we turn the home into a near-landing page for the new product? Like 70% of the home dedicated to the new product?

No. Your home works for everyone. The loyal customer coming back, the prospect discovering you, the one looking for a different product. If you turn it into a single-product LP, you break the experience for everyone who came for something else. And a home that completely changes with every launch is unmanageable.

So we keep the existing home structure, and we add two things. A banner at the top of the page dedicated to the new product, the first thing you see when you arrive. And possibly an extra hero section a bit lower down to develop it.

The objective I hammered home in the meeting was a single sentence. When you land on the site, the first thing you see is the new product. Not the whole page transformed. Just, the moment it opens, your eye lands on it.

One subtle point too, and it's not trivial. A guy who's never heard of you couldn't care less that it's a new product. The word "new" means nothing to him. But a customer who's already convinced is happy to see there are new things. So the banner has to sell the product's benefit. The word "new" on its own isn't enough.

The mobile menu, often skipped even though it decides

Most of your traffic is on mobile. So the mobile menu is one of the first decisions to sort out.

The product gets attached to the existing category, here digestion. Logical, it belongs to that family. But you've got a trade-off to make in the dropdown menu. Either you highlight only that product, or you show all the best-sellers in the category. For a launch, I lean clearly toward highlighting the new product. You don't want it fighting for attention with ten other products.

And there was a deliberate call. The brand had a "gut assessment," a diagnostic quiz that was prominently featured in the mobile nav. We bumped it down to second place, behind the new product. The quiz is good, it stays, but during the launch window, the priority is the product. You can't have three number-one priorities in a mobile menu, there's no room.

During a launch, anything that can wait should wait. That's kind of my rule. The less you touch, the clearer your message.

The timeline, concrete

What makes all this doable is that by shrinking the scope to two pieces of work, the timeline becomes manageable. Here's how it played out on this launch.

Meeting on October 7 to settle the scope. Product page mockup delivered by the following Monday at the latest. Validation the week after, directly in comments on the Figma mobile view. Integration the week of the 19th.

Roles are cleanly separated. One person on the product page and the remastering of the home and the menu. Another on the visuals. No overlap, everyone knows what they're delivering.

If you'd tried to redo all the bundles and the whole nav at the same time, forget it. You'd have a huge project that never really got addressed, and you'd have missed your launch window. Whereas here, by breaking it down, each block gets done properly before moving to the next.

On the same principle of not wasting energy, go see why a good eCommerce audit always starts with your P&L and not your campaigns. It's the same logic, you look at what actually moves sales before rebuilding everything.

What I take away

On a launch, you win by removing work, not by adding it. The most important decision we made on this project was not to redo the bundles. Everything else flowed from that.

Next time you launch, start by listing what you're not touching. For this brand, it saved us three weeks. You keep your home, you attach the product to its existing category, you focus your energy on the product page and a banner that hits the moment someone arrives, and you validate in Figma before integrating. The bundle rework, you keep that for later, when you'll have real sales data to build bundles that actually make sense.