12 September 2026, 4 min read

Posts with a number you own: why receipts beat opinions

An opinion anyone could post is easy to scroll past. A result only you could report is the post people save.

Scroll any feed for a minute and count the opinions. Remote work, hiring, AI, pricing, leadership. Most of them could have been written by anyone, and that is the problem. When a post could come from a thousand people, readers have no reason to remember who wrote it.

A receipt is different. It is a post built around a number or result that belongs to the author: something they measured, shipped, sold or lost. Nobody else can write it, so it carries its own credibility.

What counts as a receipt

  • A before and after from your own work. Churn in March against churn in June, and what changed in between.
  • A count. How many sales calls it took to close the first ten customers.
  • A cost. What a failed campaign spent before it was stopped, and what it taught.
  • A time. How long an onboarding took before and after a redesign.
  • A small, specific win. The first invoice paid by a customer who found the company through a post.

The number does not have to be large or impressive. Small numbers from real work are often more interesting, because readers can picture being in the same place.

Why receipts work

A number the author owns does three jobs at once. It proves the author was there. It gives the reader something concrete to compare with their own situation. And it makes the post hard to argue with, because the debate moves from 'is this true' to 'why did this happen', which is a more useful conversation.

Receipts also age well. An opinion about the market is stale in a month. A post that says a two-person studio went from three retainers to seven in a year, and lists the four changes that did it, is still useful to someone next spring.

Turning an opinion into a receipt

Most opinion posts have a receipt hidden inside them. The opinion came from somewhere. Find the experience behind it and lead with that.

  1. Write down the opinion in one sentence. For example: annual plans are underrated for small software companies.
  2. Ask where you learned it. Maybe a client added an annual option last year.
  3. Find the number. What share of new customers picked annual in the first quarter, and what happened to cash in the bank.
  4. Lead with the number and the situation, then let the opinion come at the end as the conclusion.
  5. Cut any sentence that argues the point without evidence. The receipt argues for you.

Never invent the number

The whole value of a receipt is that it is true. A rounded, guessed or borrowed figure turns a receipt into a claim, and readers who work in the same field can often tell. Once one number in your feed is shown to be made up, every other number loses its weight.

  • If you do not have the number, leave a gap in the draft and go and get it.
  • If you can only share a range, say so. 'Between 40 and 50 customers' is honest and still specific.
  • If a client's figure is confidential, share the direction and the method instead of the value.
  • If the number comes from someone else, name the source and link it.

Where to find your numbers

Most founders and consultants sit on more receipts than they realise. They are in the tools they already use every day.

  • Billing: new customers, churned customers, revenue this month against the same month last year.
  • Product analytics: which feature got used most after launch, how many people finished onboarding.
  • Website analytics: which page brought the most visitors, where they came from.
  • Code history: how many releases shipped this quarter, how long the average fix took.
  • Your calendar and inbox: how many calls, how many proposals, how many said yes.

Balance receipts with the rest

A feed made only of numbers can read like a report. Mix receipts with frameworks, findings and the occasional plain explanation of how something works. A good rhythm for many people is one receipt a week, with the other posts drawing on the same experience from different angles.

How GoodSocials handles this

GoodSocials can read your own figures, read-only, from Stripe, GitHub, PostHog, Plausible and Notion. When a post needs a number only you know, the card asks for it instead of making one up, and the quality gate holds any draft that contains an invented number.

Read next

Let the board keep the cadence for you.

Sign in with LinkedIn, paste your website, see seven posts on a board. 14 days free, cancel any time.