The Death of the Wishlist: How to Write an OEM Product Brief That Actually Works

In custom adult wellness manufacturing, a wishlist is not an early draft of a brief. It is a document that pre-authorises every argument you will have with your factory for the next six months. The adjectives look harmless on the page, and they are the reason projects overrun by a quarter and arrive at a product nobody can defend.

Most brand owners arrive at an OEM/ODM partner with a collection of feelings: it should feel premium, it needs to feel high-tech, it has to look expensive. To a designer those are useful provocations. To a production engineer they are a request to guess, followed by an invitation to be blamed when the guess is wrong. The gap between the two readings is where development budgets go to die.

Quick answer. A wishlist describes what you want to feel; a brief specifies what must be measured. Convert every adjective into a number with a tolerance and a test method before tooling is discussed. If more than 30 percent of your requirements are qualitative, the project is not ready to quote — each ambiguous line becomes a revision round, and each revision round costs three to five weeks and a tool or sample rework.

Why subjectivity is expensive, in numbers

The cost of an ambiguous requirement is not paid once. It is paid every time two people read it differently. Consider the phrase "premium feel." One engineer hears weight and density; another hears softness and matte texture; a third hears a magnetic closure. Three engineers, three interpretations, three samples. You reject two, approve the third, and the schedule has absorbed two full revision cycles — typically six to ten weeks — plus sample and courier costs, plus the delay cost of a launch that slipped into a worse seasonal window.

The hidden part is that this cost is not visible in any quote. No supplier line-item reads "ambiguity premium." It appears as a longer timeline, a higher sample invoice, and a persistent sense that the project is somehow harder than it should be. The product development literature is blunt about this: the cost of a design change rises by roughly an order of magnitude at each stage it survives, from concept to tooling to production [Ulrich & Eppinger, 2016]. A word that is ambiguous at concept stage becomes a tool modification at tooling stage, and a tool modification is two to four weeks plus the cost of the change.

There is a second-order cost that matters more for small brands. Ambiguity transfers control. When you cannot specify what you want, the factory chooses for you, using the criteria that matter to a factory: manufacturability, component availability, margin. Those are reasonable criteria and they are not your criteria. Every ambiguous line you leave in the brief is a decision you have delegated.

Why the wishlist exists in the first place

It is worth being fair to the wishlist, because it is not stupidity. It is what happens when a founder has strong taste, a clear mental image, and no vocabulary for tolerance. The feeling is precise and the language is not. "I know it when I see it" is a genuine design instinct that has no procurement translation.

The fix is not to suppress the instinct. It is to run two documents instead of one. The first is the brand intent document: descriptive, emotional, full of references, and addressed to your designer. The second is the specification: numbers, tolerances, test methods, addressed to your factory. Confusing the two is the single most common structural error in first-time development, because the intent document gets sent to the supplier and read as a specification.

Professional buyers in other categories solved this decades ago by separating the requirement from the verification. A purchasing specification is only complete when it contains three things: the parameter, the value with tolerance, and the method by which compliance will be demonstrated. Miss the third and you have not written a requirement; you have written an aspiration.

Figure 2 shows the translation for six common lines. The third column is the part buyers omit, and it is the part that decides who wins the argument at sample approval. "Shore A 25" without "measured with a durometer to ASTM D2240" invites the reply that the sample feels right. "Under 50 dB at 30 cm" without "measured in a quiet room at maximum power" invites a measurement taken at half power from across the room. If you want the longer treatment of how these requirements feed a quotation, the companion piece on writing a product brief that gets an accurate quote walks through the quote round-trip in detail; this article is about diagnosing and fixing a brief you have already written.

The four pillars of a brief that survives contact with a factory

A specification that can be built and audited has four sections. They are not optional and they are not interchangeable with a mood board.

Functional mandate

Describe what the product does, not what it looks like. Not "a vibrating toy" but "a dual-motor device with independently controllable internal and external channels, ten patterns, a 60-second escalation ramp, and a ninety-minute run time at medium power." Function is measurable, comparable between suppliers, and the basis of every cost difference you will see between quotes.

Materiality standard

"Silicone" is a family, not a specification. The difference between platinum-cure and peroxide-cure silicone shows up in odour, surface stability and extractables, and the difference between a Shore A 10 and a Shore A 30 body is the difference between a product that feels expensive and one that feels hollow. Name the grade, the cure chemistry, the hardness with tolerance, and the biocompatibility standard you are claiming. The grades and what they mean in practice are compared in silicone grades for adult wellness products.

Environmental constraint

Define the conditions the product must survive, because that is what drives seal design and test time. Will it meet massage oil, which attacks some elastomers? Will it be submerged, sprayed, or only wiped? Will it travel in a wash bag? Each answer maps to a different IPX level and a different reject rate, and the mapping is set out in IPX waterproofing ratings.

Dimensional boundary

"Small" is not a dimension. "118 mm by 34 mm at the widest point, 96 grams with battery" is. Dimensional constraints interact with everything else: a smaller body forces a smaller battery, which forces either a shorter run time or a more expensive cell; a narrower neck forces a smaller motor, which changes the acoustic profile. Fixing dimensions early prevents a cascade of compromises later.

The scoring test: is your brief actually a wishlist?

Run this on the document you are about to send. It takes four minutes and it reliably predicts how many revision rounds you are about to buy.

1. Count the requirements. List every distinct thing the product must do or be. Most first briefs contain 15 to 25; most are written as 5 paragraphs of prose with the rest implied.
2. Mark the measurable ones. A requirement is measurable if two people with instruments would agree on whether it passed. Aim for 70 percent or higher. Below 50 percent, the document is a wishlist.
3. Check the verification column. For each measurable requirement, write how it will be checked. If you cannot name a method, you cannot accept or reject a sample on that basis.
4. Look for conflicts. A 96-gram target, a 1,200 mAh battery, two motors and IPX7 sealing cannot all be satisfied in a 30 mm body. Conflicts found on paper are cheap; conflicts found at sample approval are tooling changes.
5. Rank by consequence. Which three requirements, if missed, make the product unsellable? Those get tolerances and test methods first; everything else can be negotiated.
6. Write the rejection criteria. State explicitly what would cause you to reject a sample. A supplier who knows the rejection criteria engineers to them; a supplier who does not engineers to the price.

The iron triangle: you cannot maximise all three

Every custom project sits inside a triangle of cost, time and complexity, and pulling one corner moves the other two. The mistake specific to this category is trying to maximise complexity — app control, dual motors, heating, IPX7, custom tooling — inside a first-order budget and a first-order timeline. The result is usually a product that has all the features and none of the reliability.

The useful discipline is to name which corner is the constraint before the project starts. If time is the constraint, use an existing platform and customise the surface. If cost is the constraint, reduce feature count rather than component quality, because quality reduction is invisible at approval and expensive at return. If complexity is genuinely the point — because the differentiation depends on it — then accept the longer timeline and the higher development spend, and plan the cash accordingly.

What you cannot do is decide the constraint halfway through. A project that starts as a fast platform customisation and grows into a new tool, a new PCB and an app is a project that will miss its window by a full quarter, and nobody will be able to say exactly when that happened.

What precision buys you

A tight brief produces four concrete commercial benefits, and none of them is abstract.

Comparable quotes. When three suppliers quote the same written specification, the differences are real cost differences. When they quote a wishlist, the differences are different interpretations, and the cheapest quote is usually the one that understood the least. Comparability is worth more than a 5 percent price difference, because it is the only way to know what you are buying.

Fewer revision rounds. Projects with a measured specification typically need one or two sample iterations. Projects with an adjective-based brief need three to five. At three to five weeks per round plus rework, that difference is a full quarter of launch timing.

A defensible price. A specification you wrote is a cost structure you understand, which means you can defend the retail price on the basis of what the product actually is rather than on the basis of what it looks like. That is the difference between a premium positioning and a premium veneer.

Repeatability. The specification becomes the component register for every future order. The second order arrives matching the first, and the third matches both, which is the operational definition of a brand rather than a batch.

The one-page form that replaces the wishlist

If the prose brief keeps collapsing back into adjectives, replace the format rather than the wording. A table forces the missing columns into existence. Six columns are enough: requirement number, parameter, target value with tolerance, verification method, priority as essential or desirable, and the consequence of missing the target. Fifteen to twenty-five rows is a complete brief for a single-SKU device.

The discipline the table enforces is the priority column. Without it every requirement behaves as essential, which is how projects acquire a specification nobody can build at the target price. With it, the factory can come back and say this device cannot hit your mass target and IPX7 and ninety minutes simultaneously, and you can decide which one moves. That is an engineering conversation. A wishlist can never host one.

Keep the brand intent document separately, and keep it short enough that your designer actually reads it. The pairing works because each document answers a different question: the intent document answers why this product should exist, and the table answers what will be measured when it does. Sending only the first is the wishlist failure. Sending only the second is a product with no reason to be bought.

One further column earns its place on the second project onwards: the source of the requirement. Mark each row as regulatory, commercial, or taste. Rows marked taste are the first to be traded when a conflict appears; rows marked regulatory are immovable; rows marked commercial have a price attached and can be renegotiated. Buyers who tag their requirements this way stop relitigating the same trade-offs at every sample round, and the same tags carry directly into the purchase order as acceptance criteria — the mechanism described in AQL inspection and defect classification and in the first-shipment sourcing sequence.

Do not outsource the requirement

The tempting shortcut is to ask the factory to write the specification, since they know the components. This produces a competent, manufacturable, entirely average product, because a factory's specification is optimised for what the factory already does well. It will be reliable and it will be unremarkable.

The division of labour that works is different. The brand owns the outcome: what the user should feel, at what price, verified how. The factory owns the architecture that delivers it: motor choice, thermal budget, seal geometry, PCB layout. When the brand cannot state the outcome in measurable terms, the factory fills the vacuum with its own defaults, and the product becomes a catalogue item with your logo on the box.

That is the real cost of the wishlist. Not the wasted samples, not the delay — the fact that an unwritten requirement is a decision you handed to somebody whose incentives are not yours.

---

Evokomoribi reviews briefs before quoting and returns written engineering comments on ambiguous or conflicting requirements, rather than quoting a number that will change later. If you have a brief you are not sure is a brief, send it to our engineering team for a specification review, or start from the OEM/ODM process overview.

---

Before you write the brief, settle which manufacturing path you are actually buying: see our OEM vs ODM decision guide for the cost, timeline and ownership trade-offs that determine what a factory can even quote you.

References

1. Wikipedia. "Durometer." Wikipedia, The Free Encyclopedia.
2. Wikipedia. "Requirements analysis." Wikipedia, The Free Encyclopedia.
3. Ulrich, K. T., & Eppinger, S. D. (2016). Product Design and Development (6th ed.). McGraw-Hill.
4. Reinertsen, D. G. (2009). The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing.
5. Wheelwright, S. C., & Clark, K. B. (1992). Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality. Free Press.
6. Norman, D. A. (2013). The Design of Everyday Things (Revised and Expanded ed.). Basic Books.