Who should use the Screen Stocks workflow?
Teams or solo builders working on finance & legal tasks who want a repeatable process instead of one-off tool experiments.
Execution Map
5-step pipeline — follow each step in order
1Setup · Step 1 of 5
Open task pageBacktest trading strategies
Prepare inputs and settings through Backtest trading strategies before running screen stocks.
Why this matters
Backtest trading strategies sets up the foundation for screen stocks; clean inputs here reduce downstream rework.
What you get
Inputs, context, and settings are ready so the workflow can move into execution without blockers.
More optionsCompare
2Input · Step 2 of 5
Open task pageAnalyze sentiment
Use Analyze sentiment to build supporting assets that improve screen stocks quality.
Why this matters
Analyze sentiment strengthens screen stocks by feeding better supporting material into the pipeline.
What you get
Supporting assets from analyze sentiment are prepared and connected to the main workflow.
3Core · Step 3 of 5
Open task pageScreen Stocks
Execute screen stocks with Screen Stocks to produce the primary final deliverable.
Why this matters
This is the core step where screen stocks actually happens, so it determines baseline quality for everything after it.
What you get
A first-pass final deliverable is generated and ready for refinement in the next steps.
4Refine · Step 4 of 5
Open task pageOptimize investment portfolios
Refine and validate screen stocks output using Optimize investment portfolios before final delivery.
Why this matters
Optimize investment portfolios adds quality control so issues are caught before the workflow is finalized.
What you get
The final deliverable is improved, validated, and prepared for final delivery.
5Deliver · Step 5 of 5
Open task pageAnalyze Market Data
Package and ship the output through Analyze Market Data so screen stocks reaches end users.
Why this matters
Analyze Market Data is what turns intermediate output into a usable, publishable result for real users.
What you get
A finalized final deliverable is ready for publishing, handoff, or integration.