tokconnectUse product research to decide which customer question a demonstration should answer. The workflow combines a topic record, one relevant public video, and a bounded comment sample. It produces a proposed demo brief with proof requirements. It does not discover winning products, expose Shop sales, measure conversion, or approve claims.
Write the demo decision
Start with a product job that a viewer can see: setup, use, maintenance, comparison, or fit. “Find products that will sell” has no research boundary. “Choose one dishwasher-area demonstration that answers a visible setup question and flags durability evidence for product review” has a clear output. List the product facts the team has verified, prohibited claims, market, and the person who can approve product language.
Collect three categories of input. Use product terms to locate topic records. Use a narrow public-video search to find examples with a matching use case. Retrieve a fixed number of comments on a selected video to surface questions or objections. Record every input and close the sample before interpretation.
| Evidence | Job in the brief | What it cannot establish |
|---|---|---|
| Topic record | Names a research lead and orders candidates | Sales, conversion, or period of demand |
| Public video metadata | Links a use case to a real example | Viewer intent or visual details without review |
| Comment sample | Supplies individual questions and objections | Population share or universal customer need |
Work the kitchen record
The saved September 18, 2026 evidence searched kitchen products. Its selected topic record is kitchen products and utensils, query ID 7668817131013701652, search-volume estimate 4,660,868, and listed video count 741. A relevance search selected video 7665799980480826642 by anya.bumag, captioned “Soap dispenser and dish brush in one,” with 3,311,470 views, 70,854 likes, 877 comments, and 14,012 shares.
Those fields make the video a useful research example because its caption names the combined dispenser-and-brush use case. They do not show the product’s maker, sales volume, shopper demographics, or why people engaged with it. A human reviewer must watch the public link before claiming details about the setup, visual sequence, or results shown.
Read comments as individual evidence
The stored request retrieved 20 comments from that video and retains two selected records. One says, “That would make washing dishes a lot easier! Let us know please!” This gives the demo brief a question: where can a viewer learn more about the product details? The other says, “se daña rápido yo lo tuve,” with 386 likes. The saved note translates it as “it breaks quickly, I had one”; keep the Spanish original in the record so a reviewer can check the interpretation.
These two records offer different roles. The first supports an information-path requirement. The second flags durability as an objection that needs product evidence. Neither comment proves typical sentiment among all viewers. Do not calculate a percentage from two selected quotations, and do not write a durability rebuttal until the product owner provides material, warranty, or test evidence that fits the claim.
Choose the demonstration
The product team can propose a concise demo that shows the actual dispenser-and-brush setup, a normal use step, a cleaning step, and a route to verified product details. Keep the spoken or captioned language to what the team can support. The open durability comment changes the production plan: do not imply long life, “never breaks,” or comparative strength unless review supplies evidence and approved wording.
Make alternatives explicit. If the product cannot show a cleaning step, choose a setup explainer. If it lacks a verified information destination, pause the test. If the item does not solve a dishwasher-area task, reject the angle and research another use case. A rejection saves more than a generic demonstration that answers no question.
Research [product category] for one demonstration brief. Return the topic record, one relevant public video link with caption and counts, and a fixed comment sample. Extract individual questions and objections without estimating their prevalence. Propose one demo that uses only verified product facts. List the exact claim, proof owner, and validation needed before filming.
Deliver the demo brief
Decision: propose one dishwasher-area product-information demo
Topic evidence: kitchen products and utensils; estimate 4,660,868; listed count 741
Video evidence: 7665799980480826642; combined dispenser and brush use case
Viewer question: where can I learn more?
Objection: “se daña rápido yo lo tuve”; retain original and seek durability evidence
Demo: setup, normal use, cleaning, verified details
Proof owner: product reviewer
Pre-film validation: watch public reference; approve every material and durability claim
Status: proposed testMove the validated test to a calendar with the product reviewer as an explicit dependency. The research record remains useful when the team changes the product or claim.
Storyboard the proposed demo before filming
The stored reference is @anya.bumag’s public post. It supplies a caption-level combined dispenser-and-brush use case. Build a new demonstration from the client’s verified product facts; do not copy visual execution from a public post. The storyboard below turns the saved question and objection into production decisions.
| Shot | Viewer job | Proposed claim or action | Proof required before filming |
|---|---|---|---|
| 1. Task | Recognize the dishwashing problem | Show the actual dispenser, brush, and sink context | Product owner confirms components match the sold item |
| 2. Setup | See how the pieces work together | Show one ordinary dispense-and-brush action | Use instructions and safety wording approved |
| 3. Cleanup | Understand routine care | Show cleaning only if the method is supported | Care instructions or product test confirms the method |
| 4. Details | Find the answer to “let us know please” | Point to verified product information | Commerce owner confirms the destination and availability wording |
Put the Spanish durability comment on a claim-review card: original text, translation checked by a reviewer, proposed response, evidence owner, and final decision. If warranty terms or testing support a precise statement, use that approved wording. If they do not, omit durability language. Replace the demo with a setup explainer if cleaning cannot be shown, pause it if there is no verified information route, and reject the use case if the product team cannot clear the first two shots.