SaaS Social Proof: Logos, Numbers and the Claims Audit

Use only proof you can produce paperwork for: logos of customers who are customers and have agreed, counts that are true today (with a date beside them), and outcome claims sourced to a named customer or labelled as illustrative. Segment the proof - a trades business is persuaded by trades logos, not by a famous startup - and keep a claims register: each public claim, its source, its date checked, its owner. The register is the difference between a proof system and a pile of assertions, and it takes an afternoon to build at small scale.

A logo asserts a commercial relationship. Using one without the relationship - the free-trial account of a famous company, the ex-customer of three years ago - is a factual claim that is false, and it is the kind of falsehood that travels. Keep the wall small, current and permitted; write to customers for permission where your terms do not already cover it, and treat a refusal as information about the relationship, not as an obstacle. Relevance beats fame for conversion: three logos from the visitor's own industry outweigh a dozen celebrities, because the evaluator's question is 'works for people like us', not 'is it known'.

User counts, transaction volumes and savings percentages decay: the count from two years ago is a historical claim wearing present tense. Date every number ('12,000 invoices sent in September 2026') or automate it from the source system. Percentages of improvement ('saves 30 percent of admin time') are the most abused claims in SaaS; they need a source - a customer study, a measured before-and-after you can describe - or they need to become a labelled illustration of the mechanism ('an hour a week at your billing rate is...') rather than a finding. The FTC's endorsement and advertising guidance sets the legal floor in the US; the claims register is how a small company stays above it without a legal department.

The convincing testimonial is specific: a named person, their role and company size, the job the product does, and a result stated in their terms. Vague praise ('Amazing tool, changed our business!') from an initialled stranger reads as set dressing because it is interchangeable across the whole category. Collect testimonials at the moment of a real win - after a successful migration, a support rescue, a renewal - with a request specific enough to prompt specifics: 'What did the first month replace?' Edit for length only, never for substance, and keep the original wording on file with the permission.

Build the register as a simple table: claim as published, where it appears, source document or person, date last verified, next check date. Sweep it quarterly alongside the pricing checks, because claims and prices decay together. The register also disciplines new claims at birth: a marketer who must fill the source column writes fewer inventions. At small scale this is an hour a quarter - cheap insurance for the asset your whole conversion system borrows against, which is being believed.

Young products have young proof. The honest substitutes: the number of trials running, the founder's relevant history stated factually, the product's operation made transparent (public status, real documentation, a working demo with sample data), and early customers quoted with their scale stated ('a four-person studio') rather than inflated by omission. Thin proof presented precisely converts evaluators who have been burned by inflated proof everywhere else - which, in SaaS, is most of them.

Where a testimonial is a sentence, a case study is the receipt: the customer's situation before, what they implemented, what changed, with the numbers they agreed to publish and the timescale they happened over. Evaluators read case studies in their own segment almost whole; everyone else skims. Produce few and real - two honest case studies with named mid-sized customers outweigh a library of anonymous success theatre - and write them with the customer as a collaborator who approves the final text. A case study the customer is proud to share becomes their referral document inside their industry, which is the highest-leverage distribution a small SaaS can earn.