Before You Build
Web AppLow Traction

VIDI

VIDI is a live contract-risk review tool where early interest still needs to become repeat behavior.

View source

Product snapshot

What it was

VIDI analyzes uploaded contracts, highlights risky clauses, explains possible downside, and offers safer wording.

Who it was for

foundersfreelancerssmall businessespeople reviewing NDAs, SaaS agreements, service contracts, leases, or vendor contracts

Problem / value

It tries to make contract risk easier to understand before a user signs a financially important agreement.

Core workflow

  • review a contract before signing
  • identify risky clauses
  • understand potential financial exposure
  • receive plain-English explanations
  • prepare safer wording

Product form

web appcontract-risk analyzerAI-assisted document review tool

Pricing model

The official site lists $59/mo Starter and $99/mo Growth plans, plus limited free trial usage.

What happened

Summary

VIDI had early attention and a promising repeat-use hint, but the public evidence does not yet quantify retention, urgency, or paid demand.

Outcome

VIDI remains live; the case is best read as an early retention-risk signal, not a failure claim.

Demand signal

The founder described early traction as attention, not proof of retention, urgency, behavior, or long-term use.

Distribution issue

The public post shows strong discussion, but the founder also noted that repeated use and unprompted return behavior are the harder signals to prove.

Timeline

  • May 30, 2026: the founder posted on Indie Hackers about the danger of confusing early traction with validation.
  • The founder wrote that early traction can validate attention without proving retention, behavior, urgency, or long-term usage.
  • The founder noted that some users were returning with multiple separate agreements.
  • The official site currently presents VIDI as a paid contract-risk review tool with limited free trial usage.

Before you build

Why it matters

For high-trust AI tools, the second real document matters more than the first curious upload because returning requires both trust and recurring need.

Primary check

Separate first-use curiosity from repeat contract workflows before scaling acquisition or product scope.

Checklist

  • Segment first-time trials from repeat document reviews.
  • Track week-two and week-four active use by acquisition source.
  • Interview users who uploaded once and did not return.
  • Measure whether paid plans correlate with higher-stakes or repeated contract workflows.
  • What percentage of users return with a second real agreement?
  • Do repeat users come from the same acquisition source as first-time users?
  • Which contract type creates the clearest repeat workflow?
  • Where does the product stop and professional review begin?

Relevant if

  • You are building an AI document review product.
  • Your early traction is mostly launch attention, comments, or first-time trials.
  • You need users to return when a new real-world event happens.

Less relevant if

  • You already have measured retention by cohort.
  • The product is a one-time service with no expected repeat workflow.
  • Users are already paying for repeated reviews.

Pre-build tests

  • Manually review repeat-contract behavior for a small cohort before adding more document types.
  • Offer a paid review path to test whether urgency converts into willingness to pay.

Transferable lessons

  • Track repeat behavior separately from first-use attention.
  • Define what a second unprompted session means for the product.
  • For trust-heavy workflows, measure whether users bring real documents back.
  • Do not scale acquisition before retention and scope are understood.

If you build this today

Track second and third real-contract sessions, source of acquisition, and paid conversion before expanding contract types or marketing spend.