Core concepts
Learn the vocabulary behind signals, rising opportunities, source evidence, product paths, credits, and launch learning.
Rising Opportunity
A Rising Opportunity is the central object in TrendRise. It is a scored market hypothesis built from source evidence, buyer pain, demand, product-format fit, channel fit, competition risk, and disqualifiers.
- A keyword can become part of an opportunity, but it is not the whole opportunity.
- A trend can inspire an opportunity, but trend movement alone is not enough.
- An opportunity should be specific enough that a small product test can prove or disprove it.
Signal
A signal is raw source input: a trend term, social post, Reddit complaint, marketplace listing, ad-library result, creator video, uploaded order row, or similar observation. Signals are preserved as evidence before they become scored interpretations.
Evidence
Evidence is source context that helps explain why an opportunity might matter. Good evidence has a source, query or context, freshness, region or channel when relevant, and enough detail to review later.
- Evidence can support an opportunity, weaken it, or show why it should be rejected.
- Evidence should stay separate from generated summaries and product recommendations.
- Cached evidence can be reused when the same public source result is still fresh.
Score
A score is a ranking aid, not proof. It helps compare opportunities by source confidence, pain clarity, product-format fit, demand, competition, channel fit, and risk.
- Use the reasons and disqualifiers, not only the number.
- Low confidence can still be worth watching if the buyer pain is sharp.
- High attention can still be rejected if it is news, celebrity, meme, unsafe, or not product-shaped.
Product path
A product path is the type of offer TrendRise thinks could fit the opportunity: digital product, physical product, service or offer, software or mini-tool, creator bundle, existing product, or custom/manual product.
Capability lane
Capability lane describes how TrendRise should help with the product. Native Builder products can be drafted inside TrendRise. Guided Setup products need a build brief. External products need positioning, launch readiness, tracking, creators, deals, and analytics rather than a generated asset.
- Native Builder: PDF guides, planners, workbooks, checklists, trackers, and simple worksheet packs.
- Guided Setup: spreadsheets, Notion packs, template packs, Canva packs, swipe files, and mixed bundles.
- External Build Brief: mini apps, software, physical products, services, existing products, and custom/manual products.
Credit-confirmed action
A credit-confirmed action is an operation that may spend credits because it asks TrendRise to generate, refresh, or prepare expensive output. The user should see the cost before running it, and the output should be saved for reuse.
Launch learning
Launch learning is the feedback loop after a product reaches real people. It can include sales, traffic, creator replies, objections, refunds, content performance, customer questions, and partner feedback.
FAQ
Why does TrendRise separate signals from opportunities?
Because raw source observations and scored hypotheses are different kinds of data. Keeping them separate makes evidence review, scoring, cache reuse, and future decisions more trustworthy.
What is the difference between Product Studio and Product Builder?
Product Studio chooses the product path and product idea. Product Builder helps create supported product assets after that decision, and only when that build lane makes sense.
What should I trust most: a score or a launch result?
Launch results are stronger. Scores help decide what to test; traffic, sales, creator response, refunds, and customer feedback show what the market actually did.