STUD
← Plays

Build · Assess & Decide · Analysis & Finance

Build a Disruptive-Channel Fit Register

A structured channel-fit register that scores each candidate channel 0 to 3 on Christensen's four disruptive-channel criteria with a written rationale per channel, and returns, by rule, a fit verdict (fueled, neutral, or starved) per channel plus a recommended channel drawn only from the fueled ones.

You receive: A JSON object with a channels[] array, each channel scored 0 to 3 on the four named criteria with a rationale of at least 15 words, a total, and a rule-computed fit verdict, plus a recommended_channel field consistent with the verdicts.

Part of Distribution

What's verified: STUD verifies the structure and arithmetic of the register: it parses as a JSON object, contains at least your minimum number of candidate channels, each channel is an object with a unique non-empty channel_name, each of the 4 named criteria (margin_pull_upmarket, motivation_vs_existing_line, aftersale_capability_fit, new_value_network_fit) is scored as an integer 0 to 3, each channel carries a scoring rationale of at least 15 words, the stated total equals the recomputed sum of the 4 scores, and the stated verdict matches the recomputed rule: fueled at or above your fuel threshold, starved at a total of 3 or below, neutral in between, and any channel scoring 0 on motivation versus the existing line is forced to starved regardless of its total. The recommended_channel must name a channel whose recomputed verdict is fueled, or be empty or null when no channel is fueled. Submissions over 200,000 characters are rejected, and parameters outside range (minimum channels 1 to 50, fuel threshold 4 to 12) are rejected. STUD does NOT verify that the scores reflect the channel's real economics, that the rationales are accurate or evidence-backed, or that the recommended channel will succeed in market: your product, target customer, candidate channel list, and current channel context are context for the operator, not machine-checked criteria.

Opens soon

Cost20 credits
ProtectionHeld until verified delivery

This play is verified and ready. It opens soon, once sign-in and payments are live.

Example

A sample of what this play produces. Your result is generated for your inputs.

Recommended channelDeveloper tool marketplaces (Vercel Marketplace, RapidAPI, GitHub Marketplace)
Channel nameMargin pull upmarketMotivation vs existing lineAftersale capability fitNew value network fitTotalVerdictRationale
Freelance marketplaces (Upwork/Fiverr referral integration)00112starvedUpwork and Fiverr earn their margin on hourly freelancer commissions, so a fixed fee verified outcome pays them less per job than the hours they already bill, leaving them almost no incentive to promote it and no verification support motion built to handle disputes.
Developer tool marketplaces (Vercel Marketplace, RapidAPI, GitHub Marketplace)333211fueledVercel Marketplace, RapidAPI, and GitHub Marketplace already sell developer integrations for revenue share, so listing a judge-verified outcome catalog next to those integrations adds a new higher-margin line without touching their existing hosting or API revenue, and their install, billing, and support tooling map directly onto onboarding it.
Boutique fractional-ops and management-consulting agencies21216neutralFractional-ops and management-consulting agencies still earn most of their revenue from billable hours, so a lower-priced verified deliverable is a mild threat to utilization even though it frees senior staff for higher-margin strategy work, and they have no process today for handling a judge dispute.
Indie-hacker and solo-founder communities (Indie Hackers, Product Hunt, r/SaaS)33028fueledIndie Hackers, Product Hunt, and solo-founder newsletters carry no billable-hours line to protect, so recommending a verified-outcome marketplace to their audience is pure upside for them, though these communities run no support desk and have zero capacity to help a member through a judge dispute.

Get early access to STUD the day it goes live.