How to build an app with AI without knowing how to code

I'm 50. I spent two decades in finance, then started a construction supply business. I had never written a line of code. In the last year I've built and shipped nine working applications using AI, and every single one of them followed roughly the seven steps below. This is the guide I wish someone had handed me on day one — no jargon, no pretending it's easy, no pretending it's hard either.

The seven steps

1. 01

   Pick a problem you already understand

   Your advantage over a 22-year-old engineer is not technical — it is that you know a real business, a real hobby, a real annoyance. Write the problem in one sentence: "Contractors miss bid invitations buried in their inbox." If you cannot write that sentence, you are not ready to open a builder yet.

2. 02

   Choose one AI builder and stay there

   There are several good AI app builders. The specific one matters far less than sticking with it for thirty days. Tool-hopping feels like progress and is actually the most expensive form of procrastination. Pick the one whose interface does not intimidate you and commit.

3. 03

   Write a first prompt that describes the outcome, not the code

   Bad first prompt: "Build a React app with a Postgres backend." Good first prompt: "Build a single page where a contractor can paste an email, and it saves the project name, the due date, and who sent it, then lists everything saved with the soonest due date first." Describe what a user does and what they see. The AI handles the rest.

4. 04

   Click every single thing before you believe it

   The single habit that separates people who ship from people who quit: verify manually. Add a record. Refresh the page. Open it on your phone. Try to break it. AI will tell you a feature is finished when it renders — not when it works. Your job title is tester.

5. 05

   Fix one thing at a time, in plain English

   When something breaks, resist the urge to describe five problems at once. Say exactly one: "When I click Save with an empty date, nothing happens and no error appears. It should show a message telling me the date is required." Symptom, expected behavior, one change. Batching bug reports is how you end up with new bugs.

6. 06

   Add accounts and a database only when you need them

   The moment more than one person uses your app, you need logins and a real database with permissions so people cannot see each other's data. Ask for that explicitly — AI will happily build an app where every user can read every row unless you say otherwise. This is the one place to be paranoid.

7. 07

   Ship it embarrassingly early

   Put it in front of one real person before it is ready. Not on social media — one person, by name, who has the problem. Their five minutes of confusion will teach you more than another week of polishing. Every app I finished was shown to someone while it still looked bad.

What actually goes wrong (and what it costs you)

Nobody warns you about the middle. The first afternoon is euphoric — you type a sentence and software appears. Week three is where people quit. Something that worked yesterday breaks today, you can't explain why, and the AI keeps confidently making it worse. That's not a sign you're too old or too non-technical. It's the normal shape of the work, and it happens to engineers too. The fix is boring: smaller changes, one at a time, and testing everything yourself.

I've written the unglamorous version of all of this in the Field Notes — including the late-night doubt, the cost surprises, and the projects I abandoned. If you want the day-by-day version of a real build instead, the journal has it, project by project.

Common questions about building apps with AI

Where to go next

If the term itself is still fuzzy, read what vibe coding actually is. If you're ready to open a builder tonight, the Prompt Pack gives you ten free prompts to start with — the exact wording that has worked for me. And if you'd rather someone just built the thing, I take on a few projects a quarter.