discover

SaaS Discovery — Phase 1

Research the SaaS product: $ARGUMENTS

Process

1. Create output directory: Derive a slug from the product name (lowercase, hyphens). Create output/<slug>/.

2. Research using WebSearch and WebFetch:

   • Product website (homepage, features page, pricing page, about page)
   • Documentation and API docs
   • Blog posts and changelogs
   • Press coverage and funding announcements
   • Review sites (G2, Capterra, Product Hunt, TrustRadius)
   • Job postings (for tech stack clues)
   • Social media presence and community
   • Traffic estimates (SimilarWeb mentions, Alexa alternatives)

3. Write findings to output/<slug>/01-discovery.md with these sections:

Output Structure

# [Product Name] — Discovery Report

## 1. Product Overview
- Name, URL, tagline
- Founded (year), headquarters
- Team size, key people
- Funding history
- One-paragraph description

## 2. Core Features
Organize by category. For each feature:
- Feature name
- Brief description
- Which pricing tier includes it

## 3. Pricing Model
- List all tiers with prices
- Feature gates between tiers
- Free tier / free trial details
- Enterprise / custom pricing

## 4. Target Market
- Ideal Customer Profile (ICP)
- Market segments served
- Primary use cases
- Company size sweet spot

## 5. Technology Stack
- Known technologies (from docs, job posts, GitHub)
- Architecture hints
- Integrations offered
- API availability

## 6. Traction Signals
- Estimated traffic / user count
- G2/Capterra ratings and review counts
- Product Hunt launch results
- Social media following
- Notable customers

## 7. Business Model Analysis
- Revenue model (subscription, usage-based, freemium)
- Estimated ARR range (if available)
- Unit economics indicators
- Growth strategy signals

4. Present findings to user:

   • Summarize key findings in 5-7 bullet points
   • Highlight anything surprising or noteworthy
   • Ask: "Is this accurate? Anything to add or correct?"
   • Ask: "Any specific areas to focus on for competitive analysis?"

5. Incorporate feedback — update the discovery document if user provides corrections or additions.

Guidelines

• Mark uncertain data as [ESTIMATED] or [UNVERIFIED]
• Always cite sources with URLs
• If a product page can't be fetched, note it and work with available data
• Prefer multiple sources over single source for key claims