Module 1: Pick a Product That Survives Sourcing

An idea is not a product until its numbers work at a quantity you can actually order. This module runs the math first — retail price, landed cost, minimums, variants — then validates demand, then locks it all into a one-page brief.

Start with the math, not the idea

Work backwards from the shelf. Pick the retail price a customer will honestly pay — not the price your spreadsheet wants, the price the market shows for comparable products. For most physical products sold direct, your landed cost (unit price plus freight, duties, and packaging, delivered to your door) needs to land at or below 25–35% of retail. Sell a $20 product and you have roughly $5–$7 of landed cost to work with. Everything in development is spent inside that envelope.

Run the envelope before you fall in love. A worked example: a pair of grip socks retails at $20. Target landed cost at 30% is $6.00. Early quotes put the unit at $3.40 in your blend, custom grip printing adds $0.35, the belly-band packaging $0.28, freight averages $0.90 a pair at your quantity, duty adds about $0.55. Landed: $5.48. It fits — barely — and now you know exactly which line to negotiate (freight and unit price) and which lines are fixed (duty).

If it does not fit, you have three honest levers: raise the retail price and accept a harder sell, simplify the product until the cost fits the price, or walk away before samples eat the budget. The dishonest lever — assuming costs will come down later — is how warehouses fill with product that loses money on every sale.

Use the calculator below with your own product. Put in real quotes when you have them and honest estimates until then. If the margin only works at quantities you cannot afford, the product is not wrong — the launch plan is. Fewer variants, one colorway, a smaller first run: the math decides the shape of the launch, not your mood board.

Landed cost & margin calculator

Play with the numbers — everything updates live.

Retail price ($) Factory unit price ($) Packaging per unit ($) Freight per unit ($) Duty rate (%)

Landed cost per unit:0

Landed cost as share of retail:0

Gross margin per unit before ads & fees:0

Your product retails at $24. Quotes put landed cost at $10.80 — 45% of retail. What is the honest move?

MOQ reality: quantities, sizes, and the variant trap

MOQ — minimum order quantity — is where launch plans go to be humbled. A factory's MOQ is rarely one number. It is per style, often per color, sometimes per size, and the real minimum is set by material minimums upstream: the yarn, fabric, or component the factory itself must buy in bulk. When a supplier quotes “MOQ 300”, your first job is to learn 300 of what, split how.

Now meet the variant trap. Your product has 6 designs, 2 sizes, and 3 colorways. That is 36 variants. At a modest 300-pair MOQ per variant, your “small first order” is 10,800 units and a five-figure wire before you have sold one. Founders hit this wall constantly because the store was designed first and the arithmetic second. Design the launch the other way: the total units your budget buys, divided by the smallest sensible variant count.

Cut variants with a hierarchy. Sizes are non-negotiable if fit is the product — but two well-graded sizes beat four sloppy ones. Designs can launch in waves: the strongest handful now, the rest as reorders prove demand. Colorways are the easiest cut and the easiest later addition, because a proven product earns its extensions.

There are legitimate ways to soften an MOQ: pay a small-lot surcharge, accept the factory's stock materials instead of custom-dyed ones, combine designs on one material run, or start with a sample-run specialist at a higher unit price. All of them trade unit cost for total exposure. That trade is usually right for a first order — you are buying information about what sells, not just inventory.

You have $2,000 for a first production run. A supplier's MOQ is 300 pairs per design, and your store concept has 12 designs. Unit cost is $4. What does the math say?

Validate before you develop

Development money is spent in the wrong order when sampling starts before anyone has shown they want the product. Validation does not need the finished product. It needs evidence that a specific person will pay a specific price for a specific promise.

The cheapest honest tests, in order: sell the promise first with a landing page and a reserve list — a small deposit beats a thousand “nice idea” comments. Show the closest existing product to your actual buyers and ask what they would change and what they paid last time; complaints about a competitor's product are a free development brief. Take pre-orders at a founders' price with a ship date you can hit. Each test costs days, not tooling.

What you are listening for is narrow: which variant they reach for, what price makes them pause, and what flaw in the current options they name without prompting. That last one is gold — the flaw your product exists to fix should come out of customers' mouths before it goes into your tech pack.

Set a kill line before you start: the number of deposits, pre-orders, or reserve signups that means “develop it”, and the silence that means “don't”. Write it down, because after two weeks of work every founder can rationalize weak signals. If the line is missed, the choices are reposition the promise and retest once, or shelve the product with your budget intact. Both are wins next to inventory nobody ordered.

Which signal is the strongest evidence that a product is worth developing?

The one-page product brief

The brief is the last planning document and the first development document. One page, seven lines, no adjectives that cannot be measured. If a line cannot be filled in, the decision has not been made yet — and the tech pack will quietly make it for you, badly.

The seven lines: Product (what it is, in one sentence a stranger could repeat). Buyer (who, specifically — “Pilates studio regulars, 25–45, who buy their own gear” beats “women”). Promise (the one improvement over what they use now). Proof points (the two or three spec choices that make the promise true — these become the tech pack's priorities). Price (retail, and the landed-cost ceiling it allows). Quantity (first-run units and variant count, from the MOQ math). Deadline (the launch date the production calendar must serve).

Worked example, grip socks: Product — a Pilates grip sock with a grip that survives washing. Buyer — reformer regulars buying 3–5 pairs a season. Promise — no slipping in class, no peeling grips after a month. Proof points — silicone grip (not PVC), 70%+ cotton blend, arch compression band. Price — $20 retail, $6 landed ceiling. Quantity — 500 pairs, 2 designs, 2 sizes. Deadline — in hand six weeks before launch.

Keep the brief where the work happens. Every spec argument, supplier quote, and sample note gets checked against it: does this serve the promise, fit the ceiling, keep the deadline? Half of development is saying no on schedule, and the brief is what you say it with.

Your turn: Draft your one-page brief — Product, Buyer, Promise, three Proof points, Price + landed ceiling, Quantity + variants, Deadline. Seven lines, no adjectives you cannot measure.

A brief says the buyer is “everyone who works out” and the promise is “premium quality”. What is wrong with it?