Specificity Builds Trust
Why does a smaller, exact claim persuade more than a bigger, vague one?
The idea
Concrete claims are easier to evaluate than broad promises.
In the real world
Reduce weekly reporting from four hours to forty minutes.
Going deeper
A vague claim is safe for the seller and therefore worthless to the buyer, and buyers know this. Dramatically improve efficiency cannot be wrong, so it carries no information and is priced accordingly — at nothing.
A number transfers risk. Four hours to forty minutes can be tested, disputed and held against you, and a buyer reads your willingness to be measured as evidence you expect to survive the measurement. This is why the smaller, checkable claim outperforms the larger vague one: persuasion here is not about the size of the promise but about what the promise costs you to make.
Where it stops applying
A specific number you cannot support is worse than vagueness, because it is falsifiable and will be falsified. Only claim what you would be comfortable being audited on.
Why it matters
A precise claim can be checked, and being checkable is what makes it worth believing.
Try this today
Add a number, boundary, or example to a vague claim.
Test yourself
One vendor promises to dramatically improve reporting efficiency. Another promises to cut weekly reporting from four hours to forty minutes. Which is riskier to publish, and why does that make it more persuasive?
Show the answer
The second, because it can be tested and shown to be wrong. Stating a number transfers risk to the seller, and a buyer reads that willingness as evidence the claim is grounded.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.