Loading video...

Video Failed to Load

Go Home

Just built an end-to-end AI agent workflow stack in 3 days that automates everything from recruiting to reminders to reporting for electrician franchises. What used to take 6+ SaaS tools and a full ops team? Now handled by 12 specialized agents: •Hiring •Screening •Follow-ups •Reminders •AI call reps •Reviews...

10,303 views • 1 year ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,343 views • 1 year ago

how to build an AI-first SaaS in 2026 1. start with a big market. finance, healthcare, real estate. then zoom into a sub-niche. 2. map the niche’s workflow end-to-end. literally write every step they do daily. ex: leads → scheduling → quoting → follow-ups → payments. 3. highlight where money changes hands. deposits, invoices, negotiations. those moments are where software captures value. 4. identify the repetitive mechanical tasks. anything someone does the same way every day is an automation opportunity. 5. quantify the pain. if a business owner spends 100 hours a year on something and their time is worth $300/hour, that’s a $30k problem. 6. manually perform the workflow yourself. most AI SaaS actually starts as a service. that’s why so many new YC companies begin with humans in the loop. 7. document every step. separate judgment tasks from mechanical tasks. agents handle the mechanical work. 8. turn those steps into agent workflows and connect them to real tools (email, slack, stripe, crm, APIs). 9. build media while you build the product. post daily about the workflow. use AI to research content ideas and scripts. the audience becomes your distribution. 10. launch narrow, show proof (hours saved, revenue generated), then expand into adjacent workflows until you become the default execution layer for that niche. people saying everyday that saas is dying it’s evolving into agents + software + media. full breakdown in the latest episode of The Startup Ideas Podcast (SIP) 🧃 lots of sauce in this one all for free because i can't wait to see what you build watch

GREG ISENBERG

188,818 views • 4 months ago