Skool About-Page Testing: Ryan Duncan's Experiment Plan

Skool About-page testing should start with one measurable change, a saved control and a consistent traffic comparison. Ryan Duncan's current Skoolers post supplies a useful experiment idea: improve packaging and test your own creatives before handing stronger assets to Growth Boost. It does not supply a proven conversion lift, a native Skool split-testing feature or a tested automation we can recommend.

Ryan DuncanShared Skool's Growth Tab is Live! My Thoughts... in Skoolers. Captured 5 October 2026; displayed 3d, 162 likes and 45 comments.

Ryan's plan, separated from its results

Ryan says his Growth tab is not yet unlocked and that he needs to improve efficiency. He describes rewriting About copy, checking nearby groups, clarifying the audience in his graphics, showing his face and adding member wins and review screenshots. Product shots from the classroom are another planned addition.

He also proposes testing video ads himself, then supplying the stronger creative to Skool. His third idea is an automated routine, using a tool he calls a grok bot, to rotate copy and collect data. We did not inspect that tool, its permissions, code or output. The post is a practitioner's account and plan, not a validated software integration.

The community behind the advice

The Ryan Duncan profile lists The Sauce as his owned room. His biography describes seven Skool Games wins; we have not independently audited that credential.

Ryan Duncan

The Sauce owner, sharing his approach to Skool acquisition, ads and offer packaging.

The offer targets community builders selling memberships below $297 per month who do not want constant sales calls or content production. The page promises Meta ads guidance, templates, a Flagship Framework, a 7-Day YES Machine, DM conversion guidance, direct support and a weekly live call. These are advertised deliverables, not independently tested services.

The body also advertises a future $109 price at 90 members, despite displaying 101 in another line. The live control showed 77 members and $99/month. Those inconsistent copy statements are not a reason to claim the higher price is already active.

Why rotating copy is not automatically an A/B test

Changing the page Monday and again Thursday compares different time periods. If an ad campaign, audience or promotion changes between them, the copy is not the only plausible cause of a join-rate difference. Simultaneous randomized exposure and sequential before/after editing are different designs.

Ryan suggests intervals based on daily visitor totals. Those are his operating suggestions, not universal sample-size rules. Optimizely's sample-size guidance identifies baseline conversion rate, minimum detectable effect and the number of variants as planning inputs, and warns about seasonal and campaign effects. Daily traffic alone therefore does not establish that a comparison is conclusive.

A practical test log for a community owner

First save the current copy and graphics with a version date. Define the question before editing: for example, whether a clearer audience statement improves paid joins per comparable visitor. Keep price, trial, promotion and acquisition creative stable where possible.

Record each version's dates, visits, joins, traffic source and any offer change. Decide how you will evaluate the result before checking it repeatedly. If the source mix or offer changes, label the result exploratory rather than treating the winning number as causal proof. Also examine refunds and continued participation; a page that attracts the wrong buyer can improve initial joins while damaging the membership.

This process is editorial guidance, not a claim that Skool exposes every field or runs randomized experiments natively. Use the measurements actually available in your account. Our analytics guide explains the broader dashboard context; the About-page guide covers writing the offer, rather than testing attribution.

Before using autonomous editing tools, retain manual approval and a rollback copy. No automation is needed to begin a version log. Read the Skool ads guide for channel context and the top-100 About-page analysis for observed packaging patterns, not guaranteed winners.

Frequently asked questions

Does Ryan's post prove an About-page conversion increase?

No. It describes changes and a testing approach without a quantified, controlled lift result.

Is changing copy every few days a randomized A/B test?

Not by itself. Sequential edits can be affected by changing traffic, seasonality, promotions and other page changes.

How long should a Skool copy test run?

There is no universal interval from visitor count alone. Baseline conversion, meaningful effect size, variants and traffic comparability matter.

Is the grok bot a verified Skool feature?

We did not verify the tool or integration. It is part of Ryan's account, not a tested native feature in this article.

How much does The Sauce cost?

Its authenticated join control displayed $99/month on 5 October 2026. Conflicting member-count and future-price copy should be clarified with the owner.

What is the safest starting point for testing?

Save a control, change one meaningful variable, log traffic context and joins, and define your evaluation rule before selecting a winner.