Verified vs Stated Numbers: How to Show Data That Persuades

The Trust Gap Between Tool-Read and Typed Numbers

Investors see many decks. Most numbers are typed by the founder. When a number comes directly from a billing system, analytics dashboard, or bank statement, it carries a built-in audit trail. That trail reduces the mental work needed to trust the claim. A verified figure feels like a signal that the data source has already done the checking.

A typed figure can be accurate, but the reader must assume the founder entered it correctly. That assumption adds a layer of risk. If the same number appears in a tool screenshot, the risk drops because the tool itself validates the calculation. Investors often ask for the source link or a screenshot to move a typed number into the verified category.

• Ask for a screenshot from the source tool
• Include a note that the number is verified
• Keep the same set of metrics across updates

How to Mark Numbers as Verified or Stated

The simplest method is to add a tag next to each metric. For example, write (verified) after a revenue figure that comes from the payment processor, and (stated) after a projection that the founder calculated. The tag tells the reader exactly how the number was obtained without extra explanation. It also creates a habit of separating hard data from estimates.

When the source is a live dashboard, include a tiny image or a link that opens the view in read-only mode. If the source cannot be shared publicly, note the tool name and the date of extraction. This level of detail lets an investor reproduce the number later if needed, and it signals that the founder is not hiding anything.

• Add (verified) or (stated) after each metric
• Provide a screenshot or read-only link
• Note tool name and extraction date

When to Use Verified Numbers in an Update

Core financials are the best place to start. MRR, churn, burn, and runway all have clear sources in accounting or subscription software. Showing a verified MRR number each month lets the investor see growth or decline without guessing. If a metric is still being built, mark it as stated and explain the plan to verify it next cycle.

Non-financial signals can also be verified. Deploy counts from a version control system, user sign-ups from an auth provider, or email open rates from a campaign tool each have a log file. When you share those numbers, attach the log reference or a screenshot. This practice builds a habit of evidence and reduces the chance that a single typo will damage credibility.

Common Mistakes When Labeling Numbers

Mixing verified and stated metrics in the same table creates confusion. Readers may assume all rows share the same level of trust. Keep verified rows together and use a separate section for estimates. This visual separation makes the credibility gap obvious and avoids accidental misinterpretation.

Another pitfall is to label a number as verified without actually providing the source. The tag then becomes empty rhetoric. If a source cannot be shown, either keep the number as stated or wait until verification is possible. Honesty about the status of data builds long-term trust faster than a polished but shaky claim.

Putting It All Together This Week

Pick three core metrics for the next update. Pull each from its native dashboard and take a screenshot. Add (verified) after each number in the draft. Then choose one metric that is still an estimate, label it (stated), and write a short note on when a tool will provide the real figure. This small routine turns vague claims into traceable facts.

Send the update to investors and ask for any missing source links. Note any feedback about clarity. In the following week, replace any (stated) items that have become (verified) after you collect the data. Over time the pattern of adding sources will become a habit that saves time and builds credibility with each new round of communication.

Questions people ask

How can I show a verified number without revealing sensitive data?

Use a blurred screenshot that hides customer details, or share a read-only link that requires login. Mention the tool name and the date of extraction, and note that the figure is taken directly from the system. This proves the source while keeping private information safe.

What if a metric I want to share has no built-in dashboard?

Export the raw data to a CSV file, then open it in a spreadsheet and take a screenshot of the summed total. Label the image with (verified) and note the export date. Even a simple file export creates a traceable source that investors can audit if needed.

Should I label every single number in an investor update?

Focus on the numbers that drive decisions: revenue, burn, runway, churn, and any key usage metric. For those, add the (verified) or (stated) tag. Less critical figures can stay untagged, but keep the tagging consistent for the core set so readers know what to trust.