Rational Magic ← Back to strategy
[ Right of reply ]

If you're at Plausible and any claim is wrong, this is where to flag it.

The strategy is built on 46 verbatim reviews (3 of 3 G2 at 4.8★ + 8 of 8 Capterra at 4.6★ + 35 Product Hunt at 4.9★ with 11 verbatim captured), 15 LLM responses across 5 models (Claude Opus 4.7, ChatGPT GPT-5.4-pro, Gemini 3.1-pro-preview, Perplexity Sonar Pro, Grok 4.20. Each running Q1, Q2, Q3 via OpenRouter API), 296 Reddit posts deduplicated across r/SaaS, r/selfhosted, r/webdev, and r/analytics, plus verbatim captures of plausible.io (homepage + pricing + about). Original capture date: 1 May 2026. Refresh capture date: 22 May 2026. The full research record is browsable on the research page.

If something is materially wrong, a quote misattributed, a number that doesn't trace, a positioning read Plausible disagrees with, reply by email and it gets corrected.

Reply by email.

Direct, named, no form. Dropped into the audit's source record within one business day.

What to include in your reply

  • The verbatim claim. Copied from the strategy page, the research page, or one of the deliverables.
  • What is wrong about it. A material fact, an outdated number, a misattributed quote, a positioning read Plausible disputes. Specifics over feelings.
  • What it should say instead. With a source we can cite. (Press release URL, plausible.io product page, blog post, founder talk.)
  • Your role at Plausible, for the correction log. ("Co-founder," "Marketing lead," "Engineer", first name is fine.)

What happens next

  1. Within 24 hours. I acknowledge receipt and confirm I'll act on the flag (or ask follow-up questions if the claim isn't yet specific enough to act on).
  2. Within 48 hours of acknowledgement. The strategy and research pages are updated, and a dated correction note is appended to this page.
  3. If the correction is material. The v1 strategy is rolled forward to v1.1 (or higher) with a public changelog. The source record is updated. Anyone who downloaded the earlier PDF gets the updated link via the same email address.
  4. If the correction reveals a gap in the audit methodology itself. The methodology is amended and the change is logged publicly on the research page.

What's welcome

A different read on the strategic positioning. The Hidden Enemy diagnostic and white-space candidate are interpretive, and a counter-read from Plausible lands here on the record verbatim.

Evidence we missed. Updated subscriber counts, ARR, employee headcount, AI-traffic attribution data, customer-success metrics. Send the source and it goes into the next mining cycle.

A pointer to a fresher version of the homepage / pricing / about page if those have changed since 22 May 2026.

The unresolved MRR discrepancy flag: the Reddit capture surfaced a third-party scrape citing $258K MRR (u/MainStreetBetz, r/SaaS, 28 March 2026) that does not reconcile with the homepage-derived 18,000+ subscribers figure. We did not use the Reddit citation in any audit claim, but a clarification from Plausible on the current MRR would close the loop.

Replies log. No replies received as of publication. Corrections will be logged here with date, responder role, claim flagged, and correction made.