On this page
This historical customer interview discusses Marcus Campbell’s use of Content at Scale, the earlier content product associated with BrandWell’s history. The interview is a customer’s account of his operation at that time, not a current pricing offer or an independently audited performance study.
The useful lesson is to examine the whole content workflow, including topic selection, drafting, review and delivery. Current BrandWell readers should use RankWell for the content workflow and evaluate their own evidence rather than expecting the interview’s reported timeline.
What the original interview supports
In the original interview at approximately 4:27, Campbell reports that his site-and-content delivery process changed from about a month and a half to roughly four days. This is a historical self-report about a combined process, not a controlled measurement of writing time alone.
The available interview does not establish that every customer can obtain the same result, that a particular article will rank within days, or that current subscriptions have a fixed cost per article. Do not use the old case-study figures as today’s product specifications.
Separate the workflow from a ranking promise
Site delivery involves more than generating a draft. The team may need to configure a site, choose topics, verify claims, prepare media, approve the article and publish it. A change in delivery time can reflect several changes at once.
When evaluating your process, record which steps are included and who completes them. Separate active working time from elapsed waiting time. Include revision and approval work rather than counting only the first draft.
- Planning: choose the reader’s task and the evidence required.
- Production: prepare the brief and initial article.
- Review: verify sources, examples, attribution and product details.
- Delivery: check the published result and complete the handoff.
This is a practical evaluation framework, not a claim that the historical interview documented every step in the same way.
Expired-domain tactics need current policy context
The earlier article promoted purchasing domains to exploit existing rankings. That should not be presented as a current shortcut to guaranteed results. Google’s expired-domain-abuse policy addresses repurposing expired domains primarily to manipulate rankings with little user value.
Assess the actual audience and purpose of a site. A domain’s history does not establish that a new article serves readers or that inherited visibility will persist. Do not publish irrelevant material solely because a domain once ranked.
An original content-cost example
Suppose a hypothetical team spends $600 on a project that delivers six approved articles. The project cost averages $100 per approved article. If only four pass review, the cost per approved article is $150. Those figures are an illustration, not BrandWell pricing or a reported Campbell result.
Include the costs relevant to your own operation: research, production tools, editorial labor, media and revisions. Compare like-for-like deliverables. A price for an initial draft and a price for a reviewed published article describe different scopes.
Keep review in the production process
Do not turn a customer’s historical account of minimal editing into a recommendation to publish unread drafts. Check factual claims, links, product details and examples. A fluent sentence can still contain an unsupported promise.
For a hypothetical vehicle article, an editor should identify the model year, distinguish measured test data from opinion and verify safety or reliability claims against appropriate evidence. A keyword alone cannot supply that review.
- Read the complete draft against the brief.
- Verify the material claims with direct supporting sources.
- Remove invented experience and unsupported guarantees.
- Check media, attribution and mobile readability.
- Approve the final article and inspect the published result.
Apply the useful workflow in current BrandWell
Use Visibility to investigate keyword opportunities, then use RankWell to develop a brief, draft and reviewed article. Check the content, sources, media and search preview before using your configured publishing workflow.

Keep the prior version and a change log. Measure approved production, qualified outcomes and the search evidence actually available. A case study can suggest questions to investigate, but it does not remove the need to evaluate your own operation.
Common questions
Is the reported four-day timeline guaranteed?
No. It is a historical customer self-report about his combined delivery process.
Does the interview establish current pricing?
No. Use the current BrandWell pricing page for current products and plan details.
What should a team take from the case study?
Review the complete production process, define comparable deliverables and keep accountable editorial review in the workflow.
Reviewed and updated October 3, 2026.


Julia McCoy