← back to blog

How I Built My First AI Agent (No CS Degree)

"Agent" is the buzzword of the year, and most explanations make it sound like rocket science. It isn't. Here's the honest version of how I went from "what even is an agent?" to one that quietly does a real job for me — without a computer science degree.

First: what an agent actually is

A regular chatbot answers when you ask. An agent is a chatbot that's been given a goal, some tools, and permission to take steps on its own until the goal is met.

Think of the difference like this:

• Chatbot: "Here's a draft email you could send." (You do the rest.)
• Agent: "I checked your calendar, found a free slot, drafted the email, and put it in your drafts." (It used tools to take action.)

That's the whole concept. Goal + tools + the ability to loop until done.

The mindset shift that made it click

I stopped thinking "I need to learn to code agents" and started thinking "I need to describe a job clearly enough that software can do it." Eighty percent of building a good agent is just writing a clear job description — what should it do, what should it never do, and what does "done" look like.

Pick a tiny first job

Don't build "an AI employee." Build one boring task you do every week. Mine was: "When a new lead fills out my contact form, summarize it, tag how urgent it is, and draft a reply for me to approve." Small, real, and low-risk if it gets something wrong.

The no-code tools I'd start with

• Make or n8n — visual automation where you drag boxes and drop an AI step in the middle. Best for "when X happens, do Y."
• Lindy — purpose-built for assistant-style agents (email, scheduling, follow-ups).
• A plain chat model (ChatGPT or Claude) — honestly, for many "agents" a really well-written prompt plus a couple of automation steps is all you need.

You can find all of these in the tools directory.

The build, in five steps

1. Trigger — what kicks it off? (A new form submission.)
2. Gather — pull in the info it needs. (The form fields.)
3. Think — the AI step. I gave it a prompt: "Summarize this lead in one line, rate urgency 1–5, and draft a friendly 3-sentence reply."
4. Act — do something with the result. (Save the draft, send myself a notification.)
5. Guardrail — the most important step. Mine never sends anything automatically; it always waits for my approval.

The difference between a helpful agent and a scary one is a single word: approval. Let it draft. Let it suggest. Make a human press send — at least until you trust it.

What I got wrong (so you don't)

• I made it do too much. Version one tried to handle five tasks. It was unreliable. One job, done well, beats five done badly.
• I was vague. "Be helpful" gets you mush. "Rate urgency 1–5 using these rules" gets you something useful.
• I gave it too much power too fast. Start with "draft only." Earn the autonomy.

Where to go next

Once one tiny agent works, you'll see them everywhere — inbox triage, content repurposing, research digests. Build them one boring job at a time. That's genuinely how the pros do it too.