The person behind V12 DFS.
I'm Jorge Perez, founder and lead developer of V12 DFS. V12 is the optimizer I built because the tools I used to play DFS with kept hiding the math that mattered — ownership modeling, contest simulation, slate-aware projections — behind opaque “trust us” UIs.
I started shipping V12 publicly in early 2026. Every slate has a public post-mortem with real P/L, real entry IDs, and real lessons. When I'm down -90% ROI on a play-in slate I write that up the same way I write up the profit days. Nothing on this site is a black box.
What V12 does for you
V12 turns a slate into a ranked portfolio of lineups built for the contest shape you're playing. It reads injuries, lineups, pitching, weather, and ownership signals. It builds the candidate pool, simulates the contest, and ships a FanDuel-ready CSV — same workflow every night, no manual lineup surgery.
The dashboard lets you adjust the inputs that actually matter for a slate (contest type, entry count, exposure caps, lock players) and shows you the ranked output. No hidden “Optimal lineup of the day” pop-ups, no upsells inside the build flow.
Editorial process for the journal
The DFS news posts on /blog are produced with an AI assistant under my supervision. The headline, source, and impact ranking come from a transparent scoring function that weighs DFS-specific language (injuries, OUT/NS, confirmed lineups, pitching changes, weather, role movement). The narrative body is drafted by Claude Haiku with a strict system prompt I wrote — no hype, no guarantees, no invented stats, no betting-tip language.
Posts only ship after the body draft exists. If the model can't produce a usable draft, the post is held back rather than shipped with boilerplate. Every post is bylined under my name because I'm the editor of record: the prompt, the ranking math, the publication gate, and the cleanup process all sit with me.
This is on purpose. Most DFS “news” sites churn AI text with no attribution, no editorial process, and no track record. If something on this site is wrong or stale, that's on me to fix.
Track record
Public post-mortems live in the journal. Each one includes the contest, entry count, best/worst lineup rank, and the cash-line P/L. Highlights this season: a +124.7% ROI day on May 14 (#3/30 ace finish, $$19 entry → $$43 payout), and the inverse — a -90% ROI play-in disaster on Apr 2 where the lock engine excluded the players that ended up dominating. Both are written up the same way.
If you want the unfiltered version of what works and what doesn't in this game, those are it.
Contact
Reach out on X: @v12_dfs. DMs open for bug reports, slate corrections, and questions about the methodology.
Try V12 on tonight's slate
The optimizer is in the dashboard. Free dashboard access while V12 is in beta; an active subscription unlocks the per-slate generators.