“Make a shampoo for a sensitive scalp.”
“Put a lot of this ingredient in.”
“Make it feel more premium.”
“I think this sample is fine.”

BUILDB / COSMETIC PRODUCT DEVELOPMENT RESIDENCY
01 / THE REAL PROBLEM
A manufacturer develops what it is asked to develop. Without founder-owned criteria, the decision becomes choosing the ‘least bad’ option among factory proposals.
01Who is this product for?
02How should it feel?
03Which ingredients matter—and why?
04What must differ from the benchmark?
05What proof is actually needed?
06What must it cost?
02 / BEFORE → AFTER
“Make a shampoo for a sensitive scalp.”
“Put a lot of this ingredient in.”
“Make it feel more premium.”
“I think this sample is fine.”
01Keep sufficient first-lather cleansing while defining the primary and secondary surfactant system for a sensitive-scalp target.
02Improve dry-down root volume and residue against the benchmark.
03Separate the marketing ingredient from the Active System that drives performance.
04Sample B feels good initially but raises sebum perception at four hours; revise this in the next round.
03 / 3 MONTH STRUCTURE
Market → Customer → Benchmark → Product → Texture → Formula
One 3-hour class weekly × 4 + daily assignment feedbackPrompt → OEM → Ingredient → Package → Clinical
Build product-development prompts and apply them in the fieldKEEP → CHANGE → DROP → TEST
Two 30-minute reviews weekly × 4 / eight 1:1 reviews04 / MONTH 01 · DEFINE
Collect demand, price, review, complaint and proof language on one product-development standard—not a single search-volume number.
Move from Customer Need → Product Performance → Sensory → Formula Architecture → Manufacturing Brief.
Score appearance, dispensing, spread, immediate feel, 30 minutes, four hours, eight hours, repeat and over-use on a timeline.
Connect Claim → Formula → Clinical → Content while deciding proof priority and commercially viable cost.
05 / MONTH 02 · BUILD
This is not ‘plan a cosmetic product with ChatGPT.’ Each prompt is built with role, context, constraints and a defined output for real development work.
06 / FIELD
“This ingredient is used at a high level.”At what percentage?
“It is patented.”Which patent? Ingredient, composition, claim—and what is the patent number?
“This is the best formula.”Best by which standard: benchmark, sensory, stability, cost or efficacy?
07 / MONTH 03 · CONTROL
Manufacturer replies · samples · quotes · ingredient documents · package samples · clinical bids · cost
What stays, changes, stops or requires another test is logged with the reason and next action.
08 / FINAL DELIVERABLES
09 / BUILDB READY GATE
Why does this product need to exist?
Whose problem does it solve?
Does the formula deliver the product goal?
Is the target sensorial experience achieved?
Can the economics support a business?
Can clinical proof support the claim?
Are specifications complete enough to enter production?
10 / WHO IS THIS FOR?
You cannot decide what to build first.
Samples arrive, but you do not know what to revise.
INCI, texture, cost and proof need to be rebuilt.
You want to direct ODM work—not only receive proposals.
11 / COHORT 01 · FIELD RECORD
Product candidates existed, but the decision standards were scattered.
Market signals, competitive structure and portfolio priority were compared on one standard.
Demand and differentiation were reviewed to decide the next product-development priority.
Market analysis · Product direction · Decision criteria
Three initial SKUs existed, but their roles and factory criteria were disconnected.
Target problems, competitive structure, brand direction, texture and sensory standards were connected.
The three SKU roles and sample criteria became one development system.
Brand definition · 3-SKU system · Development brief · Clinical structure
Only publicly shareable teams, actual starting questions and the scope covered in the program are shown. No invented testimonial language is used.
3 MONTHS / MAX 5 TEAMS
BUILDB / COSMETIC PRODUCT DEVELOPMENT RESIDENCY
COHORT 02 / APPLICATION