How to Verify a Customer Story Before You Publish It

Why Verification Is Its Own Step, Not an Afterthought

A customer says, on camera, that working with you doubled their results. It is a great line. It is also, at that moment, unverified. Maybe it is exactly right. Maybe the customer rounded up from a smaller number because it sounded better, or misremembered the timeline, or is comparing two periods that are not actually comparable. None of that requires bad intent. It just requires a human being talking casually about their own business, which is exactly what makes an interview feel real and exactly why it needs a check before it goes public.

In the Share One Method, verify sits right after the interview and before editing, on purpose. A story only becomes an asset the business can stand behind once it has been checked, not the moment it is recorded.

What Verification Actually Protects

Verification is not about doubting your customers. It is about protecting three things at once: the customer's own credibility, the business's credibility, and the accuracy of the story itself. A published claim that turns out to be wrong does not just embarrass the business that published it, it puts the customer in an awkward position too, since their name and face are attached to it. Getting it right before publishing is a form of respect for everyone involved.

Five Things to Check Before Anything Goes Live

1. Identity and role

Confirm the customer's name, title, and company are accurate and current, and that they are comfortable with exactly how those details will be presented. Titles change, companies get acquired, and a small error here undermines trust in everything else in the story.

2. Specific numbers and claims

If a customer cites a percentage, a dollar figure, or a timeframe, check it against something concrete where possible: an internal report, a dashboard, a follow-up confirmation from the customer in writing. If the number cannot be confirmed, it either gets softened to language the customer is genuinely sure about, or it gets left out. This is also why Share One only ever cites its own first-party customer numbers, like Doug Tanner's 45 percent response rate at Salezilla or Greg Platz's 30 percent reduction in ad costs, because those are figures the customers themselves confirmed and stand behind.

3. Context and timeline

A true statement taken out of context can become misleading. If a customer says results improved "within a month," confirm that is actually the timeframe, not an approximation that later gets treated as fact. Editing for length should never quietly change what happened.

4. Consent and how it will be used

Every customer should know, in plain terms, where their story might appear: the website, sales materials, social media, advertising. Getting explicit consent before publishing is not just good practice, it is what allows the business to use the story with confidence anywhere it might help, rather than worrying later whether a customer expected it to stay in one place.

5. Internal consistency

Read or watch the finished story once, straight through, and ask whether every part of it hangs together. If a customer describes a problem and then a result that does not logically follow from the solution being described, that is worth a follow-up question before publishing, not after.

What Verification Is Not

Verification is not a legal deposition. It should not feel like an interrogation to the customer, and it rarely needs to. Most of the work happens after the interview, cross-checking what was said against records the business already has, and following up with a quick, friendly confirmation if something needs clarifying. Done well, the customer barely notices this step is happening. They just notice that the final story feels accurate and that they are comfortable with it going out into the world.

Who Should Own Verification

In most businesses, verification works best when it sits with someone who was not in the room for the interview. A second set of eyes, someone checking the story against records rather than against memory of how the conversation felt, catches things the interviewer is more likely to miss simply because they were caught up in a good story as it was being told. This does not need to be a formal legal review. It can be as simple as a marketing lead cross-checking a claim against a dashboard, or a quick email back to the customer confirming a specific detail before it goes into a final draft.

What matters is that verification is a distinct step with its own owner, not something folded silently into editing, where it is easy to skip under a deadline. The Share One Method treats it as separate for exactly this reason: a step without an owner tends to get skipped the first time a launch date gets tight.

A Quick Example of Verification in Practice

Consider a customer who says in an interview, "we basically doubled our lead volume within a month of using this." Verification does not mean doubting the customer. It means confirming three things before that line gets published: what "doubled" is being measured against, whether "within a month" is accurate or an approximation, and whether the customer is comfortable with the claim being quoted publicly exactly as stated. Often the customer will refine their own language once asked directly, "just to make sure we get this right, can you confirm the timeframe," and the result is a claim that is both more accurate and, because it is more specific, more persuasive.

What Happens When This Step Gets Skipped

Skipping verification is one of the most common and most costly mistakes we see, and we cover it alongside four other common missteps in 5 mistakes businesses make when collecting customer testimonials. The short version: an unverified claim is a liability sitting in plain sight. It might never get questioned. But if a prospect, a competitor, or even the customer's own team later disputes a number attached to their name, the business's credibility takes the hit, not just the claim's.

Verification Makes the Rest of the Method Work

Every step after verify, editing, publishing, measuring, depends on the story being accurate. Edit shapes a true story for clarity. Publish puts a true story in front of the right audience. Measure tracks the real effect of a true story on conversion. None of that works if the underlying story was never checked. This is part of why the method treats verify as a distinct, non-negotiable step rather than folding it into editing, where it is easy to skip under deadline pressure.

You can see the full seven-step process, including where verify fits alongside invite, interview, edit, publish, measure, and repeat, on our frameworks page. And if you want to see verified stories in action, our case studies page is built entirely from testimonials that went through this process.

A Simple Standard to Hold Every Story To

Before anything gets published, ask one question: if a skeptical prospect looked into this claim, would it hold up? If the answer is yes, publish it with confidence. If the answer is uncertain, that uncertainty is exactly what the verification step exists to resolve. Trust compounds, but only when every story it is built on is true.