On this page
This archived customer case study described Dom Wells of Onfolio testing approximately 500 AI-assisted articles across nine websites. It records a historical Content at Scale publishing experiment, not a controlled evaluation of today’s RankWell product or a promise of comparable results.
The original headline claimed a 150% cost reduction. That percentage is not a valid ordinary reduction from a positive starting cost: reducing a cost by 100% already brings it to zero. The archive does not provide comparable before-and-after expense totals that establish a corrected savings percentage, so that claim has been removed.
What the historical experiment described
The original account focused on informational articles and compared publishing approaches across several sites. Some articles were released together; others were spread over time. It described limited editing and adding an image before publication. Those were features of the reported experiment, not the editorial standard recommended here.
The account reported mixed observations: some pages appeared to gain rankings while other sites disappointed. It also described differences in existing site activity, keyword competition, and site condition. Those differences prevent treating every result as a clean measurement of the writing tool alone.
The approximate article and site counts are retained as customer-reported historical scope. They have not been independently audited against a complete publishing log. The original screenshots do not establish a complete, current performance record, and outdated image assets have been replaced with a clearly identified current product view.
What the account cannot establish
- A universal cost reduction. A fair comparison needs the same included expenses, workload, period, and approval standard.
- Equivalent performance for every site. Different topics, established audiences, technical conditions, and other SEO changes can affect outcomes.
- Guaranteed rankings from volume. Publishing more pages does not establish that they answer the right questions or attract useful visitors.
- No need for human review. A minimally edited historical test is not evidence that facts, product claims, or instructions should be published unchecked.
- Current entitlements or prices. The historical product and its offer should not be confused with today’s BrandWell plans.
A better way to evaluate your content workflow
Start with a limited group of articles serving known reader needs. Decide which pages you will update and which genuinely require a new URL. Define acceptance criteria before preparing the drafts, and record the work needed to meet them.
- Set the brief. Identify the audience, question, useful answer, current product context, and appropriate next action.
- Prepare evidence. Use original examples and verifiable sources. Clearly label hypothetical calculations.
- Review the draft. Check claims, links, images, headings, and the instructions a reader would follow.
- Record total effort. Include research, writing, editing, software allocation, publishing, and revisions.
- Compare results carefully. Monitor relevant search visibility and qualified actions separately from publication counts.
Use a change log and comparable time periods. A group of pages published together may have different discovery timing from a staggered group. A short ranking snapshot should not be presented as a sustained traffic or revenue result.
Use the current RankWell workflow
RankWell supports the content workflow within today’s BrandWell portal. The Content Hub organizes articles, strategy, queue, and calendar work. The editor brings together the draft, search preview, SEO recommendations, NLP, media, sources, and history.

Review recommendations against the actual reader task and supporting evidence. Approve the finished article, then inspect the live page at your configured publishing destination. A generated draft or optimization score is an input to review, not a guarantee of rankings or conversions.
Calculate savings from comparable costs
Hypothetical example: If a team’s comparable monthly content costs fall from $10,000 to $4,000, the reduction is $6,000. Dividing $6,000 by the original $10,000 gives a 60% reduction. The original cost is 2.5 times the new cost; that does not make the savings 150%.
Then check output and review requirements. A cheaper month with fewer approved articles may not represent a more efficient process. Include quality control and maintenance in the comparison rather than assuming the subscription is the entire cost.
The archive’s useful contribution is a reason to test a workflow carefully, with mixed outcomes and limitations visible. Explore the current RankWell workflow and build a small, accountable review process for your own content.
Reviewed and updated October 3, 2026.



Julia McCoy