Hypothesis Scoring — the pre-launch queue

Takes a pile of hypothesis ideas and returns a launch queue: which three go into work now, which wait, which are disqualified and why.

The point of this skill is to end the argument that usually follows a batch of outbound tests — "did it work or not" — with a number agreed on before the send.

Output language: the team's working language (Ukrainian by default for Ukrainian-speaking teams; English if the input is English). Plain words, no jargon.

What you need

• A list of hypothesis ideas — a matrix from hypo-generator, a workshop output, the team's own list, or raw text.
• Per idea, ideally: ICP · trigger (or static data point) · offer · channel · proof (a case with a number) · where the list comes from.

Missing fields are not a blocker — they are a finding. An idea with no proof or no list source fails the gate at Step 1. Never invent either one.

Ask for, if not given: which channels are live and how many senders (LinkedIn accounts / mailboxes), and whether the team has its own campaign history (own numbers always beat market benchmarks).