AI research SaaS: $1.2M seed round closed 2 weeks post-launch

Pre-seed AI research startup, USA

Live in 18 days. Seed round closed 16 days later. 7 enterprise clients at launch.

$1.2M

Seed round closed

18

Days to ship

100K+

Documents indexed

The situation

  • The founding team, an ex-Google researcher and a product designer, had created genuinely beautiful UI in v0. Clean, intuitive, exactly right for enterprise research teams. But there was no backend.
  • Document processing was fake, it just displayed uploaded files without actually parsing them. Search was client-side filtering of titles only. AI features were non-functional stubs.
  • They had a term sheet contingent on a working demo. The investor had set a 3-week deadline. They needed: vector search across 100,000+ research documents, multi-model AI orchestration (different models for different query types), team workspaces with role-based access, and a usage analytics dashboard for the enterprise tier.

What we did

  • Document ingestion pipeline: PDF parsing → chunking → embedding → Pinecone upsert
  • Hybrid search: vector similarity + BM25 keyword search with Reciprocal Rank Fusion
  • Multi-model AI router: Claude for reasoning, GPT-4 for extraction, Mistral for lookups
  • Team workspaces with role-based access, shared libraries, and search history
  • Enterprise analytics: usage patterns, cost tracking, productivity metrics
  • SSO via Google Workspace OAuth for enterprise procurement compliance
  • Async document processing queue via Bull + Redis, zero UI blocking

The result

  • The seed round closed 16 days after launch. The investor's term sheet was unconditional, no further technical conditions.
  • Three months post-launch, the platform has 7 enterprise clients (research institutions and consulting firms), $28K MRR, and a Series A process underway. The founder reports that 100% of enterprise deals cite the analytics dashboard and SSO as table-stakes features during procurement.

Timeline

How it unfolded

  1. Day 1

    Architecture + data modeling

  2. Days 2-4

    Document ingestion pipeline

  3. Days 4-7

    Query engine + multi-model routing

  4. Days 7-10

    Team workspaces + permissions

  5. Days 10-14

    Enterprise analytics dashboard

  6. Days 14-17

    Frontend integration + testing

  7. Day 18

    Investor demo + launch

The investor's technical advisor spent 3 hours trying to break it. He found one edge case with PDFs that had rotated pages. That was it. We closed 2 weeks later.

Co-founder · AI Research Platform · New York, NY

Stack

PineconeOpenAI EmbeddingsAnthropic ClaudeOpenAI GPT-4MistralLangChainSupabaseAWS S3Bull + Redis

Want to be the next case study?

Book a call →