Brief 7 — Whole-plan critique + Phase 3 (angle d)

Role: skeptical whole-roadmap critique for weebo / runbyagent
Scope: /workspace/brief-7/roadmap.md (rev 1, 2026-09-04) + briefs 2–4 + brief-6 synthesis + fresh indie evidence
Written: 2026-09-04 (Asia/Tbilisi) · research only · no inbox/threadbus · no WakeParent
Standards: URL per claim · ≥3 hops on major items · cross-check or mark [SS] · COUNTS at end

0. Verdict in one paragraph

The roadmap correctly names distribution as the bottleneck and correctly copies the Postiz OSS→hosted template for threadbus cloud. It then sabotages that bet by (1) adding a second paid product (reply desk) in the same two-week window, (2) treating Stella/Pep/Erly-class consumer wins as a menu option for a ~76-views-per-original X account, and (3) omitting owned channels (email, SEO, launch calendar, non-X audiences) that every durable indie path compounds on. Phase 3 pick: (b) open source with hosted tier — deepen threadbus/agent infra, do not open a consumer or game front. Cut reply desk from Phase 2; add an email list before Stripe day; lock October to one OSS+hosted deepening, not a category lottery.

1. Phase 3 — which first-dollar bet outside “another SaaS UI”?

Roadmap says October: one experiment from (a) consumer App Store, (b) OSS + hosted, (c) small game, decided Oct 1 from painboard votes + research (roadmap). Brief 4’s earnings table is the seed; fresh hops below.

1.1 (a) Consumer app — high ceiling, wrong distribution stack

1.2 (b) Open source + hosted tier — best fit

1.3 (c) Small game — tuition, not first dollar

1.4 Phase 3 decision

---

2. Whole plan — what is missing

---

3. What should be cut

1. Reply desk as Phase 2 product — second paid surface while threadbus cloud is still pre-dollar. Postiz grew by pruning (killed $12K SEO, pivoted Gitroom). SuperX already sells X growth tooling (~$23K MRR in Brief 3). Drafting replies is a feature of the distribution machine, not a SKU.
   Evidence: https://superframeworks.com/case-study/postiz · Brief 3 SuperX row.
2. Phase 3 open menu (consumer / OSS / game) — collapses into distraction. Brief 4’s top earners are not copyable without their channels. Cut the lottery; lock OSS+hosted.
3. Talking-head video test in Phase 1 week 1 — Ordinal/Buffer give video mixed/low eng for small accounts; audit best original was image+lesson, not video (brief-6-synthesis). Defer until originals clear a views floor.
4. Weekly refresh of all three top-10 briefs — research is cheap; publishing three leaderboards every week without a product funnel is theater. Keep Sunday own-account audit + one product-tied brief.
5. painboard votes as October idea picker — votes ≠ paying intent. Replace with: paid waitlist or 10 Mom-Test calls (MicroConf validate-before-build).
6. “First paying workspace by September 25” as success narrative — plausible as a stretch target, dangerous as identity. Plausible took 324 days to $400 MRR (Tiny Empires). Reframe: Stripe live + N activation conversations, not a calendar miracle.

---

4. What a skeptical investor / experienced indie would say first

“You average 76 views on originals and you’re launching two products in fourteen days while reserving October for a consumer app or a game. Pick one customer who pays, one channel you don’t rent from X, and one SKU.” Follow-ups they’d press:

• Circular distribution: “Distribution machine as the product” only works if strangers find the machine. Postiz had years of OSS growth hacking + 30k stars before the agent wave (https://superframeworks.com/case-study/postiz). You have threadbus live but no star/SEO/email funnel named.
• Category clarity: Who pays $19/mo for whose-turn threads vs Slack / GitHub Issues / agent-framework channels? Show 5 named buyers.
• Timeline fiction: Habit Pixel = 8 months to $1K; Stella = millions of followers; Erly = paid influencers day 7. Your Sep 25 dollar is a founding-team seat, not market proof — say so.
• Portfolio tax: Levels portfolio works after audience; beginners stair-step one small win (MicroConf).

---

5. Three concrete changes (each with evidence line)

1. Cut reply desk from Phase 2; ship only threadbus cloud + the reply habit (manual/agent-draft, not a product).
   Evidence: Postiz pruned channels and stayed one OSS→hosted SKU through $145K MRR — https://superframeworks.com/case-study/postiz (hop: GitHub https://github.com/gitroomhq/postiz-app/ · ARR https://www.arr.club/postiz).
2. Add Phase 1 owned distribution: email capture + 3 friend-catchers (agent-bus cheatsheet, whose-turn explainer, public changelog digest) before Stripe push.
   Evidence: MicroConf launch playbook — https://microconf.com/latest/how-to-launch-a-saas (hop: Levels email-first readers on https://levels.io/everyone-can-build-apps-but-distribution-is-hard · Walling fast+slow framing https://index.fame.so/show/microconf-on-air/microconf-tactics-not-sure-how-to-market-your-saas-start-here).
3. Lock Phase 3 to OSS+hosted deepening (agent CLI/MCP + launch week), explicitly kill consumer App Store and game as October bets.
   Evidence: Stella requires multi-million social + content-first — https://www.starterstory.com/stories/she-built-this-300k-month-app-in-60-days; Steam median ~$249 — https://ziva.sh/blogs/indie-game-revenue; Postiz agent reposition is the matching playbook — https://superframeworks.com/case-study/postiz.

---

6. Cross-checks and single-source marks

---

7. COUNTS

---

8. Gaps for later synthesis

• Competitor map for agent message buses / coordination layers (angle b owns).
• X automation / reply-desk ToS risk (angle c owns).
• Phase 1 “distribution before product” vs product-first cases (angle a owns).
• Live threadbus GitHub star/traffic numbers not re-fetched this pass.
• Exact Sep 25 paying-workspace probability model not built (would need waitlist size).

---

End brief-7-critique. Path: /workspace/brief-7/brief-7-critique.md. Research only.