Newest Research Pages: Inventory and Publishing Gaps

Research Summary

Executive Summary

The newest research pages are best identified from the local HTML inventory, not from index.json or search-engine results. The top five newest reports are first-month-metrics, zero-ad-spend-mrr, clone-but-better, instagram-distribution, and viral-x-mrr, and each of those pages is also publicly reachable on research.briankeefe.dev.

Newest Pages

1. Month One: What Your Post-Launch Numbers Actually Mean (first-month-metrics)

2. Zero Ad Spend, Real Revenue: How Solo Founders (zero-ad-spend-mrr)

3. Clone But Better: How Solo Founders Win Against Established Tools by Doing Less (clone-but-better)

4. Instagram as Distribution: How Indie Brands Drive Revenue in Days, Not Months (instagram-distribution)

5. Viral on X: When a Tweet Adds $500 MRR and Why It Almost Never Happens Twice (viral-x-mrr)

6. User One: The Psychology and Playbook of Your First Real User as a Solo Founder (first-user-psychology)

7. Launched to Silence: Why Solo Founders Get Crickets and What to Do in the Next 48 Hours (launch-crickets)

8. Build in Silence: The Psychology and Paradox of Stealth Building (stealth-building)

What The Newest Cluster Says

The recent batch leans heavily toward founder distribution, traction interpretation, and post-launch reality checks rather than broad market maps. Titles about zero-ad-spend growth, Instagram distribution, virality on X, launch silence, first-user psychology, and stealth building all point to a practical operator audience.

Verification

The live homepage scrape confirmed that the site is browseable and that the recent slugs are exposed publicly. Individual scrapes of the newest pages also confirmed they render correctly on the public domain, so these are not just leftover local files.

Gaps

index.json is stale. It currently contains only one entry even though the output directory has 77 report HTML files and the public homepage exposes 78 unique report links. For inventory work, the homepage and file mtimes are reliable; index.json is not.

Implications

If the goal is to know what is newest right now, use local file modification times as the source of truth and treat search results as secondary confirmation only. If the goal is to power downstream tooling, fixing index.json generation is the main operational issue surfaced by this audit.