Turn a brainstorm into a shipped product.

Botman is the multiplayer software factory. Your team brainstorms together; assembly lines of AI agents execute — spec, architecture, code, tests, release — and handoffs disappear.

Runs in your VPC · works with the AI subscriptions you already pay for
Truly multiplayer

Product development, finally multiplayer.

Today the work lives in single-player tools: PMs spec alone in Claude or Notion, engineers run solo coding sessions, designers are somewhere else entirely — and nothing meets until a handoff.

Botman joins the brainstorm where your team already talks, then owns execution end to end. The knowledge transfer never has to happen — it's already in the build.

  • PMs, engineers, and designers in one shared context
  • A Slack thread becomes a spec — decisions land in the artifact
  • No handoffs, fewer hops: higher quality, faster turnaround
# product — Slack
A
Aarav 10:02
what if traders could export their PnL history as a shareable card?
S
Sumer 10:03
love it — needs time windows + sub-account support. @Botman take this one?
B
Botman 10:03
On it. Checked the board — it's new. Drafting the product spec now; open questions coming to #prd-review.
PR openedspecs/pnl-cards.md7 open questions →
Botman — pnl-cards · pipeline #12
Product spec Architecture Code 2 Tests
Reading hooks/use-pnl-history.ts
$ pnpm test pnl-cards
Editing components/pnl/share-card.tsx
Opening PR against preprod…
The factory floor

Assembly lines you can watch.

Every feature moves down a line — product spec, architecture, code, tests — agents executing, your team steering. Watch the work in real time, drop feedback mid-run, and ship each stage as a pull request the team reviews together.

  • Spec authors, architects, coders, reviewers, testers, correctors
  • Your ideas drive the line — agents do the execution
  • Live activity for every agent, not a black box
A real thought partner

Edge cases, found before they're expensive.

Humans miss edge cases — usually at the moment they're cheapest to fix. Botman pressure-tests your thinking during ideation, speccing, and planning, and it learns your product's ideal behaviour, getting sharper with every feature it ships.

  • Grounded in your actual codebase, not vibes
  • Open questions with proposed answers, not homework
  • Gets better at your product over time
#prd-review — open questions
B
Botman 10:06
Open questions before this ships:
1. Sub-accounts: pool them or per-account cards?
2. Empty window: hide the card or show “no trades”?
3. Should hidden-balance mode apply here?
A
Aarav 10:11
pooled by default, allow per-account. Good catch on #3 — yes, respect it.
B
Botman 10:11
Folded all three into the spec — PR updated. Merge to move to architecture.
Botman — board · what to build next
Ideas
Livestream embeds
Fees preview on order ticketqueued
Wallet analytics
PnL share cardsqueued
Up next
News tagging v2
Fees preview on order ticket
PnL share cards
A
Akshay Mon 9:00
what should we ship next sprint?
B
Botman Mon 9:00
Went through 214 support threads, usage data, and 38 feature requests. Two clear winners:
1 · Fees preview — 31 traders asked; fee confusion is the #1 churn driver. Small build.
2 · PnL share cards — organic sharing loop, reuses the chart endpoint. Low effort, high reach.
B
Queued both to Up next — say go and I'll start the lines.
Prioritisation

Know what to build next — with evidence.

Ask Botman what to ship next: its product agent weighs reach, impact, and effort for every candidate — from your user feedback, support threads, and usage data — and queues the winners on the board. You approve the order; the factory takes it from there.

  • Recommendations grounded in real feedback and usage, not vibes
  • Ranked queue → running assembly line in one click
  • Spend your time on strategy — delegate the implementation
The swarm

Agents with job titles.

Deploy and monitor a swarm across every function of product development — each one accountable to a stage, each stage accountable to you.

Botman — agents · 24 active
Product agentFees preview #109product specDrafting edge cases for partial fills…
Product agentReferral rewards #112product specResolving open questions with the team
Product agentNews tagging v2 #157product specFolding Slack decisions into the spec
DesignerPnL share cards #69designLaying out the share card states
CoderPnL share cards #69codeEditing components/pnl/share-card.tsx
ReviewerNews tagging v2 #157arch specVerifying the data flow
TesterLivestream embeds #6tests$ pnpm test embeds
CorrectorWallet analytics #70codeFolding review feedback into the PR
ArchitectSearch profiles #84arch specPR opened — awaiting review
9:41●●●
● 3 agents working
PnL share cardsin review
✓ Spec● Arch○ Code
A
Akshay 21:04
should the card render server-side or in the client?
● run #64 is updating the arch spec
B
Botman now
Server-side, off the existing chart endpoint — cards stay shareable as images. Data flow + code map added to the arch spec.
PR updatedarchitecture-specs #7
Makes sense — merging
On the go

The factory doesn't close when your laptop does.

Agents run in the cloud, not on your machine. Review a spec from your phone, answer an open question from Slack, approve a PR from the couch — the line keeps moving.

  • Cloud agents keep working around the clock
  • The full dashboard on mobile — monitor, steer, approve
  • Slack-native reviews, wherever your team already is
Your infrastructure

Your VPC. Your subscriptions. Your terms.

Runs in your VPC

Botman deploys on your own infrastructure. Your code, your data, and your agents never leave it.

No API bill shock

Plugs into the Claude Pro/Max or ChatGPT/Codex subscription you already pay for — plus OpenCode and any model you bring.

Frugal by design

Optimised for minimal token spend, so you can scale the factory aggressively while costs stay boring.

Built for the people who ship.

More time on strategy and taste. Less time on the conveyor belt.

CTOsProduct managersEngineersDesigners

See the factory run.

A 20-minute walkthrough: from a Slack message to a merged PR.