Opportunity workflow
How raw source signals become Rising Opportunities, product decisions, pipeline items, launch tests, and learning loops.
Signals are raw input
Signals are source observations from search behavior, social movement, communities, marketplaces, ads, creators, uploaded exports, or customer language. They are useful, but they are not finished opportunities.
- Examples: a Google Trends topic, Reddit complaint, Etsy listing pattern, TikTok engagement signal, YouTube creator topic, Meta ad-library clue, or uploaded sales row.
- Signals should preserve source context so they can be reviewed later.
- Most signals should be filtered, ignored, or watched rather than turned into products immediately.
Opportunities are structured hypotheses
An opportunity combines source evidence, buyer pain, product-format fit, competition, timing, channel fit, creator or affiliate fit, risks, and disqualifiers. It should be specific enough that a small product test can prove or disprove it.
- A useful opportunity names the buyer or audience.
- It shows what pain, confusion, cost, or desired outcome is visible.
- It has at least one believable product path and launch channel.
Opportunity Detail is the evidence dossier
Opportunity Detail exists so the user can understand the hypothesis before building. It should show source confidence, buyer segment, pain language, product paths, competition, channels, risks, disqualifiers, and next recommended action.
- Opportunity Detail can lead to Product Studio, Creator Finder, or Pipeline.
- It should not spend credits just because it was opened.
- Deep narrative reports should be explicit saved or credit-confirmed actions.
Product Studio makes the product decision
Product Studio turns one opportunity into product paths and then exact product ideas. It should decide whether the user needs Product Builder, Product Setup, Existing Product Import, Pipeline, or Creator Finder.
- Digital Product is a parent path, not automatically a PDF builder route.
- Physical, service, existing, custom, and external paths should use setup/import lanes.
- Users can save the product decision without generating a full product draft.
Product Builder and Setup are execution routes
Product Builder helps create supported product assets. Product Setup and Existing Product Import capture products TrendRise cannot or should not build directly. Both routes should preserve context for Pipeline, Launchpad, Creator Finder, Deal Room, and Analytics.
Pipeline status belongs to execution
Once an idea is worth action, move it into the workflow where statuses describe what you are doing next. Status should describe the current operational decision, not how exciting the idea feels.
- captured: saved but not reviewed.
- reviewing: worth a human look.
- watch: not ready, but may become useful.
- test: ready for a concrete experiment.
- building: being turned into a product, page, or launch asset.
- launched: live in market.
- rejected: not worth pursuing right now.
Launch and creator work need context
Launchpad, Creator Finder, and Deal Room should start from a selected opportunity, product, launch batch, or deal. They should not operate as disconnected lists because the product, audience, offer, terms, and tracking plan determine what good distribution looks like.
Analytics closes the loop
The workflow is not finished when the product launches. Analytics should connect traffic, orders, creator activity, customer objections, refunds, and learning back to the original opportunity so future decisions improve.
What not to skip
Skipping evidence review can turn TrendRise into a generic idea generator. The safest shortcut is not to skip validation; it is to use the correct fast lane for the situation.
- If you already have a product, skip discovery and import/setup the product.
- If you only have a trend, inspect evidence before choosing a product.
- If you have a product path, save the decision before generating assets.
- If you have creator interest, record terms and tracking before treating traffic as live.
FAQ
Should every signal become an opportunity?
No. Most signals should be ignored or watched. The point is to preserve attention for opportunities with clear buyer pain and a testable product path.
When should an opportunity move to Pipeline?
Move it to Pipeline when there is an operational next step: review it, watch it, test it, build it, launch it, or reject it. Pipeline should not become a dumping ground for every noisy signal.
When does an opportunity become a product?
It becomes a product candidate when the buyer, promise, format, channel, and next build or setup step are specific enough to act on.
Where do creator deals fit?
Creator work usually starts after there is an opportunity, product idea, product profile, or launch batch. Accepted proposals and concrete terms belong in Deal Room.