Start Here
How this workbook works (and how to pace yourself).
Who This Workbook Is For
This workbook is for people who have ideas for apps, tools, or websites but have never built one because they assumed it required skills they don't have.
Specifically, it's for:
- People who have said "I wish there was an app that..." more than once
- People who have Googled "how to build an app" and immediately closed the tab
- People who think "technical" means "not me"
- People who have ideas but no idea where to start
- People who tried a coding tutorial once, got stuck on lesson 3, and quit
- People who assume building software requires a computer science degree
If you're neurodivergent: This workbook was designed with you in mind. Every module has clear "done when" criteria so you know when to stop. Spoon ratings help you plan your energy. There are brain-dump boxes instead of perfect-answer blanks. You\'re allowed to skip around, take breaks, and do things out of order. The goal is progress, not performance.
You do not need:
- Any coding experience
- A computer science background
- To understand how the internet works
- To be "good at computers"
- To have built anything before
Who This Workbook Is NOT For
To be clear about what this is and isn't:
This is NOT a coding course. You won\'t learn to code. You\'ll learn to communicate with an AI that codes. Those are different skills. If you want to become a developer, this isn't that. If you want to build things without becoming a developer, keep reading.
This is NOT for complex enterprise software. You can build surprisingly sophisticated things with this approach, but if you need HIPAA compliance, financial trading systems, or apps that serve millions of users simultaneously, you need actual developers. This is for MVPs, internal tools, personal projects, and small business solutions.
This is NOT magic. It still requires effort. You still have to think clearly about what you want. You still have to iterate when things aren\'t right. The AI does the coding, but you do the thinking and the decision-making. That\'s the work.
The honest truth: Building with AI is easier than learning to code, but it's not effortless. The difference is: with coding, you spend years learning before you can build. With AI, you can build on day one and learn as you go. Same destination, different path. This workbook is the map for that second path.
What You'll Actually Build
By the end of this workbook, you will have:
1. A working app on the internet
Not a mockup. Not a prototype in someone's preview window. A real thing with a real URL that real people can visit and use.
2. The ability to build more
The first app teaches you the process. After that, you can repeat it for any idea. Different app, same workflow.
3. Confidence that you can figure it out
When things break - and they will - you\'ll know how to troubleshoot. When you get stuck, you\'ll know what to ask. That's the real skill.
Examples of what people build: A booking form for a small business. A tracker for personal goals. A calculator for industry-specific math. A simple game. A portfolio website. A tool that automates a repetitive task. A dashboard that displays data. An internal tool for a team. If you can describe it clearly, you can probably build it.
How This Workbook Works
Six modules. Each one builds on the last.
| Module | Name | What You'll Do |
|---|---|---|
| 1 | The Blueprint | Define what you want to build |
| 2 | Your First Conversation | Talk to Claude and see something built |
| 3 | WTF Is Happening | Learn 15 words to understand Claude |
| 4 | The Feedback Loop | Test, give feedback, iterate |
| 5 | Making It Real | Deploy to the actual internet |
| 6 | Now What? | Maintain, improve, build more |
Do them in order (mostly): The modules build on each other. Module 1 creates the blueprint you\'ll use in Module 2. Module 2 creates the artifact you\'ll learn about in Module 3. And so on. That said, Module 3 (vocabulary) can be read anytime you feel lost. And you can always skip ahead to peek at what's coming.
Understanding the Spoons System
Every module has a "spoons" rating. This tells you how much energy and focus it requires.
| Rating | What It Means |
|---|---|
| Low | Reading and light thinking. Can do when tired. No accounts to create, nothing to install, minimal decisions. |
| Medium | Active thinking and some doing. Requires focus. Might create an account or make choices. Best when you have 30-60 uninterrupted minutes. |
| High | Setup, installation, new tools, troubleshooting. Requires patience and problem-solving. Block off dedicated time. Have coffee. |
The "DONE WHEN" at the top of each module tells you exactly when you can stop. Not "when it\'s perfect." When it\'s done. There's a difference.
Permission to stop: If a module says "done when you have a written blueprint" and you have a written blueprint, you're done. You can stop. You don\'t have to revise it 47 times. You don't have to make it perfect. Done is done. Move on. You can always come back.
Check the spoons rating before you start a module. If you're exhausted and the module is HIGH, save it for another day. This isn\'t about pushing through. It's about working with your brain, not against it.
Before You Start: Quick Checklist
Make sure you have these things ready:
Required:
- A computer (Mac or Windows, either works)
- Internet connection
- An email address you can access
- An idea for something you want to build (even a vague one)
Helpful but not required:
- A quiet place to focus
- 30-60 minute blocks of uninterrupted time
- Something to drink
- This workbook printed (or open on a second screen)
Not required:
- Coding experience
- Technical background
- Design skills
- Previous app-building experience
- Understanding of how AI works
- Confidence (you'll build it as you go)
About that idea: If you don\'t have a clear idea yet, that\'s okay. Module 1 will help you figure it out. If you have too many ideas, that\'s also okay. Module 1 will help you pick one. Either way, you're ready to start.
The Mindset That Makes This Work
A few things to internalize before you begin:
Iteration is the process, not a sign of failure. The first version will not be right. You\'ll give feedback, Claude will adjust, you\'ll give more feedback. This is how software gets built. Professionals do this. It's not because you explained it wrong.
Done beats perfect. Ship something that works. Learn from it. Improve it later. The graveyard of never-launched projects is full of things that were going to be "perfect someday." Don't add to it.
You\'re allowed to not understand everything. Claude will say things you don\'t understand. That\'s fine. You don\'t need to understand how the engine works to drive a car. You need to know enough to steer. This workbook teaches steering.
Starting over is sometimes faster than fixing. If you're 30 minutes into debugging something and getting nowhere, try a fresh conversation with a clearer prompt. Sometimes the fastest path forward is to restart with what you\'ve learned.
Your ideas are valid. That thing you want to build? It\'s not too simple. It\'s not too silly. It\'s not "not a real app." If it would be useful to you or someone else, it\'s worth building. Don't let imaginary gatekeepers stop you.
The real secret: The people who successfully build things aren\'t smarter or more technical. They\'re just willing to try, fail, adjust, and try again. That\'s it. That\'s the whole secret. Persistence beats talent when talent gives up.
Ready?
You have an idea.
You have a computer.
You have this workbook.
That's everything you need.
Your first step: Turn to Module 1: The Blueprint. You\'ll spend 20-30 minutes figuring out exactly what you want to build. By the end, you\'ll have a clear description you can hand to Claude. That\'s it. One module. One outcome. Let\'s go.
The only way to fail is to never start.