SolopreneurAI Agent自動化Claude CodeBuildInPublicSaaS

How I Manage 5 Products as a One-Person Company: The Coordinator Architecture

· 10 min read
Table of Contents
  1. Let's Be Honest: This Isn't Normal
  2. The Core Problem: It's Not About Getting Things Done, It's About Deciding What to Do
  3. The Coordinator Architecture
  4. Weekly Schedule
  5. How Each Day Starts
  6. 5 Minutes: TG Notification Triage
  7. If There's a Red Alert
  8. If Everything's Green
  9. Claude Code as a Multiplier
  10. Tech Stack Overlap Strategy
  11. What's Automated vs. What's Not
  12. Fully Automated (Lobsters)
  13. Semi-Automated (I trigger, Claude executes)
  14. Fully Manual (Only I can do)
  15. Monitoring: One Screen for All Products
  16. The Honest Cost
  17. What Breaks
  18. What I've Sacrificed
  19. Why Not Do Fewer Things?
  20. Can You Replicate This System?
  21. Need Help Managing Yours?

Disclosure: Ultra Lab, MindThread and Ultra Advisor are products of the same group, Ultra Creation (傲創實業).

Let's Be Honest: This Isn't Normal

Running 5 products as one person is, in any sane world, a suicide mission.

Product Purpose Tech Stack Status (as of 2026-04-02)
UltraLab AI product studio React + Vite + Vercel Live, primary brand
MindThread Threads automation 110+ accounts (75 active), 4M+ views (per-post insights, 2026-08-09) Live
Ultra Advisor Clause-level AI workbench React + Firebase + 16 tools Live
UltraTrader Taiwan stock trading bot Python + Shioaji + FastAPI In development
OpenClaw AI Agent fleet WSL2 + Ollama + 34 timers Running 24/7

These 5 products span 3 machines, 4 programming languages, and 2 Firebase projects. If each product needed a 3-person team, I'd need 15 people.

I have me. And Claude Code. And 4 lobsters.


The Core Problem: It's Not About Getting Things Done, It's About Deciding What to Do

The biggest enemy of a one-person company isn't lack of skill. It's decision paralysis.

Every morning I wake up to:

UltraLab:    Growth page needs CTA changes → ~2 hours
MindThread:  3 accounts got throttled by Threads → need strategy adjustment
Advisor:     Client reported chart breaks on mobile → need debugging
UltraTrader: Simulation lost 2% yesterday → need to review strategy logic
OpenClaw:    Lobster #2 memory usage is high → need to check logs

5 things, all important. All urgent. If I deliberated which to do first, deciding alone would eat an hour.

So I built a system that doesn't require daily decisions.


The Coordinator Architecture

┌──────────────────────────────────┐
│        Coordinator (me)           │
│                                   │
│   Daily rules:                    │
│   1. Check TG notifications (5m)  │
│   2. Red alert → fix it           │
│   3. No alerts → today's product  │
│   4. Other products → lobsters    │
└───────┬──────────────────────────┘
        │
  ┌─────┴─────────────────────────┐
  │         Claude Code            │
  │   (2-3 sessions simultaneously)│
  │   Each session = one product   │
  ├───────────────────────────────┤
  │ Session 1: ~/UltraLab         │
  │ Session 2: ~/financial-planner │
  │ Session 3: ~/UltraTrader      │
  └───────────────────────────────┘
        │
  ┌─────┴─────────────────────────┐
  │    WSL2 OpenClaw (autonomous)  │
  │                                │
  │  Lobster #1: Probe Agent       │
  │  Lobster #2: MindThread Agent  │
  │  Lobster #3: Advisor Agent     │
  │  Lobster #4: Main Agent        │
  └────────────────────────────────┘

To run the "2-3 sessions simultaneously" part on Windows, see how to set up WSL2 + tmux to run several Claude Code sessions in parallel.

Weekly Schedule

Day Primary Product Why
Mon UltraLab Most energy on Monday → most important product
Tue Ultra Advisor Clients typically respond on Tuesdays
Wed MindThread Adjust content strategy, review weekly data
Thu UltraLab Double-hit the main site
Fri UltraTrader Market closes, review weekly simulation data
Sat-Sun Flex Blog / open source / new features

The key: don't touch all 5 products every day. Focus on one. The rest run on lobster autopilot. Intervene only when something breaks.


How Each Day Starts

5 Minutes: TG Notification Triage

Open Telegram → check @Ultra_Agentbot notifications

🟢 Normal (ignore):
  - "Probe Agent: scan complete 20/20"
  - "MindThread: published 3 posts"
  - "Discord: +2 new members"

🟡 Needs attention (handle later):
  - "Advisor: new inquiry form submitted"
  - "Newsletter: 3 bounces"

🔴 Handle immediately:
  - "Gateway: memory > 1800MB"
  - "Probe Agent: Gemini 429 rate limit"
  - "Build failed on Vercel"

5 minutes to triage. Decision made.

If There's a Red Alert

Fix it via TG Plugin:

Phone TG: "Restart the OpenClaw gateway"
Claude Code: systemctl restart openclaw-gateway → reports normal

2 minutes. Done. Go back to the day's primary product.

If Everything's Green

Great. Open today's primary product, launch Claude Code session, deep work.


Claude Code as a Multiplier

Managing 5 products alone is possible because Claude Code doesn't need onboarding.

Traditional company, new hire:

Week 1: Learn the codebase
Week 2: Small tasks
Week 3: Start being productive
Week 4: Work independently

Claude Code + CLAUDE.md:

Second 1: Read CLAUDE.md, full context acquired
Second 2: Start working

Every product has its own CLAUDE.md documenting:

  • Tech stack
  • File structure
  • Style conventions
  • Known pitfalls
  • Deploy workflow

When I switch from UltraLab to Ultra Advisor, I don't spend 30 minutes "getting into the zone." Claude Code reads the CLAUDE.md and instantly enters that product's context.

CLAUDE.md is my coordinator protocol. I don't need to memorize 5 products' details. I just keep each CLAUDE.md current.


Tech Stack Overlap Strategy

5 products on 5 different tech stacks would kill me. So I deliberately share the core:

Shared layer:
├── React 18 + TypeScript    → UltraLab, Advisor, MindThread(frontend)
├── Vite                     → All frontend projects
├── Tailwind CSS v4          → All frontend projects
├── Firebase Firestore       → UltraLab, Advisor, MindThread
├── Vercel                   → UltraLab, Advisor
├── Resend (Email)           → All products that send email
└── Lucide React (Icons)     → All frontends

Independent layer:
├── Python + Shioaji          → UltraTrader only
├── Ollama + systemd          → OpenClaw only
└── Playwright + FFmpeg       → MindThread short video only

80% shared, 20% independent. A Tailwind trick I learn in UltraLab works in Advisor. A Vercel pitfall I hit in UltraLab won't hit me again in Advisor.


What's Automated vs. What's Not

Fully Automated (Lobsters)

Task Frequency How
Threads posting 10x/day MindThread + Ollama
Discord welcomes Every 3 min discord-intro-responder
SEO scanning Daily UltraProbe batch scan
Cold email 3 rounds/day prospect-engine
Content splitting Daily content-cascade
Fleet monitoring Every 5 min fleet-status.sh
SSL certificate check Daily ssl-check.sh

Semi-Automated (I trigger, Claude executes)

Task Frequency How
Blog writing 2-3/week I pick topic, Claude Code writes + builds + deploys
Feature development Daily I describe need, Claude Code implements
Bug fixes As needed Lobster alerts → TG Plugin → Claude Code fixes
Deploys Multiple/day git push + vercel --prod

Fully Manual (Only I can do)

Task Frequency Why
Product direction Weekly Requires business judgment
Client meetings 2-3x/week Requires human interaction
Pricing strategy Monthly Requires market intuition
Content review 5 min/day Quality gate

Ratio: roughly 70% auto, 20% semi-auto, 10% manual.


Monitoring: One Screen for All Products

I don't look at 5 dashboards. I look at 1 Telegram conversation.

@Ultra_Agentbot past 24 hours:

🦞 [Probe] Scan complete 20/20, 3 emails sent
🧵 [MindThread] Published 8 posts, reach +12K
💰 [Advisor] New inquiry: Mr. Chang, insurance planning
📊 [UltraTrader] Simulation: +0.3%, 2 positions
🖥️ [Fleet] CPU 12%, MEM 1.2GB, 34 timers active

If everything's normal → I don't open any dashboard. If something's wrong → TG buzzes, I deal with it.

The highest form of monitoring is not needing to look at it. It comes to you when it has something to say.


The Honest Cost

What Breaks

  1. Context switching tax: Even with CLAUDE.md, switching from Python (UltraTrader) to TypeScript (UltraLab) takes mental adjustment. Solution: one product per day.

  2. Lobster quality ceiling: Ollama 7B social posts are maybe 60% the quality of Claude Opus. But 10 posts at 70/100 get more reach than 1 post at 95/100.

  3. Tech debt accumulates: 5 products' tech debt adds up fast. Strategy: spend 2 hours every Saturday cleaning up the worst offender.

  4. No redundancy: If I get sick, everything except lobster auto-tasks stops. No backup. This is a structural risk of being solo.

What I've Sacrificed

  • ❌ Perfectionism: 80/100 is good enough for each product
  • ❌ Manual community management: lobsters handle it all, I pop into Discord occasionally
  • ❌ Detailed spec documents: CLAUDE.md + verbal description is enough
  • ❌ Long-term planning: anything beyond 90 days is meaningless, market moves too fast

Why Not Do Fewer Things?

The most common question: "Why not just focus on one product?"

Because these 5 products feed each other:

UltraProbe scans       → generate prospect data
                       → feed cold email pipeline
                       → convert to UltraGrowth clients

MindThread posts       → drive brand awareness
                       → bring traffic to UltraLab
                       → some convert to Advisor clients

OpenClaw automation    → reduces ops cost across all products
                       → is itself an open-source project that earns stars

Ultra Advisor clients  → word of mouth in financial advisor circles
                       → cross-sell UltraLab services

UltraTrader            → future passive income engine

Cut any one, and the others lose efficiency. These aren't 5 independent products. They're an ecosystem.


Can You Replicate This System?

Yes. But you need:

  1. A good CLAUDE.md: I open-sourced a starter template. Take it.
  2. Automated notifications: doesn't need to be as complex as lobsters. A Telegram bot + a few cron jobs is enough.
  3. Overlapping tech stacks: 5 products on 5 stacks is suicide. Share as much as possible.
  4. One product per day: don't try to touch everything daily.
  5. 80/100 mindset: perfection is the enemy of throughput.

If you're also running multiple products solo, join our Discord. About 400 people in there as of 2026-09-27, keeping each other sane.


Need Help Managing Yours?

If you have a product but no time for SEO and social distribution, UltraGrowth is the software we built to automate exactly this.

AI handles your online presence. Setup NT$19,800, from NT$6,800/month.

You focus on your product. AI does the rest. Just like I do.


"Running 5 products alone isn't about being hardworking. It's about being lazy enough to build a system that works without you."

FAQ

How can one person manage multiple products at the same time?

Don't touch every product every day; focus on one. Plan which product gets which day of the week, and keep the daily rules fixed: spend 5 minutes on Telegram notifications, fix anything that is broken, otherwise work on the day's primary product, and let automation run the rest, stepping in only when something breaks. That removes the morning decision of what to do first.

What do you need to run several products as a one-person company?

Five things: a good CLAUDE.md for each product; an automated notification system, where a Telegram bot plus a few cron jobs is enough; overlapping tech stacks; one product per day; and an 80/100 mindset, where 80/100 is good enough for each product instead of chasing 95/100.

What should a CLAUDE.md file include?

Keep one per product, documenting the tech stack, where the code lives, style conventions, known pitfalls and the deploy workflow. Claude Code reads it and enters that product's context, so switching from one product to another no longer costs 30 minutes of getting into the zone.

How should a solo founder choose tech stacks across multiple products?

Share the core as much as possible. In this setup the frontends share React, TypeScript, Vite and Tailwind CSS, and the database is Firebase Firestore, for roughly 80% shared and 20% independent. A trick learned or a pitfall hit in one product carries over to the next; 5 products on 5 different stacks is more than one person can handle.

What are the costs of running multiple products alone?

They include the mental cost of switching (even with CLAUDE.md, moving from Python to TypeScript takes adjustment), tech debt that accumulates across products, and no redundancy: if you get sick, everything except the automated tasks stops, which is a structural risk of being solo. The countermeasures are one product per day and 2 hours every Saturday cleaning up the worst tech debt.

Weekly AI Automation Playbook

No fluff — just templates, SOPs, and technical breakdowns you can use right away.

Join the Solo Lab Community

Free resource packs, daily build logs, and AI agents you can talk to. A community for solo devs who build with AI.

Want to try it yourself?

UltraProbe is free and needs no sign-up. One scan tells you whether Google and AI engines can find your site.