Citation provenance pass and scale notes added across seven company pages
Second audit pass following the May 1 corrections. Statistics now cite the original research instead of write-ups of it. Contested claims on Automattic, Buffer, and Basecamp got live citations or hedged phrasing. The 20–30 person fracture-point framework was reframed from empirical fact to working hypothesis. Every What Founders Can Copy item on the original seven company pages now carries an explicit scale-applicability note.
The May 1 audit closed the most visible factual gaps. This pass closes a different gap — citation provenance. The site’s methodology page commits to citing primary sources, not write-ups of primary sources. Several claims on the Doist and async-communication pages were citing a Business of Software interview as the source for productivity statistics that originated in academic and vendor research; they now cite the original studies. Several Automattic and Buffer claims had text-attribution but no live link; they now have inline citations or were softened where the underlying source could not be defended.
Corrections, by page
Doist
- 23-minute interruption recovery, 60% coordination time, 252% meeting growth — three productivity statistics in the Core Philosophy section previously cited a Business of Software interview where Amir Salihefendić paraphrased them. Now cite the underlying primary sources directly: Gloria Mark’s research at UC Irvine for the 23-minute figure, Asana’s Anatomy of Work Index for the 60% figure, and Microsoft’s 2022 Work Trend Index for the 252% figure. The Business of Software interview is retained as the venue where Doist articulates the cluster.
Async Communication (practice)
- 23-minute interruption recovery — same correction as Doist. The figure is now cited directly to Gloria Mark’s UCI research instead of the Business of Software write-up.
Automattic
- “Powers ~42% of the web” — corrected. The 42% W3Techs figure measures WordPress, the open-source CMS Automattic stewards, not Automattic the company. The summary, headline statistic, and Snapshot opener now distinguish the two. Live W3Techs link added inline.
- 60–80 deploys per day on WordPress.com — hedged. The figure traces to early-to-mid-2010s Automattic engineering writeups and does not appear on the current
automattic.com/how-we-workpage. The body now frames it as historical and notes the absence of a current published number.
Buffer
- ~198,500 MAU and ~70,000 paying customers — softened from “per Buffer’s December 2025 shareholder update” to “in late-2025 reporting periods” and given a live citation to
buffer.com/shareholders. - 75 employees, $23.3M ARR, $2.51M net profit — given live citations to the 7th profit share post.
- 2012 fully-remote decision and 2015 office closure — given a live citation to the working-at-buffer post.
- Country list (USA, Australia, Canada, UK, France, Spain, Poland, Taiwan, Nigeria, South Africa) — softened. The country-by-country list overstated what Buffer publishes; rewritten as a hedged regional summary citing the salary-system page where the per-teammate country data lives.
Basecamp
- 2021 political-discussion policy change — replaced the hand-wavy “[This was discussed publicly in numerous posts by DHH and Jason Fried at the time.]” attribution with a primary citation to Jason Fried’s April 26, 2021 HEY World post “Changes at Basecamp” and a strong-secondary to The Verge’s April 30, 2021 reporting on the resulting ~33% departures.
20–30 Person Fracture Point (framework)
- Thesis reframed as cross-company hypothesis. Previously the thesis read as empirical fact (“Most distributed companies fail at 20–30 people…”). The page now states the framework as a working hypothesis grounded in the named cases on this site, with an explicit caveat about selection bias (companies that quietly fail at this scale do not write handbooks about it).
Original 7 company pages — What Founders Can Copy
- Per-item scale notes added. Every What Founders Can Copy item on Basecamp, Automattic, GitLab, Doist, Buffer, Zapier, and Wolfram now carries an explicit scale-applicability note in parentheses (e.g., “Cleanest at 10–80; harder above 200”). This matches the pattern already present on GitHub, Linear, and Shopify (added May 1) so a founder reading at 25 people can see at-a-glance which practices apply at their stage.