Systems Are Systems · a step-by-step build guide by Michael Kapin

Build the app
you wish existed.

A step-by-step book for anyone who has ever said "there should be an app for this" and had no idea where to start.

You bring the problem. This book hands you the exact steps to build the tool yourself, with real copy-and-paste prompts that get you building in the first chapter. No masterclass. No coding course. No computer science degree. Just real-world tools, built by you, this weekend.

Buy the Book See what's inside $19 founder price $29

Read this first

Who this is for. Who it is not.

This is for you if

You work with your hands and you think in systems already.
You run a small trade business and you are tired of doing the same paperwork twice.
You read an article, thought "I want to build that," then hit a wall on the how.
You are smart and practical but you are not a programmer, and you do not plan to become one.
You want one small tool that fixes one real problem, not a startup.

This is not for you if

You want a course on becoming a software engineer.
You are chasing a SaaS exit or a pitch deck.
You want hype about robots taking every job.
You already ship production code for a living.
You want someone to build it for you instead of showing you how.

The contents

What's inside

Six parts. The story earns the trust, the method shows you how, and the toolkit gets you building. Around 150 pages, no filler, plus real working files you download and keep.

The Story

Electronics, the auto industry, eleven years running my own heating and cooling shop, into teaching, then the day AI collapsed the gap between an idea and a working tool. Why I stopped accepting "normal" and started building my own answers.

The Mindset

The unlocks. A furnace, a course, and a piece of code are the same system. Build small. Fix the bottleneck before you automate. AI is leverage, not a replacement for the people who hold the context.

The Method

The repeatable pipeline. Notice the annoyance, describe it plainly, ask the machine to build it, use it, fix what's wrong, ship it. Your stack, how to talk to the machine, and how to iterate like you are fixing a furnace.

Worked Examples

Real tools I built, taken apart so you can copy the pattern. A quoting tool for small contractor work. A health tracker. A meeting recorder that turns talk into notes. A two-household scheduling calendar. Each one ends with "your version."

Do It

A guided weekend project you actually finish. By Sunday you have a small tool that solves one annoyance, running on your own machine, built by you. Plus cheat sheets and a plain-language glossary.

The Toolkit

The hands-on part. A prompting playbook packed with copy-and-paste prompts, a plain-English guide to which AI tools to use for what (Claude, ChatGPT, Gamma and more), and four step-by-step tutorials you follow start to finish. Plus real working files you download with the book: a jobsite maintenance checklist, printable templates, and a job estimator you can use on Monday.

Who is writing this

About Mike

I am a guy in Ontario with a day job and a habit of building things. I spent over twenty years in heating and cooling. Before that, electronics, then about a decade in the auto industry. I ran my own heating and cooling business for eleven years. The job was simple to describe: you fix the furnace, and the job is done when the house is warm.

I started teaching in 2017 and was coordinating the program by 2020. Around 2023, AI got good enough that the distance between "I have an idea for a tool" and "I have the tool" almost disappeared. So I started building. No computer science degree. I learned by making real tools that I needed, not toy projects, and I put the ones that worked where other people could find them.

This book is the part the articles leave out. The articles make you nod. This one shows you exactly how I do it, step by step, with nothing held back.

20+

Years in the trade

Years running my shop

2017

Teaching since

2023

Building since

The payoff

What you'll walk away with

A method you can repeat. Notice, describe, ask, use, fix, ship. The same loop every time.
A working tool you built yourself. Not a tutorial you watched. A thing you can open and use on Monday.
A way to spot the real bottleneck. So you automate the step that matters and leave the rest alone.
A simple stack that fits a non-coder. What each piece is for, what it costs, and what to skip.
The language to talk to the machine. How to describe a tool so the AI builds the right thing.
The honesty to know when it's done. Fix the furnace, then move on. No shipping for the sake of shipping.
Copy-and-paste prompts that work. Not theory. The actual prompts to paste in and adapt to your own job, so you are building in minutes, not reading for a month.
Real working files, included. A jobsite maintenance checklist, printable templates, and a job estimator you can use the day you download the book.

Straight answers

Questions

Do I need to know how to code?

No. That is the whole point. This book is written for a sharp apprentice, not a developer. You describe the tool in plain words and the machine writes the code. I show you how to describe it well, how to check the result, and how to fix it when it breaks. There are copy-and-paste prompts so you are not staring at a blank box wondering what to type.

What do I actually need to start?

A computer, an internet connection, and an AI assistant account. There is a chapter on the stack that lays out every tool, what it is for, roughly what it costs, and what you can skip. Most of it is cheap or free to start.

How long is it, and how long until I build something?

Six parts, around 150 pages, no filler. Part five is a guided weekend build, and part six is a toolkit of step-by-step tutorials with copy-and-paste prompts plus real working files you download with the book. Sit down on a Saturday and you can have a working tool by Sunday.

Will this go out of date when the AI tools change?

The method is built to outlast the tools. Tool names change. The loop of noticing a problem, describing it, building, fixing, and shipping does not. I keep the specifics tool-agnostic so the thinking still holds when the brand on the button is different.

Is this a get-rich course or a startup pitch?

No. I build small, single-purpose tools that solve exactly one problem for one person. Not platforms, not SaaS, not a hustle. If you want to build something bigger later, the foundation transfers. But this guide is about craft, not a sales funnel.

What's the founder price about?

The book is $29. Early readers get it for $19 while the founder price lasts. Same book, lower number, because the first people in get the better deal.

Get the book

Stop nodding. Start building.

You already think in systems. You fix things for a living. This book hands you the steps, the prompts, and the working files to turn that same brain on the annoyances that AI can finally solve. Buy it, open it, build something this weekend.

Buy the Book

$19 founder price (regular $29). Instant download from mikekapin.com.

Build the appyou wish existed.