A Mindjax Venture Lab experiment
Scout
An AI-assisted research workflow for finding, evaluating, and carrying forward organizations with practical problems worth solving.
AI / BUSINESS INTELLIGENCE
Problem
Manual prospect research is slow, noisy, and easy to repeat. Finding an organization is only the first step: a useful lead needs context, evidence, a plausible problem, and a reason to investigate further. As the geographic search space grows, previously discovered organizations and accepted opportunities also need to influence what gets researched next.
Approach
Treat discovery as an evolving research workflow rather than an autonomous sales machine. Scout searches within a geographic and business context, assembles evidence, evaluates a candidate's practical problem and fit, and produces a structured report for review. Previously surfaced pipeline context is passed into the run so the system can account for existing opportunities instead of rediscovering the same obvious leads indefinitely. Human review remains the boundary between a research signal and a working opportunity.
Build
Scout is a configured Python CLI with a linear search → evidence → analysis → buyer gate → technology landscape → qualification → ranking → report pipeline. The repository isolates Tavily and replayed-JSON search providers, uses OpenAI structured outputs behind an LLM provider, validates typed evidence and opportunity models with Pydantic, and writes both a readable Markdown brief and replayable JSON run artifacts. Command Center launches it without a shell, captures its run status and bounded output, finds the newest Markdown report, and parses the report into reviewable candidates. The report carries scores, industry, location, likely buyer, observed problem, evidence, existing-solution risk, Mindjax role, next action, and discovery questions. Imported candidates remain separate until a person adds one to the opportunity pipeline.
Research pipeline
Search providers are isolated behind a small interface, so live Tavily research and replayed JSON evidence follow the same analysis path.
Qualification and memory
Typed models carry evidence, scores, buyer access, technology landscape, unknowns, and duplicate-match reasons through the run.
Handoff
Scout writes a Markdown brief and JSON artifacts. Command Center imports the newest report for review before anything becomes a persistent opportunity.
Implemented
- Structured research reports with candidate scoring, evidence, observed problems, buyer context, solution risk, and recommended next actions.
- Local execution contract consumed by Command Center, including a report folder and a Markdown report handoff.
- Pipeline context supplied by Command Center so prior opportunities and reviewed candidates can inform later work.
- Human review before a candidate becomes a persistent opportunity.
Experimental / planned
- Expanding research breadth without increasing noise or duplicate results.
- Improving feedback from accepted, ignored, and deleted candidates across future runs.
- Evaluating the research workflow against real discovery conversations rather than raw result volume.
Technologies
- Python CLI
- Pydantic typed models
- OpenAI Responses API
- Tavily search
- Replayable JSON evidence
- Markdown reports
- Geographic targeting
- Deterministic scoring and deduplication
Outcome
Scout demonstrates a working path from broad research to a reviewable business-development signal. Its value is in the workflow around the model: context, persistence, evidence, deduplication, and a clear handoff to human judgment. The project continues to evolve as I learn which research patterns produce genuinely useful opportunities.
Screenshots
What I learned
- Agents need memory and state. Without pipeline context, research repeats itself.
- Search breadth does not automatically produce better leads. Evidence and fit matter more than raw volume.
- Human review is part of the product boundary, not a failure of automation.
- A research report becomes more useful when it carries a next action and clear unknowns.
- Business usefulness is a better measure than how many names a run returns.