How I Built an AI Tool Without Knowing How to Code

You’re picturing a bootcamp, right. Weeks of tutorials, a computer science degree I don’t have, some moment where it finally “clicks” and I become a developer. That’s what I pictured too when I first thought about building an AI tool without knowing how to code, which is probably why I put this off for so long.

What actually happened was smaller and slower than that.

What the tool does

I built something that takes a company name and an industry, and gives back a market research summary and a set of strategy notes I can use before a work conversation. Nothing exotic. The kind of research I used to do by hand, opening a dozen tabs, reading through a company’s site and recent news, and writing up my own notes before ever talking to them.

Now I type in a name, wait a bit, and get a starting draft of that same research. Not a finished product. A draft that often gets me most of the way to where my own notes would have ended up, which turns out to be exactly the part that used to eat the most time.

What building it actually looked like

I didn’t start by learning a programming language. I started by writing down, in plain English, what I wanted the tool to do.

The first version was basically a list of inputs and outputs:

• I enter a company name and industry.
• The tool gathers the information it needs.
• It turns that information into a structured research summary.
• It gives me strategy notes in a format I can actually use.

From there, I built it one piece at a time. I’d describe what I wanted, see what came back, and if it wasn’t right, I’d try to describe it differently until it was. I don’t have a background in how any of this is architected underneath, so a lot of it was less like programming and more like negotiating: try something, look at the result, ask for it a different way.

By the end of the first week or two, I had something usable. I still couldn’t have recreated it from scratch by myself, but I could tell when something was off and describe what needed to change until it wasn’t.

The one to two weeks it actually took to build an AI tool without knowing how to code

Here’s the part I didn’t expect: it took about one to two weeks, spread out around everything else I was doing, and I built it without really understanding what I was doing for most of that time.

That sentence is doing a lot of work, so let me be specific about what “not really understanding” looked like in practice. It meant describing what I wanted in plain language, getting something back that mostly worked, and not being able to explain why the parts that didn’t work, didn’t. It meant a lot of trying something, seeing what changed, and trying again, closer to poking at a machine than programming one.

If you’re waiting for the moment where I hit a wall and had to learn to code to get past it, that moment didn’t really happen for me, at least not yet. The tool worked well enough on that first pass. What’s pulling me toward learning more isn’t a crisis. It’s that I can feel the ceiling of what I can do by only describing things in plain language, and I’d rather build the next version with more control than luck.

Why I’m learning more now, even though I didn’t have to

This is the part I feel a little sheepish about. I’m not learning to code because something broke and I needed to fix it. I’m learning because I want to understand what I already built well enough to actually improve it, instead of prompting my way around it and hoping for the best.

There’s a difference between a tool that works and a tool you understand. Mine currently works. I don’t yet understand most of it. That gap doesn’t bother me the way I thought it would, but it’s the reason I’m putting time into learning now instead of just shipping the next idea the same way I shipped this one.

Where I’m still honestly unsure

I don’t yet have a clean answer for how much I should trust what the tool gives me versus how much I should rewrite before using it. Some outputs feel ready to use as they are. Others clearly need a pass from me first. I haven’t figured out a reliable way to tell which is which before I’ve already read the whole thing, which somewhat defeats the point of automating it in the first place.

That’s probably the next thing I need to solve. Building the tool turned out to be easier than learning when to trust it. I’m starting to think that second part is the real work.