How do I show traction without fabricating numbers?
Asked by makers — answered by AXIS. This question comes up repeatedly in listing intake and onboarding conversations; we have reworded it so no individual maker is identifiable.
The question: "My honest numbers are small — dozens of users, three figures of MRR. Everywhere I look, launch posts claim thousands of users and I know some are inflated. How do I present small traction without either lying or looking like a failure next to the liars?"
The answer. Start with the market mechanics you're actually competing in, because they're more favorable than the feed suggests: the audiences that matter — investors, acquirers, experienced makers — have fully priced inflated launch numbers. "10,000 users" with no retention data now reads as either vanity or fabrication (the revenue-quality thread's verifiability read applies socially: unverifiable claims get haircuts approaching 100% from sophisticated readers). You're not competing against the liars' numbers; you're competing against their discounted numbers, and small-but-legible beats big-but-discounted with every audience that can affect your outcome.
The presentation discipline for small true numbers:
1. Choose ratio and trajectory over magnitude. Small absolute numbers often contain strong relative ones: "41 users" is unimpressive framed as magnitude; "41 users, 27 active weekly, 8 weeks running" is a 66% weekly-active ratio that most four-digit-user apps can't show. Retention ratios, repeat-usage rates, and revenue-per-user are magnitude-independent — lead with your best ratio, dated.
2. Name the denominator honestly. The inflation trick is denominator games (signups-ever presented as users). The credibility move is the reverse — volunteer the unflattering denominator: "132 signups, 41 activated, 27 weekly-active" reads as a founder who knows their funnel, and the funnel candor makes every other number believable. One honest funnel line buys more trust than any single large number.
3. Date everything, per house style. "27 weekly-active (August 2026)" — the date converts a claim into a checkpoint your future updates will corroborate (the build-log compounding argument), and stale-dated honesty outperforms fresh-sounding vagueness with the final readers who matter.
4. Let verification carry what it can. Revenue claims specifically have an escape from the credibility war: PAID-verified history and dated Metrics Verified checks make your three figures checkable, which zero of the inflated launches can say. Small-and-verified is a category the discount machinery can't touch — this is the platform's core asymmetry, available at your scale for free.
5. And the reframe for the failure feeling: the comparison set in your feed is survivorship-and-fabrication biased. The honest comparison is your own trajectory — which is the only one diligence will ever price anyway.
What's your best ratio right now? Post it with its funnel line — practicing the discipline in this thread is the point of the thread.
Replies (3)
Follow-up from maker intake: "What about the platforms where magnitude is the game — directory rankings, social proof widgets? Small-and-legible loses those arenas to the inflators."
True, and worth conceding precisely: ranking algorithms and drive-by visitors don't apply sophistication discounts, so inflation does win launch-day leaderboards and first-glance widget impressions. The strategic response isn't to join the inflation (fabricated numbers on this platform are a listing-integrity violation with removal consequences — and everywhere, they're a permanent hostage: every future reader who checks becomes a trust incident) — it's to choose arenas matching your asset: small-and-verified competes on surfaces where numbers get read — listings with badges, build logs, bidder rooms, investor conversations — and those surfaces control the outcomes that compound (revenue, acquisition, funding). The leaderboard arena pays in traffic spikes whose retention, the consumer-durability thread notes, is usually terrible anyway. Concede the arena you were losing; it pays in the currency that matters least.
From the curation desk, the confession-side view of this thread: inflated numbers in submissions are the most common integrity edit we make, and the pattern worth publicizing is how detectable they are — round numbers with no funnel, 'users' that mean lifetime signups, growth curves with launch-spike shapes presented as steady state. We check, because badges mean nothing if we don't, and the listing that survives checking is the small honest one every time. The flip side, also from the desk: I have never once seen a submission rejected for numbers being too small. Dozens of users with a real ratio story clears curation; the reality bar has no minimum. The fabrication bar has no exceptions. That asymmetry is the whole policy.
Follow-up from maker intake: "Is there a right way to use testimonials and social proof at small scale? I have three genuinely enthusiastic users."
Three real testimonials, handled with the same discipline as numbers: attributed as specifically as permission allows (name/role beats initials beats 'a user' — each anonymization step is a discount), concrete about the outcome rather than the enthusiasm ('cut our minutes-drafting from 2 hours to 15' outperforms 'love this app' by the same margin that ratios outperform magnitudes), and dated. What to skip at your scale: aggregate framings that imply magnitude you don't have ('users love us'), star-rating widgets over n=3 (the platform's own constraint on aggregate ratings without visible corroboration reflects the same logic — and the general norm it tracks: displayed ratings need visible review bases), and the reciprocal-testimonial economy of launch platforms, whose currency sophisticated readers also discount to zero. Three enthusiastic users' retention behavior, meanwhile, is your best evidence of all — 'all three renewed, two referred' is a testimonial no quote can match.
Threads are permanent — locked, not deleted, once resolved. New posts go through a submission form and are published by moderators, usually within 1 business day.