> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibescale.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Discovery

> The platform automatically analyzes your repository and builds a dashboard with your product's key data.

Discovery is the first step in the opportunity pipeline. Once you connect your GitHub repository, the platform starts the analysis automatically — no additional setup required.

## What happens during the analysis

VibeScale examines the code, structure, and metadata of the repository to infer your product's profile. While the analysis runs, the dashboard shows **"Analyzing your app..."** — this is normal and usually takes a few minutes.

You don't need to do anything at this point. You can leave the page open or come back later — the result is saved on the dashboard.

## What is displayed after Discovery

When the analysis finishes, the dashboard shows a set of automatically inferred fields:

<CardGroup cols={2}>
  <Card title="App Category" icon="tag">
    The market segment your app fits into (e.g., productivity, fintech, health).
  </Card>

  <Card title="Target Audience" icon="users">
    Who the app was built for — user profile or customer segment.
  </Card>

  <Card title="Problem Solved" icon="triangle-exclamation">
    The main pain point the app addresses, identified from the code and product structure.
  </Card>

  <Card title="Differentiator" icon="star">
    What makes your app stand out from existing alternatives.
  </Card>

  <Card title="Wow Moment" icon="bolt">
    The moment when the user first realizes the real value of the product.
  </Card>

  <Card title="Use Case" icon="list-check">
    The concrete scenario where the app is used and delivers the most value.
  </Card>

  <Card title="Main Feature" icon="puzzle-piece">
    The central feature that supports the app's value proposition.
  </Card>

  <Card title="Competitors" icon="chart-bar">
    Products or alternative solutions competing in the same market space.
  </Card>
</CardGroup>

In addition to these fields, the dashboard also shows:

* **Detected Features** — tags with features identified in the repository
* **Confidence Score** — a bar indicating how solid the inferences are, based on repository completeness and clarity
* **Tech Stack** — detected languages, frameworks, and tools
* **Routes and Endpoints** — mapping of routes or endpoints found in the code

## Data sources: web research vs. AI inference

<Note>
  Some fields, especially **Competitors**, indicate the source of the information:

  * **via web research** — data obtained through active search in external sources
  * **via AI inference** — data deduced from the code and repository structure

  This distinction helps you assess the reliability of each field before confirming it in the Alignment step.
</Note>

## What to do if the analysis takes too long

<AccordionGroup>
  <Accordion title="The dashboard shows 'Still processing...'">
    Larger repositories or those with more complex structures may take longer to analyze. Please wait a few minutes and reload the page — the result is saved automatically as soon as the analysis finishes.
  </Accordion>

  <Accordion title="The status remains 'In Progress' for a long time">
    If after 10 minutes the status is still **In Progress**, check if the connected repository is accessible and contains significant code. Contact support if the problem persists.
  </Accordion>

  <Accordion title="The status changed to 'Failed'">
    Click **Run again** on the dashboard to restart Discovery. If the error continues, contact support with the repository name and the time of the attempt.
  </Accordion>
</AccordionGroup>

## Next step

When Discovery is **Completed**, proceed to the [Alignment](/en/opportunity/alignment).