Skip to main content
Discovery is the first step of the opportunity pipeline. As soon as you connect your GitHub repository, the platform starts the analysis automatically — no additional configuration 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 panel displays “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 panel.

What is displayed after Discovery

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

App category

The market segment your app fits into (e.g., productivity, fintech, health).

Target audience

Who the app was built for — user profile or customer segment.

Problem solved

The main pain point the app addresses, identified from the code and product structure.

Differentiator

What makes your app distinct from existing alternatives.

Wow Moment

The moment when the user first realizes the real value of the product.

Use case

The concrete scenario in which the app is used and delivers the most value.

Core feature

The central feature that sustains the app’s value proposition.

Competitors

Products or alternative solutions competing in the same market space.
In addition to these fields, the panel also displays:
  • Detected features — tags with features identified in the repository
  • Confidence score — a bar indicating how solid the inferences are, based on the repository’s completeness and clarity
  • Tech stack — languages, frameworks, and tools detected
  • Routes and endpoints — mapping of routes or endpoints found in the code

Data origin: web search vs. AI inference

Some fields, especially Competitors, indicate the source of the information:
  • via web search — data obtained through active search from 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.

What to do if the analysis takes too long

Larger repositories or those with more complex structures may take longer to analyze. Wait a few minutes and reload the page — the result is automatically saved as soon as the analysis finishes.
If after 10 minutes the status is still In Progress, check that the connected repository is accessible and has meaningful code. Contact support if the issue persists.
Click Run again on the panel to restart Discovery. If the error persists, contact support with the repository name and the time of the attempt.

Next step

When Discovery is Completed, proceed to the Alignment step.