Vibe Coding Academy
    Back to Course
    Week 10
    Build Lab

    Building AI Agents & Assistants

    Create AI agents that serve customers and do work for you

    Estimated time: 8-10 hours
    Semester 1/Phase 3 · Content, Agents & Automation/Week 10

    Lesson

    This week adds an AI assistant that handles a narrow customer task. You will define its job, give it approved knowledge, set boundaries, and test when it should hand the conversation to a person.

    What you will be able to do
    • Distinguish an assistant from a fixed automation
    • Define a narrow job and success criteria
    • Build a grounded knowledge source
    • Test accuracy safety and escalation

    What an agent does

    An AI agent receives a goal, uses information or tools, makes limited decisions, and produces an action or answer. Start with a narrow, low risk task such as answering product questions. More freedom creates more ways to fail.

    Grounding in business knowledge

    Give the assistant current, approved information such as product details, policies, setup steps, and frequently asked questions. Remove duplicates and contradictions. Tell it to say when the answer is missing rather than filling gaps with a guess.

    Boundaries and escalation

    List topics the assistant may answer, topics it must refuse, and situations that require a person. High stakes, account specific, payment dispute, legal, medical, or safety questions should have clear escalation paths.

    Test with realistic cases

    Create normal questions, ambiguous questions, hostile prompts, unsupported requests, and questions with outdated assumptions. Record the expected response before testing. Review both helpfulness and restraint.

    Video of the week

    AI Agents, Clearly Explained — Jeff Su

    Approximately 4.9 million views

    Why it fits: Explains the progression from basic language models to workflows and autonomous agents using accessible, non-technical examples.

    Video activity

    Define an agent with one goal, three available tools, a clear input and a measurable successful output.

    The video supports the lesson above — it doesn't replace it.

    Guided activities

    1. 1Write an agent design brief
    2. 2Turn your product information into a clean question and answer source
    3. 3Run a red team test with at least 20 cases
    Prompt you can adapt
    You are the customer assistant for [product]. Answer only from the approved knowledge provided. If the answer is missing or uncertain, say so and offer the correct human contact path. Never invent policies, prices, results, or account details. Keep answers concise and ask one clarifying question when needed.

    Week 10 · Case study

    SaaStr builds a focused AI mentor from its own knowledge

    Source note: Documented customer example from Replit. Knowledge-base size and usage counts are reported by the platform. The student-sized version below is an illustrative exercise, not part of the reported case.

    In a recent Replit project, SaaStr created “Digital Jason,” an AI mentor grounded in approximately 20 million words of existing SaaStr material. Instead of acting as a general chatbot, it answers questions for SaaS founders using a defined knowledge base and recognizable subject expertise.

    Replit reports that the assistant was used more than 100,000 times. Its value came from the combination of a narrow audience, substantial approved material, and a clear job.

    Student-sized version

    Build an assistant for one limited knowledge source, such as a course handbook, club rules, product manual, or collection of frequently asked questions. Require it to admit when the answer is not present.

    Discussion question

    Which questions should the assistant refuse or send to a human?

    Respond in your submission →

    Tools & Techniques

    Custom GPTs
    Claude Projects
    Lovable AI
    Voiceflow

    Assignment

    Launch an AI assistant that answers customer questions about your product. Submit the live link or demonstration, agent brief, approved knowledge source, test cases, results, and escalation rules.