Before You Build
Web AppLow Traction

VIDI

VIDI is an AI-assisted contract-risk tool for people reviewing agreements before signing. The useful lesson is not that VIDI failed; it is that early attention only matters if users return with real contracts and a clear reason to keep using it.

View source

Product snapshot

What it was

VIDI is an AI-assisted contract-risk tool that helps users understand agreements before signing.

Who it was for

people reviewing contracts before signingsolo founders and freelancers handling agreementssmall-business users without easy legal review access

Problem / value

It aims to make contract review more understandable by highlighting risks and helping users reason about agreements.

Core workflow

Upload or review an agreement before signing.; Understand contract risks in plain language.; Return with multiple separate agreements when the need repeats.

Product form

web appcontract-risk analyzerAI-assisted document review tool

Pricing model

Pricing is not disclosed in the captured public sources.

Competitors or alternatives

manual contract readinglawyer reviewgeneric AI document chat toolscontract analysis tools

What happened

Summary

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

Outcome

The case is an early retention-risk signal: repeat use on real contracts matters more than launch attention or curiosity-driven trials.

Core risk

Early attention can be mistaken for retention proof

Timeline

  • The founder posted on May 30, 2026 that VIDI was still early.
  • The founder separated attention from retention, behavior, urgency, and long-term usage.
  • The founder said some users returned with multiple separate agreements.
  • The public sources do not disclose user count, revenue, pricing, retention cohorts, or accuracy evaluation.

Before you build

Why it matters

Contract-risk tools need trust, urgency, and repeated real-document usage before early attention can be treated as product validation.

Primary check

Measure repeat use on real contracts, urgency, and willingness to pay before treating early AI-tool attention as product validation.

Checklist

  • What repeat behavior proves this is more than curiosity?
  • Which user segment has recurring contract-review needs?
  • What legal scope and accuracy bar must be clear before users trust the result?
  • Measure users who return with a second real document.
  • Track which contract types create urgent repeat use.
  • Ask users what decision they changed because of the review.
  • Validate willingness to pay for accuracy, confidence, or saved legal review time.

Relevant if

  • You are building an AI review tool where users may try it once out of curiosity.
  • You need users to trust the output for important decisions before they will pay or return.

Less relevant if

  • The product has already proven repeat use on real documents across multiple cohorts.
  • The tool is internal and does not need user trust, legal scope, or paid conversion.

Pre-build tests

  • Run a concierge review workflow on a narrow contract type before building broad automation.
  • Ask returning users whether they would pay for the next contract review.

Transferable lessons

  • Separate attention, activation, retention, urgency, and willingness to pay.
  • Track repeat use on real documents instead of launch reactions.
  • Treat a second real agreement as a stronger signal than compliments or signups.
  • Define accuracy, legal scope, and liability boundaries before users rely on the output.