Your first denim sample: what should you prepare before asking for development?

The situation this is written for

You have decided to make the jeans. You have references, maybe an audience, and a real sense of the product — and now you are about to contact someone to develop a sample. The instinct at this moment is to send the prettiest image you have and write “can you make something like this?” It feels like enough. It rarely is.

This is the creator-led founder’s most common stumble, and it is not a knowledge gap so much as a sequencing one. The information a development team needs is mostly already in your head; it has just never been written down in one place. The cost of not writing it down is invisible until it arrives — as a sample that is technically “like” your reference but wrong in the ways that matter, followed by a round of revisions you could have skipped.

So this is a preparation checklist, not a production manual. If the companion question is whether you can start denim sampling from reference images instead of a full tech pack — and you can — this guide is the next step: what to assemble so those references actually function as a brief. The thread running through all of it: everything you specify now is a decision the development team does not have to guess later.

Why preparation decides your sample more than the development team does

Here is the counterintuitive part. Founders tend to believe sample quality is mostly a function of who they hire — find a good team and a good sample follows. The team matters, but on a first sample the larger variable is usually what you handed them. A development team can only execute what is specified; the areas where new brands most often under-specify are exactly where the early rounds get spent.

The mechanism is simple. Every element you leave blank does not stay blank — it gets filled with a default. Unspecified weight becomes a reasonable weight. Unspecified wash becomes a plausible wash. Unspecified fit becomes the team’s standard block. None of those defaults is wrong, but each is a guess, and each guess that misses is a round of sampling. Good sourcing guidance frames the brief as something a supplier should be able to act on without coming back to ask basic questions about the garment — which is another way of saying the brief’s job is to pre-empt the questions that otherwise become delays.

A first sample is rarely ruined by bad work. It is usually shaped by the blanks you left for someone else to fill.

That reframes preparation from admin to leverage. The thirty to sixty minutes you spend assembling the package below is the cheapest revision round you will ever buy — because it is the one you do not have to pay for.

The five things to prepare — the core checklist

Everything you need fits into five items. None requires technical software or a tech pack. Together they turn a folder of images into a brief a team can run with.

The rest of this guide takes each item in turn, because the difference between a weak version and a strong version of each is where the real preparation lives.

1. Fit intent: the decision a photo cannot make for you

Fit is the item founders most assume their reference image carries, and the one it carries least. A styled photo shows a silhouette in a single pose; it does not state where the waist should sit, how high the rise is, or where the leg should break — and those are decisions, not observations. Denim fit is also unusually sensitive: even a deviation on the order of a centimeter in hip or thigh can shift how the fit reads on the body, which is why “looks about right in the photo” is not a specification.

You do not need measurements yet. You need intent, in plain words: a one or two word silhouette, the rise you want, where the hem should land, and how close or relaxed it should be through the thigh. If you have a pair of jeans whose fit you love, say so and send them — a real garment is the single most useful fit reference you can give, because the team can measure it rather than interpret it. When the sample comes back and you want changes, the same principle applies in reverse: give feedback in specifics, not vibes. “Increase the rise” beats “make it sit higher,” and a target measurement beats both.

It also helps to know how fit is actually judged, so you can prepare to judge it well. Fit is not evaluated on a hanger or in a single standing pose — it is assessed in movement. Sitting, walking, reaching, and bending all reveal problems a static photo hides, which is why brands test fit on a body rather than a flat surface. When your sample arrives, plan to evaluate it the same way: put it on a real body in your base size, move in it, and check the things a photo would never have shown you — crotch depth, thigh ease, whether the waist gaps when you sit. Preparing for that kind of review, rather than a glance-and-approve, is part of preparing for the sample at all. The founders who get to a sellable jean fastest are usually the ones who treat the fit review as seriously as the brief.

2. Fabric direction: brief a spec, not an adjective

“Make it in nice denim” is not a fabric brief. Buyer guidance for denim is blunt about this: do not brief fabric as “blue jeans fabric,” brief it as a measurable spec — composition, a weight range, a stretch target, construction — paired with a physical or approved reference swatch. The reason the guidance says weight range rather than a single number is that it lets the mill propose options that actually exist, instead of chasing one exact figure that may not.

For a creator-led founder, the practical version is lighter than that sounds. You need three things: a rough weight direction (light, mid, or heavy — and a familiar comparison such as “around a classic five-pocket weight” communicates more than a number to most people), whether you want it rigid or with stretch, and a physical reference if you can get one. The physical reference is the highest-leverage item here, because weight and hand are physical properties — how a fabric drapes and feels does not fully survive translation into an image. A swatch you like, or a garment whose fabric you want to approximate, removes more ambiguity than a paragraph of description.

There is one fabric-related fact worth carrying into preparation even though you will not act on it yourself: denim shrinks when it is washed, sometimes substantially in heavy wash processes, and the amount varies with the fabric and the wash. Pattern makers account for this by oversizing the pattern with a shrinkage allowance so that the washed garment lands at the intended finished size; skip that allowance and a finished pair can come back noticeably smaller than cut. You do not calculate any of this. What it means for your preparation is narrower and important: the measurement that matters is the finished, washed measurement, so when you compare your sample to a reference garment, make sure you are comparing like with like — a washed sample against a washed reference, not against an unwashed bolt or a differently treated pair. Whether the fabric is sanforized (pre-shrunk) or not also changes this picture, which is another reason a physical fabric reference, with its behavior already known, beats a description.

3. Wash direction: the variable that hides inside a color

Wash looks like the easiest item on the list and behaves like the hardest, so it is worth a moment of care now to save rounds later. In a photo, a wash reads as a color and some contrast. In production, it is a set of process variables — and the development team translates your reference into a recipe, rather than matching a pixel.

What this means for preparation is modest but specific. Send the closest wash reference you have. Then say, in words, how your target differs from it: cleaner, darker, more distressed, less contrast. Do not rely on the screen to carry the shade, because color is properly judged against a physical standard under controlled lighting, not from a phone. Expect that an exact physical wash standard will be established during sampling rather than fixed by your reference alone. If your reference is a finished garment you own, note whether it has been worn and washed, since a wash you love on a three-year-old pair is the result of wear, not a starting recipe.

One more preparation habit pays off disproportionately here: once you have settled on the main fabric, it is reasonable to ask the development team for shrinkage and colorfastness behavior before you commit to bulk, because shrinking and bleeding are exactly the problems that surface after a customer washes the garment rather than during your review. You are not running these tests yourself, and you do not need to understand the methods. You are simply signalling, in your brief, that wash performance matters to you — which tells the team to treat the wash as controlled development rather than a finishing afterthought, and sets you up to approve a wash standard you can actually hold a reorder to.

Brief a wash like a color and you have specified almost nothing; brief it as a direction away from a real reference and the team has something to build from.

4. Sizing and market: name the body before you grade the range

You do not need a full graded size chart to start. The first sample is typically made in a single base size to confirm the proto and the fit; grading to a full range comes after that base fit is approved. What you do need to decide is the base size itself and — more importantly — who the jeans are for.

This is where denim development quietly rewards the founders who think like designers. Defining a customer persona before sourcing is standard practice: who wears these, how old, what they wear them with, what they would pay. Those answers are not marketing fluff at the sample stage; they shape construction and fit decisions. A relaxed skate-influenced jean and a refined tailored one might share a silhouette word and need completely different blocks. Naming the body and the market gives the team a real target instead of a generic one, and it makes your fit feedback legible later because everyone is aiming at the same customer.

5. The short written brief: the cheapest thing that saves the most

The final item is the one that ties the other four together, and it is genuinely short — three to five lines. Its entire job is to let a development team read it and start, without coming back to ask what you meant. A workable brief states the garment and end use, the fit intent, the fabric direction, the wash direction, the base size and customer, and one line on why you want the sample.

Here is the difference in practice. A weak brief: “Hi, can you make jeans like the attached photo? Let me know cost.” A strong brief: “Looking to develop a women’s high-rise straight jean for a 25–35 streetwear customer. Mid-weight rigid denim, around a classic five-pocket weight — swatch attached. Mid-contrast vintage wash, slightly cleaner than the reference image, not distressed. Base size 27. This is a first proto to confirm fit and fabric before a small first run.” The second version is four sentences and removes nearly every question the first version invites. That is the whole game.

How preparation depth changes by brand stage

What counts as “enough preparation” is not fixed — it scales with where your brand is. Preparing too little stalls a first sample; preparing as if you were a scaling brand wastes effort you do not yet need to spend. The checklist above is calibrated for creator-led founders; here is how the same five items deepen as you grow.

Notice the through-line: the creator-led column is not a worse version of the scaling column — it is the right amount for the stage. The danger is not under-preparing relative to a scaling brand; it is under-preparing relative to the five basics. Get those five right and you have prepared correctly for a first denim sample, full stop.

What to expect once you have prepared: timeline and rounds

Preparation sets up the next question every founder asks: how long, and how many rounds? The honest answer is that both depend on the complexity of the garment and the wash, and on how complete your brief was — which is exactly why the preparation above is the lever you actually control. As a directional expectation rather than a promise, sampling a denim style commonly runs over a span of weeks rather than days, because a proto has to be made, reviewed, and usually revised before fit and wash are locked. Aligning wash and fit expectations early is repeatedly cited as the single most effective way to keep that span from stretching, because last-minute changes are the costly ones.

It helps to know the shape of the path you are entering. A first denim sample is rarely the last sample. Development typically moves through three stages, and what you prepare now is aimed at the first of them:

The practical takeaway is to budget for iteration rather than hope to avoid it. Treat each round as buying down the risk you carry into bulk, and resist the urge to read a normal proto — which is meant to be reacted to, not sold — as a disappointment. A founder who expects one perfect sample experiences ordinary development as failure; a founder who expects two or three productive rounds experiences the same process as progress. The preparation you did does not eliminate the rounds. It makes each one shorter and more about refinement than about discovering the basics you could have stated up front.

You cannot control how many rounds a wash needs to settle. You can control whether round one is spent refining your idea or reconstructing it.

The three pitfalls we see most often

1. The “make it like this” message with one image. A single styled photo and a request for a quote. The team can see the look and nothing about fit, weight, or wash, so it either guesses or emails back a list of questions — and the project stalls before the first round. The fix is the five-item package; it converts a mood into a brief.

2. Comparing a washed sample to an unwashed reference. A founder judges the returned sample’s fit or shade against a reference garment that was washed differently — or worn for years — and reads a mismatch as a mistake. Denim changes through wash and wear, so fit is judged on the washed sample, and a wash you admire on an old pair is an outcome, not a recipe. The fix is to note the state of any reference garment up front.

3. Treating the proto as the finished product. A founder expects the first sample to be sellable and is disappointed it is not. A proto exists to confirm the concept is executable and the fabric works; fit and pre-production samples come after. Expecting round one to be perfect turns normal iteration into a sense of failure. The fix is to budget for rounds and treat each as buying down risk before bulk.

A reference example

On a first run of roughly 1,200 pieces for a creator-led brand we supported, what separated a smooth development from a stalled one was almost entirely the brief. The founder arrived with the five items assembled without being asked: a women’s high-rise straight silhouette described in words, a loved vintage pair sent as the fit and fabric reference, a wash reference image with a one-line note that the target should be slightly cleaner and not distressed, a stated base size, and a three-sentence summary of the customer and the purpose of the sample. Because the fabric direction and wash direction were in the package from the start, the proto came back close on fit and in the right wash family — and the rounds that followed were refinements, not rediscoveries of the basics.

The contrast worth drawing is not with a “bad” founder but with the common case: the same product, briefed as a single image and a request for a quote, would have spent its first round establishing the very things the prepared founder had already decided. The preparation did not make the team better. It let a good team spend its rounds on the things that actually needed iterating.

After approval: capture what you prepared so the reorder holds

Preparation has a back end most first-time founders skip. The work you do before the sample has a mirror image after approval: capturing what was approved so it survives into bulk and the reorder. A pre-production sample — the final, gold-standard sample built with the production fabric, trims, and exact wash — is commonly sealed and signed by both sides and held as the official reference for bulk, and production units are checked against it. For a creator-led founder, the lightweight version is to record three things the day you approve: the measurements of the approved sample, the fabric reference (composition, weight, finish), and the wash standard, ideally a kept physical sample plus the recipe.

This matters because reorders typically run on new fabric and dye lots, and an approved physical reference is what a sensible production run compares the new lot against before cutting. The preparation you did to get the sample and the capture you do to keep it are two halves of the same discipline: writing your decisions down while they are fresh, so neither you nor anyone downstream has to reconstruct them from memory next season.

FAQ

What is the minimum I need before asking for a first denim sample?
Five things, none of which require a tech pack: a fit intent (silhouette, where it sits, where it breaks), a fabric direction (weight range and rigid versus stretch), a wash direction with the closest physical or visual reference you can supply, your base size and target market, and a short written brief tying them together. Industry sourcing guidance is consistent that a good sample brief lets a supplier proceed without having to ask basic questions about the garment. If a development team has to email you to ask what weight you want or where the waist should sit, the brief was incomplete, and that exchange is time you could have saved. None of these five items needs technical software, and assembling them is usually a matter of thirty to sixty minutes rather than a separate project.

Do I need a physical fabric swatch, or is an image enough?
An image gets you started, but a physical reference is far stronger for denim, because weight, hand, and drape are physical properties an image cannot fully encode. Buyer guidance for denim specifically recommends briefing fabric as a measurable spec, such as composition, a weight range, and stretch direction, paired with a physical or approved reference swatch, rather than as a vague description like blue jeans fabric. You do not need a lab report at this stage. A swatch you like the feel of, or a garment whose fabric you want to get close to, communicates more than any adjective.

How precise does my wash reference need to be?
Precise enough to show contrast level and whether you want distressing, and ideally paired with a physical reference rather than only a screen image. A wash is a set of process variables, not a color, so the development team translates your reference into a recipe rather than matching a pixel. Color is also assessed against a physical standard under controlled light rather than from a phone screen. The practical move is to send the closest wash reference you have, state plainly whether you want it cleaner or more distressed than the reference, and expect the physical standard to be set during sampling.

Should I decide sizing before the first sample?
You should decide your base size and who the garment is for, even if you do not have a full graded size chart yet. The first sample is usually made in one base size to confirm the proto and fit, and grading to a full range comes after that fit is approved. Denim fit is sensitive: even a roughly one-centimeter deviation in hip or thigh can change how the fit reads, so naming your base size and intended body and market early gives the team a real target. The full size chart can follow once the base fit is locked.

Why does denim need shrinkage thought about before sampling?
Because denim is washed, and washing shrinks fabric, so the finished measurement after wash is what matters, not the cut measurement before it. Industry guidance notes denim can shrink meaningfully in heavy wash processes, with commonly cited ranges varying by fabric and wash, and that patterns are oversized with a shrinkage allowance so the washed garment lands at the intended size. You do not calculate this yourself as a founder. You simply need to know that fit is judged on the washed sample, and that if your reference garment was unwashed or differently washed, the comparison is not apples to apples.

What is the difference between a proto, fit, and PP sample, and which am I preparing for?
You are preparing for the proto. A prototype sample is the first physical version of your design, made to see whether the concept is executable and how your chosen fabric works with it. A fit sample then focuses on size and wearability, and a pre-production sample, often sealed as the gold-seal standard, is built with the final fabric, trims, and exact wash, and must be signed off before bulk. What you prepare now feeds the proto, but preparing it well, with fabric and wash direction included, also shortens the path through fit and PP, because fewer fundamentals are still unresolved when you get there.

Sources

• Fabrikn — Pre-Production Sample Request Checklist (a sample brief should let a supplier proceed without asking basic questions; separate cost lines; ask for measurement tolerances and QC checkpoints): fabrikn.com
• Arcus Apparel Group — Fashion Design Checklist for Startup Apparel Brands (a manufacturer can only execute what is specified; where startups under-specify; use case affects construction and costing): arcusag.com
• Antor — Denim Manufacturing Process buyer guide (brief denim as a measurable spec — composition, weight range, stretch, construction — with a physical/approved reference swatch; approval gates): antor.xyz
• House of Ari Jogiel — Sample Making for Fashion Brands (measure samples against spec; give feedback in measurements, not “make longer”): jogiel.com
• Successful Fashion Designer — How to Review a Garment Sample (proto, fit, and development samples; request shrinkage and colorfastness reports; fit testing through movement): successfulfashiondesigner.com
• HAPA — How Are Jeans Manufactured (denim shrinks in heavy wash; patterns oversized with a shrinkage allowance; proto, fit, and PP sample stages): hapagarments.com
• Denimhunters — How Jeans Are Made: Design and Development (defining a consumer persona before sourcing; what denim designers check — weight, width, weave, grain): denimhunters.com
• Techpacker; HKTDC — pre-production sample stages, gold-seal/sealed samples as the bulk reference: techpacker.com; hktdc.com
• Cotton Incorporated / CottonWorks — Denim Finishing (wash as a set of process variables): cottonworks.com
• AATCC EP9 — Visual Assessment of Color Difference of Textiles (color judged against a standard under controlled light): standards.globalspec.com

For creator-led founders preparing a first denim sample, this is the kind of work SkyKingdom runs as an external denim product team — helping turn a folder of references into a brief a development team can build from, then capturing the approved sample so it holds into the reorder. If you are still deciding whether your references are enough to start, read whether you can start denim sampling with reference images instead of a full tech pack, or work through the denim sampling guide.