What Aesop Knows About Software

The Australian skincare company Aesop has, over the better part of forty years, built a small empire on a set of principles that almost nobody in the software industry has bothered to study. The company sells what is, materially, soap and hand cream. Its bottles are brown amber glass with a printed label and no photograph. Its stores are designed by different architects but share an absolute consistency of restraint. Its prices are fixed and never discounted. Its staff are trained to consult rather than to convert. Its marketing is largely literary. In 2023 it was sold for two and a half billion dollars to a company that, by all accounts, has had the wisdom to leave it alone.

The reason this matters to anyone designing software is that the conditions of Aesop's success are very nearly the opposite of the conditions software companies have decided are required for theirs. Aesop has built a brand in slow growth, fixed pricing, almost no marketing, and zero discount activity. Most software companies are built in fast growth, dynamic pricing, constant marketing, and aggressive promotional cycles. The two strategies, on the face of them, should not be cross-applicable. They are. What follows is what Aesop has worked out, why it transfers, and how we have tried to apply it to REN.

What Aesop Actually Does

The principles, drawn from the brand's published behaviour, are roughly these.

The bottle is the marketing. Aesop does not run a model in a beach scene. It does not show a before-and-after of skin. It does not commission celebrity ambassadors. The packaging itself, sitting on the shelf in a serious shop, does the work that other brands hire models and photographers to do. The argument is that an object made carefully will read as careful, and that no amount of marketing applied to a careless object will save it.

The naming is functional. The hand wash is called Resurrection Aromatique Hand Wash. It is not called Bliss or Awaken or Glow. The name describes what is in the bottle and how it smells. It does not promise transformation. The trust the customer extends to the brand is built up in the absence of those promises, not in the presence of them.

The pricing is fixed. There is no sale at Aesop. There has never been a sale at Aesop. The bottle costs what it costs in February and it costs the same in November. The customer who pays the price in full is not punished by seeing the same product offered at thirty per cent off two weeks later. The brand maintains its meaning by refusing to participate in the depreciation that discounting performs.

The staff consult rather than sell. The training inside an Aesop store is to ask the customer what their skin is doing, to listen to the answer, and to recommend the right product based on the answer rather than the highest-margin one. The transaction often ends with the customer buying less than they would have bought at a competitor. The relationship lasts longer.

The architecture is varied; the brand is constant. Every Aesop store is designed by a different architect, often a serious one. One store will be raw timber and concrete. Another will be panelled like an old chemist's. A third will be unfinished plaster, lit from a single lantern. They do not look alike. They feel alike. The discipline holds across radical formal variety because the underlying decisions about light, materials, scent, and pace are kept consistent.

The voice is editorial. Aesop's marketing reads as if it were edited rather than written. The product cards have the cadence of a small magazine. The brand publishes a literary review. It distributes books. It associates itself with poetry rather than with pop culture. The cultural posture is closer to a publishing house than to a beauty company, and the customers who arrive through that posture stay for a long time.

Why the Principles Transfer

Software has tended to assume that its medium requires a different posture from physical luxury, and that growth metrics mandate a louder voice than what an Aesop bottle is allowed. This is, on closer inspection, false. The medium is different, but the customer is the same human being who walks into a serious shop and notices, without being able to say why, that the air is calmer than it was on the street outside. The aesthetic muscles that customer has developed do not switch off when they open a browser tab. The same impulses that read a logo-free Hermès bag as serious will read a logo-free interface as serious. The same instincts that mistrust a thirty-per-cent-off banner in a luxury shop window will mistrust a sixty-per-cent-off banner in a software dashboard. The category collapse has been a failure of imagination, not a property of the screen.

The translation is mostly direct. The interface is the bottle. The button labels are the product names. The pricing page is the price tag in the window. The onboarding flow is the conversation with the staff member. The brand voice is the editorial cadence of the catalogue. The frequency of marketing emails is the equivalent of how often the staff would phone the customer at home, which is to say, not at all unless the customer has asked for it.

Software companies have rarely built this way because the venture capital model rewards rapid growth, and rapid growth has been understood, by default, to require the noise that Aesop has refused. The understanding has held for so long that it now reads as common sense. It is not common sense. It is one possible commercial posture among several, and it happens to be the wrong one for a small number of categories where slow trust is the actual product.

How We Have Tried

REN has been built on the assumption that the Aesop posture is available to a software company that is willing to accept slower growth in exchange for the kind of brand value that compounds. We do not run discounts. We do not run upsell modals on dashboard load. We do not send promotional emails on bank holidays. We do not put a percentage off in the email subject line to lift open rates. The pricing page lists the prices and the features, and that is the whole of the pricing page.

The interface is its own marketing. The screenshots in the press kit are the product, not a brochure of the product. The labels on the buttons describe what the buttons do. The error messages are written in the same voice as the welcome email, which is written in the same voice as the legal terms. The consistency is not an aesthetic preference. It is the only way to maintain the trust that the absence of marketing requires us to earn directly.

The staff consult rather than convert. When somebody emails support, the answer is the right answer for that person, not the answer that maximises retention. If the right answer is to use a different product, we say so. If the right answer is that the person is on the wrong plan, we move them to the cheaper one. The lifetime relationship matters more than the next billing cycle, because the lifetime relationship is the asset.

What the Soap Knows

The most useful sentence Aesop has ever taught the rest of us is the unwritten one inside its packaging. The bottle, when held, says: this brand believes the object is enough. The customer, by the time they have used a few drops, agrees. There is no further argument required. The product has done the persuading.

A piece of software, properly made, can do the same. The interface, when used, can say the same thing. The user, by the time they have spent ten minutes in the product, can be persuaded by what is in front of them rather than by anything wrapped around it. We have tried to make REN that kind of object.

That is the lesson.