The prototype is live. Customers can sign in. Records are accumulating. A payment integration works on the happy path. The founder now needs someone else to maintain it—and nobody can say exactly which branch reached production, which services hold the data, whether backups restore, where the secrets live, or what will break during the next change.The Vibe Code Cleanup Business begins at that transition. It is not another guide to generating an app from prompts. It is a practical o...

An AI answer can be ignored. An AI tool call can change the customer record, send the message, issue the refund, expose the file, or touch production before anyone understands what happened.This manual begins with that external side effect. It does not assume an autonomous workforce, an enterprise governance committee, or a security team. One small-business workflow and one risky verb are enough.The book shows how to inventory actions instead of broad tools; separate user i...

The documentation exists, but nobody uses it. The passwords are stored, but the backup does not know which account matters. A coworker has watched the job, but the usual person still answers every question on vacation. A year-end task, supplier problem, customer exception, or recovery sequence remains "all in her head."No One Else Knows How treats those conditions as operating dependencies, not personality defects and not a reason to document everything.The method starts wi...

If customers are waiting, staff are busy, urgent requests keep replacing older work, and the owner still cannot say how much accepted work remains, the operation needs a reliable record of what it has promised and what it can actually finish.The Queue Is the Business is a practical guide for small service businesses, solo operators, repair shops, agencies, appointment businesses, and support teams. It begins at the point where an inquiry becomes an accepted obligation. From there, ...

A meeting ends. A chat says "approved." An AI summary says a decision was made. Months later, nobody can tell whether the conclusion was a recommendation, an authorized answer, or simply the last thing someone said.The Decision Log teaches the record that should exist between discussion and action. It isn't a meeting-notes system, and it doesn't assume that a complete form makes a choice correct. It shows how to preserve an authorized answer in a form that another person can inspec...

You know how to do the work. The trouble is keeping every open promise visible when a request starts in email, a deadline lands on a calendar, approval arrives by text, an invoice sits in a folder, and payment appears in another app.Track What Is Still Open shows how to gather that scattered work into a small back office you can inspect, maintain, export, and recover. The method starts with one case register. Each open job gets a stable ID, source, current state, next action, date,...

The official procedure is only one record of the work.The real process may also depend on a private spreadsheet, an email thread, an unwritten approval, a worker who recognizes difficult cases, or a repair step performed after the system says the job is complete. When these parts remain hidden, a new procedure, process map, software system, or AI workflow can formalize the wrong version of the work.Workflow Archaeology is a practical field manual for finding what actually h...

You do not need an app yet. You need a customer, a defined result, and enough paid work to reveal what the app must actually do.Most founders build the interface first and discover the operation later. They encode guessed inputs, guessed rules, and guessed workflows, then spend months patching the cases they never saw coming.The Manual-First Startup gives you a stricter path. Sell one narrow result. Deliver it manually. Record every input, action, decision, delay, ...

Companies already pay people to copy data, chase missing information, update spreadsheets, prepare invoices, route requests, rename files, check documents, and send the same follow-ups every week.That work is usually too small for a major software project. It is also too expensive to ignore.The Boring Automation Business shows you how to find repetitive office work, calculate what it costs, build a reliable fix, and sell the implementation to a small business.You wi...

You do not need a million users. You need enough of the right customers at a price that covers every obligation your software creates.A working product is only the beginning. Small Software, Real Money shows how to turn a narrow software tool into a controlled, durable business designed for hundreds of customers rather than millions.Work backward from the income you need. Set a customer ceiling. Calculate contribution by plan. Price support, hosting, payment fees, AI usage,...

A month is enough time to become attached to a bad business idea.You can buy a domain, design a logo, build features, write a business plan, create social accounts, and prepare a launch without learning whether a customer will take action. Visible work makes the idea feel real. It does not prove that anyone will pay for the result.The One-Weekend Business Test reverses that order.This book gives you a complete Friday-to-Sunday protocol for turning an idea into a cha...

Most AI products begin with a chatbot because chatbots are easy to demonstrate. The user types a request, the model produces an answer, and the real work remains unfinished.The Useful AI Product presents a different method. Start with a repeated task. Study how people currently perform it. Identify the records, decisions, rules, exceptions, permissions, and handoffs involved. Then build the smallest system that produces a result people can actually use.This book explains ho...