In this blog post I'm going to walk you through how to build your first AI agent for a marketing workflow, written for a non-technical founder, with the architecture decisions explained in plain English. The version that gets you to a working agent in 2-4 weeks. Not the version that gets you to a 6-month engineering project.
Most "build an AI agent" content is written by engineers for engineers, or by hype merchants who skip the actual implementation. Neither is useful if you're a founder or marketing leader trying to figure out whether you should build something, and if so, what.
I've been a marketing consultant for twenty-one years. I went all in on AI in 2024. I've built and shipped multiple AI agents in my own business and for clients, none of them written in code by an engineer. I'm not technical in the traditional sense. If I can do it, you can too.
By the end of this blog you'll know what an agent is (without marketing fluff), when to build one vs use a SaaS tool, what architectures work for marketing use cases, the realistic build timeline, and what NOT to build in 2026.
TL;DR
The honest version:
- An AI agent is a workflow where an LLM makes decisions and takes actions on your behalf, not just generates text
- Most "marketing AI agents" in 2026 are wildly over-scoped, the right first agent is small and specific
- Non-technical founders can absolutely build agents using platforms like Claude Code, n8n, Make.com, or Zapier with LLM steps
- Realistic first-agent timeline: 2-4 weekends, not 2-4 months
- The bottleneck is almost never technical, it's clarity on what you want the agent to do
What an AI agent is (no marketing fluff)
The buzzword definition: "AI agents are autonomous systems that can reason, plan, and execute tasks."
The useful definition: an AI agent is a sequence of decisions and actions where an LLM is in the loop making choices, instead of you. The agent reads something (an email, a CRM record, a webpage), decides something (categorise it, write a response, take an action), and then does something (sends an email, updates a record, calls another API).
That's it. No magic.
Three things distinguish an agent from a "just use ChatGPT" workflow:
- It runs without you triggering it. Scheduled, event-driven, or webhook-based.
- It takes actions, not just produces text. Writes to a system, sends a message, makes an API call.
- It can branch. The decision the LLM makes determines what happens next.
If your "AI agent" requires you to copy-paste prompts and outputs by hand, it's not an agent yet, it's an assisted workflow. That's fine, most useful AI work is assisted workflow. But it's not an agent.
When to build an agent vs use a SaaS tool
The default should be SaaS. Build only when SaaS doesn't fit.
Use SaaS when:
- The use case is standard (lead enrichment, meeting summarisation, email drafting)
- The SaaS tool has good integrations with your existing stack
- The cost is reasonable relative to the value
- You expect to use it for at least 12 months
Build your own when:
- The use case is specific to your business (no SaaS does it well)
- You're paying multiple SaaS subscriptions to glue together what should be one workflow
- You want the workflow to embed in your existing systems rather than live in another tool
- The SaaS option is wildly overpriced relative to the actual capability
For most marketing teams, the first agent worth building is one that connects 2-3 of your existing tools in a way that no off-the-shelf product does.
What to build first: the "minimum useful agent"
The mistake I see most often: people try to build agents that do too much. "An agent that handles all our inbound enquiries" or "an agent that runs our content marketing." Both fail because the scope is too broad.
The minimum useful agent has these properties:
- One trigger (event that starts it)
- One decision (LLM-driven judgement)
- One action (what it does as a result)
- One person who knows when it runs and can shut it down
Examples of well-scoped first agents:
- Lead-triage agent: Reads new inbound enquiry → LLM categorises by likely deal size and fit → Adds to CRM with priority tag
- Newsletter prep agent: Pulls past week's published blog content + tracked metrics → LLM drafts the newsletter teaser section → Saves to a Google Doc for human review
- Discovery call brief agent: Detects new meeting on calendar with new prospect → LLM pulls their LinkedIn + company website → Drafts a 1-page prep brief → Emails it to you 30 mins before the call
- Inbound sponsorship classifier: Reads new sponsorship enquiry → LLM scores against your criteria → Tags as high/medium/low priority → Routes to the right inbox folder
Each of these is buildable in 2-4 weekends by a non-technical founder using the platforms below.
The non-technical agent stack in 2026
Three categories of tooling, ranked by accessibility:
Tier 1: No-code agent platforms
The easiest entry point. Visual workflow builders with LLM steps built in.
Best options:
- n8n, open-source, self-hostable, strong LLM integration. Currently my preferred choice for serious workflows.
- Make.com, visual builder, good library of integrations, AI modules built in.
- Zapier, most integrations, simplest interface, more expensive at scale.
What you can build: Any agent that's a linear or lightly branched workflow with a clear trigger.
What you can't easily build: Agents with complex multi-step reasoning, agents that need to maintain state across many runs.
Realistic timeline: First useful agent in 1-2 weekends.
Tier 2: Low-code with LLM IDEs
The next step up. You're not writing code from scratch, but you're working in a more code-aware environment.
Best options:
- Claude Code, Anthropic's CLI for building with Claude. Excellent for non-technical founders who want to build sophisticated workflows. The platform I use for everything.
- OpenAI's Assistants API, more setup, but powerful for stateful agents.
- Cursor, IDE with AI built in, useful when you're ready to touch code occasionally.
What you can build: Anything in tier 1 plus stateful agents, complex branching, custom integrations.
Realistic timeline: First useful agent in 2-4 weekends.
Tier 3: Full agent frameworks
Engineering-grade. Skip these unless you have or are willing to develop real coding skills.
Examples: LangChain, LangGraph, AutoGPT, BabyAGI, custom Python with Anthropic/OpenAI SDKs.
For most non-technical founders, you don't need these. The use from tier 1 and tier 2 is enormous.
The architecture of a useful marketing agent
Even simple agents benefit from clear architecture. Here's the pattern that works:
1. Trigger layer
What starts the agent. Webhook from another tool, scheduled cron, manual button push, email arrival. Decide this first, it determines everything else.
2. Context layer
What information the agent needs. Inputs from the trigger, plus lookups (CRM records, past emails, knowledge base). Don't skip this, agents fail when they have insufficient context.
3. Decision layer
What the LLM decides. A specific question with a structured output. Not "what should we do", that's too open. "Is this lead enterprise, mid-market, or SMB?" with allowed answers.
4. Action layer
What happens as a result of the decision. Branching logic. Each branch ends in a specific action, write to a database, send an email, create a task.
5. Logging layer
What gets recorded. Every agent run logged. Every decision the LLM made. Every action taken. You'll need this when (not if) something goes wrong.
6. Kill switch
The button you press to turn it off. Hardcoded. Easily accessible. Always tested.
Most failed agents skip layers 5 and 6. Don't.
How long does it take?
Honest timelines for a non-technical founder:
Week 1 (1-2 evenings): Pick the use case. Write the agent design on one page. Sign up for the platform.
Week 2 (1 weekend): Build the trigger and context layers. Test that the agent receives inputs correctly.
Week 3 (1 weekend): Build the decision layer. Iterate on the LLM prompt until decisions are reliable.
Week 4 (1 weekend): Build the action layer. Test end-to-end in a sandbox.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Week 5 (1 weekend): Add logging. Add the kill switch. Run it live with you watching every output for a week.
Week 6 onwards: Trust the agent for autonomous runs. Review outputs weekly. Iterate.
About 30-40 hours total spread over 5-6 weekends. Faster if you have help. Faster still if you've already built one before.
The four-step prompt structure for agent decisions
The LLM step is where most agents succeed or fail. Use this four-part prompt structure:
Part 1: Role. Who the LLM is. ("You are a sales operations specialist...")
Part 2: Task. What it's deciding. ("Categorise this inbound enquiry as one of: enterprise, mid-market, SMB, or unqualified.")
Part 4: Format. Exactly what to return. ("Return JSON with keys 'category' (one of: enterprise/mid-market/SMB/unqualified), 'confidence' (high/medium/low), and 'reasoning' (one sentence).")
Without the format constraint, the LLM returns prose, which breaks your action layer. Always specify the format.
What NOT to build in 2026
Three categories of agents I've seen fail repeatedly:
Don't build: "Full automation" sales agents
The temptation: an agent that handles inbound enquiries end-to-end. Reads, qualifies, replies, books meetings.
The reality: prospects can tell when sales is automated. Response rates collapse. Your personal brand takes a hit. The few sales you close were the ones you'd have closed anyway with a 2-minute manual reply.
Build instead: An agent that prepares you to respond, not one that responds for you.
Don't build: "Full automation" content agents
The temptation: an agent that researches topics, writes posts, generates images, publishes, distributes on social.
The reality: Google penalises AI-only content. Audiences disengage from low-signal posts. You'll save time and lose the traffic you were trying to build.
Build instead: An agent that handles the operational tail of publishing (SEO meta, image generation, internal linking, distribution scheduling) while you handle the strategic head (topic selection, voice, opinions).
Don't build: Generic "AI assistant" agents
The temptation: an agent that "can help with anything." Multi-modal, multi-purpose, conversational.
The reality: open-scope agents underperform every specific tool you'd use otherwise. They become novelty toys.
Build instead: Specific agents for specific workflows. The narrower, the more useful.
The cost of building vs buying
Rough comparison for a typical marketing-team-sized first agent:
Build it yourself:
- 30-40 hours of your time
Buy equivalent SaaS:
- 20-40 hours of integration time
For a single use case, the maths is close. For 3+ use cases on the same custom platform, building wins decisively.
What you'll need to know
You don't need to learn to code. You do need to learn:
- How HTTP requests work (the basics, GET, POST, headers, body)
- How JSON works (it's just a way of structuring data)
- How webhooks work (one system tells another that something happened)
- Basic prompt engineering (covered in my AI prompts for marketers guide)
- The interface of your chosen platform (n8n, Make, Zapier, Claude Code)
This is roughly 20-30 hours of learning. Most of it can happen alongside your first build.
When to bring in help
You probably don't need to. But three cases where outside help speeds things up:
Case 1: Tight deadline. If you need the agent shipped in a week and you've never built one, paying for help compresses the timeline meaningfully.
Case 2: Complex integration. If your CRM is a custom-built system without a clean API, an engineer will save you days of frustration.
Case 3: Stakes are high. If the agent will run with real customer interactions and a mistake would be embarrassing, having a more experienced builder validate your design pays back.
In all three cases, hire by the project, not by the hour. And insist on documentation so you can maintain the agent yourself afterwards.
Frequently asked questions
Can I really build this if I've never written code? Yes. The platforms above are designed for non-coders. I'm not a coder in the traditional sense and I've built dozens of working agents.
Which platform should I start with? n8n if you want maximum capability and don't mind a learning curve. Make.com if you want a faster start. Claude Code if you're willing to learn a bit of Python and want the most powerful tooling.
How do I keep API costs under control? Set budget alerts on day one. Use caching where possible. Choose smaller models for routine decisions (Claude Haiku, GPT-4o-mini) and only escalate to larger models for high-stakes decisions.
What happens when the agent makes a mistake? It will. Mistakes are expected. Build the kill switch first, log everything, review weekly, iterate on the prompts. The mistake rate drops dramatically over the first 4-6 weeks of operation.
Should I deploy my first agent to production? Run it shadow mode first. Let it make decisions for a week without taking any actions. Compare its decisions to what you'd have done. Only deploy to production once you trust the decisions.
What's the most common reason first agents fail? Scope creep. Founders try to build the all-singing all-dancing agent before they've shipped a single small one. Build small, ship, then expand.
Want help building your first agent?
If your situation is "just use an off-the-shelf SaaS for this," that's the recommendation, and you walk away with the diagnosis and no further pitch.
Book an agent design session →
I'm Lilach Bullock. I've been a marketing consultant for twenty-one years. I went all in on AI in 2024. I work with founders and marketing leaders who want AI to move their numbers, not just their tool stack.
Related: the best content repurposing tools
Want the complete version? Read where I break down AI marketing.
