What It Does

X Investor Radar turns fresh follow activity from your scout roster into a working research system. Instead of watching X manually, you organize scouts, pull the latest followings, review the resulting candidate stream, and move the strongest names into active tracking.

  • Organizes scouts into category, fund, and role-aware branch structures.
  • Pulls the latest followings for each scout through the backend and stores those snapshots.
  • Builds merged candidate records with bio, profile image, follower counts, website, timestamps, and overlap.
  • Lets you review the feed, hide duplicates, and push strong names into Monitor.
  • Keeps Monitor as a category-first queue for tracked deals, statuses, scout attribution, and Telegram handoff.
  • Generates Daily Reports and Follow Up surfaces from the same saved state.

Page By Page

  • Overview: top-level operating summary for branches, scouts, signals, and flagged projects.
  • Curated Lists: create branches, add scout accounts, store roles, import or export JSON, and inspect the branch map.
  • Pull Data: choose scope, category, sub-branch, and pull size, then run scouts individually or in selected batches.
  • Followers Feed: review fresh follow events, filter by scout or state, hide duplicates, and flag accounts into Monitor.
  • Monitor: manage tracked deals by category and status, assign which scouts follow them, and send deals to Telegram.
  • Check Who Follows: type any X handle to see which stored scout snapshots currently include it.
  • Daily Reports: review day-based report surfaces, worth-checking names, and AI-flagged activity.
  • Email Follow Up: generate project-specific outreach copy and internal notes.

Core Workflow

  1. Build the scout roster in Curated Lists by category, fund, and role.
  2. Run Pull Data for all scouts or a specific branch or fund.
  3. Each pull stores a snapshot and creates fresh follow events for returned accounts.
  4. Followers Feed becomes the triage surface: search, dedupe, inspect metadata, and flag to Monitor.
  5. Monitor keeps the tighter deal queue, where you track status, category, and scout-followed context.
  6. Daily Reports and Follow Up pages turn the strongest names into repeatable output.

What Counts As A Signal

A signal is a recorded event that one of your tracked scouts followed a candidate account during a pull. The app keeps the scout source, detection time, and the candidate profile as that profile accumulates across multiple scouts and days.

  • Overlap rises when the same candidate is surfaced by multiple scouts.
  • AI Flagged marks candidates that look like projects, companies, or thesis-relevant entities based on profile clues.
  • Duplicates matter because repeated pickup often signals stronger attention shifts than one-off follows.
  • Monitor is the manual queue where you decide what deserves ongoing work.

Pull Size And Scope

Pull size controls how many latest-following accounts are requested per scout during a refresh.

  • Range: 1 to 10
  • Default: 3
  • All Branches includes every scout in the saved branch map.
  • Specific Branch narrows the run to one chosen branch or fund.
  • The Pull Data page also supports selected-account runs and previous-run reruns.
  • Lower pull sizes stay tighter to the newest follows and help control upstream API usage.

Monitor And Follow Up

Monitor is where flagged or manually-added deals become active working items.

  • It opens category-first, then reveals tracked projects once you click into a category.
  • You can add deals manually, assign which scouts follow them, and set category or status.
  • Telegram Setup lets you send tracked deals out to a bot/chat flow.
  • Email Follow Up provides copy surfaces once a name moves from signal to outreach.

Persistence

App state is saved through /api/state. The system keeps your working state together so branches, scouts, monitor items, and signal history all survive refreshes.

  • Branch structure, scout roles, candidates, snapshots, signal history, monitor queue, and page UI state are persisted.
  • Local fallback data lives in .data when the backend is not using a database.
  • Pull usage and refresh state are tracked so the dashboard can show recent activity and scope summaries.

Recommended Use

  1. Start in Curated Lists and make the scout roster clean before you run anything.
  2. Use Pull Data narrowly on the branch or fund you care about right now.
  3. Triage in Followers Feed, especially duplicate pickup and AI-flagged names.
  4. Move the strongest deals into Monitor and assign status fast.
  5. Use Daily Reports, Check Who Follows, and Follow Up as downstream operating surfaces rather than separate workflows.