AI Venture Scout
An AI Venture Scout identifies, evaluates, and sources high-potential AI startups and founding teams for venture capital firms, co…
Skill Guide
A structured, multi-disciplinary process for systematically evaluating a startup's viability, competitive edge, and risks by scrutinizing its technology stack and codebase, total addressable market and business model, and founder capability and team dynamics.
Scenario
You are provided with the anonymized pitch deck and basic financial summary of a recently funded B2B SaaS startup.
Scenario
You are given a completed, positive due diligence memo for a consumer social app. Your role is to act as the 'skeptic' and find the weaknesses.
Scenario
A venture capital fund partner asks you to evaluate a Series B fintech startup with a pre-money valuation of $80M. You have access to the data room, management calls, and customer references.
Apply TAM/SAM/SOM to pressure-test market claims. Use CAC/LTV to gauge business model sustainability. Analyze CAP tables to understand incentive alignment. Evaluate founder-market fit for founder risk. Use technical debt models to assess long-term engineering cost.
Use Crunchbase/PitchBook for funding history and competitor landscape. Use SimilarWeb/SEMrush for traffic and customer acquisition channel analysis. Review public GitHub activity for engineering team productivity. Use visualization tools to synthesize financial and market data.
Answer Strategy
Structure the answer using the pillars (Architecture, Data, Team, Scalability). Mention specific tools (e.g., reviewing model versioning, infrastructure costs). The red flag should be concrete, e.g., 'proprietary training data with unclear provenance or licensing, which creates significant legal and competitive risk.' Sample Answer: 'I'd first review the AI model architecture and its dependency on proprietary vs. open-source data. A major red flag would be unclear data provenance, creating IP risk. I'd also assess infrastructure costs against projected scale, as AI-heavy operations can have non-linear scaling costs.'
Answer Strategy
Tests ability to disaggregate individual genius from team/system risk. Probe for frameworks to assess team scalability. Sample Answer: 'I would conduct separate interviews with the core engineers to assess their clarity on architecture, technical debt management, and deployment processes. I'd look for established practices like code review and CI/CD pipelines. The risk isn't the CTO's inexperience per se, but whether the technical foundation can scale without a crisis if the CTO needs to be augmented or coached.'
1 career found
Try a different search term.