▲ 1 r/bet365

If you could build one betting research tool, what would it actually do?

Been messing around building my own research setup, mostly because I got tired of “edges” that looked great and turned out to be nothing once the line closed. Tracking CLV instead of my record was a humbling wake-up call lol. Curious what you all would actually want. Not picks, research. What’s the thing you wish existed that would genuinely help you bet sharper?

reddit.com
u/Clean_Reference_9927 — 3 days ago

Why is Encompass/Calyx so slow? Is it the local network or the software architecture?

I'm a Navy veteran (ITS on the USS Montana) and I've been helping some friends in the mortgage industry look at their office setups.

Coming from a background where 2-second lag is a system failure, I’m genuinely confused by what I'm seeing. These platforms feel like they're running on 20-year-old legacy code.

For the people using these daily: Is the lag usually during the initial file load, or is it specifically when you're trying to run credit and upload docs? I'm trying to figure out if there's an actual fix for the latency or if the industry is just stuck with "spinning wheels" as a standard feature in 2026.

What’s the worst technical glitch you’ve dealt with lately that almost killed a deal?

reddit.com
u/Clean_Reference_9927 — 2 months ago
▲ 44 r/IBRX+1 crossposts

FDA went live today with Real-Time Clinical Trials (RTCT). Makary and Walsh on stage. Two pilots already live:

Tech stack: Paradigm Health platform pulls trial data directly from EHRs. AI flags FDA-defined safety and efficacy signals, sends them to regulators automatically. No more quarterly batched submissions.

Stack this with the broader Makary regime: Elsa AI rolled agency-wide June 2025, one-pivotal-trial default (NEJM Feb 19, 2026), CNPV vouchers cutting select reviews to 1-2 months (16 awarded, first one already approved), Plausible Mechanism Pathway for ultra-rare. The entire development-to-approval pipeline is compressing simultaneously.

What I think this changes for catalyst trading:

Inter-phase catalysts collapse. The "Phase 1 readout, wait 9 months for Phase 2 announcement" trade pattern stops working. If real-time data feeds let FDA clear a phase transition near-instantly, the window where retail used to position disappears.

Interim analyses stop being discrete events. They go continuous. The pre-announced "interim data update at ASH" catalyst loses some of its volatility premium because the FDA already saw the data as it accrued.

Clinical hold risk becomes intraday. Real-time signal flagging plus automated escalation means halts mid-trading-day instead of in pre-announced disclosures. Bad for momentum trades, neutral for risk-layered analysis.

Insider edge on phase transitions narrows. When sponsor execs and FDA see the same dashboard, the information asymmetry shrinks. Worth watching pre-announcement insider sale patterns over the next 6 months.

Tech-forward biotech's get a moat. Sponsors that integrate EHR-feed trial infrastructure first move faster than peers running paper-batched submissions. Small and mid-cap names that partner with Paradigm Health or similar platforms early are the cleanest near-term edge.

Big pharma LOE math intensifies. AZN and AMGN getting pilot status give them faster pipelines. For peers facing real LOEs (BIIB Tecfidera 2025, BMY Eliquis 2026, MRK Keytruda 2028, ABBV Imbruvica 2027), a competitor compressing development by 6-12 months creates buyout urgency on clinical-stage targets that just got cheaper to advance.

Things I'm not sure about:

  1. Does FDA get veto power on phase transitions in real time, or is this primarily paperwork reduction? Big difference for sponsors.
  2. Do trial sponsors opt in voluntarily, or does this become standard infrastructure for new IND submissions?

Of the PDUFA outcomes my scanner has resolved, 3 of 11 approvals dropped on the news despite high PoA. REPL -30%. RCKT -20%. BIIB -5%. The PoA model called all three approvals correctly. The actual trade was the second-order layer. Compression makes those second-order layers more important, not less. (Submarine Catalyst, $29.99/mo, link in profile.) Quantitative research classifications, not financial advice.

How is everyone thinking about this? Specifically: anyone tracking which clinical-stage names are EHR-integrated already? That looks like the cleanest near-term edge.http://submarinecatalyst.com

u/Clean_Reference_9927 — 2 months ago

Posting because this is a data-layer problem I've spent serious time on, and I haven't seen it discussed cleanly anywhere.

Most quant infrastructure for event-driven trading assumes a simple mapping: event E happens to ticker T, so T's price reaction is what you model. For corporate actions and earnings, that mapping is usually clean because the SEC filer is the listed entity. For FDA biotech catalysts, it isn't, and the failure mode is structural, not occasional.

The setup. A drug has multiple economic stakeholders: the original developer, the company that licensed it for commercial rights, royalty holders from the original IP, and partners in specific geographies. When the FDA issues a decision on that drug, every public PDUFA calendar I've found lists exactly one ticker, usually whichever entity the calendar provider's scraper found first in the press release. That ticker becomes "the PDUFA stock."

The problem is that ticker is frequently not the entity with primary economic exposure. Sometimes it's the licensee. Sometimes it's a royalty holder whose upside is capped at a milestone payment. Sometimes the listed ticker has no exposure at all and the calendar is just wrong.

Concrete example from this month. MGNX (MacroGenics) shows up on every PDUFA calendar I've checked for an April 29 decision on TZIELD pediatric expansion. MGNX is not the sponsor. Sanofi is. TZIELD was originally MacroGenics' program, licensed to Provention Bio in 2018, and Sanofi acquired Provention in 2023. MGNX retained royalty and milestone rights. Per the 10-K, MGNX's economic exposure to the April 29 decision is a single milestone payment within a remaining schedule on the order of low hundreds of millions, paid out over time as commercial sales tiers hit. SNY is a $100B+ market cap and a pediatric label expansion barely registers. MGNX is a $200M cap and the milestone, if material, is a fraction of market cap and not a clean read because the per-event tier amount isn't disclosed.

If your model treats this as "MGNX has a binary catalyst on April 29," your sizing, your IV expectations, your post-decision expected move, all of it is wrong. The actual question is "what's the tier amount, what's the probability of approval, and what's the present value of that single milestone discounted for time and execution risk." Different model, different result.

This generalizes. LGND was the royalty holder on TVTX's sparsentan. When TVTX got the FSGS expansion approved on April 13, LGND moved off a passive royalty interest. Calendars that listed only TVTX missed the LGND opportunity entirely; calendars that listed LGND but treated it as a primary filer mispriced both the upside and the timing.

The structural fix. I built a drug_assets table that maps each drug to four columns of ticker exposure: parent_ticker (original developer), licensee_tickers (commercial rights holders), royalty_tickers (passive economic interest), partner_ticker (geographic or co-development partner). Every event in my pipeline joins through this table before scoring. Each ticker that surfaces get a ticker_role tag, primary, licensee, royalty, and the scoring layer treats them differently. Royalty exposure on a partner's PDUFA is a different model than primary commercial exposure, and the position sizing has to reflect that.

The engineering pieces that surfaced:

Sponsor name resolution is the bottleneck. ClinicalTrials.gov v2 returns lead sponsor as free text. "Pfizer Inc.", "Pfizer, Inc.", "Pfizer Pharmaceuticals", and "Pfizer Limited" are all the same parent, and the API doesn't normalize them. I wrote a tokenizer that strips legal-form suffixes and matches on the first remaining significant token. Catches roughly 92% automatically; the rest are manual map entries. The same pattern shows up in EDGAR filer name fields and FDA Orange Book extracts. Without normalization, the join doesn't work, and the whole layer collapses. Anyone who's worked on corporate actions infrastructure recognizes this as the same problem in a different domain.

The mapping has to be updated on M&A. TZIELD moved Provention → Sanofi in 2023. The drug assets row had to update or every TZIELD event from 2024 forward would point at the wrong parent. Acquired entities, name changes, and ticker changes (BGNE→BONE this year as one example) all require maintenance. There's no clean public feed for this, I run a watcher off SEC 8-K Item 1.01 and 2.01 filings and triage by hand. It works but feels brittle.

Polygon's per-ticker endpoints 404 hard on delisted, renamed, and CIK-only tickers. I added a regex validator that rejects anything starting with a digit (CIKs leak in from upstream sources) or anything outside ^[A-Z]{1,5}(?:[.-][A-Z]{1,2}|\d)?$. Cut error log noise meaningfully. The bulk snapshot endpoint silently returns nothing for the same tickers, so the validator runs upstream of any per-ticker fetch. Standard data hygiene for any equity dataset built on third-party feeds.

The valuation question on royalty/licensee tickers is genuinely hard. Even with clean mapping, what's the right model? For a primary filer, the expected move is a function of PoA, market cap, and historical post-approval volatility distribution. For a royalty holder, the expected move is a function of the milestone tier amount (often undisclosed in the public license) and the present value of the royalty stream. Different model entirely. I'm using a heuristic discount based on a cap-weighted milestone-to-market-cap ratio, but I don't think it's right and I'd take input from anyone who's modeled royalty equity exposure cleanly.

The questions I'd actually like input on:

  1. For corporate-actions-style mapping problems with non-stationary ground truth (M&A, name changes, license restructures), is there a cleaner pattern than the watcher + manual triage approach? I'm essentially running a CDC pipeline over SEC 8-K filings, and it works but I keep wondering if I'm reinventing something well-understood.
  2. Anyone modeled royalty equity exposure to a partner's binary event in a generalizable way? The literature on milestone payment valuation is thin, and most of what I've found is buy-side internal.
reddit.com
u/Clean_Reference_9927 — 2 months ago

A week ago, I posted about MGNX being a royalty ticker on TZIELD's pediatric expansion, with SNY as the actual filer. A lot has changed on the scanner since then, and April 23 ran two binaries, so worth an update going into Wednesday's MGNX PDUFA.

April 23 ran two binaries.

SNY Sarclisa for myeloma. Scanner called APPROVE 74%, STN 10. Approved. Stock did +2%. The STN layer was the interesting part. Most calendars had this as a high-volatility setup. Sarclisa is a Sanofi flagship; the move was already discounted, and a +2% close on approval is exactly what a STN score of 10 means in practice. STN is scored 0 to 100 on an inverted 80-baseline, with higher = more sell-the-news risk, so 10 sits at the very bottom of the range. Not a sell-the-news crash, not a moonshot, just absorbed. 2-for-2 on the SNY event, PoA right, STN right.

GRCE GTx-104 IV nimodipine for aneurysmal subarachnoid hemorrhage (NCT05995405). Scanner called APPROVE 72%, STN 10. CRL. Stock did roughly -50%. PoA wrong, STN wrong. Honest miss. Worth saying what the scanner did flag and what it didn't. It flagged an infinite runway anomaly (999-month implied runway with no commercial capex near the PDUFA, which usually means a sponsor that hasn't started building inventory or a sales force). It flagged the first-time approver. It did not flag the manufacturing risk that landed in the CRL. The CMC layer rated this as low risk because nimodipine is a small molecule with mature manufacturing. The CRL was specifically about the IV reformulation manufacturing, not the API. That's a real gap. 483 inspection history doesn't catch a sponsor's first commercial-scale fill-finish run. Adding that as a separate flag for first-time approvers with novel formulations of approved APIs is the fix.

Track record stands at 9 of 11 resolved. REPL and GRCE are the two misses. Both were APPROVE calls that turned into CRLs. Both involved manufacturing-adjacent risk; the CMC layer didn't surface. That's a pattern worth fixing rather than a single-event fluke.

Now MGNX Wednesday. The thesis is the same as last week. MGNX is not the filer; Sanofi is. TZIELD (teplizumab-mzwv) pediatric age expansion from 8+ down to 1+ for Stage 2 T1D is on the FDA's desk on April 29. PETITE-T1D phase 4, n=23 open label, 89.6% no progression to Stage 3 at 1 year, no new safety signals. EU already approved the same expansion as Teizeild in January. Priority review granted.

MGNX's economic exposure is the milestone ladder from the 2018 Provention Bio license (Sanofi bought Provention in 2023 and inherited the obligation). Per FY25 10-K, up to $330M remaining in regulatory and commercial milestones over time. Not revenue, not commercial infrastructure. One milestone payment if approved on Wednesday, amount not disclosed in the redacted version of the license.

Scanner output for the MGNX row this week: PoA 74% STN 88 of 100 (inverted 80-baseline, so 88 sits in the high band, scoring engine is weighting first-time-approver dynamics and royalty-recipient milestone uncertainty more heavily this week than last) Dilution MINIMAL, no ATM, no active shelf Net Edge 53 Innovation 45 of 100 Cash runway into late 2027 per the 10-K

The reason the catalyst page tags ROYALTY EXPOSURE VIA SNY at the top is the same reason I posted last week. Most calendars don't flag this. They show MGNX with an April 29 PDUFA and let the reader assume it's MacroGenics' own filing. It isn't. The MacroGenics-owned narrative on this ticker is Margenza (margetuximab) for HER2+ breast cancer, accelerated approval back in 2020, totally different drug. Every AI tool I've tested on MGNX hallucinates the Margenza story when you ask about April 29, including the AI summary on my own catalyst page, until I added the ticker role layer to the prompt.

What changed on the scanner since last week: Drug name resolver is now in production. Pulls verified drug, indication, and NCT number from SEC filings and matches against an internal drug assets table. GRCE resolved cleanly to nimodipine / GTx-104 / NCT05995405 with HIGH confidence the day before the CRL. MGNX still shows Margenza in some legacy views because the drug assets entry for teplizumab needs the royalty tickers array updated, fixing today. STN correctness threshold for the low band moved from "move > +20%" to "move >= -5%". The old threshold would not have credited SNY's +2% as an STN win, even though a score of 10 correctly predicted no crash. New threshold matches what a low STN actually means. Manual override map for the 17 indication-classifier mislabels (score-events defaults unrecognized strings to "Infectious," known bug). Long-term fix is a separate classifier function with its own table, next sprint.

Same question as last week. Does anyone have the milestone tier breakdown from the original 2018 Provention Bio license exhibit? Public filings show $330M remaining cap. The redacted exhibit doesn't show the per-event amounts. If you've read an unredacted version in an older S-1 or proxy, I'd like to put the schedule on the catalyst page.

Not telling anyone what to trade. Classifying a setup that's still wrong on most calendars three days before the event. I trade my own book off this and post resolutions when they hit, including the misses.

reddit.com
u/Clean_Reference_9927 — 2 months ago
▲ 4 r/Biotechplays+1 crossposts

GRCE / GTx-104 Update.

CRL on April 23rd, the stock dropped about 50%. My scanner called this APPROVE with PoA 79.1%. Bad call on the binary. Worth walking through what actually went wrong, because the bear case that hit was one I flagged.

FDA cited CMC and Non-Clinical issues. Specifically: leachable data for product packaging, non-clinical toxicology risk assessments, and manufacturing deficiencies at the contract manufacturing organization. The FDA did not request additional clinical data. That last part matters, and I'll come back to it.

In my pre-PDUFA post, I listed four bear cases. The third one was CMC risk and a narrow label as a real outcome that isn't a full CRL. I got the category right and the severity wrong. I was thinking about labeling language. The actual outcome was a full CRL on CMC grounds, which is a meaningfully worse miss because the company now has to remediate at the CMO, redo the leachable work, and address the tox risk assessments before they can even resubmit.

Here's the wrinkle that keeps the underlying thesis alive. The clinical case for GTx-104 was always that IV nimodipine solves a real bedside problem in the neuro ICU. STRIVE-ON didn't get questioned. The mechanism didn't get questioned. The 505(b)(2) regulatory path didn't get rejected. What got rejected was the manufacturing package and supporting non-clinical work. Those are fixable. The timeline and the cash burn during the fix are the new problem.

The balance sheet I described as lean going in is now a liability rather than a confidence signal. December 31 cash was 18.7M. Roughly another 15M in potential warrant proceeds. No active ATM, no active shelf. That setup made sense if you believed approval was 6 days away and product revenue was 6 months away. With a CRL plus a Type A meeting plus a resubmission cycle, you're looking at 12+ months of additional burn before they can even refile, and the company will almost certainly need to raise. The absence of a shelf flips from insurance-not-needed to has-to-file-into-bad-news.

Scanner output going in: PoA 79.1, STN Risk 18, Dilution Risk 0, Net Edge 74.7. The Dilution Risk score is the one I want to think about hardest. It was 0 because the structural setup looked clean: no active shelf, no active ATM, narrowing losses. The model treated those as positives without weighing the conditional scenario where a CRL forces them into the market from a position of weakness. That's a real model gap because the same setup is going to appear again on other names.

Two things I'm taking from this. First, no shelf and no ATM is not unconditionally bullish. It's bullish on approval. It flips to bearish on a CRL because forced dilution into bad news is worse than pre-PDUFA insurance dilution. The dilution layer needs to score the conditional case, not just the static one. Second, the qualitative CMC risk flag I raised wasn't weighted hard enough in the quantitative composite. Knowing a trial was safety-only and labeling could matter is a different statement from saying CMC manufacturing readiness is a binary risk on its own. STRIVE-ON's design was a clinical signal. The CMO and packaging work was a separate operational signal I had no real visibility into. That gap is the actionable lesson.

Anyone with FDA CRL remediation experience, I'd genuinely like to hear what realistic timelines look like for leachable and packaging work, plus a Type A meeting, plus CMO requalification. The street is throwing around 9 to 12 months as if it's settled. If anyone has worked through a similar CRL on a 505(b)(2), what did your actual cycle look like, and how much of the timeline is the CMO side versus the FDA review side?

Not making a recommendation on GRCE. I run quantitative classifications off public data and trade my own book. This was a miss on the binary, and I want to be honest about that. The clinical thesis didn't get touched, which is a different post-CRL setup than most.

submarinecatalyst.com

u/Clean_Reference_9927 — 2 months ago