Pipeline

Pipeline's job

Pipeline is the execution board for opportunities and products that deserve action. It should show what has been captured, reviewed, watched, tested, built, launched, rejected, or removed from active work.

What belongs in Pipeline

Pipeline can hold Rising Opportunities, Product Studio decisions, Product Profile Drafts, promoted products, and launch candidates. It should not be used as a dumping ground for every raw trend or source result.

• Opportunity: a market hypothesis with evidence.
• Product profile: a specific product or offer being prepared.
• Launch candidate: a product/profile that can move into launch prep.
• Imported product: an existing product brought in for research, launch, creator, or analytics work.

Status meanings

Pipeline status describes execution state. It does not replace opportunity score, source confidence, or launch readiness.

• 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, landing page, or launch asset.
• launched: live in market.
• rejected: not worth pursuing right now.

Open, launch prep, or remove

A Pipeline item should make the next action obvious. Open returns to the best detail screen. Launch Prep creates or opens Launchpad context. Remove should be a workspace-scoped soft archive, not deletion of the original evidence.

Readiness is separate

A product can be in the Pipeline before it is launch-ready. Launch readiness depends on storefront or checkout setup, delivery method, target date, tracking, assets, creator content, and measurement. Pipeline should route to Launchpad when those checks need to be completed.

Keep context attached

Pipeline becomes useful when every item keeps its upstream and downstream context: opportunity, product path, product idea, product profile, generated outputs, launch batch, creator prospects, deals, and analytics scope.