Why RaveHQ's Before/After Numbers Are Labeled "Illustrative" — And What That Actually Means

If you have spent any time on RaveHQ's vertical pages, you will have noticed a small piece of text sitting next to every before/after scenario: "Illustrative — modeled, not a real client." It appears on all twelve vertical pages, attached to every projected outcome. It is not a footnote buried in fine print. It sits directly beside the number it qualifies.

That label exists because it is true. RaveHQ has no paying customers as of this writing. The About page therefore commits to labeling launch-stage projections and illustrative examples rather than presenting them as delivered customer results. This article answers the question that disclosure raises for a careful reader: if the numbers are not from real clients, what are they, why publish them, and how should they be read?

I. What "illustrative" means, precisely

An illustrative or modeled number is a projection built from stated assumptions and realistic inputs, used to explain a mechanism — not a report of something that already happened to a specific business. When RaveHQ shows a before/after scenario, the page must identify it as illustrative and expose the starting assumptions a reader needs to interpret it. The scenario is checked against the public RaveScore framework, but it does not publish or claim to replay RaveHQ’s proprietary normalization, calibration, or operating logic. What is not real is a specific business that achieved that result.

This is a meaningfully different category of claim from a case study, and the difference matters enough to spell out plainly:

A case study says: "This specific, named or anonymised business had these specific numbers at this specific time, we did this specific work, and here is what happened afterward — verifiable, in principle, by asking the business directly."

An illustrative model says: "If a business with these starting characteristics went through this process, based on how the scoring mechanism works, here is what the trajectory would look like."

Both can be honest. Both can also be dishonest, depending on how they are presented. A case study is dishonest if the business is invented, or if the "before" numbers are cherry-picked, or if a normal fluctuation is presented as a caused outcome. A model is dishonest if it is presented as though it were a case study — if the "modeled" label is removed, buried, or contradicted by the surrounding copy's tone. The dishonesty is not inherent to either format. It is a function of whether the label matches the reality, and whether that label is visible where it needs to be.

II. Why publish a modeled number at all, rather than nothing

The more defensible alternative might seem to be silence: if you don't have real client data, don't show any numbers, and just describe the product in words. There is a real case for that approach. But it has a real cost too, and it's worth being explicit about the trade-off rather than pretending the safer-sounding option is free.

A methodology described only in vague prose is hard to evaluate. Saying "RaveHQ scores your Google reviews and drafts AI-written responses ready for you to approve" tells a reader what the product does, but not how a modeled scenario was framed. A defensible illustration ties its assumptions to the published evidence framework, headline weights, and visible labels. That makes the example inspectable without turning RaveHQ’s normalization, calibration, or orchestration into a public build recipe.

The test for whether a modeled number earns its place on the page is whether it is doing real explanatory work, or whether it is doing the emotional work a testimonial normally does — borrowed credibility standing in for evidence. If the number's job is "here is the mechanism," and the label makes that job clear, publishing it is legitimate. If the number's job is "trust us because someone else already did," and there is no someone else, publishing it is not legitimate — no matter what label sits next to it. RaveHQ's own product thesis is that specific, structured, verifiable claims perform better than vague marketing language, both for customers and for AI systems evaluating trustworthiness. Applying a lower standard to its own before/after content than it recommends applying to a customer's website copy would be an obvious inconsistency. The label is the mechanism that keeps that inconsistency from happening.

III. What real proof will look like as it exists

The honest answer to "when will there be real numbers" is: as soon as there are real customers to measure, and not before. That is not a marketing deferral — it is the actual constraint. A before/after number requires two things that cannot be manufactured: a real starting state, and enough elapsed time under the product for a real ending state to exist. Here is what will change, specifically, as that happens.

Named case studies, with permission

As businesses onboard and see measurable movement in their RaveScore, review rating, or local rank, the plan is to publish named or attributed case studies — not composite or anonymised "a dental practice in the Midwest" stories, but specific businesses willing to be named, with specific before and after numbers a reader could ask the business owner to confirm directly. A case study that cannot be traced back to a real, nameable business it happened to is not meaningfully different from a modeled scenario — except that it is dishonestly presented as though it were.

Published, not cherry-picked, outcomes

The credibility risk in any case-study program is selection bias: publishing only the customers who had an unusually good outcome and staying quiet about the median or the disappointing cases. The commitment worth making — and the one that will actually distinguish real proof from marketing proof — is publishing outcome data at the cohort level, not just the anecdote level: what a representative sample of customers' RaveScore and review metrics looked like at signup versus at ninety days, including the range and the median, not just the best story. A single glowing case study proves a best case exists. A cohort distribution proves what a typical customer should expect.

Willingness to show the raw number, not just the headline

The difference between "clients see an average 40% increase in reviews" and a screenshot of an actual client's actual Google Business Profile review count over time, dated, is the difference between a marketing claim and a verifiable one. Real proof means defaulting to the second format wherever a customer's privacy allows it — the same instinct that produced the published, auditable RaveScore methodology in the first place.

IV. Why admitting "we don't have proof yet" is itself a trust signal

This is the part of the argument that requires the most care, because it is easy to state it in a way that sounds like spin — "look how honest we are, therefore trust us" is its own kind of manipulation if it isn't backed by something real. So it's worth being precise about the actual mechanism, not just asserting the conclusion.

The reputation management and local-marketing SaaS category has a structural incentive problem: vendors sell trust as a product, and the fastest way to sell trust is to manufacture the appearance of it — invented testimonials, composite "customer" stories presented as real, before/after numbers with no verifiable source, stock photos captioned as real business owners. None of this is hypothetical; it is a well-documented pattern across the category, and it exists because it works in the short term. A prospective customer skimming a landing page rarely has the time or the means to verify a testimonial's authenticity in the moment they're evaluating the product.

Against that backdrop, a vendor that says plainly "we have no paying customers yet, and every number on this page reflects that" is making a claim that is trivially falsifiable if untrue — a competitor, a journalist, or a skeptical prospect could disprove it easily by finding a hidden customer base, and the cost of being caught in that lie would be severe. The statement is costly to make falsely and cheap to make truthfully. The same principle applies to methodology: publish the signals, evidence rules, labels, and safeguards that let a buyer challenge an output, while keeping proprietary implementation intelligence protected.

None of this means the label alone should be enough to earn trust indefinitely. A company that says "no customers yet" in year one and is still saying it in year three, with no cohort data ever published, has converted an honest disclosure into a permanent excuse. The trust the label earns is provisional — it buys credibility for the current state of the company, not a blank check against ever having to show real proof. The test of whether the honesty was genuine or merely a temporary marketing posture is whether real proof actually gets published once it exists, in the same prominent, unhedged way the "illustrative" label is shown today.

V. The question worth asking any vendor showing you a case study

The practical value of this article is not really about RaveHQ specifically — it is about a habit worth building as a buyer evaluating any vendor in any category. The next time you see a before/after number, a client logo wall, or a glowing testimonial on a company's website, ask the specific question this article has tried to answer honestly for RaveHQ's own numbers: is this a report of something that happened to a real, nameable business, or is it a model — and if it's a model, does the page say so anywhere you can actually see it?

A few concrete tells to check, in roughly descending order of reliability:

Can you find the business independently? A named case study should let you search for the business, find its actual Google reviews or actual website, and cross-check the claimed numbers against something the vendor doesn't control. A testimonial attributed only to "Sarah, small business owner" or "a dental practice in the Midwest" cannot be checked at all — which does not prove it is fabricated, but does mean you have no way to know either way.

Does the number have a date and a timeframe? "Clients see 40% more reviews" with no denominator, no timeframe, and no cohort size is a claim shaped like a statistic without the substance of one. "This client's review count went from 22 to 61 between March and September 2026" is a claim you could, in principle, verify.

Is there an inspectable methodology behind the number? Look for the headline inputs and weights, evidence sources, coverage or confidence labels, and safeguards against fabricated data. A credible vendor should disclose enough to explain and challenge the result. It does not need to publish the normalization curves, prompts, calibration data, QA, or orchestration that make the product proprietary.

Does the surrounding language match the label? A number correctly labeled "illustrative" in an 8-point footnote, sitting beneath headline copy that says "see how we transformed this business," is using the label as legal cover while the actual reader-facing message contradicts it. The test is not whether the disclosure exists somewhere on the page. It is whether an ordinary reader, reading normally, would come away with an accurate understanding of what they just saw.

None of these checks require special expertise. They require treating a vendor's proof claims with the same scrutiny you would apply to a stranger's claim in any other context — and understanding that the absence of proof, honestly disclosed, is a meaningfully different situation from the presence of fabricated proof, dishonestly disclosed. The first is a company being straight with you about where it is. The second is a company lying to you about where it is. Both categories exist in this market. Learning to tell them apart is the actual skill worth building.