Before You Build
Web AppLow Traction

TruthScore

TruthScore is a free web tool that checks YouTube videos for scam or high-pressure monetization signals. The useful lesson is not that the product failed; it is that free scans, product fixes, and founder-led comments still need a tested path to repeat use, trust, and revenue.

View source

Product snapshot

What it was

TruthScore is a free web tool for checking whether a YouTube video may contain scam, high-pressure monetization, or suspicious offer signals.

Who it was for

YouTube viewers evaluating make-money-online or finance contentpeople checking suspicious video offersbrowser users who want a quick legitimacy score

Problem / value

It helps viewers run a quick legitimacy check before trusting a video, creator, or funnel.

Core workflow

Paste a YouTube URL, review legitimacy and scam-risk signals, then decide whether to trust the video or offer.

Product form

web toolYouTube video checkerChrome extension link on official site

Pricing model

The official page presents the tool as free; the founder post reports revenue still at $0. Public sources do not disclose a paid plan.

Competitors or alternatives

manual YouTube skepticismbrowser safety extensionsscam-detection contentAI content classifiers

What happened

Summary

TruthScore had visible free usage and product learning, but the public follow-up still showed $0 revenue and unresolved distribution friction.

Outcome

This is an active low-traction case, not a shutdown case: free usage and product iteration existed, but public sources did not show a paid path or repeat-use proof.

Core risk

Free usage before paid or repeat-use validation

Timeline

  • The founder said an earlier post described TruthScore at $0 revenue and about 2,400 scans.
  • The follow-up post reported revenue still at $0, with 13 email subscribers, 10 YouTube subscribers, and 2,400+ total scans.
  • The founder said YouTube comments containing the product link were visible to him but invisible to other people.
  • A public creator response exposed a false positive, and the founder said it led to a scoring fix.

Before you build

Why it matters

A user may try a free checker out of curiosity, but paid demand requires repeat need, trusted results, and a channel that can actually move users into the product.

Primary check

Prove repeat use, a channel that can carry calls to action, and a paid path before treating free scans as market validation.

Checklist

  • Who needs this result repeatedly enough to pay?
  • What action proves trust beyond a one-time scan?
  • Which channel can reliably send qualified users?
  • What paid offer follows the free check?
  • Track repeat use by user, not only total scans.
  • Define the first paid conversion path.
  • Test a channel where calls to action are visible.
  • Track false positives and trust complaints separately from acquisition metrics.

Relevant if

  • You are building a free AI utility as the top of a funnel.
  • Your main traction metric is scans, checks, generations, or other free actions.
  • Your acquisition depends on comments, replies, or platform surfaces you do not control.

Less relevant if

  • You already have repeat usage tied to a paid workflow.
  • You sell to a known buyer through a channel you control.

Pre-build tests

  • Ask repeat users to pay for alerts, reports, or a browser workflow before adding more free features.
  • Run distribution tests in channels where product links are visible to other users.
  • Interview users who scanned more than once to find the paid job behind the behavior.

Transferable lessons

  • Do not treat total scans as proof of willingness to pay.
  • Measure repeat scans and retained users before expanding the free surface.
  • Test whether the distribution channel allows visible calls to action.
  • Use false positives to improve trust, but do not confuse accuracy fixes with business validation.