Skillrove: make the next step clearer

Experiment board

hypothesis

Assigned priority / effort: 1 / 1 (1–5)
Stage: Inspect result
Why test: A clearly named result link near the purchase action may help visitors evaluate fit; the current placement is an observation, not evidence of friction.
One change: Add one result-preview link beside the existing purchase action; keep all pricing and checkout behavior unchanged.
Observed basis: product-example: Loaded detail page has Buy now at $4.99 and a separate Open working example link under the video preview. The package produces landscape and portrait videos.
Primary metric: Eligible detail sessions opening the working example / eligible detail sessions
Guardrail: Verified paid access per eligible session and browser error rates remain acceptable under the agreed evaluation
Decision before starting: Agree on assignment, exposure definition and sample sufficiency before activation. Report inconclusive if the data cannot support the chosen evaluation.
Rollback: Remove the added link if the target is wrong or the defined guardrail is breached

hypothesis

Assigned priority / effort: 2 / 2 (1–5)
Stage: Purchase intent
Why test: A concise access comparison may help visitors choose a fitting option; no increase in sales is asserted.
One change: Add one fact-checked explanatory block about single-skill and membership access.
Observed basis: pricing-choice: Pricing presents Flex $9.99/month, Studio $79/year and Forever $169 one-time; a status block links Browse available skills, and text explains individual purchases.
Primary metric: Eligible sessions beginning the access option that they selected / eligible pricing-page sessions
Guardrail: No mismatch between displayed period/amount and actual checkout; monitor support confusion
Decision before starting: Recheck prices and released-package availability at implementation time, then evaluate a defined cohort; no presumed winner.
Rollback: Restore the current explanation if any amount, period or inclusion statement is inaccurate

hypothesis

Assigned priority / effort: 3 / 1 (1–5)
Stage: Inspect result
Why test: A more explicit setup label may help visitors understand the technical requirements before buying; this remains a hypothesis.
One change: Change only the Start setup link label, preserving its #first-run destination.
Observed basis: first-run: The purchase panel has Runs with and Start setup. The first-run section explains Python, Pillow, FFmpeg, sample commands and generated files.
Primary metric: Eligible detail sessions reaching the first-run section / eligible detail sessions
Guardrail: No broken in-page anchor or loss of accessible link clarity
Decision before starting: Validate the label and anchor in desktop/mobile keyboard flows before collecting a defined evaluation cohort.
Rollback: Restore the previous label if accessibility or navigation becomes worse