The Age of Building: AI Made It Possible for Everyone
Five years ago, building an app required a dev team and $50K. I built three this week by talking to my computer. This isn't hype — here's exactly what happened.
By Jonathan Lee

Five years ago, if I wanted to build an app, I’d need to hire someone. A developer, a designer, maybe a project manager. Six months. Fifty thousand dollars. Minimum.
This week I built three apps. By talking to my computer.
I’m a financial planner. I don’t know any programming languages. I wouldn’t know where to start if you asked me to write code from scratch. And yet — three working apps, live on the internet, in seven days.
This isn’t me bragging. This is me telling you: something has changed. And if you’re not paying attention, you’re going to miss it.
Quick Check: Who Is This For?
You’re not a programmer. You’re not planning to become one. But you’ve seen people building things with AI — apps, websites, tools — and part of you is thinking, “I wish I could do that.”
You can. I’m proof.
I’m a financial planner in Hong Kong. A year ago, I didn’t know what a terminal was. Now I build things with AI every day. If you want the full origin story, the Mac Mini post covers how I went from zero to my first AI assistant.
What I Actually Built This Week
I want to be specific here. Not “I played around with some AI tools.” Not “I experimented a bit.” Here’s what I actually made — and all of it is live right now, working, with real people using it:
A financial data tool for my insurance team. It goes to government websites, downloads price files for 19 different funds, reads the numbers, and shows how each fund moved today vs. yesterday. It also collects news articles about the market and figures out which articles are relevant to which funds — so my team can see everything in one place. 152 days of historical prices. 238 connections between news and funds. A dashboard where anyone on my team can check fund performance in seconds.
This blog — in two languages. The site you’re reading right now. Six pages. English and Traditional Chinese. A content system where I write a post and it shows up on the site. A newsletter that sends weekly. A free starter kit you can download. Social media content for Instagram, Twitter, and LinkedIn — all generated from the same blog post.
A writing assistant that learns my voice. I have a system that reads my daily work logs, picks out the interesting stories, and writes a first draft of a blog post — in my style. It knows I say “worth it” at the end. It knows I use “spoiler:” before a twist. It learned these things by watching how I edit its drafts.
I didn’t type any code. I described what I wanted, the AI wrote it, I tested it, we fixed what broke, and we kept going until it worked.
The Part Nobody Talks About
Here’s the thing everyone gets wrong about AI: it didn’t do this for me. It did this with me.
It was like having a really smart colleague who can type incredibly fast but needs you to make all the decisions.
I said “I need a tool that tracks fund prices.” The AI asked “where should the prices come from?” I said “the government website.” It tried. The website didn’t work because it loads too slowly for a computer to read. So I said “what about the Excel files they publish?” The AI figured out how to read those instead.
That back-and-forth happened hundreds of times. Something would break. I’d describe what went wrong — in plain English, not in code. The AI would suggest a fix. Sometimes the fix worked. Sometimes it made things worse. We’d try again.
Every problem still needed a person to notice it. Every decision still needed a person to make it. The AI just did the typing — really, really fast.
That’s not “AI replacing people.” That’s a new kind of builder. Someone who can’t code but can think, decide, and describe what they want clearly enough for AI to build it.
Why This Moment Is Actually Different
People have been saying “technology will change everything” for decades. Most of the time it’s hype. This time it’s different, and I can tell you exactly why.
The internet changed who could learn. Before the internet, if you wanted to know something, you needed access to a library or a university. The internet made knowledge free. Anyone could read anything.
But there’s a massive gap between knowing how something works and actually building it. You can read every tutorial on YouTube about building an app. You’re still not going to build one unless you learn to code — and that takes months or years.
AI closed that gap.
Now the barista who wants a stock-tracking app can describe what she wants and an AI will build it. The teacher who needs a custom grading system can have one by Friday. The financial planner who wants a fund comparison dashboard — that’s me — can ship it in a week.
You don’t need to learn code. You need to learn how to describe what you want. And honestly? Most people are already pretty good at that. They just didn’t have anyone listening.
Three Types of Things I’m Building
I had a realization this week. When you’re building with AI, you’re not just building one thing. You’re actually building in three layers:
Layer 1: Your tools. These are the systems that save you time. My writing assistant. My daily work log. My SEO checker. Nobody else uses these — they’re just for me. But they make everything else ten times faster.
Layer 2: Your content. Blog posts, Instagram carousels, newsletters. The stuff that reaches people. Here’s the interesting part: without Layer 1 (the tools), creating content is slow and exhausting. With them, I can go from a rough idea to a published blog post, three carousel designs, and a newsletter — in one sitting.
Layer 3: Your product. The things people actually use and pay for. The financial data tool for my insurance team. This blog. The future projects I haven’t started yet. This is where the value lives.
The beautiful thing? Each layer feeds the next. Better tools → faster content → bigger audience → more product ideas → need for better tools. It’s a cycle that keeps accelerating.
What This Means for You
If you’ve been thinking about building something with AI but you’re waiting for the “right time” — the right time was six months ago. The second best time is right now.
Here’s what you don’t need:
- A degree in computer science
- To understand technical jargon
- A specific type of credit card (though being outside the US makes things harder — I wrote about that)
- Anyone’s permission
Here’s what you do need:
- An idea. Even a half-baked one.
- A good AI to work with. (The quality of the AI matters more than anything else — I learned this the hard way when my AI lobster died.)
- Stubbornness. Because things will break, and your job is to not quit.
I started with a Mac Mini and zero knowledge. This week I shipped three production apps. Not because I’m special. Because the tools finally exist for people like me.
The take away:
- We are living in the age of building. The distance between “I have an idea” and “I have a working product” has never been shorter. For the first time, you don’t need to be technical to build real software.
- AI doesn’t replace the builder. It creates one. Every decision, every “this broke, what do we try next,” every pivot — that’s still you. AI handles the typing. You handle the thinking.
- Start messy. Ship broken. Fix it live. My fund dashboard went live five times in one day because I kept finding things to fix. That’s not failure — that’s how building works.
- Build the tools that build the tools. The writing assistant, the daily logs, the starter kit — they compound over time. Every system you create makes the next project faster. This is where the real advantage is.
I’m going to keep building. Keep putting broken things on the internet and fixing them in public. Keep writing about it so the next person starting from zero has a slightly easier path.
If you want to follow along, subscribe to the newsletter. One email a week. What I built, what broke, and what I learned. No hype.
The tools are here. The age of building is now.
What will you build?
Enjoyed this post?
Get new guides and tools delivered to your inbox every week.