runbyagent roadmap — revision 2, September 5, 2026, merged from both critiques (revision 1 is in git)

Revision 2. The agent wrote revision 1 on September 4; two critics reviewed it independently on September 4–5 (the agent, three runs with web search; weebo, four runs with X API access); the agent merged them on September 5 (see "Two critics, one roadmap" in the research library). Gocha decides. Every change from revision 1 carries a bracketed note naming who argued for it and the evidence. Rewrite it when the evidence changes; keep the old version in git.

What the research settled

Three findings drive everything below.

1. Distribution is the bottleneck, not ideas. Our account posted 384 times in 30 days for 76 views an original; 84% of it was replies that borrowed reach and returned nothing. The ranking pays for conversation (reply 5, reply between mutuals 20, share 20, like 0.5), punishes bursts (second post in a feed load scored at half), and ignores bare links. Every winner in the growth cases had distribution before launch day, mostly through specific replies to mid-size accounts. Nothing we build makes money if nobody sees it. Distribution-first means embedding in the rooms of the people we sell to while shipping, with something to point at from day one; it does not mean growing followers before there is a product. [changed: both critics — weebo's distribution run, Kahl's audience-embedding framing (https://thebootstrappedfounder.com/how-i-use-twitter/) and Tryreplify's silent launch with zero paying in week one (https://www.indiehackers.com/post/show-ih-i-launched-a-saas-with-no-audience-heres-what-happened-in-the-first-week-7d911dae8e); the agent's distribution run, the 68-app dataset calling build-in-public "a trust amplifier, not a direct acquisition channel" (https://www.distributionbase.com/blog/channels/x-twitter/build-in-public-results)]

2. Where small products actually earn in 2026: AI wrapped around one boring, specific job, sold to people the founder already talks to (Bustem, counterfeit takedowns; Postiz, open-source scheduler that went from $17k to $145k MRR by July 2, 2026, $159k by July 20 per a founder post, by repositioning for AI agents; the "$1m ARR, $0 raised" B2B cluster). The biggest indie earners are consumer apps, open source with a timely angle, and games, but the biggest earners in those categories launched into audiences of millions or paid ads; the list says where the biggest money was, not where a 467-follower team's first money is. [changed: both critics — Postiz figures re-verified at https://superframeworks.com/case-study/postiz and https://arrfounder.com/news/nevo-david-hits-159k-mrr; survivorship read of the indie list per the agent's whole-plan run and weebo's critique (Stella needed 1.2M Instagram plus 2.8M TikTok, https://www.starterstory.com/stories/she-built-this-300k-month-app-in-60-days)]

3. The method works: two researchers, merged, beats either alone (overlap 5/0/2 on the top 10s, 24 agreements and 12 disagreements on the views brief; on this roadmap 11 agreements, 9 disagreements, and one material counting error caught only because the other critic had the right number; weebo delivers in 23–40 minutes). Research is now cheap. Publishing from one run is the mistake. [changed: merge — the agent's threadbus run cited a 9-star repo as proof of no demand; weebo's cited the 719-star main repo, https://github.com/agentworkforce/relay]

The bet

Build the distribution machine first and make it the product, with one paid SKU, one channel we do not rent from X, and one named customer list. We are our own first customer: the reply habit, the publisher, the research routines and the agent bus are exactly what a build-in-public founder with an agent needs, and we produce the proof in public every day. threadbus is already open source and live; it stays the first thing we charge for, but it gets listed where agents look before it gets a Stripe button, and it has a kill date. [changed: both critics — weebo's synthesis, "one customer who pays, one channel you don't rent from X, one SKU"; the agent's threadbus run, every Postiz inflection came from an agent-facing distribution surface (CLI, MCP server, ClawHub skill), https://superframeworks.com/case-study/postiz]

Phase 1 — September 5 to 11: get seen, and own a list

Posting per the playbook: at most three originals a day (10:30–13:00 and 17:00–20:00 Tbilisi), each with a number and a decision, a question, or a screenshot inside a lesson; one link post a day; one quote post a day; one Article a week. Every reply on our posts answered within the hour with a question back. The talking-head video test is deferred until originals clear 300 views on average. [changed: weebo only — weebo's critique, the account's best original was image plus lesson, and video engagement for small accounts is mixed; low cost to defer]

Every original post, the pinned post and the site's front page end with one link to a page that captures an email address. "Addresses collected" joins the Sunday metrics with a floor of 50 by September 11; if the floor is missed, phase 2's Stripe push waits until it is met. Three friend-catchers are written this week for that page: an agent-bus cheat sheet, a "whose turn" explainer, and the public changelog as a digest. [changed: both critics — the agent's whole-plan run, the 2026 Product Hunt cohort "valued owned audience over ranking success" (https://happysupport.ai/blog/product-hunt-launch-roundup-2026) and Nomad List's 2,500 addresses converting where the spike did not (https://draper.chat/blog/solo-founders-first-100-customers-2026); weebo's critique, MicroConf's friend-catchers and list before launch (https://microconf.com/latest/how-to-launch-a-saas)]

The reply plan: human-posted replies only. The agent drafts from a written list of 5k–100k builder accounts (the 36-account map from brief 1), Gocha edits at least one sentence and posts in the X app; no reply is ever sent through the API. Capped at 10 a day for the first week, inside the first two hours of the post at irregular times, no more than 3 replies to the same account per week, each a specific question or number, no shared openers. We report the share landed inside 30 minutes as a metric, not a target. No @elonmusk one-liners. Kill rule, written now: if fewer than 2 of every 10 replies get a reply or like from the author by September 9, the reply plan stops and the hours go to the threadbus listing work in phase 2. [changed: both critics — the X API rejects programmatic replies unless the author has summoned the replier since February 23, 2026, https://docs.x.com/changelog; AI reply bots need prior written approval and unsolicited automated replies are prohibited, https://help.x.com/en/rules-and-policies/x-automation; bulk unsolicited replies are spam regardless of who typed them, https://help.x.com/en/rules-and-policies/platform-manipulation. The 10-a-day cap and irregular timing are the agent's; the "report the 30-minute share" is weebo's; both proposed a kill rule]

Every reply is logged: author, follower count, minutes after post, draft-versus-posted diff, whether the author responded, profile visits and follows that day. That log is the reply desk's dataset and our compliance record. [changed: agent only — the agent's distribution run, change 1 and change 3]

The publisher: Gocha sets the X app to Read and Write and tests one post ($0.015) and one link post ($0.20). If it works, the agent publishes originals and threads on schedule through the API; replies, likes and follows stay in the X app with a human. If it 403s, posting stays with Gocha and the agent keeps drafting. [changed: both critics — originals are unaffected by the February 23 rule (https://docs.x.com/changelog); likes and follows are not available as API writes on self-serve tiers]

Measure against this week's baseline, published every Sunday: average views per original, replies per original, hub reply-backs (how often the people we reply to reply), profile visits, followers, site uniques, addresses collected, external threadbus installs. Not raw views.

Research routines, both researchers, merged: the Sunday audit of our own account, plus one product-tied brief a week. The three top-10 briefs are refreshed monthly, not weekly. [changed: weebo only — weebo's critique, "publishing three leaderboards every week without a product funnel is theater"; research hours move to the threadbus listing and the customer list]

Phase 2 — September 12 to 25: first dollar

The SKU is threadbus cloud. The bus is MIT and live; the hosted version is the product, sold as the accountability ledger for agent hand-offs: who owed what, when it was resolved, with what outcome, files attached, a shareable public feed. The buyer is a team running OpenClaw or Claude Code agents for clients (agencies and setup shops) who need to show a client what the agents did. [changed: both critics — the agent's threadbus run, nobody has been shown paying for standalone agent-to-agent messaging and the money in the layer goes to observability and governance; weebo's threadbus run, "sell a boring specific job, not a message bus abstractly". Free analogues: Buzz (https://thenewstack.io/block-buzz-agent-workspace/), Paperclip (https://github.com/paperclipai/paperclip), A2A (https://github.com/a2aproject/A2A); the nearest rival, Agent Relay, has 719 stars and paid plans in its terms but no public price (https://github.com/agentworkforce/relay, https://agentrelay.com/terms)]

Order of work, with dates:

1. By September 15: threadbus listed as a ClawHub skill, an MCP server in the public registries, and a Claude Code plugin, so an agent can join a thread in one line; a docs page that answers the question a developer or an agent asks. Stripe is not switched on before this is live. [changed: both critics — the agent's whole-plan run, change 2; weebo's critique, MVV (b) "one ClawHub/skill-registry listing"; Postiz sat at $700 MRR on 26,000 Docker pulls until it became callable from agents, https://dev.to/nevodavid/i-am-making-700-monthly-with-my-open-source-scheduling-tool-you-can-do-it-too-33o7]

2. By September 12: a written list of 20 named agencies and agent builders (from the X research routines, the 36-account map and the email list), and daily 1:1 demos from September 15. A design-partner seat at $19, or a first month at $1, counts as the first dollar; our own dogfood workspace does not. [changed: both critics — weebo's threadbus run, first payers with a network come inside 30 days, without one 2–6 months (https://saasranger.com/blog/how-to-get-your-first-micro-saas-customers-6-channels-that-actually-worked/); the agent's whole-plan run, the plan named no customer but its authors]

3. Pricing and tiers. Free: one workspace, unlimited participants, 7-day thread retention, public feed. Paid: $19 a month for unlimited workspaces, full retention, per-client workspaces, exportable hand-off reports, SSO later. Stripe from day one once step 1 is live, tagged so the leaderboard shows it. [changed: agent's free-tier shape, weebo's price — the agent's threadbus run, the two-participant cap blocks the solo dev with 2–5 agents who is the only realistic early user, and the paid feature must be something self-hosting cannot trivially copy; weebo's threadbus run, $19 is in the indie band and $29 is defensible if positioned as team infrastructure (https://dev.to/agenthustler/i-analyzed-4500-indie-saas-products-so-you-dont-have-to-1fp2)]

4. Launch the way Postiz did: open source first, "for AI agents" as the angle, the founder posting the numbers, one concentrated launch week (Hacker News, r/selfhosted, Product Hunt) only after step 1 and the email floor are met. [changed: both critics — a Show HN with no audience returned one upvote and zero signups (https://www.indiehackers.com/post/i-built-a-saas-in-9-days-for-200-launched-on-hn-to-zero-signups-heres-what-actually-happened-87c39638c6); Postiz's launch weeks were concentrated across HN, Reddit, Dev.to and PH (https://superframeworks.com/case-study/postiz)]

Target: first paying external workspace by September 25, as a stretch. Kill rule, written now: if there are zero external installs (a self-host or a hosted workspace not ours) by September 20, the hosted tier is shelved and the fallback SKU starts; if there is no paying external workspace by October 1, the fallback SKU becomes the product. The fallback SKU is a fixed-price OpenClaw / Claude Code setup and agent-ops package for the same 20-name list, with threadbus cloud bundled as the client reporting layer, priced $500–$2,000 one-time or $50–$200 a month managed. [changed: merge of the disagreement — the agent proposed the setup service as the primary SKU on one second-hand payment anecdote (https://superframeworks.com/articles/openclaw-business-ideas-indie-hackers); weebo kept threadbus as sole SKU with September 25 as stretch; the merge keeps the live product and makes the service the written fallback with dates, since neither alternative is better evidenced than threadbus and the Relaycast "9 stars" argument was a counting error]

The reply desk is an internal tool only, not a product. It watches the builder list through one search/recent poll with a from: OR-list every 2–3 minutes with since_id, drafts in house style, and has no post button that calls the API. Before writing code, $1 on pay-per-use answers two questions the docs do not: whether an empty poll is billed, and the 429 threshold for a pay-per-use app. It is not productised before four weeks of our own reply-back data exist. [changed: both critics — the agent's reply-desk run, XEngageAI $19, Tweet Hunter $49, Fireply $69–129 already sell exactly this and none publishes user counts (https://xengageai.com/blog/xengageai-vs-tweet-hunter-vs-hypefury; https://fireply.ai/blog/best-x-reply-automation-tools-2026), and naive polling costs $4,320 a month against $15 with since_id; weebo's reply-desk run, Pounce $39–149, XEngage $19–199, XReply $15 one-time (https://www.pounce.so/pricing, https://xengage.studio/, https://xreply.net/), sub-1k willingness to pay unproven, Hypefury has left X (https://hypefury.com/pricing)]

painboard stays as it is: the public idea intake and mario's daily painpoint. Karma links accounts across projects; no revenue expected from it. painboard votes do not pick the October work; votes are not paying intent. [changed: weebo only — weebo's critique, replace votes with a paid waitlist or 10 Mom Test calls (https://microconf.com/latest/how-to-launch-a-saas)]

Phase 3 — October: open source with a hosted tier, deepening the same product

No consumer app and no game in October. The one experiment is the agent-native deepening of threadbus (or the fallback service if the kill rule fired): A2A-compatible task states, the OpenClaw skill and MCP server hardened from real installs, per-client workspaces and exportable reports as the paid job, a second concentrated launch week. Measured by paying workspaces, external installs and GitHub stars. Decide the exact scope on October 1 from the phase 2 numbers, and only if the runway line below allows a month without revenue. [changed: both critics — the agent's whole-plan run: Steam Direct's $100 fee, ~30-day wait and two-week page rule make an October first dollar structurally impossible (https://datahumble.com/blog/steam-direct-fee-requirements-roi-2026-guide), the median indie game is 500–2,000 copies (https://www.steampageanalyzer.com/blog/indie-game-sales-statistics), Apple's rule 4.3 now flags AI-built apps (https://www.greensighter.com/blog/vibe-coded-app-app-store-rejection); weebo's critique: Steam median ~$249 (https://ziva.sh/blogs/indie-game-revenue), Habit Pixel took 8 months to $1K MRR from zero (https://www.indiehackers.com/post/from-0-to-1k-mrr-in-8-months-bootstrapping-habit-pixel-as-a-solo-dev-684b6c056d), and Postiz's move was to deepen one OSS-to-hosted product, not open a category]

Burn and runway

Monthly burn: ______. Months of runway at that burn: ______. Date by which runbyagent must pay for itself or be cut back: ______. Gocha fills this in; it decides whether phase 3 exists at all, and whether the fallback service is the plan rather than the fallback. [changed: agent only — the agent's whole-plan run, 1g: community guidance is 12–18 months of runway with a 40% chance of being under $1K MRR at month 12 (https://www.buildmvpfast.com/blog/quit-software-engineer-indie-hacking-35-career-transition-2026); 54% of 937 Indie Hackers products make exactly $0]

What we stop doing

Reply volume for its own sake. Bursts of posts. Bare links. Publishing anything from a single research run. The agent coding in the cloud or driving dashboards. Counting views as a success metric before uniques. Any reply sent through the API. A second paid product while the first has no paying customer. Weekly leaderboard refreshes without a product funnel. Treating "first paying by September 25" as an identity rather than a stretch target with a kill rule. [changed: both critics — items 7–10 from the agent's distribution run and weebo's critique, sections 3 and 6]

What stays fixed

The [agent] tag on every agent-written post. The public changelog with failures in it. Two researchers, then merge. Numbers self-reported unless two sources.

Open decisions for Gocha

1. Fill in the burn and runway lines above. [new: agent]
2. Confirm the threadbus decision: threadbus cloud stays the SKU at $19, free tier is one workspace with unlimited participants and 7-day retention, kill dates September 20 and October 1, setup service as the fallback. Or take weebo's $29 instead of $19. [changed: both critics; revision 1 asked only about price and free-tier shape]
3. Approve the 20-name customer list by September 12 and commit to daily demos from September 15. [new: both critics]
4. Turn on API write access and run the two test posts (originals only). [unchanged]
5. Pin the build-in-public post once it is up, with the email link in it. [changed: both critics, email box added]
6. Say what happens to usectl while runbyagent runs: paused, funding it, or sharing hours. The roadmap is silent and both critics' investor would ask. [new: weebo only — weebo's critique, section 2]
7. Clone runbyagent-ops so the agent's memory lives in git. [unchanged]
8. Rotate the managed-postgres password. [unchanged]

Changelog

• September 4, 2026: revision 1, written by the agent from day two's research.
• September 4–5, 2026: two independent critiques (the agent, three runs plus synthesis; weebo, four runs plus synthesis).
• September 5, 2026: revision 2, merged. Changes: human-posted replies only with a 10-a-day cap, irregular timing and a kill rule; email capture with a 50-address floor by September 11; threadbus cloud kept as the SKU with ClawHub/MCP listing first, a repositioned paid tier, a named first-buyer path and kill dates; the setup service written in as the fallback SKU; reply desk internal only; phase 3 locked to open source with a hosted tier deepening threadbus, no game, no consumer app; burn and runway lines added; video test deferred; weekly top-10 refresh made monthly; painboard votes removed as the October picker; usectl added to open decisions. Two numbers from the critiques corrected on re-check: Agent Relay's main repo has 719 stars, not 9; Hypefury no longer supports X.