Interview: Stramgt 5961 Bradyjordan — 2026-05-08
Key Themes
1. This was an internal ops meeting, not an external interview. Bliss and Dustin spent the full session designing their research operations infrastructure. No external subject matter expert was present. The agenda was almost entirely process and tooling — not market discovery or hypothesis testing.
2. Daily debrief process formally codified. The team locked in a daily end-of-day call structure: one point person per meeting (whoever scheduled it) owns initial synthesis and runs that meeting’s debrief segment. Explicit goal is tactical execution only — capturing to-dos, contacts, resources, companies, and scraps. Hypothesis generation is reserved for a separate weekly meeting with a living working-hypotheses document.
3. Tooling stack is built but not integrated. Notion, Kanban, Telegram multi-channel, and DJ (AI assistant) are all partially operational but disconnected. A ~4-hour sprint is needed to wire everything together. Critical gaps: no owner fields on action items, Kanban not linked to debrief flow, DJ not yet connected to calendar or email.
4. Telegram channel architecture agreed. Four channels: General (catch-all + DJ quick queries), Debriefs (daily meeting outputs), Research (longer queries), and a combined Briefs/Logistics channel for pre-meeting primers and scheduling. Mobile input preferred for to-dos; web UI for triage.
5. Pre-meeting briefing seen as high-leverage. Both team members cited the Yisrael primer as concretely useful. Goal is to systematize: DJ ingests calendar, generates a pre-meeting brief (who, why, relevance, suggested talking points), delivers to inbox or Telegram before each meeting.
6. Pharma tabled; semiconductor focus held. Pharma dismissed as a distraction for now. Will revisit in two weeks if scheduling is easy. Semiconductor RDI track continues.
Notable Quotes
- “There has to be that human checkpoint every day where we look at all of this and we affirm it so that we’re actually tracking it.”
- “Like that little write up on Yisrael — was mad helpful. How do we just have it?”
- “I need another four-hour sprint just to wire everything up.”
- “The goal is explicitly not new hypothesis generation… it just needs to be running down tactical things so they don’t get dropped.”
Surprises
- The Bird meeting produced an unresolved open question (why did Aaron leave?) that nearly fell through the cracks entirely due to back-to-back scheduling — a live example of the exact failure mode the new process is meant to prevent.
- Semis Analysis subscription costs ~$20K; team believes Stanford access may exist as a workaround, or contacts could forward reports.
- Steve Blank meeting is on the horizon this month — flagged as a relationship worth managing carefully.
Open Questions
- Why did Aaron leave? (Outstanding from Bird meeting — still unresolved.)
- Does Stanford provide institutional access to Semis Analysis?
- Should pharma be formally scoped out or just deprioritized? Bigger strategic question deferred.
- What does the fully wired mission control dashboard look like, and when does it get built?