Back to the blog

Case Studies

Keith Bresee Case Study: Reported Content Costs and Review Lessons

Review Keith Bresee’s historical content expense account, the limits of its traffic claims, and how to evaluate a current RankWell editorial workflow.

Julia McCoy4 min read

Current BrandWell RankWell editor showing article content, search preview, SEO recommendations, and growth-tool navigation
RankWell in the live BrandWell app, captured September 22, 2026. The article and score shown are an example from this workspace.
On this page
  1. What the original interview establishes
  2. Why the old traffic headline needed qualification
  3. The repeatable editorial lesson
  4. Apply the workflow in today’s RankWell
  5. Build your own cost comparison

In an archived customer interview, Keith Bresee described reducing monthly writing expenses from roughly $14,800 to below $5,000 while using Content at Scale, the historical product behind today’s RankWell content workflow. These are customer-reported figures from that period, not a current price, independently audited result, or savings guarantee.

The useful lesson is the operating process: learn what customers need, build a focused topic map, prepare drafts, and have people review the result. The current RankWell product should be evaluated against your own workload, review requirements, and business outcomes.

What the original interview establishes

The original interview’s expense discussion begins around 6:40. Bresee described approximately $14,800 in monthly writing expenses and, around 7:49, said spending was below $5,000 after changing his production process. He also described a team managing the work rather than an entirely unattended publishing process.

Using $5,000 as a comparison point gives a $9,800 monthly difference, or approximately 66.2% of $14,800. Because the later figure was described as below $5,000, this is a conservative illustration based on the reported amounts. It does not establish a current subscription cost or comparable savings for another business.

The interview does not provide an audited invoice set, a complete breakdown of included expenses, or a controlled comparison of identical content workloads. Treat the numbers as an account of this customer’s experience. Research, editing, management, software, and publishing costs should all be included when evaluating your own process.

Why the old traffic headline needed qualification

At approximately 11:38 in the traffic discussion, Bresee described one site moving from about 2,200 monthly visitors to 18,000 and subsequently falling to roughly 4,000 to 6,000. He also discussed other SEO interventions. That account does not support presenting a sustained ninefold increase caused solely by the writing product.

For the two reported endpoints, 18,000 divided by 2,200 is approximately 8.18 times the starting figure. The increase is approximately 718%, not an independently verified product effect. The later decline matters when interpreting the story; a peak is different from a sustained result.

Other traffic and revenue claims in the older article are not repeated here because the available interview does not establish audited analytics, complete attribution, or comparable measurement conditions.

The repeatable editorial lesson

A customer interview is most useful when it helps you test a process rather than copy someone else’s headline. For your own business, work through these steps:

  1. Collect real questions. Ask customers which decisions, obstacles, and comparisons they needed help with. Obtain permission before publishing identifiable responses.
  2. Map the topic. Group related questions into distinct reader tasks. Avoid creating several pages that repeat the same answer.
  3. Prepare evidence. Gather current product information, original examples, and primary sources for claims that need support.
  4. Review the draft. Check accuracy, reader fit, product descriptions, images, and next actions before approving publication.
  5. Measure the finished work. Record total preparation time and expense separately from impressions, clicks, qualified inquiries, and revenue.

A list of topics is not a year’s guaranteed publishing plan. Prioritize what your audience needs and what your company can substantiate. Revisit the plan when the product, evidence, or customer questions change.

Apply the workflow in today’s RankWell

BrandWell’s current Content Hub organizes articles, strategy, queue, and calendar work. Use the RankWell editor to review the article with its search preview, SEO recommendations, NLP, media, sources, and history. Bring your own evidence and editorial judgment to the recommendations.

Current RankWell editor used to review article content and supporting sources
The current RankWell interface is shown for today’s workflow. It is not Keith Bresee’s historical workspace or analytics.

After approval, inspect the page at your configured publishing destination. Keep a review date and record of substantive changes. A recommendation score is a review input, not a ranking or conversion forecast.

Build your own cost comparison

Hypothetical example: A team spends $2,000 on software and $3,000 on research, editing, and publishing in a month, for $5,000 total. If it publishes 20 approved articles, the allocated cost is $250 per article. Compare that with a previous period only after checking that scope, review standard, and included expenses are comparable.

This archive preserves the expense account while separating historical results from current product promises. Explore RankWell and assess the current workflow against your own content preparation and review needs.

Reviewed and updated October 3, 2026.

Written by

Julia McCoy

Julia McCoy has contributed articles to BrandWell on content marketing, writing, and search engine optimization. This archive retains her original bylines; individual articles may be updated by the BrandWell editorial team.

Put your next growth opportunity to work.

Start with the product you need. Connect the work with AIMEE.