VERDIKT
← Home

History, patterns, and worked examples

Skip this until you've seen the memo on the homepage. These sections show how archives and flags look over time — illustrative, not a promise of analytics depth.

History

See verdict drift across reruns — when you save them.

Signed-in users keep a timeline of memos per idea. Helpful when you change pricing, ICP, or wedge and want before/after without digging through chats.

conviction trajectory

Example: six revisits over eight weeks as the wedge narrowed.

Mar 14Mar 28Apr 12Apr 26May 03May 08

assumption ledger

Four assumptions on file. Two broken, two holding.

  • 01

    buyer is enterprise legal IT

    ✕ broken
  • 02

    $199/mo procurement-friendly price

    ↘ softened
  • 03

    solo lawyers will pay below procurement

    ↗ rising
  • 04

    case-state primitives are the wedge

    ↗ rising

recurring blind spots

Patterns the archive keeps flagging.

Three illustrative patterns surfaced across reruns on file. Each one is flagged on every new memo.

  • scope creep

    across 4 ideas

    Your first-pass framing tends to be enterprise-grade. By revisit 3, you narrow to a single segment. The archive flags this on file 02.

  • pricing optimism

    across 3 ideas

    Your initial price points sit roughly 2.1x higher than what holds after market contact. The archive lowers the next initial estimate accordingly.

  • buyer misidentification

    across 2 ideas

    You tend to name the budget-holder as the buyer. Your wedges actually target the user. Flagged as a soft assumption on every new memo.

Pattern notes are illustrative — shipped product surfaces may summarize differently.

Examples

Four mismatches we often flag in drafts.

Illustrative excerpts — yours will cite the wording you supplied.

  • 01·pricing

    ICP / pricing mismatch

    Your ICP does not match your pricing.

    example brief

    B2B procurement automation, $499/mo

    trace

    ICP is named as solo operators, but $499/mo lands above their discretionary spend. Buyer cannot purchase without procurement, which adds 6 to 12 months of cycle. Pricing or ICP must move.

  • 02·build cost

    build cost vs wedge

    Integration cost is larger than the wedge.

    example brief

    vertical CRM for solo immigration lawyers

    trace

    Integration surface (state-bar APIs, USCIS forms, e-filing) is 6 to 9 months of build. The wedge itself is one workflow primitive. The moat thickens with each integration, but capital efficiency is at risk.

  • 03·wedge mismatch

    buyer / user mismatch

    The buyer you describe is not the actual user.

    example brief

    AI copilot for clinical operations

    trace

    Brief names the practice owner as buyer. Wedge UX is built for the front-desk staff. Owner has purchase authority but no daily contact with the product. Adoption stalls inside the first 30 days.

  • 04·retention

    retention assumption

    Retention depends on behavior that rarely repeats.

    example brief

    yearly tax-prep tool for solo creators

    trace

    Core action (file taxes) repeats once a year. Retention model assumes monthly engagement. Either the product needs adjacent monthly value, or pricing needs to absorb the annual reality.

Every flag links back to the specific line in your brief that triggered it.

Try it once.

Describe the wedge bluntly — get the full memo shape with angles, tensions, verdict band, and a two-day checklist. Then decide what's worth a second filing.

Run a memoOpen sample memo

2 free runs / day · private · no card required