In clothing, overproduction starts when a brand commits to more SKUs and more volume than it can realistically sell at a stable full price.
The waste problem is usually described at the end of the chain, but the operational mistake happens at the beginning: range width, speculative buying, and inventory targets set before anyone has bought anything.
The first real decision you make when building a clothing brand is not about color or price. It is about range. How many products do you launch with?
Most answers land somewhere between "enough to feel credible" and "as many as we can afford to sample." Both of those answers share a problem. They treat range width as a confidence signal instead of a forecasting bet.
From the start, transparency and limited resources were the constraints. That combination made the choice for me: one product, not a collection.
I would have liked to start with more. A hoodie, a crewneck, maybe a tee. But more products means more specs, more suppliers, more decisions to get right before you have answered the basic question of whether anyone wants the first thing at all.
The hoodie was an easy call after that. It is the piece I wear most. When I am playing with my daughter. When I am on the couch with my wife. A hoodie is not a fashion statement for me. It is just what I wear when I am not performing anything.
The problem is not taste. It is forecasting.
Most young brands do not fail because they picked the wrong shade of grey. They fail because they build a range before they have any proof that people want a range from them at all.
A ten-product launch is not one bet. It is ten bets running at once on a single budget, each with its own forecasting question:
That is exactly where deadstock culture begins. Not at the landfill. At the planning spreadsheet.SRC 01SRC 02
What a one-product launch actually changes
Unsold stock pressure, and even the destruction rules the EU is now beginning to enforce, are downstream symptoms of earlier forecasting mistakes. They are not separate surprises that appear at the end of the chain.SRC 02SRC 03
Clothing was completely new territory for me. I had almost no knowledge of materials or construction. What I did have was that familiar accusation sitting in the back of my head: clothes used to last longer. I wanted to understand why, and whether anything could be done about it.
That kind of learning only works with one product. The variables that contribute to durability alone, like yarn, knit structure, finishing, and construction, are already more than enough for a part-time project. Adding a second garment would have meant spreading attention across twice as many decisions before I had mastered any of them.
What it does not solve
A smaller first range does not make a brand virtuous. It just removes some excuses.
What one product does not fix is straightforward.
A narrow range does not rescue a poor fabric choice or cheap trim package.
A smaller launch still needs named proof, not soft language from a factory or mill.
One product can still miss in the shoulder, body, or sleeve if the pattern work is weak.
If the quality bar is sloppy, a tight assortment only concentrates the mistake.
Bad pricing and weak transparency do not become honest just because the range is smaller.
What it does do is reduce the number of places where a brand can hide behind complexity.
What the experiment is actually testing
The question behind the first batch is narrow. Can a product survive on its own terms, without ad spend, without fake urgency, and without a catalog to disappear into?
I want to do this right and stand behind the decisions publicly. There will be compromises. I want to name them openly, because honesty about mistakes and limitations is something people are actually looking for, even if most brands do not offer it.
The real worst case is that the minimum order quantities are not reached and the hoodie never goes into production. That would still leave me with a lot learned and more genuine interest than most hobbies have given me. Testing new tools, building processes, figuring out how to move fast with limited resources. All of that has value either way.
If the batch fills, that means something. If it does not, that also means something. Both outcomes are clearer than a launch padded with extra SKUs, soft discounts, or inventory that gets explained away later.
The point is operational honesty.
If you want to follow the build in real time, the waitlist is open. And if you want to see what this thinking costs in actual euros, the cost breakdown is public.