What do you think?
Rate this book
Stop Working for Your Software: How a Shop Owner Discovered He Could Build His Own Software Using AI — and You Can Too
I bought four ERPs in four years. The first three taught me the same you don't buy business software, you hire a boss.
Every one of them arrived promising to fix the shop. Every one of them ended the same way — my people doing extra work to keep the software happy. Renaming things we'd called something else since the day we opened. Entering the order twice because the module that knows about art doesn't talk to the module that knows about garments. Keeping a spreadsheet on the side for the part nobody's software has ever handled.
None of that shows up on the invoice. It shows up in payroll.
The fourth system we built ourselves. Not with a development team. Not with a six-figure implementation. Not by stopping production for six months. A mature open platform underneath, AI writing the code, and the one thing no vendor could somebody who already knew how the work actually gets done.
Today I run a forty-person shop's ERP from my phone. Not a dashboard — the system itself. I ask what shipped, correct a record, describe a change in plain language and watch it get built.
This is the account of that build, and the method underneath it.
What's insideConfigure, Customize, Connect, Build — the ladder for deciding what to change, what to buy, what to wire together, and what is genuinely worth building yourself. Picking the wrong rung turns a two-hour fix into a two-month project.Working with AI as a builder instead of a chatbot — the rules, the context it needs, and where a human still belongs between it and your database.One real order followed from inbox to invoice, through every system it touches.The ten prompts I actually use, and a worksheet for your first project.The ROI ledger, the team, and the objections — including the one about jobs.Who this is forOwners, GMs and operations leads at companies specific enough that no generic system has a field for the thing that matters. Decoration, fabrication, field service, custom manufacturing. You don't need to write code. You need the authority to change a process, and enough knowledge of your own business to say how the software should work.
I am not a software developer, and I say so early and often. I own a custom apparel decorating shop outside Seattle. Everything in this book was written in the middle of running it, which is why it's short on theory and long on the decisions that cost me time.
Every one of them arrived promising to fix the shop. Every one of them ended the same way — my people doing extra work to keep the software happy. Renaming things we'd called something else since the day we opened. Entering the order twice because the module that knows about art doesn't talk to the module that knows about garments. Keeping a spreadsheet on the side for the part nobody's software has ever handled.
None of that shows up on the invoice. It shows up in payroll.
The fourth system we built ourselves. Not with a development team. Not with a six-figure implementation. Not by stopping production for six months. A mature open platform underneath, AI writing the code, and the one thing no vendor could somebody who already knew how the work actually gets done.
Today I run a forty-person shop's ERP from my phone. Not a dashboard — the system itself. I ask what shipped, correct a record, describe a change in plain language and watch it get built.
This is the account of that build, and the method underneath it.
What's insideConfigure, Customize, Connect, Build — the ladder for deciding what to change, what to buy, what to wire together, and what is genuinely worth building yourself. Picking the wrong rung turns a two-hour fix into a two-month project.Working with AI as a builder instead of a chatbot — the rules, the context it needs, and where a human still belongs between it and your database.One real order followed from inbox to invoice, through every system it touches.The ten prompts I actually use, and a worksheet for your first project.The ROI ledger, the team, and the objections — including the one about jobs.Who this is forOwners, GMs and operations leads at companies specific enough that no generic system has a field for the thing that matters. Decoration, fabrication, field service, custom manufacturing. You don't need to write code. You need the authority to change a process, and enough knowledge of your own business to say how the software should work.
I am not a software developer, and I say so early and often. I own a custom apparel decorating shop outside Seattle. Everything in this book was written in the middle of running it, which is why it's short on theory and long on the decisions that cost me time.
143 pages, Kindle Edition
Published September 13, 2026
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
No one has reviewed this book yet.