Fluent Collective / courses
0-day streak 0 XP Explorer rank
← Idea to Inventory

Module 0: Start Here

Product development is the unglamorous work between having an idea and having inventory: specifying the product exactly, finding who can make it, proving they can, and landing it at a cost that leaves you margin. This module maps the whole road so every later step has a place to land.

Product development is a system, not a shopping trip

Most first products fail in a predictable place: the founder goes shopping before they go specifying. They find a supplier with nice photos, ask “how much for something like this?”, get a friendly price, order samples, and discover three months later that the price was for a thinner material, a smaller size, and packaging that was never included. Nothing went wrong by accident — there was never a written spec for the factory to be wrong against.

Product development fixes that by reversing the order. You define the product on paper first — materials, measurements, construction, artwork, packaging, quality limits — in a document called a tech pack. Then you source: you send that same document to several suppliers and compare quotes on an identical product instead of five different interpretations of your idea. Then you sample, revise, test, and only then commit to a production order.

Think of the system in five stages: brief, tech pack, sourcing, sampling, production. Each stage produces one concrete thing. The brief produces a decision. The tech pack produces a document. Sourcing produces comparable quotes. Sampling produces an approved physical sample — the golden sample — that defines what “correct” means. Production produces inventory that matches that sample, verified by inspection before your balance is paid.

Skipping stages does not save time; it moves the cost later, where it is bigger. A spec question answered in the tech pack costs an email. The same question answered after 1,000 units are sewn costs a remake, a refund, or a warehouse corner of product you cannot sell. This course walks the five stages in order, with the actual documents and messages used at each one, so your first product is built on paper before it is built in a factory.

A founder finds a supplier, asks for a price on “something like this photo”, and orders 500 units. Three months later the product arrives thinner and smaller than expected. What actually failed?

The three ways to get a product made

Every physical product you can sell sits on a spectrum of how much of it is yours. Knowing where your product belongs saves you from paying custom prices for a stock product — or expecting custom control from a stock one.

Stock / white label. The factory already makes the product. You buy it with your label, your packaging, sometimes your color. Development cost is near zero, minimums are low, and you can launch in weeks. The trade: your competitors can buy the identical product tomorrow. White label wins when speed and cash matter more than uniqueness — a first product to learn selling with, or an add-on to an existing line.

Private label with modifications. The factory's base product, changed where it counts: your fabric blend, your grip pattern, your size run, your embroidery. You are developing on top of a proven base, so sampling is fast and the factory's existing machinery does the work. This is where most successful small brands live — genuinely differentiated where the customer can feel it, standard everywhere else.

Fully custom (OEM). The product is built from your tech pack alone: your pattern, your materials, your construction. Maximum differentiation, maximum cost — tooling, higher minimums, longer sampling, and every mistake is yours. Custom is the right call when the product itself is the brand, and the wrong call when you are still learning what customers want.

The practical rule: start as stock as you can stand, and buy customization only at the points a customer can see, touch, or compare. A grip sock brand does not need a custom yarn mill; it needs the right blend, a grip that survives washing, and artwork nobody else has. Spend development money where it shows.

You are launching your first product with a small budget. The base product exists at several factories, but you want your own fabric blend, your own artwork, and your own packaging. Which route fits?

What you will build in this course

By the final module you will hold a complete development file for one real product — yours. Not notes about developing a product; the documents themselves, filled in, ready to send. Here is the build order, which matches the modules.

Module 1 produces your one-page product brief and your numbers: target retail price, target landed cost, and a quantity plan that survives minimum-order reality. Module 2 turns the brief into a full tech pack, page by page — the document this whole process runs on. You will write a real one, for a worked example product, and then for yours.

Module 3 produces comparable quotes: where to find suppliers, how to vet them with a scorecard before you ever chat, and the exact request-for-quote message that gets real pricing on your spec instead of a catalogue and a shrug. Module 4 runs sampling: the sample ladder, how to review a sample against the tech pack, how to negotiate the whole deal, and the wash-and-wear testing that separates a good photo from a good product.

Module 5 lands it: the purchase order and deposit terms, quality inspection, freight and duties in plain English, and the landed-cost sheet you will price from — plus the reorder system so your second order is a formality, not a second education.

One scope note: the worked examples lean on soft goods — socks, apparel, simple sewn and printed products — because that is where tech packs and sampling matter most visibly. The system itself is the same for hard goods: spec, source, sample, produce. Where a step differs for molded or electronic products, the lesson says so.

Why does this course make you finish the product brief before writing the tech pack?