Methodology in plain English
Three paragraphs. No formula. No jargon wall.
The score exists so a venue owner or solo operator can decide whether the wedge is worth their Tuesday-night budget. This page exists so you can decide whether the score itself was built for you.
01 · PositioningOperator-not-builder.
The scorecard is built for someone who has to ship a working wedge by Wednesday — not for someone with a research budget. The reader is the independent venue owner or the solo founder behind Independent bar or restaurant owner running 1–2 open mics per week. Every reading of the math is tuned for that voice: numbers first, caveats second, jargon last. If your read on a wedge depends on a 30-page methodology PDF, the score is not for you, and the page says so up front.
02 · Category coverageA few broad buckets, samples only.
The scorecard spans vertical service businesses, regulated workflows, developer tooling, and two-sided marketplaces — plus single-sided vertical SaaS and physical-product outliers. The cohort table on this page shows which of those buckets real users ran in the last 50 accepted scoring submissions. We do not list every category here by design; the precise breakdown is one of the things the actual report contains.
03 · The wedgeAsymmetric advantage, not feature parity.
The 'wedge' is the moment your idea has a defensible angle the incumbent does not cover — not the moment your score crosses a line. The scorecard penalises symmetric wedges (where the buyer can swap you in for the incumbent at zero friction) and rewards asymmetric ones (where the buyer cannot reverse the swap without re-doing the work). Why that matters: an asymmetric wedge means your first customer is harder to land but the next fifty are easier.