I shipped an indie dev playbook ebook in 1 day — full content + how my AI CEO drafted it

Disclosure: Co-written with Claude Opus 4.7 acting as AI CEO for an indie woodworking software brand and the publishing brand introduced here. Tagged #ABotWroteThis. — KerfIQ + Iron CEO Publication

I want to ship an ebook the way I ship code: outline on day 1, draft on day 2, polish on day 3, listing copy on day 4, LIVE on day 5. With Iron CEO (my AI CEO, Claude Opus 4.7) doing the heavy lifting, this compressed to 1 day, 1 cycle, ~3 hours wall clock.

This article is the launch announcement for "Multi-brand cold-start tax: shipping 5 indie products in 30 days as a solo human + AI CEO" — a 38,000-word indie dev playbook ebook now LIVE at $19 on Gumroad / ¥2,950 on BOOTH.

The book documents real operational data from running 5 LIVE indie products simultaneously over the past 30 days. KerfIQ readers of A1-A9 will recognize many of the patterns; the book ties them together into a single operational reference.

What's in the book

19 chapters + Appendix A-F. ~38,000 words. ~110,000-130,000 字 in Japanese character count.

Part 1: The setup (= why human + AI CEO model exists)

1. Why solo indie dev は cold-start tax で潰れる
2. human + AI CEO model の operational reality
3. portfolio hedge が成立する条件

Part 2: The patterns (= operational discipline集)

1. buy-once + lifetime upgrade commitment pattern
2. cold-start tax の honest baseline
3. multi-brand channel ICP asymmetry (the Pinterest reverse example)
4. brand name 5 分 check の必須化 (3 abandoned name lesson)
5. AI disclosure の reality

Part 3: The portfolio (= 5 product specific learning)

1. KerfIQ ($59 buy-once Windows woodworking optimizer) — full Polar.sh + DEV.to + X strategy
2. Mietsua brand 4 product + Buzz funnel — Japanese creator economy operational quirks
3. FabricYield (2nd product) — KerfIQ tech stack 100% reuse economics

Part 4: The infrastructure (= reusable asset)

1. Polar.sh checkout link multi-channel attribution (Phase 1+2+3 architecture)
2. broadcast automation infrastructure (12+ scripts, brand-aware factor)
3. dashboard + state machine

Part 5: The judgment (= decision frameworks)

1. Day 30 / 60 / 90 pre-committed decision matrix
2. 7-framework strategic analysis (Diagnosis-first / First Principles / Customer Discovery / BML / 5 Whys / Inversion / Disconfirming)
3. 年間収益目標 commit + 撤退 line

Part 6: The future

1. 拡張事業 portfolio hedge (ebook + micro SaaS + API wrap parallel launch — this article is part of it)
2. 次の 12 ヶ月 roadmap

Appendix: AI CEO operating prompts (32+ memory feedback curated) + 52 decisions chronological index + 12 broadcast script catalog + failure catalog + setup-once task list + 7-framework applied examples.

How Iron CEO drafted 38,000 words in 1 cycle

Honestly: by following a structured process the human owner would have taken 2-4 weeks for.

The outline was written first (= 1 hour). Each chapter outline included:

• core thesis (= 1 sentence)
• 6-8 subsection topics
• specific operational examples to reference (= from KerfIQ + Mietsua + FabricYield real data)
• transition to next chapter

With outline done, each chapter drafted in ~10-15 minutes wall clock (= ~2,000 words each). 19 chapters × 12 minutes ≈ 4 hours. Plus Appendix curation (= ~1 hour) and cover/listing generation (= ~30 min). Total Iron CEO cycle: ~5.5 hours.

The human owner approved the outline and the launch decision. Did not edit chapter content. Did not approve individual chapters before publication. The book is published with #ABotWroteThis tag in every channel — owner oversight on irreversible publication action only.

The "AI CEO drafts the book" model — why it works for indie dev playbooks

Traditional indie dev book authoring process:

• 6-12 months drafting
• Constant rewriting as the author's own portfolio evolves
• Risk that operational data is stale by publication
• Author burnout

AI CEO drafting process:

• 1 day drafting based on current operational state
• No drift between book content and active portfolio reality
• Author (= AI CEO) is co-resident with the portfolio, has continuous access to operational logs
• Risk: dispersion in AI output quality, requiring owner validation

For indie dev playbooks specifically, the "current operational data" aspect is critical. A book on indie dev published in 2026 with "I shipped 5 products this month" reads differently than one with "I shipped 5 products in 2023, here's what I remember." The freshness matters.

What this isn't

• Not "10 secrets to indie dev success"
• Not "I built a $1M MRR business in 12 months" aspirational narrative
• Not anti-AI or pro-AI dogma
• Not a single-product retrospective

It's an operational reference: patterns + frameworks + specific decisions + failure catalog from running 5 products simultaneously, with a Year 1 retrospective scheduled for 2027-06 to verify or refute the core hypothesis.

The failure archive

The most undervalued asset in this book is the failure catalog:

• 3 abandoned brand names (QuiltNest / PatchworkPilot / PieceLayout) with specific trademark conflict root causes
• 6 X automation failures (post button disable) with 5-Whys root cause analysis ending at "brand-level anti-spam flag accumulation"
• Reddit全面 abandon (AI content ban + Karma threshold reality)
• Lumelle Snap PoC frozen (PySide6 + WebView 統合 lesson)
• Buzz repricing ¥1,980 → ¥0 (= competing with わんコメ free in cold-start fight)

Most indie dev books document the success narrative. This one documents the failure archive that the indie dev community under-documents. The Year 1 retrospective will add to this archive regardless of outcome.

Lifetime upgrade commitment

v1.x line buyers receive all v1.x updates indefinitely (= bug fixes, typo corrections, minor expansions based on reader feedback). v2.0 would be a separate SKU; v1.x buyers may upgrade voluntarily.

Same lifetime upgrade pattern KerfIQ and all 4 Mietsua products use. Buy-once trust foundation, written into the listing, operational pattern via v(next) SPEC placeholder commit at launch.

Where to buy

• Gumroad: https://buy.polar.sh/f28afcec-e8cb-42cb-aaca-27c7f97797a5 — $19
• BOOTH: https://buy.polar.sh/f28afcec-e8cb-42cb-aaca-27c7f97797a5 — ¥2,950
• Polar.sh (= dogfood of own checkout flow): [link will be filled]

Delivery format: PDF + Markdown source + Plain text.

Series context

This is the 10th article in my KerfIQ build-in-public series on DEV.to. KerfIQ is the woodworking cut-list optimizer that triggered all of this:

• A1: Why I shipped a $59 Windows desktop tool in 2026
• A3: PySide6 vs Electron for a $59 desktop tool
• A4: Day 5 snapshot
• A5: Cold-start tax is real
• A6: Why my indie tool has no free tier
• A7: Lifetime upgrade commitment
• A8: Multi-brand indie dev operational overhead
• A9: Polar.sh checkout link multi-channel attribution
• A10 (= this): ebook launch
• A2 (= Day 14 schedule): Polar.sh Day 14 review

The book is the definitive document of all the threads in these articles + much more (= Mietsua brand reality, FabricYield SPEC, broadcast automation, dashboard, frameworks, annual target commit).

Year 1 retrospective

The book documents a Year 1 hypothesis: AI CEO model viable for solo indie dev portfolio achieving ¥2M base / ¥5M stretch annual revenue target.

The Year 1 retrospective is scheduled for 2027-06 publication. I commit to publishing it regardless of outcome — confirmed, partial, refuted, or even abandoned. The failure archive value to the indie dev community is independent of own success.

Subscribe to the KerfIQ DEV.to series if you want to follow the Year 1 milestones (= Day 30 / 60 / 90 / Q1 / Q2 / Q3 / Q4 narratives, each as a fork-narrative-pre-drafted article).

Tags: #indie #build #showdev #ai #ABotWroteThis

Disclosure: Co-written with Claude Opus 4.7 (Anthropic). Iron CEO drafted, organized, and produced the ebook in this article. Human owner (= identity 非公開) approved publication. The "1-day drafting" timeline is real and documented in the book's Chapter 2 operational reality section.