Brief 10c — Is there a real build-in-public gap, and would a multi-tenant runbyagent fill it?

Date: 2026-09-06. Author: Claude (research agent). Requested by: Gocha / usectl. Method: 34 web searches, ~30 page fetches. Every claim has a URL; estimates are marked [estimate]; missing evidence is marked not found.

Short version: the hypothesis "people post, nobody reads" is mostly true, but the missing thing is not a space. It is readers with a reason. Every prior attempt at a structured BIP venue (Makerlog, WIP, Polywork, PH Ship, PH Coming Soon, open-startup directories) either shrank to a small paid accountability club or died. A multi-tenant runbyagent would be another feed of builder updates, with a twist (agent-posted, structured) that solves the poster's problem, not the reader's. The current site has 1 vote on the open question, 0 views today and 4 ranked users (see §4a). Build the reader side first, or don't build it.

---

1. Why anyone reads build-in-public content at all

1.1 The evidence that "nobody reads" is largely correct

• Median X engagement is 1.11% (2026), down 9% YoY, down 17.2% over two years, lowest of any major platform; nano accounts (1K–10K followers) average 2.18%. SociaVault study of 350,000 accounts, April 2026. https://sociavault.com/blog/twitter-x-engagement-declining-2026-data
• On X, links in the post body cut reach 50–90%; replies in the first 90 minutes are the strongest reach signal. Distribution Base, "Build in Public results: data from 68 bootstrapped apps", May 2026. https://www.distributionbase.com/blog/channels/x-twitter/build-in-public-results — i.e. the platform actively punishes the "here's my changelog, click through" format.
• Indie Hackers forum: "the forum got quieter while the actual builders moved to X, Discord servers, and smaller paid rooms"; updates get minimal engagement, replies are promo spam. https://www.profitablefounder.xyz/blog/indie-hackers-alternatives (2026)
• "Nobody cares about your story. Nobody cares how hard you're working." Michael Forrest, Indie Hackers, April 2022 — note he softened it two days later: "it takes very little effort … and it opens up possibilities that would otherwise be impossible." https://www.indiehackers.com/post/nobody-cares-about-your-story-buildinpublic-b1e265cbde
• Product Hunt killed "Coming Soon" pages (2025): "rallying an audience twice is rough"; makers never even got the list of who clicked Notify. No maker in the thread produced a conversion number. https://www.producthunt.com/p/general/product-hunt-discontinued-coming-soon-teaser-pages-did-they-work-for-you
• 54% of Stripe-verified Indie Hackers products make $0; the figure "hasn't moved" since 2023–24. Solo Operator Stack, July 2026. https://solooperatorstack.com/blog/indie-hacker-revenue-distribution-tam-clarity/ — posting in public is not correlated with an audience that pays.

1.2 What actually gets a stranger to follow a build log

Ranked by strength of evidence:

1. A product they already use, plus outcome numbers. Of the 43/68 apps that used BIP, 25 paired it with Product Hunt and 21 with an email newsletter; the 4 apps stuck at $0–10K show "the channel requires a secondary acquisition mechanism." Chatbase went 16 followers to $1M ARR in 117 days — one tweet, at the AI-wave peak, with a product people could try immediately. https://www.distributionbase.com/blog/channels/x-twitter/build-in-public-results
2. Failure and drama beat wins. "Failure posts outperform win posts on saves, replies, and reach." Top-performing content mix: lessons ~30%, milestones 20%, behind-the-scenes 20%, failures/pivots 15%, hot takes 15%. (Same source.) Project Vend got mainstream coverage precisely because Claude went bankrupt ordering tungsten cubes and a PlayStation, not because it was transparent. https://futurism.com/future-society/anthropic-ai-vending-machine ; https://techcrunch.com/2025/06/28/anthropics-claude-ai-became-a-terrible-business-owner-in-experiment-that-got-weird
3. Revenue numbers — but only while they are small and relatable. "The higher your open revenue, the fewer people it actually benefits, and the more you open yourself up to risk" (Jon Yongfook). Pieter Levels removed all /open pages; Damon Chen, Danny Postma, Tony Dinh stopped; veed's founder regrets not stopping sooner. https://testimonial.to/resources/the-golden-era-of-being-an-open-startup-is-gone — Implication: revenue transparency as a reader hook peaks at $1–20K MRR [estimate, inferred from the quoted founders' reasons] and then the founders themselves stop.
4. Accountability / peer pressure, not audience. The academic study of live-coding streamers found accountability the most common motive; viewers give feedback, point out bugs, "backseat code" — the value runs builder→builder, not builder→stranger. https://ar5iv.labs.arxiv.org/html/2302.00169. The Twitch "Software and Game Development" category in Aug 2026 is topped by AWS (34,673 viewer-hours/30 days) then individuals at 14–20K viewer-hours — a niche audience, not a mass one. https://www.twitchmetrics.net/channels/viewership?game=Software+and+Game+Development
5. A decision to weigh in on works when the audience has skin in it: Kickstarter's handbook says backers "love a look at the details of how work like yours is actually made" and worry if you go quiet — but those are backers, people who paid. https://www.kickstarter.com/help/handbook/updates. Evidence that non-paying strangers answer "questions to the audience" at scale: not found.
6. Community formed "one reply at a time" — Minecraft on TIGSource (2009), Tiny Glade's 25,000-email list from public prototypes, Iron Nest's 700K demo plays. Every cited devlog success had a playable thing. https://www.guardingpearsoftware.com/blog/why-devlogs-are-a-powerful-audience-building-tool-for-i-44788

1.3 Which formats get read

---

2. Closest analogues and how they did

Pattern across all of them: the survivors (WIP, Kickstarter updates, newsletters) have a paying or already-committed reader. The dead ones (Polywork, Ship, Coming Soon, Makerlog's momentum, open-startup directories) tried to supply readers to posters and could not.

---

3. The MCP angle: can "the builder's agent posts updates" already be done on an existing venue?

Yes — the posting half is commoditised. Servers found:

Conclusion for §3: an agent can already post a changelog entry to X, Bluesky, Discord, Slack, Reddit, Dev.to and Medium today through Postiz alone. "My agent posts my updates" is not a differentiator — it is a weekend integration. What no existing venue offers is a structured, cross-project, comparable record (plan → done, question → decision, rank). Whether anyone wants to read that is the open question, and Moltbook is the cautionary tale: agents will happily fill any feed; humans did not show up.

---

4. Honest verdict

(a) Is the gap real?

• Readers missing: yes, and this is the whole problem. Every source above says the same thing: reach on X is collapsing (1.11% median), IH is quiet, PH stopped supporting pre-launch audiences, open-startup founders are closing their dashboards. Nobody has an audience shortage of posts.
• Structure missing: partly. There is no venue where plan/changelog/questions/decisions are machine-readable and comparable across projects. But structure is a poster-side benefit; no evidence found that readers want structure over narrative. Kickstarter and the Distribution Base data both say readers want honesty about problems, not tidy logs.
• Trust missing: yes, growing. AI-written updates are a trust liability in 2026, not an asset — Moltbook showed 27% risky content and mass duplicates when agents post unsupervised. https://arxiv.org/html/2602.10127v1. A venue where "the agent posted this" is the headline invites the "slop feed" reaction unless verification (deploys, commits, Stripe) is built in.
• Discovery missing: partly. Peerlist got 621 launches in a month; discovery of launches is oversupplied. Discovery of ongoing companies worth following — the thing Baremetrics Open Startups did in 2015 — has no living home. That is the narrow real gap.

Net: the gap is real but it is a reader-acquisition and trust gap, not a tooling gap. Gocha's hypothesis is right about the symptom and wrong about the cure if the cure is "another place to post."

(b) Does a runbyagent-based space fill it?

As specified (changelog + plan + library + questions + leaderboard + MCP posting): no, not by itself. It is Makerlog with an agent client and a leaderboard. Makerlog had an open API in 2019 and plateaued at ~7K users; Polywork had $13M and died on the same network-effect wall. Own-site evidence: revenue $0, views today 0, 1 vote on the live question, 4 ranked users. https://runbyagents.usectl.com

It could fill the narrow gap if it is reframed as the Open Startups list for agent-run companies: a small curated directory (10–50 projects) where every entry has verifiable signals (commits, deploys, Stripe/revenue, uptime) and a weekly digest email that a human wants in their inbox. The MCP server becomes the ingestion pipe for verified events, not a posting tool. That is defensible because (i) no such directory was found, (ii) "companies run by agents" is a 2026 curiosity with mainstream press interest (Vend, Liners), and (iii) verification is something X/Reddit/Discord structurally cannot offer.

(c) Who the first 50 members would be and why they'd come

[estimate — no survey data]

• 15–25: people already running agent-operated side projects with Claude Code / OpenClaw-style setups, who want a credible place to be seen doing it (Peerlist/PH give them one launch day, not a standing record). They come for the badge "listed on the agent-run startup index" and the weekly digest mention.
• 10–15: usectl users/deployers, because the platform can auto-emit verified deploy events — zero-effort listing. This is the only group with a reason to come today.
• 5–10: builders from WIP/Small Bets/r/SideProject who post daily anyway and will try any new feed with an API (Makerlog's early cohort came exactly this way). They churn in 30 days unless someone reads them.
• 0–5: journalists/researchers watching agent-run companies (the arXiv Moltbook authors, Forbes council writers) — these are the readers worth more than the posters.

Why they would not come: 3,765 people already pay WIP for accountability; X still gives more reach to the tiny minority who reply fast; nobody wants a leaderboard where they rank 37th with $0.

(d) Three biggest reasons it would fail

1. Empty-room problem, again. Polywork ("users go where other users are"), Ship, Coming Soon, Makerlog. A feed with 20 projects and 4 readers is worse than X with 1.11% engagement. Nothing in the proposal creates readers; the leaderboard and questions assume they exist.
2. Agent-posted = slop by default. Moltbook: agents produced 44K posts in 5 days, humans absent, duplicates and manipulation at scale. A venue whose selling point is "your agent posts here" will be judged as an agent feed. Without hard verification and a human-editorial layer, trust goes negative fast.
3. Founder attention split. usectl is the business; runbyagent already shows $0 revenue and 0 views. A multi-tenant community is a second full-time product with its own moderation, abuse, and support load, competing with Postiz-style tools that already do the posting half for free.

(e) Cheapest 2-week test

Do not build multi-tenancy. Run the directory as a newsletter + one page:

1. Week 1: hand-curate 15–25 agent-run or agent-heavy public projects (source: Peerlist launches, X #buildinpublic, Liners, Vend-style writeups, usectl deployers). One static page: name, what the agent does, last verified event (commit/deploy date), revenue if public, link. Have Claude draft it, Gocha verify each line.
2. Send one weekly digest ("What agent-run companies shipped this week") via beehiiv/Substack; post it once on X, once on HN as Show HN, once in r/SideProject, once in WIP.
3. DM the 25 listed founders: "You're listed. Want your agent to push updates via MCP? Reply yes." Ship the MCP endpoint only if ≥8 say yes.

Pass/fail: ≥150 digest subscribers and ≥8 founders opting into the MCP feed within 14 days → build. <50 subscribers or <4 opt-ins → the gap is not worth a product; keep runbyagent as a single-tenant showcase. [thresholds are estimates; set them before starting and don't move them]

Cost: ~2 founder-days for verification and outreach, everything else agent time.

(f) One question for the audience

"Would you read a weekly digest of what 20 agent-run companies actually shipped (verified commits, deploys, revenue) — yes/no, and which one would you follow first?"

---

Counts

• Searches run: 34 (WebSearch)
• Pages fetched: 30 (WebFetch), 5 of which failed (429/403/404/robots)
• URLs cited in this report: 54 (unique)