Lesson 001Field guide · Build With AI
Turning Ideas into Tools
Recognize when an idea is really a small tool waiting to be built.
You'll learn
- The signal that an idea is really a small tool: a task you keep repeating by hand
- The difference between a workflow you run and a tool that runs
- What right-sized first projects look like — and what's honestly out of reach
- How to scope an idea down until it's actually buildable
01Section
The signal: a task you keep repeating
Tool ideas rarely arrive as "I should build an app." They arrive as a small groan: ugh, this again. You reformat the same list every Monday. You recalculate the same quote for every customer. You copy numbers from one place to another and total them by hand — again.
That groan is the most reliable signal in this entire path. A task you do the same way, over and over, with the same steps each time, is a tool waiting to be built. You already know exactly what it should do, because you've been doing it yourself.
What the signal looks like in real life
Every Friday, Sam copies hours from a notes app, adds them up on a phone calculator, formats the total into the same message template, and sends it. Four steps, ten minutes, every single week. Nothing about it ever changes — which is exactly the point.
Key takeaway
If you've done the same small task the same way three times, you're probably looking at a tool.
Checkpoint
02Section
A workflow you run vs. a tool that runs
Before you build anything, it's worth knowing which kind of thing you're looking at. Some repeated tasks are workflows: a series of steps you perform, maybe with AI helping at each one. Others are tool-shaped: the steps never change, so a small piece of software could do the whole thing.
Plain-language definition
Tool — a small piece of software that does one job on its own: you give it input, it gives you output, and it works the same way every time — without you re-doing the steps.
A workflow you run
Every Friday: open notes, find this week's hours, ask an AI assistant to total and format them, paste the result into the message template, adjust, send.
A tool that runs
Every Friday: paste the week's hours into a small page you built once. It totals them and produces the finished message. You copy it and send.
Same job. The workflow needs you at every step; the tool needs you at the start and the end.
Workflows are a skill of their own — turning one-off prompts into repeatable processes is what the AI Workflows path teaches. This path is about the other case: when the steps are so fixed that they can become a thing.
Checkpoint
03Section
What a right-sized first project looks like
Here's the honest part. With AI assistance, non-developers really can build small working tools — that's new, and it's real. But small tools are not the same as production software, and a first project has a natural size. These four shapes fit it:
Checklist generator
Answer two or three questions, get a ready-to-use checklist — packing lists, event prep, opening and closing routines.
Calculator
A few inputs, one useful number out: a price quote, a recipe scaled up, a cost split between friends.
Formatter
Messy text in, clean text out: notes into a tidy list, a data dump into a readable table, a draft into your standard template.
Single-page utility
One page that does one job — a countdown, a unit converter, a random picker, a simple tracker.
Anything with user accounts, payments, or other people's private data is not a first project — no matter how helpful AI is. Those need experienced review, because getting them wrong affects people other than you. That's not a scare line; it's just where the line is.
Checkpoint
04Section
Scoping down is the skill
The number one reason first projects die isn't lack of coding ability — AI covers a lot of that. It's size. The idea starts as "a quote calculator" and grows into "a quote calculator with saved customers and email and a dashboard" before anything exists at all.
Scoping down means shrinking the idea until version one is almost embarrassingly small — and then building that. Small enough to finish is the feature that matters most.
Name the one job: Finish the sentence: "This tool takes ___ and gives me ___." If you need two sentences, you have two tools — pick one.
Cut every "and": "Calculates the quote and saves customers and sends it" — version one is the part before the first "and."
Serve one person: you: No settings, no options for other people's preferences. It works exactly the way you work.
Ask what version one can skip: Almost everything. Anything you could do by hand in ten seconds afterward doesn't need building yet.
Key takeaway
Version one does one thing, for one person: you. Everything else is version two — if it ever earns its place.
Pause and think: What did you do by hand this week — for the third time or more — that a tiny tool could have done?
Checkpoint
Prompt exercise
Find your tool-shaped task
Copy this prompt into ChatGPT, Claude, Gemini, Copilot, or whichever AI tool you have access to — the website doesn't run AI itself. It will help you find the most tool-shaped task in your week and scope it down to a buildable version one.
I'm learning to spot small tools worth building. Ask me one question at a time to uncover tasks I repeat regularly — at work, at home, or in a hobby. After a few questions, list the tasks you heard, tell me which ones are tool-shaped (same steps every time, clear input and output, no judgment calls in the middle) and which are better left as workflows. Then help me pick the single most tool-shaped one and scope it down to a version one I could realistically build: one input, one output, no extras. Finish by stating it in this exact form: "This tool takes ___ and gives me ___."
Reflection: Look at your final sentence. Is there an "and" hiding in it? If so, cut it — that's the scoping skill working.
Quick check
3 quick questions — no pressure
There's no pass or fail here. Answer them all, and we'll show you the answers either way.