Guide 01 / Validation
Validate a micro-niche before making products.
Turn a broad identity into one falsifiable launch hypothesis before you buy samples, build a store, or generate dozens of designs.
Planning guide only. No market result is guaranteed, and the content has no subject-matter expert review.
Write one narrow hypothesis
Use one sentence: “For [specific community] during [specific buying moment], we will test [one original design angle] on [one physical product] plus [one digital companion].” If the audience, moment, and angle cannot be named, the niche is still too broad.
List the language the community uses for itself, phrases outsiders misuse, and references that require permission. Do not turn scraped community language into a product before checking context and rights.
Build an evidence grid
Collect repeated questions, gift occasions, product complaints, price expectations, and existing alternatives from public community discussions and marketplace search. Record the source and date instead of relying on memory.
Use Google Trends as directional seasonality evidence, not proof of purchase intent. Compare several terms and regions; a rising line does not guarantee a viable store.
Score the first concept
Score community specificity, originality, rights risk, repeatable distribution, production margin, and digital add-on fit from one to five. Write the evidence beside each score.
Reject concepts that depend on protected logos, characters, employer marks, celebrity likenesses, or medical and professional claims you cannot substantiate.
Run the smallest test
Test three original concepts as mockups with one audience and one call to action. Use saves, qualified replies, and clicks as learning signals; do not manufacture testimonials or imply that a concept is already a customer favorite.
Advance only when one concept earns clear preference and passes the rights screen. Order a sample before promising quality, fit, color, packaging, or delivery.