A software company that runs itself.

Software Factory is a whole software team — product, engineering, QA, support and research — built on Claude agents. It watches how people use your product, notices what gets in their way, decides what to build, ships it and checks whether it worked. Then it starts again.

Sheet 01 — The loopPre-launch · in development
Example · 01 Observe

01 — The loop

Six stations. One line. It never stops moving.

Most tools help one person do one job faster. Software Factory runs the whole cycle a software company runs — and every turn of the loop leaves it knowing your product a little better.

01 · Research, support

Observe

Reads product analytics, session behavior, production logs, the support inbox and what competitors ship.

02 · Product

Decide

Weighs every signal against your goals, picks what matters most and writes a short, reviewable spec.

03 · Engineering

Build

Writes the change in your codebase, in your conventions, with tests written alongside it.

04 · QA, release

Ship

Runs the real flows end to end and opens a pull request with the reasoning attached. You approve.

05 · Analytics

Measure

Watches what actually happens after release. Did the drop-off close? Did errors fall? Did anyone complain?

06 · Company brain

Learn

Writes down what worked, what didn't and why — so the next decision starts from evidence, not from zero.

02 — What it watches

Everything your users are already telling you.

Your product produces a constant stream of evidence about what to do next. Most of it goes unread. Software Factory reads all of it. Each case below is a working machine — press, drag and watch it do the job.

SF-01 · Fig 1

Customer behavior

Notices
Where people hesitate, rage-click, backtrack or quietly leave.
Does
Finds the bottleneck, fixes it, and watches throughput recover.
SF-02 · Fig 2

Anomalies

Notices
A conversion dip, a latency creep, a flow that suddenly behaves differently.
Does
Flags it the moment it leaves its normal range, then traces the cause.
SF-03 · Fig 3

Production logs

Notices
Thousands of error lines that are really a handful of causes.
Does
Groups them by signature, fixes the biggest at the root, and the group goes quiet.
SF-04 · Fig 4

Support inbox

Notices
The same problem described five different ways by five customers.
Does
Answers what it can. When a pile forms, it becomes a fix — and the tickets stop.
SF-05 · Fig 5

Feature requests

Notices
What users ask for, what their behavior says they need, and what it is worth.
Does
Weighs the evidence against the cost of building it, and builds when it tips.
SF-06 · Fig 6

Competitors

Notices
Launches, pricing changes and changelogs across your market.
Does
Tells you which moves matter and what to answer with.
03 — Company brain

One memory, shared by every role.

The product agent knows what support heard yesterday. The engineer knows why that module was written the way it was. Nothing gets lost between teams, because there is only one place to remember it.

Files in
  • Code & commits in
  • Specs & decisions in
  • Customer behavior in
  • Support threads in
  • Market & competitors in
Read by
  • Product out
  • Engineering out
  • QA out
  • Support out
  • Research out
04 — Ground rules

Autonomous, not unsupervised.

You set the direction. The Factory does the work and shows it.

R1
Every change is a pull request.

With the signal that prompted it, the reasoning and the tests. Nothing ships that you haven't seen — unless you decide it can.

R2
You draw the boundaries.

Choose which repos, data sources and kinds of change it may touch. Widen them as trust is earned.

R3
Every decision has a paper trail.

Why this, why now, what else was considered. Readable by anyone on your team.

R4
Built on Claude.

Each role is a Claude agent with its own job, tools and limits, working from the same shared memory.

05 — Where we are

We're building it now.

No launch date yet, and no customer logos to show you. We're looking for a few teams with a live product who want to run the first version of the Factory with us and shape what it becomes.