Methodology

DFS lineup optimizer methodology
from projections to rosters.

Courtside's DFS optimizer is built around transparent rules: projection target, roster legality, salary rules, strategy, and portfolio diversity.

◆ChalkCash

Highest-projected player at each position. Pure expected value — consistency wins.

PosPlayerSalaryProjFPPGCeilP50+Val
PG
Quentin Grimes
PHI@NYK
$4,00040.7—85.024%10.2x
SG
Stephon Castle
SASvsMIN
$7,00037.8—68.513%5.4x
SF
Josh Hart
NYKvsPHI
$6,00034.0—70.610%5.7x
PF
Kyle Anderson
MIN@SAS
$3,20028.0—62.42%8.8x
C
Victor Wembanyama
SASvsMIN
$10,80049.5—90.048%4.6x
G
De'Aaron Fox
SASvsMIN
$6,90042.6—79.526%6.2x
F
Harrison Barnes
SASvsMIN
$3,10028.8—56.12%9.3x
UTIL
Anthony EdwardsQ
MIN@SAS
$8,70047.3—81.541%5.4x
Projected
308.7
Ceiling
593.7
Floor
137.1

Value Rank

Grimes
10.2x
Barnes
9.3x
Anderson
8.8x
Fox
6.2x

Top Projection

Wembanyama
49.5 pts · $10.8K

Best Value

Grimes
10.2x · +3.2 above avg
● Live componentLineup card · live
Sports
NBA + MLB DFS workflows
Builder
Rule-based lineup optimizer
Controls
Salary · exposure · diversity · strategy
Output
Inspectable lineup cards
Primary keyword
DFS lineup optimizer methodology
Search intent
Understand how Courtside turns projections, salaries, rules, and strategy settings into DFS lineups.
Updated
May 30, 2026
How it works4 steps

From question to inspectable answer.

  1. I
    Step 1
    Define the build

    Sport, contest type, strategy, count.

    Cash and tournament strategies prioritize different things. Multi-lineup requests add portfolio rules, such as exposure caps and minimum roster differences.

    Example

    “Set up 5 MLB tournament lineups with 40% max exposure on any hitter.”

  2. II
    Step 2
    Solve under rules

    Salary cap, salary floor, positions, eligibility.

    The optimizer enforces DraftKings position rules and salary cap. A salary floor (default 96% of cap) prevents the optimizer from leaving money on the table because of projection noise.

    Example

    “Explain why this NBA cash lineup leaves $400 of salary unspent.”

  3. III
    Step 3
    Diversify

    Add lineup differences and exposure caps.

    Each new lineup must differ from prior lineups by a minimum number of players, and no single player can exceed your exposure cap.

    Example

    “Generate 20 lineups with at least 3 different players in every pair.”

  4. IV
    Step 4
    Inspect and export

    Lineup card → CSV.

    Each lineup card shows projection, ceiling, floor, salary used, and per-player reasoning. Where DraftKings draftable IDs are present, the CSV exports cleanly.

    Example

    “Export these to a DraftKings CSV.”

What it doesCapabilities

Three layers, one conversation.

01 / Optimization

The optimizer solves a constrained roster problem.

A DFS lineup is not just the top projected players. It has positions, salary cap, slate eligibility, and strategy rules. Courtside builds within those rules.

  • I

    Cash strategies prioritize projected fantasy points.

  • II

    Tournament strategies can prioritize upside or lower-owned players.

  • III

    Salary floor and cap rules help avoid unrealistic projection-noise builds.

02 / Portfolio

Multiple lineups need diversity by design.

When you ask for several lineups, Courtside can enforce player exposure caps and minimum roster differences so the set behaves like a portfolio.

  • I

    Exposure caps prevent one player from dominating every lineup.

  • II

    Diversity rules reduce duplicate roster structures.

  • III

    Strategy labels make it easier to see why each lineup exists.

03 / Inspection

A lineup card should explain the roster, not hide the model.

Courtside surfaces each player's salary, projection, ceiling, and role in the build so you can challenge the answer before exporting.

  • I

    Ask why a player made the build over a similarly priced alternative.

  • II

    Force, ban, or swap players in follow-up requests.

  • III

    Export lineups when the roster IDs are available for the slate.

GlossaryTerms used throughout this page

A short dictionary for DFS lineup optimizer methodology.

01
Lineup optimizer
The part of Courtside that searches through eligible players and finds legal rosters that match your strategy and rules.
02
Archetype
A preset strategy, such as safe projected points, upside, or lower-owned players.
03
Salary floor
A lower bound on salary used (default 96% of cap) so the optimizer does not leave salary on the table because of projection noise.
04
Minimum lineup difference
A diversity rule requiring at least a set number of different players between any two lineups.
Common questionsAnswered

Frequently asked, cleanly answered.

Q1.

What makes Courtside's DFS optimizer different?

It is chat-first and explanation-first. You can ask for a lineup, inspect why it was built, and revise rules conversationally.

Q2.

Does Courtside support multiple lineup strategies?

Yes. Courtside supports strategies such as cash-style, upside-focused, lower-owned, game-stack, paired-teammate, and steady builds.

Q3.

Can Courtside export lineups?

Courtside supports DFS lineup export flows when the necessary DraftKings slate identifiers are available.

Q4.

Does the optimizer factor ownership?

Tournament strategies can account for expected popularity, so Courtside can trade a little projection for a lineup that fewer opponents are likely to duplicate.

ContinueRelated research

Adjacent reading for the next step.

Read next

NBA DFS lineup optimizer

Use the methodology in a concrete NBA lineup workflow.

Open
Read next

Projection methodology

See how player expectations feed the optimizer.

Open
Read next

Bet verdict methodology

See how the same math layer underwrites betting verdicts.

Open

Stop dashboard-hopping.
Ask a question.

Start askingJoin Discord

Join the Discord for pick notes, slate questions, product drops, and smarter NBA and MLB conversation.