Skip to main content

HOW WE SCORE

Two questions. Two methods. Both published.

The build score is a rubric applied to your hours, skill and budget. The market answer follows written rules over evidence collected the day you run it. Neither is a prediction, and you can read both below.

See both on a real report

CAN I BUILD IT?

Build score

Scope clarity16%

Tells you if the first version is one product or three wearing a hoodie.

Build complexity23%

Shows the hard parts: workflows, realtime, payments, custom engines.

Dependencies18%

Names the APIs, stores, and approvals that can stall a solo MVP.

Ongoing workload18%

Counts the support, content, and ops that continue after launch.

Builder fit25%

Scores the idea against your hours, skill, and budget, not a fake team.

SHOULD I BUILD IT?

Market answer

Search demand
Monthly Google search volume for keywords specific to your idea, in your country.
Verified competitors
Products found in live search results and confirmed on their official site, with estimated traffic.
Entry prices
The cheapest paid plan read on each competitor pricing page, when it is public.
Switching demand
Monthly searches for an alternative to each competitor.
Market judgment
A typed judgment of how open the market is, made from the collected evidence only.

VIBE CHECK / Vibe Engine v0.8

How the build score is computed.

Five weighted dimensions give a base score. A typed judgment of the whole brief for your profile is averaged in, then bounded adjustments for workload, runtime and content apply. Some builds hit a ceiling no matter how simple the rest is, such as live dispatch or a custom engine. The report shows each step for the scope you asked about.

Your setup, not a fake team

The same idea scores differently for a beginner with five hours a week and an experienced builder with twenty. That is the point.

Count unique work once

Extra workflows and templates add effort without counting the same work twice. Large datasets do not become thousands of screens.

Unknowns stay unknown

Missing technical knowledge removes the score instead of guessing it. Unverified costs stay unknown. Stale data lowers confidence.

A rubric, not a prediction

70+ is IT VIBES, 45 to 69 is IT COULD VIBE, below 45 is NOT REALLY. These are product thresholds, not success rates or delivery promises.

MARKET CHECK / Market Engine v0.6

How the market answer is decided.

Build it

A clear opening and strong evidence: demand found, at least three verified competitors, at least two public prices and no research gap.

Find a wedge

Real demand with established products in place. You can win on a narrow angle, and the report names where to look.

Test first

The evidence is too thin to call: no demand found and fewer than two verified competitors, or too little to judge. You get the test to run.

Not yet

No observable demand, or a two-sided marketplace facing established players that already serve the job.

Evidence level

Strong
Demand found, three or more verified competitors, two or more public prices, no research gap.
Moderate
Some of the above. The answer holds, with gaps the report names.
Thin
No demand found and fewer than two verified competitors.

GUARDRAILS

Rules the answer cannot break.

  • Search volume alone never makes demand strong.
  • A crowded market is not a closed market.
  • A public price does not prove your buyer will pay.
  • A competitor is listed only once verified on its own site.
  • A language model writes the report; it never sets the answer.
  • The same evidence always gives the same answer.

YOUR NEXT MOVE

Score the idea you are about to spend a weekend on.

The Vibe Check is free. Every report shows its numbers, its sources and what is still unknown.

Check if I can build it