What the specification has to survive
Short, anonymised notes from the export desk: what the product has to do, what is held on every batch, and what fails when it is specified badly. No logos, no adjectives.
Why these notes are anonymised
A distributor will let us describe how a product has to behave. Almost none will let us put their name on a page next to their buying pattern, their return rate, or the price they pay. That is the same reason your own customers will not let you publish theirs.
So each note strips the identity and keeps the engineering: the sector, the market, the trade-off the product presents and the control held per batch. If you need a named reference before you place an order, ask on the contact page and we will ask a customer in your market whether they are willing to take a call.
What every note records
The format is fixed, which is what makes the notes comparable. A note that skips one of these fields is a story, not a case.
| Field | What goes in it |
|---|---|
| Client profile | Sector, market and how long we have supplied them — no name, no logo. |
| Starting point | The trade-off or ambiguity the product presents, stated plainly. |
| What we hold on every batch | The control that keeps a specification stable across repeats. |
| What goes wrong in the field | The failure modes this product exists to avoid. |
| Timeline | How long we have supplied, and what has changed in that time. |
| Products | Links to the catalogue pages involved. |
| What we would tell another buyer | The judgement that transfers to a different customer. |
2 project notes
Cotton roll: one specification, two channels
A cotton roll is asked to do three jobs with one setting. Which job you sacrifice decides who complains.
First aid kit: writing a list a factory can build
A kit is not a product, it is a list. The work is making that list mean one thing to the person packing it and the same thing to the person opening it.