One Website, Two Products, Zero Customers
A company that sells two things on one page often sells neither. Why clarity beats completeness, and how to tell which offers belong together.
I recently read a company's entire website. When I closed the tab, I still couldn't have told you what they sell.
That isn't a complaint about bad writing. The sentences were fine, and most of the details were even relevant. The problem sat one level above the sentences: the page had never decided what it was for.
Every page, and still no idea
The company sells two things. One is software for booking appointments and running meetings: calendars, invitations, reminders, the rooms and the people in them. The other is HR software with payroll processing: employee records, holidays, salaries, the monthly run that gets everyone paid. Both are real products, and both, I'm told, work well.
On the website, they are one thing. The homepage opens with meetings, turns to payslips in the second paragraph and comes back to calendars below the fold. The pricing page lists plans that combine seats, rooms and employees in ways that only make sense if you already know which product you need. The examples are written for people who have used the software for a year: a feature named after an internal module, a scenario that assumes you know how the two halves connect.
I read all of it, because reading websites closely is part of my job. A potential customer doesn't. A potential customer gives a page a few seconds to answer one question: what is this, and is it for me? When the answer doesn't come, they don't write in to ask. They click the X, and nobody inside the company ever learns they were there.
That was when it settled for me. A company that can't say plainly what it offers won't sell it, however good it is, because the customer never gets far enough to find out.
Why nobody inside the company sees it
Nobody sets out to build a confusing website. The confusion is a side effect of knowing too much.
The person writing the page usually knows the products better than anyone. They know why the booking tool and the payroll engine share a database, which customer asked for which feature, and what "Plan B with the room add-on" means. All of that sits in their head as obvious, so it lands on the page as implied. Every sentence leans on an assumption the writer doesn't notice making.
The visitor has none of it. They meet the page cold, without the history, the vocabulary or the internal map. Where the writer sees one coherent offer, the visitor sees fragments: something about meetings, something about salaries, and a price table that doesn't say which is which. Confusion turns into irritation surprisingly fast, and irritated people don't buy.
This is also why a company can rarely fix it alone. You can't un-know what you know, and reading your own page the way a stranger would is close to impossible. The most useful reader is usually someone from outside, who will tell you plainly where they got lost.
Two questions that decide it
None of this means a company should only ever sell one thing. It means every combination has to earn its place on the same page, and two questions decide whether it does.
Do the offers belong together? A car wash that also sells car shampoo, fragrances and microfibre cloths makes sense: everything on the shelf serves the same car. A pizzeria that also sells tyres doesn't. Both could be good businesses, but under one roof they confuse.
Does the customer want them together? This is the subtler question, because two products can be related and still be bought separately. Someone ordering a pizza very often adds a soft drink. In the customer's mind the two belong together, so offering them together helps. Someone buying running shoes rarely buys a phone at the same time, even though they might well call home at the end of a run. Put the phone next to the shoes and you haven't made a sale more likely, only the decision harder.
Ask both questions of the company I read about, and the answer draws itself. HR software and payroll belong together: the same person buys them, for the same reason, in the same conversation. They can share a website. Booking and meeting software has a different buyer with a different problem. It deserves its own site, with its own homepage, its own prices and its own examples.
"Two websites cost twice as much"
That's the objection I hear first, and it's true. Two websites mean two designs, two sets of copy and two things to maintain.
But a website nobody understands isn't the cheaper option. A visitor who leaves confused brings in nothing at all, and measured against zero, the cost of a second site is easy to justify. One clear page that sells beats a crowded page that sells nothing.
Two websites don't need two brands, either. One company with one name and several products, each at its own clear address, is entirely normal. Whether the products eventually get names of their own is a separate decision. The first one is simply: one offer, one page.
Separate sites, one memory
There's a reasonable fear behind keeping everything on one page: that a visitor who lands on the wrong product will never find the right one. Splitting the sites seems to risk losing exactly the customer who wanted the other half.
This is where an avatar earns its place. At Temu Studio, the avatar (the figure that welcomes visitors and answers their questions) can live on several websites at once, while its knowledge lives in one place: the Temu dashboard. What it learns on one site, it knows on every site. Each fact can belong to a single website or to all of them, so the booking site never starts explaining payroll unprompted, and the HR site never forgets that the company also sells booking software.
For the company in my example, that means two clear websites with one guide between them. A visitor on the booking site who starts asking about salaries is taken to the HR site, and a visitor reading about payroll who mentions meeting rooms is pointed back. Each page stays simple, and nobody gets lost at the border between them. The Atelier shows how the avatar works.
A test for tomorrow morning
Before you change anything, find out whether you have the problem. Open your homepage and show it for ten seconds to someone outside your company: a friend, a supplier, the person behind you in the queue for coffee. Then close it and ask them one question: what do we sell?
If they can answer in one sentence, your page is doing its job. If they hesitate, list three things, or describe something you stopped offering two years ago, you've found the leak, and you've found it before your next customer did.
That outside eye is what temu.swiss provides: a reader who isn't carrying your assumptions, who tells you where your offer stops being clear, and who helps you say it so a stranger understands it in seconds.
A customer who understands you can still say no. A customer who doesn't understand you will never say yes.