Ship Factory: build and maintain a lot of software with your agents

Build and maintain a large surface area of software with your agents. You build the systems that keep many apps, sites and tools shipping and running.

Ship Factory is about building and maintaining a large surface area of software.

You and your agents, building systems.

Shipping quickly used to be a competitive advantage that now is being democratized by AI. Building the first version of an app is the easy part today.

The hard part comes after. Every app, website, CLI and tool you ship needs updates, bug fixes, dependency upgrades and new features, for years. If we want to build a lot of software and keep all of it alive, I think we have to take more of a managerial role.

The question this program answers: How do I build and maintain a lot of software with my agents without becoming the bottleneck?

The first edition is planned for January 2027. Enrollment isn’t open yet. Join the waiting list and I’ll let you know the moment it opens.

Join the waiting list

What it is

One app is a project. Ten apps, a website, a few CLIs and some internal tools are a surface area, and you can’t keep all of that in your head or update it by hand.

So instead of working on each product, we start working on the system that builds and maintains them.

Treat your agents like employees. You set the direction and then empower them to help you get there.

Stop micro managing the agents. Review the result, not every line of code. Stop making every minor decision yourself. It’s a bad use of your time.

Focus on building systems. Setting directions. Keep experimenting and invest in what works.

Don’t software factories fail?

You have probably seen the stories. Agents left running unattended for a weekend, tens of thousands of lines of code, nothing worth keeping. The lights-off factory, where nobody reads the code and nobody sets the direction, does not work. I agree.

Those factories fail because someone left the room. Ship Factory is about being the person who stays in it. You set the direction, you decide what gets reviewed and how deep, and you own the result. The agents do the work. You stay in charge of what ships.

You and your agents

You don’t stop caring about the product or give up responsibility. Call it going from indie maker to indie manager.

You still choose the direction, set the standards, review the outcome, and make the decisions that matter. But you stop spending your time on work an agent can handle, and you build the systems that let agents do that work well across everything you run.

We’ll work on:

• Building systems that let agents build and maintain your software
• Keeping many apps, sites and tools updated, tested and running
• Setting direction, outcomes, constraints, and standards
• Empowering agents without micro managing every step
• Reviewing results instead of reviewing every line of code
• Running more experiments
• Reading the signal and investing in what works

This is also how you improve your product engineering and product judgment. You design better systems, make better decisions, and learn from more real outcomes.

Who it’s for

• Indie makers who already know how to build software
• Builders who have shipped more apps, sites and tools than they can maintain by hand
• Builders who want to create more without becoming the bottleneck
• People who spend too much time micro managing agents

What it is not

Ship Factory does not teach coding from zero or offer a tour of every AI tool.

It is not about producing more AI slop or removing yourself from the process. You remain responsible for the direction, the systems, the standards, and the result.

Get notified when enrollment opens

Drop your email below and I’ll let you know.