Pressure-test a product before you build around it
Give Claude a product idea, supplier link, screenshots, competitor examples, and the research you already have, then ask for a structured validation read rather than a winner prediction.
Prepare
Bring the evidence and boundaries
Claude is most useful here when the source material and the stopping rule are explicit.
- The product idea or supplier listing plus any screenshots, pricing, reviews, or market notes you collected
- The buyer, problem, buying moment, and alternative products you believe matter
- Your landed-cost estimate, target selling range, testing budget, and reasons you are considering the product
Run
Start with a prompt built for this test
Replace the placeholders with your product, store, supplier, creative, or metric context.
Analyze the product idea, supplier material, screenshots, and competitor notes I provide. Build a fact-versus-assumption table, assess demand logic and saturation risk, then return go, revise, or no-go with the evidence that would change your call.
Review
Check the reasoning before the action
Keep facts, assumptions, production choices, and consequential decisions easy to inspect.
- Separates supplied facts from assumptions and identifies evidence gaps before making a call
- Tests the demand story against the buyer problem, purchase trigger, and available alternatives
- Assesses differentiation options, saturation signals in your examples, and likely creative constraints
- Returns a go, revise, or no-go recommendation with the evidence that could change it
What you get
A useful output, with the limits still visible
A validation memo with demand reasoning, angle options, saturation risk, unresolved questions, and a conditional decision—not a guaranteed winner.
Ready to run it
Take the next decision out of the guesswork.
Open the prompt in Claude, review the assumptions, and keep store changes or spend behind your approval.
Direct answers
What to know before you run this workflow
What do I need to start pressure-test a product before you build around it?
Start with the product idea or supplier listing plus any screenshots, pricing, reviews, or market notes you collected. Add the remaining context listed in the steps so Claude can distinguish confirmed facts from assumptions.
What should I verify before using this product research workflow?
Verify the source material, cost or policy assumptions, and any missing fact Claude marks. Treat the output as a structured operating draft. Keep store changes, spend, supplier decisions, and legal or platform-policy judgments behind your own review.
Does Claude make the final decision for me?
No. A validation memo with demand reasoning, angle options, saturation risk, unresolved questions, and a conditional decision—not a guaranteed winner. You remain responsible for checking the evidence, approving consequential actions, and deciding whether the result fits the store, customer promise, economics, and current platform requirements.