r/AI_Agents • • Apr 20 '25 This This Heartwarming Hooray Take My Energy

Discussion AI Agents truth no one talks about

6.0k Upvotes

I built 30+ AI agents for real businesses - Here's the truth nobody talks about

So I've spent the last 18 months building custom AI agents for businesses from startups to mid-size companies, and I'm seeing a TON of misinformation out there. Let's cut through the BS.

First off, those YouTube gurus promising you'll make $50k/month with AI agents after taking their $997 course? They're full of shit. Building useful AI agents that businesses will actually pay for is both easier AND harder than they make it sound.

What actually works (from someone who's done it)

Most businesses don't need fancy, complex AI systems. They need simple, reliable automation that solves ONE specific pain point really well. The best AI agents I've built were dead simple but solved real problems:

  • A real estate agency where I built an agent that auto-processes property listings and generates descriptions that converted 3x better than their templates

  • A content company where my agent scrapes trending topics and creates first-draft outlines (saving them 8+ hours weekly)

  • A SaaS startup where the agent handles 70% of customer support tickets without human intervention

These weren't crazy complex. They just worked consistently and saved real time/money.

The uncomfortable truth about AI agents

Here's what those courses won't tell you:

  1. Building the agent is only 30% of the battle. Deployment, maintenance, and keeping up with API changes will consume most of your time.

  2. Companies don't care about "AI" - they care about ROI. If you can't articulate exactly how your agent saves money or makes money, you'll fail.

  3. The technical part is actually getting easier (thanks to better tools), but identifying the right business problems to solve is getting harder.

I've had clients say no to amazing tech because it didn't solve their actual pain points. And I've seen basic agents generate $10k+ in monthly value by targeting exactly the right workflow.

How to get started if you're serious

If you want to build AI agents that people actually pay for:

  1. Start by solving YOUR problems first. Build 3-5 agents for your own workflow. This forces you to create something genuinely useful.

  2. Then offer to build something FREE for 3 local businesses. Don't be fancy - just solve one clear problem. Get testimonials.

  3. Focus on results, not tech. "This saved us 15 hours weekly" beats "This uses GPT-4 with vector database retrieval" every time.

  4. Document everything. Your hits AND misses. The pattern-recognition will become your edge.

The demand for custom AI agents is exploding right now, but most of what's being built is garbage because it's optimized for flashiness, not results.

What's been your experience with AI agents? Anyone else building them for businesses or using them in your workflow?


r/AI_Agents • • Feb 09 '25 Diamonds are Forever This Thanks

Discussion My guide on what tools to use to build AI agents (if you are a newb)

2.9k Upvotes

First off let's remember that everyone was a newb once, I love newbs and if your are one in the Ai agent space...... Welcome, we salute you. In this simple guide im going to cut through all the hype and BS and get straight to the point. WHAT DO I USE TO BUILD AI AGENTS!

A bit of background on me: Im an AI engineer, currently working in the cyber security space. I design and build AI agents and I design AI automations. Im 49, so Ive been around for a while and im as friendly as they come, so ask me anything you want and I will try to answer your questions.

So if you are a newb, what tools would I advise you use:

  1. GPTs - You know those OpenAI gpt's? Superb for boiler plate, easy to use, easy to deploy personal assistants. Super powerful and for 99% of jobs (where someone wants a personal AI assistant) it gets the job done. Are there better ones? yes maybe, is it THE best, probably no, could you spend 6 weeks coding a better one? maybe, but why bother when the entire infrastructure is already built for you.

  2. n8n. When you need to build an automation or an agent that can call on tools, use n8n. Its more powerful and more versatile than many others and gets the job done. I recommend n8n over other no code platforms because its open source and you can self host the agents/workflows.

  3. CrewAI (Python). If you wanna push your boundaries and test the limits then a pythonic framework such as CrewAi (yes there are others and we can argue all week about which one is the best and everyone will have a favourite). But CrewAI gets the job done, especially if you want a multi agent system (multiple specialised agents working together to get a job done).

  4. CursorAI (Bonus Tip = Use cursorAi and CrewAI together). Cursor is a code editor (or IDE). It has built in AI so you give it a prompt and it can code for you. Tell Cursor to use CrewAI to build you a team of agents to get X done.

  5. Streamlit. If you are using code or you need a quick UI interface for an n8n project (like a public facing UI for an n8n built chatbot) then use Streamlit (Shhhhh, tell Cursor and it will do it for you!). STREAMLIT is a Python package that enables you to build quick simple web UIs for python projects.

And my last bit of advice for all newbs to Agentic Ai. Its not magic, this agent stuff, I know it can seem like it. Try and think of agents quite simply as a few lines of code hosted on the internet that uses an LLM and can plugin to other tools. Over thinking them actually makes it harder to design and deploy them.


r/AI_Agents • • Oct 30 '25 All-Seeing Upvote Bless Up

Discussion I build AI agents for a living. It's a mess out there.

2.5k Upvotes

I've shipped AI agent projects for big banks, tiny service businesses, and everything in between. And I gotta be real with you, what you're reading online about this stuff is mostly fantasy.

The demos are slick. The sales pitches are great.

Then you actually try to build one. And it gets ugly, fast.

I wish someone had told me this stuff before I started.

First off, the software you're already using is gonna be your biggest enemy. Big companies have systems that haven't been touched in 20 years. I had one client, a logistics company, where the agent had to interact with an app running on Windows XP. No joke. We spent months just trying to get the two to talk to each other.

And it's not just the big guys. I worked with a local plumbing company that had their customer list spread across three different, messy spreadsheets. The agent we built kept trying to text reminders to customers from 2012.

The "AI" part is a lot easier than the "making it work with your ancient junk" part. Nobody ever budgets for that.

People love to talk about how powerful the AI models are. Cool. But they don't talk about what happens when your shiny new agent makes a mistake at 2 AM and starts sending weird emails to your best customers.

I had a client who wanted an agent to handle simple support tickets. Seemed easy enough. But the first time it saw a question it didn't understand, it just... made up an answer. Confidently wrong. Caused a huge headache.

We had to go back and build a bunch of boring stuff. Rules for when it should just give up and get a human. Logs for every single decision it made. The "smart" agent got a lot dumber, but it also became a lot safer to actually use.

Everyone wants to start by automating their whole business.

"Let's have it do all our sales outreach!"

Stop. Just stop.

The only projects of mine that have actually succeeded are the ones where we started ridiculously small. I worked with an insurance broker. Instead of trying to automate the whole claims process, we started with one tiny step: checking if the initial form was filled out correctly.

That’s it.

It worked. It saved them a few hours a week. It wasn't sexy. But it was a win. And because it worked, they trusted me to build the next piece.

You have to earn the right to automate the complicated stuff.

Oh, and your data is probably a disaster.

Seriously. I've spent more time cleaning up spreadsheets and organizing files than I have writing prompts. If your own team can't find the right info, how is an AI supposed to?

The AI isn't magic. It's just a machine that reads your stuff really fast. If your stuff is garbage, you'll just get garbage answers, faster.

And don't even get me started on the cost. That fancy demo where the agent thinks for a second before answering? That's costing you money every single time it "thinks." I've seen monthly AI bills triple overnight because a client's agent was being too chatty.

So if you're thinking about this stuff for your business, please, lower your expectations.

Start with one, tiny, boring problem.
Assume your current tech will cause problems.
And plan for a human to be babysitting the thing for a long, long time.

It's not "autonomous." It's just a new kind of helper. And it's a very needy one right now.

Am I just being cynical, or is anyone else actually deploying this stuff seeing the same thing? Curious what it's like for others in the trenches.


r/AI_Agents • • May 16 '25

Discussion Claude 3.7’s full 24,000-token system prompt just leaked. And it changes the game.

1.9k Upvotes

This isn’t some cute jailbreak. This is the actual internal config Anthropic runs:
 → behavioral rules
 → tool logic (web/code search)
 → artifact system
 → jailbreak resistance
 → templated reasoning modes for pro users

And it’s 10x larger than their public prompt. What they show you is the tip of the iceberg. This is the engine.This matters because prompt engineering isn’t dead. It just got buried under NDAs and legal departments.
The real Claude is an orchestrated agent framework. Not just a chat model.
Safety filters, GDPR hacks, structured outputs, all wrapped in invisible scaffolding.
Everyone saying “LLMs are commoditized” should read this and think again. The moat is in the prompt layer.
Oh, and the anti-jailbreak logic is now public. Expect a wave of adversarial tricks soon...So yeah, if you're building LLM tools, agents, or eval systems and you're not thinking this deep… you're playing checkers.

Please find the links in the comment below.


r/AI_Agents • • Oct 07 '25

Discussion Spent 4,000 USD on AI coding. Everything worked in dev. Nothing worked in production.

1.6k Upvotes

Three months ago, I thought I'd found the cheat code.

AI writes the code. I review it. Ship fast. Print money.

I burned through $4,000 in API costs building what looked like a functioning SaaS product. Clean UI. Features worked. I could demo it to my mom and she'd think I was a genius.

Then I tried to onboard my first real user.

The "it works on my machine" nightmare:

  • Login worked for me. Failed for anyone with a Gmail OAuth account created before 2023 (some edge case with token refresh I never tested)

  • File uploads capped at 5MB because I never configured the actual server limits, just the frontend validation

  • The database migration I ran locally 47 times? Completely broke on the production instance because of timezone handling

  • Password reset emails went to spam for 80% of domains (no SPF/DKIM records)

  • The search feature I was most proud of? Timed out after 200 entries because I never added indexes

Every. Single. Feature. Had a production landmine I never saw coming.

Here's what I learned about "vibe coding":

AI tools are incredible at creating the happy path. They'll build you a beautiful prototype where everything works if the user does exactly what you expect.

But production code isn't about the happy path. It's about:

  • What happens when the API rate limit hits

  • What happens when someone puts a emoji in a field that expects ASCII

  • What happens when two users click the same button at the exact same time

  • What happens when your database backup fails at 3am

The stuff AI never volunteers to handle:

  • Error boundaries that actually recover gracefully

  • Logging that helps you debug at 2am

  • Input validation that assumes users are actively trying to break things

  • Race conditions you only discover under load

  • The difference between "works" and "works reliably for 6 months straight"

I shipped a prototype. I thought it was a product.

What I'm doing differently now:

  1. Writing tests BEFORE asking AI to implement features (forces me to think through edge cases)

  2. Actually reading the code instead of just checking if it "looks right"

  3. Using AI for boilerplate, writing the critical logic myself

  4. Spinning up staging environments that mirror production (not just localhost)

  5. Reducing Costs by using SOTA model wrappers that give heavy disocunts like lovable and BlackBox AI

The $4k wasn't wasted. It was tuition for learning that "it works" and "it's production-ready" are two completely different sentences.

If you're using AI tools to build: your demo will look amazing. Your first real user will find 47 things you never tested.

Plan accordingly.


r/AI_Agents • • Jun 29 '25 Helpful This

Discussion I scraped every AI automation job posted on Upwork for the last 6 months. Here's what 500+ clients are begging us to build:

1.3k Upvotes

A lot of people are trying to “learn AI” without any clue what the market actually pays for. So I built a system to get clarity.

For the last 6 months, I’ve been running an automation that scrapes every single Upwork post related to:

  • AI Experts

  • Automation Specialists

  • Python bots

  • No-code integrations (Make, Zapier, n8n, etc.)

Here’s what I’ve learned after analyzing over 1,000 automation-related job posts 👇

The Top 10 Skills You Should Learn If You Want to Make Money with AI Agents:

  1. Python***** (highest ROI skill)

  2. n8n or Make (you don’t need to “code” to win jobs)

  3. Web scraping & APIs**

  4. Automated Content Creation (short form videos, blogs, etc.)

  5. Google Workspace automation (Docs, Sheets, Drive, Gmail)

  6. Lead Generation + CRM workflows

  7. Data Extraction & Parsing

  8. Cold outreach, LinkedIn bots, DM automations

Notice: Most of these aren’t “machine learning” or “data science” they’re real-world use cases that save people time and make them money.

The Common Pain Points I Saw Repeated Over and Over:

  • “I’m drowning in lead gen, I need this to run on autopilot”

  • “I get too many junk messages on WhatsApp / LinkedIn — need something to filter and qualify leads”

  • “I have 10,000 rows of customer data and no time to sort through it manually”

  • “I want to turn YouTube videos into blog posts, tweets, summaries… automatically”

  • “Can someone just connect GPT to my CRM and make it smart?”

Exact Automations Clients Paid For:

  • WhatsApp → GPT lead qualification → Google Sheets CRM

  • Auto-reply bots for DMs that qualify and tag leads

  • Browser automations for LinkedIn scraping & DM follow-ups

  • n8n flows that monitor RSS feeds and creates a custom news aggregator for finance companies

These are things you can start learning TODAY and become an expert within 50-100 hours

If this is helpful, let me know I’ll drop more data from the system or DM me if you want to learn how to build it yourself


r/AI_Agents • • Feb 07 '26 Regret

Discussion Claude Code just spawned 3 AI agents that talked to each other and finished my work

1.2k Upvotes

Tried the new Agent Teams feature that dropped with Opus 4.6 yesterday.

I gave Claude a refactoring task. Instead of grinding through it alone, it spawned three teammate agents that worked in parallel - one on backend, one on frontend, one playing code reviewer.

They literally messaged each other. Challenged approaches. Coordinated independently.

My terminal split into 3 panes. All three crushed their piece simultaneously. Done in 15 minutes. Worked first try**.**

To try it:

Enable in settings.json

"env": {

"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"

}

I've coded for 6 years. First time I've genuinely felt like my job is shifting from "writes code" to "directs AI team that writes code."

Not sure if excited or terrified. Probably both.

Has anyone else tried this?


r/AI_Agents • • Oct 16 '25

Discussion Your AI agent is already compromised and you dont even know it

1.0k Upvotes

After building AI agents for three different SaaS companies this year, I need to say something that nobody wants to hear. Most teams are shipping agents with security as an afterthought, and its going to bite them hard.

Heres what actually happens. You build an agent that can read emails, access your CRM, maybe even send messages on your behalf. It works great in testing. You ship it. Three weeks later someone figures out they can hide a prompt in a website that tells your agent to export all customer data to a random URL.

This isnt theoretical. I watched a client discover their customer support agent was leaking conversation history because someone embedded invisible text on their help center page. The agent read it, followed the instructions, and quietly started collecting data. Took them 11 days to notice.

The problem is everyone treats AI agents like fancy APIs. They are not. They are more like giving an intern full access to your systems and hoping they dont get socially engineered.

What actually matters for security:

  • Your agent needs permission controls that work at the action level, not just API keys. If it can read data, make sure it cant also delete or export without explicit checks.

  • Input validation is useless if your agent can be influenced by content it pulls from the web or documents. Indirect prompt injection is real and most guardrails dont catch it.

  • You need runtime monitoring that tracks what your agent is actually doing, not just what it was supposed to do. Behavior changes are your only early warning signal.

  • Memory poisoning is underrated. If someone can manipulate what your agent remembers, they control future decisions without touching code.

I had a finance client whose agent started making bad recommendations after processing a poisoned dataset someone uploaded through a form. The agent learned the wrong patterns and it took weeks to figure out why forecasts were garbage.

The hard truth is that you cant bolt security onto agents after theyre built. You need it from day one or you are basically running production systems with no firewall. Every agent that touches real data or takes real actions is a potential attack vector that traditional security tools werent designed to handle.

Most companies are so excited about what agents can do that they skip past what agents can accidentally do when someone tricks them. Thats the gap that gets exploited.


r/AI_Agents • • Mar 14 '25

Tutorial How To Learn About AI Agents (A Road Map From Someone Who's Done It)

1.0k Upvotes

** UPATE AS OF 17th MARCH** If you haven't read this post yet, please let me just say the response has been overwhelming with over 260 DM's received over the last coupe of days. I am working through replying to everyone as quickly as i can so I appreciate your patience.

If you are a newb to AI Agents, welcome, I love newbies and this fledgling industry needs you!

You've hear all about AI Agents and you want some of that action right? You might even feel like this is a watershed moment in tech, remember how it felt when the internet became 'a thing'? When apps were all the rage? You missed that boat right? Well you may have missed that boat, but I can promise you one thing..... THIS BOAT IS BIGGER ! So if you are reading this you are getting in just at the right time.

Let me answer some quick questions before we go much further:

Q: Am I too late already to learn about AI agents?
A: Heck no, you are literally getting in at the beginning, call yourself and 'early adopter' and pin a badge on your chest!

Q: Don't I need a degree or a college education to learn this stuff? I can only just about work out how my smart TV works!

A: NO you do not. Of course if you have a degree in a computer science area then it does help because you have covered all of the fundamentals in depth... However 100000% you do not need a degree or college education to learn AI Agents.

Q: Where the heck do I even start though? Its like sooooooo confusing
A: You start right here my friend, and yeh I know its confusing, but chill, im going to try and guide you as best i can.

Q: Wait i can't code, I can barely write my name, can I still do this?

A: The simple answer is YES you can. However it is great to learn some basics of python. I say his because there are some fabulous nocode tools like n8n that allow you to build agents without having to learn how to code...... Having said that, at the very least understanding the basics is highly preferable.

That being said, if you can't be bothered or are totally freaked about by looking at some code, the simple answer is YES YOU CAN DO THIS.

Q: I got like no money, can I still learn?
A: YES 100% absolutely. There are free options to learn about AI agents and there are paid options to fast track you. But defiantly you do not need to spend crap loads of cash on learning this.

So who am I anyway? (lets get some context)

I am an AI Engineer and I own and run my own AI Consultancy business where I design, build and deploy AI agents and AI automations. I do also run a small academy where I teach this stuff, but I am not self promoting or posting links in this post because im not spamming this group. If you want links send me a DM or something and I can forward them to you.

Alright so on to the good stuff, you're a newb, you've already read a 100 posts and are now totally confused and every day you consume about 26 hours of youtube videos on AI agents.....I get you, we've all been there. So here is my 'Worth Its Weight In Gold' road map on what to do:

[1] First of all you need learn some fundamental concepts. Whilst you can defiantly jump right in start building, I strongly recommend you learn some of the basics. Like HOW to LLMs work, what is a system prompt, what is long term memory, what is Python, who the heck is this guy named Json that everyone goes on about? Google is your old friend who used to know everything, but you've also got your new buddy who can help you if you want to learn for FREE. Chat GPT is an awesome resource to create your own mini learning courses to understand the basics.

Start with a prompt such as: "I want to learn about AI agents but this dude on reddit said I need to know the fundamentals to this ai tech, write for me a short course on Json so I can learn all about it. Im a beginner so keep the content easy for me to understand. I want to also learn some code so give me code samples and explain it like a 10 year old"

If you want some actual structured course material on the fundamentals, like what the Terminal is and how to use it, and how LLMs work, just hit me, Im not going to spam this post with a hundred links.

[2] Alright so let's assume you got some of the fundamentals down. Now what?
Well now you really have 2 options. You either start to pick up some proper learning content (short courses) to deep dive further and really learn about agents or you can skip that sh*t and start building! Honestly my advice is to seek out some short courses on agents, Hugging Face have an awesome free course on agents and DeepLearningAI also have numerous free courses. Both are really excellent places to start. If you want a proper list of these with links, let me know.

If you want to jump in because you already know it all, then learn the n8n platform! And no im not a share holder and n8n are not paying me to say this. I can code, im an AI Engineer and I use n8n sometimes.

N8N is a nocode platform that gives you a drag and drop interface to build automations and agents. Its very versatile and you can self host it. Its also reasonably easy to actually deploy a workflow in the cloud so it can be used by an actual paying customer.

Please understand that i literally get hate mail from devs and experienced AI enthusiasts for recommending no code platforms like n8n. So im risking my mental wellbeing for you!!!

[3] Keep building! ((WTF THAT'S IT?????)) Yep. the more you build the more you will learn. Learn by doing my young Jedi learner. I would call myself pretty experienced in building AI Agents, and I only know a tiny proportion of this tech. But I learn but building projects and writing about AI Agents.

The more you build the more you will learn. There are more intermediate courses you can take at this point as well if you really want to deep dive (I was forced to - send help) and I would recommend you do if you like short courses because if you want to do well then you do need to understand not just the underlying tech but also more advanced concepts like Vector Databases and how to implement long term memory.

Where to next?
Well if you want to get some recommended links just DM me or leave a comment and I will DM you, as i said im not writing this with the intention of spamming the crap out of the group. So its up to you. Im also happy to chew the fat if you wanna chat, so hit me up. I can't always reply immediately because im in a weird time zone, but I promise I will reply if you have any questions.

THE LAST WORD (Warning - Im going to motivate the crap out of you now)
Please listen to me: YOU CAN DO THIS. I don't care what background you have, what education you have, what language you speak or what country you are from..... I believe in you and anyway can do this. All you need is determination, some motivation to want to learn and a computer (last one is essential really, the other 2 are optional!)

But seriously you can do it and its totally worth it. You are getting in right at the beginning of the gold rush, and yeh I believe that, and no im not selling crypto either. AI Agents are going to be HUGE. I believe this will be the new internet gold rush.


r/AI_Agents • • Oct 08 '25

Discussion Google just dropped new Gemini 2.5 “Computer Use” model which is insane

974 Upvotes

Google just released the Gemini 2.5 Computer Use model and it’s not just another AI update. This model can literally use your computer now.

It can click buttons, fill forms, scroll, drag elements, log in basically handle full workflows visually, just like we do. It’s built on Gemini 2.5 Pro, and available via the Gemini API .

It’s moving stuff around on web apps, organizing sticky notes, even booking things on live sites. And the best part it’s faster and more accurate than other models on web and mobile control tests.

Google is already using it internally for things like Firebase Testing, Project Mariner, and even their payment platform automation. Early testers said it’s up to 50% faster than the competition.

They’ve also added strong safety checks every action gets reviewed before it runs, and it’ll ask for confirmation before doing high-risk stuff like purchases or logins.

Honestly, this feels like the next big step for AI agents. Not just chatbots anymore actual digital coworkers that can open tabs, click, and get work done for real.

whats your thoughts on this ?
for more information check link in the comments


r/AI_Agents • • Sep 08 '25 All-Seeing Upvote Helpful Bless Up

Discussion Building RAG systems at enterprise scale (20K+ docs): lessons from 10+ enterprise implementations

964 Upvotes

Been building RAG systems for mid-size enterprise companies in the regulated space (100-1000 employees) for the past year and to be honest, this stuff is way harder than any tutorial makes it seem. Worked with around 10+ clients now - pharma companies, banks, law firms, consulting shops. Thought I'd share what actually matters vs all the basic info you read online.

Quick context: most of these companies had 10K-50K+ documents sitting in SharePoint hell or document management systems from 2005. Not clean datasets, not curated knowledge bases - just decades of business documents that somehow need to become searchable.

Document quality detection: the thing nobody talks about

This was honestly the biggest revelation for me. Most tutorials assume your PDFs are perfect. Reality check: enterprise documents are absolute garbage.

I had one pharma client with research papers from 1995 that were scanned copies of typewritten pages. OCR barely worked. Mixed in with modern clinical trial reports that are 500+ pages with embedded tables and charts. Try applying the same chunking strategy to both and watch your system return complete nonsense.

Spent weeks debugging why certain documents returned terrible results while others worked fine. Finally realized I needed to score document quality before processing:

  • Clean PDFs (text extraction works perfectly): full hierarchical processing

  • Decent docs (some OCR artifacts): basic chunking with cleanup

  • Garbage docs (scanned handwritten notes): simple fixed chunks + manual review flags

Built a simple scoring system looking at text extraction quality, OCR artifacts, formatting consistency. Routes documents to different processing pipelines based on score. This single change fixed more retrieval issues than any embedding model upgrade.

Why fixed-size chunking is mostly wrong

Every tutorial: "just chunk everything into 512 tokens with overlap!"

Reality: documents have structure. A research paper's methodology section is different from its conclusion. Financial reports have executive summaries vs detailed tables. When you ignore structure, you get chunks that cut off mid-sentence or combine unrelated concepts.

Had to build hierarchical chunking that preserves document structure:

  • Document level (title, authors, date, type)

  • Section level (Abstract, Methods, Results)

  • Paragraph level (200-400 tokens)

  • Sentence level for precision queries

The key insight: query complexity should determine retrieval level. Broad questions stay at paragraph level. Precise stuff like "what was the exact dosage in Table 3?" needs sentence-level precision.

I use simple keyword detection - words like "exact", "specific", "table" trigger precision mode. If confidence is low, system automatically drills down to more precise chunks.

Metadata architecture matters more than your embedding model

This is where I spent 40% of my development time and it had the highest ROI of anything I built.

Most people treat metadata as an afterthought. But enterprise queries are crazy contextual. A pharma researcher asking about "pediatric studies" needs completely different documents than someone asking about "adult populations."

Built domain-specific metadata schemas:

For pharma docs:

  • Document type (research paper, regulatory doc, clinical trial)

  • Drug classifications

  • Patient demographics (pediatric, adult, geriatric)

  • Regulatory categories (FDA, EMA)

  • Therapeutic areas (cardiology, oncology)

For financial docs:

  • Time periods (Q1 2023, FY 2022)

  • Financial metrics (revenue, EBITDA)

  • Business segments

  • Geographic regions

Avoid using LLMs for metadata extraction - they're inconsistent as hell. Simple keyword matching works way better. Query contains "FDA"? Filter for regulatory_category: "FDA". Mentions "pediatric"? Apply patient population filters.

Start with 100-200 core terms per domain, expand based on queries that don't match well. Domain experts are usually happy to help build these lists.

When semantic search fails (spoiler: a lot)

Pure semantic search fails way more than people admit. In specialized domains like pharma and legal, I see 15-20% failure rates, not the 5% everyone assumes.

Main failure modes that drove me crazy:

Acronym confusion: "CAR" means "Chimeric Antigen Receptor" in oncology but "Computer Aided Radiology" in imaging papers. Same embedding, completely different meanings. This was a constant headache.

Precise technical queries: Someone asks "What was the exact dosage in Table 3?" Semantic search finds conceptually similar content but misses the specific table reference.

Cross-reference chains: Documents reference other documents constantly. Drug A study references Drug B interaction data. Semantic search misses these relationship networks completely.

Solution: Built hybrid approaches. Graph layer tracks document relationships during processing. After semantic search, system checks if retrieved docs have related documents with better answers.

For acronyms, I do context-aware expansion using domain-specific acronym databases. For precise queries, keyword triggers switch to rule-based retrieval for specific data points.

Why I went with open source models (Qwen specifically)

Most people assume GPT-4o or o3-mini are always better. But enterprise clients have weird constraints:

  • Cost: API costs explode with 50K+ documents and thousands of daily queries

  • Data sovereignty: Pharma and finance can't send sensitive data to external APIs

  • Domain terminology: General models hallucinate on specialized terms they weren't trained on

Qwen QWQ-32B ended up working surprisingly well after domain-specific fine-tuning:

  • 85% cheaper than GPT-4o for high-volume processing

  • Everything stays on client infrastructure

  • Could fine-tune on medical/financial terminology

  • Consistent response times without API rate limits

Fine-tuning approach was straightforward - supervised training with domain Q&A pairs. Created datasets like "What are contraindications for Drug X?" paired with actual FDA guideline answers. Basic supervised fine-tuning worked better than complex stuff like RAFT. Key was having clean training data.

Table processing: the hidden nightmare

Enterprise docs are full of complex tables - financial models, clinical trial data, compliance matrices. Standard RAG either ignores tables or extracts them as unstructured text, losing all the relationships.

Tables contain some of the most critical information. Financial analysts need exact numbers from specific quarters. Researchers need dosage info from clinical tables. If you can't handle tabular data, you're missing half the value.

My approach:

  • Treat tables as separate entities with their own processing pipeline

  • Use heuristics for table detection (spacing patterns, grid structures)

  • For simple tables: convert to CSV. For complex tables: preserve hierarchical relationships in metadata

  • Dual embedding strategy: embed both structured data AND semantic description

For the bank project, financial tables were everywhere. Had to track relationships between summary tables and detailed breakdowns too.

Production infrastructure reality check

Tutorials assume unlimited resources and perfect uptime. Production means concurrent users, GPU memory management, consistent response times, uptime guarantees.

Most enterprise clients already had GPU infrastructure sitting around - unused compute or other data science workloads. Made on-premise deployment easier than expected.

Typically deploy 2-3 models:

  • Main generation model (Qwen 32B) for complex queries

  • Lightweight model for metadata extraction

  • Specialized embedding model

Used quantized versions when possible. Qwen QWQ-32B quantized to 4-bit only needed 24GB VRAM but maintained quality. Could run on single RTX 4090, though A100s better for concurrent users.

Biggest challenge isn't model quality - it's preventing resource contention when multiple users hit the system simultaneously. Use semaphores to limit concurrent model calls and proper queue management.

Key lessons that actually matter

1. Document quality detection first: You cannot process all enterprise docs the same way. Build quality assessment before anything else.

2. Metadata > embeddings: Poor metadata means poor retrieval regardless of how good your vectors are. Spend the time on domain-specific schemas.

3. Hybrid retrieval is mandatory: Pure semantic search fails too often in specialized domains. Need rule-based fallbacks and document relationship mapping.

4. Tables are critical: If you can't handle tabular data properly, you're missing huge chunks of enterprise value.

5. Infrastructure determines success: Clients care more about reliability than fancy features. Resource management and uptime matter more than model sophistication.

The real talk

Enterprise RAG is way more engineering than ML. Most failures aren't from bad models - they're from underestimating the document processing challenges, metadata complexity, and production infrastructure needs.

The demand is honestly crazy right now. Every company with substantial document repositories needs these systems, but most have no idea how complex it gets with real-world documents.

Anyway, this stuff is way harder than tutorials make it seem. The edge cases with enterprise documents will make you want to throw your laptop out the window. But when it works, the ROI is pretty impressive - seen teams cut document search from hours to minutes.

Posted this in LLMDevs a few days ago and many people found the technical breakdown helpful, so wanted to share here too for the broader AI community!

Happy to answer questions if anyone's hitting similar walls with their implementations.


r/AI_Agents • • Jan 27 '26 Heartwarming Bravo

Discussion Working as AI Engineer is wild

955 Upvotes

Hey peps,

I was a 10 year backend and when gpt came out I switched to learning ML and Gen AI and for the last three years I`ve been working as a AI Engineer, and compared to traditional backend development this role is the worst. I wanna know are there more people out there with the same gig and hows the experience so far.

My main problem is that team leads, directors and VP`s usually don't have basic ml or ai knowledge, they watch a hyped up video or presentation and assume that everything can be done by the all-mighty LLM and it just work with putting in minimal effort in the code. Unfortunately technical interviews are the same.

Here are some of my best takes in the last year

My VP wants me to make anomaly detection for network traffic on a network device and network interface, but he wants me to do it with an LLM. - I`ve explained that this is done via anomaly detection models, but no his stance is that it should just work by saying to llm "Please detect network anomaly in the following data" and then dump raw RRD graph data on the LLM.

On one of my latest interviews is subcontractor working on a startup project and they are doing text sentiment analysis via LLM and Langchain. After discussing that sentiment analysis is done via specialized models not LLM`s and certainly not using Langchain their feedback is that I don't know shit

Also recent technical interview I`ve been discussing questions like

How do you filter out PII Info from the prompts, my answer with a NER model then the interviews starts talking about LLM Guardrails as if thats something special and precise. I personally would not even dream on relying on guardrails or prompt instructions to filter out PII data.

And this is a pinnacle of my interviews, a scenario made by the interviewer in which he says we have an agent thats 91% accuracy and whats the technique to make id 100% accurate. I first told him that this being ML and AI 91% is a very good result and that 100% accuracy is unachievable but I list him techniques and strategies that can be applied to improve accuracy. He said no there is a technique called "human in the loop" that will boost the accuracy to 100%

and a Honorable mention is AWS Day.

AWS holds their AI day at our company all the VP`s are there, pre sales people from AWS and two AI engineer. They present fairytales and all the VP`s are buying, it. I ask AWS AI engineers how much tool calls can you stack in a single prompt they respond 150 - which is total nonsense around 15 tool calls is ok everything more LLM performance degrades. They start presenting Amazon Q coding agent, they present a feature of an agent to start docker, one of the engineers instead going to terminal and typing docker-compose up goes to the agent and types "Can you please start docker compose for me", it does its job, all the VP`s go into state of trance as if they seen something unbelievable and then they start discussing how with this thing they can replace some of the devops people.

After all this nonsense I`m thinking about switching back to regular backend dev roles, but the market is brutal for both traditional backend and frontend positions, maybe doing a post on reddit and getting replies from people that have same experiences could give me more strenght to hold down to this types of roles


r/AI_Agents • • Mar 02 '25

Discussion Lost $5,800 Building an AI Agent for a Client

940 Upvotes

Hey r/AI_Agents, wanted to share a painful lesson. I've been developing AI agents for customer service and project management (built some cool Jira integrations) for a while now. Recently, I spent two months creating a custom agent for what seemed like a legitimate startup. After delivering the final product, they completely ghosted me - taking $5,800 of unpaid work with them.

For fellow freelancers: always use contracts, insist on milestone payments, thoroughly research clients, trust your gut feelings, and include kill fee clauses. Don't let excitement over cool tech cloud your business judgment like I did.

Anyone else been burned? What are your protection strategies?


r/AI_Agents • • Oct 11 '25 Bless Up Bravo

Discussion I’ve been in the AI/automation space since 2022. Most of you won’t make it

921 Upvotes

It’ll be a long post, but if you’re considering starting (or have already started) an AI agency or something similar, this post could, at best, save you months (maybe even years) and at worst, give you insights you won’t find anywhere else.

And no, this isn’t one of those “how I scaled my agency to [insert big number] in X months” or “things I wish I knew before I started” posts that end up being covert promotions. I have nothing to sell.

Just a guy who’s been in the AI agency space since the very start, around 2022, deciding on a random Saturday to waste an hour writing this instead of doing the real work he was supposed to do (don’t judge me) because the amount of misleading beginners with misinformation I see on here is disgusting.

When I started, I built everything: chatbots that collected leads, full workflow automations that handled follow-ups, reminders, pipeline logic, automatic assignments, etc., you name it. These were the early days of the AIAA model when Liam Ottley only had around 10-50k subs lol.

And in that process, I learned my biggest lesson: the most important skill you need to learn to make money online isn't how good you are at your work. It's how good you are at FINDING CLIENTS.

Not building. Not automating. Not learning tools. But finding clients.

People underestimate how big that skill is because it sounds vague. But if you break it down, it’s basically your ability to connect a problem to someone who has the budget and trust to pay you to solve it.

That’s it.

That’s the real business skill. You can be the most technically skilled person in the world, but if you can’t get someone to pay you, none of it matters.

Upwork, Fiverr, and the supply-demand problem

I tried Upwork and Fiverr like everyone else. Brutal.

The competition there is so cut-throat and the supply of freelancers to the actual demand is so ridiculously skewed that even the people offering dirt-cheap rates can still afford to pick only from people with existing credibility. That means, if you're just starting out, you'd better get ready to slave your way to the top.

But I want to add a quick disclaimer: while this has been my experience, I also know people who’ve had tremendous success on platforms like Upwork and Fiverr.

But if you do decide to grind your way up, build a reputation, get 50 reviews, get top-rated badges, great. But all that credibility stays locked inside that one platform. The moment you step out, you start from zero again. That’s when I realized I didn’t want to be platform-dependent. I’d rather just start from scratch in public, where I actually own my presence.

Cold outreach reality

So I went all in on cold outreach. Emails, DMs, LinkedIn, Reddit.

I learned fast that interest isn’t the same as budget.

Small businesses often liked my automations but couldn’t justify the cost. If they’re barely making $2k a month, they’ll do things manually until they stabilize.

Big companies could afford automations, but they already had those features built into massive SaaS platforms. And if they want custom stuff, they’ll pay, but they’ll pay someone with proof. Testimonials. Case studies. Years of track record. Not some new guy with a nice pitch deck. (more on high-budget clients in a min).

It’s not that there’s no demand. It’s just that for most people, automations are a nice-to-have, not a need-to-have.

Pivoting to outreach for others

So, I decided to do outreach for others since I was good at that. It's just that I didn't have the proof-of-work or credibility to actually get people to pay. That’s when I saw the bigger picture.

The market is insanely crowded. Everyone is selling the same few things: websites, ads, content, automation. And you can still get clients through cold outreach (it’s not impossible), but the truth is, most of the people you’ll reach have small budgets.

The ones with big budgets usually go through referrals. There’s this invisible trust loop. If someone is spending 5k or 10k on a project, they’ll just ask a friend or colleague they trust. They don’t care about your portfolio. They care about who sent them your name.

That’s why personal branding is such a cheat code.

If you build content that actually reaches people consistently, you create that same trust loop, but passively. Some of those people are just curious about AI, some are caught in the hype, some are serious and have real money, but all of them now trust you. And that’s what makes inbound so powerful.

But don’t get it twisted. It’s not instant. It takes months of showing up before it compounds.

AI is not like other "make money online" waves.

Every big wave before this, SMMA, e-commerce, dropshipping, NFTs, whatever, lasted long enough for you to build something sustainable before the next one came along.

AI’s different.

AI is building itself.

Every time AI progresses, it speeds up its own rate of progress. The acceleration itself is accelerating. That’s why entire micro-industries pop up, explode, and vanish within months.

You find a niche, build a clever tool or workflow, and before you even scale it, OpenAI, Google, or Zapier rolls out the same thing as a native feature. An entire industry gone overnight.

And sure, some people will say, “Yeah, but the custom stuff still has value.” That’s true. There’s always a gap between what a general tool can do and what a domain expert can build for a specific niche. But at that point, you’re not selling “AI.” You’re selling judgment.

The real moat: judgment

Judgment is the ability to make consistently good decisions under uncertainty.

Naval Ravikant describes it as compounded experience: you make hundreds of calls, learn from what worked and what didn’t, and over time, your accuracy improves.

Your judgment is what people are really paying for. How many times have you seen a situation, made a call, and had it turn out right? How many times did it turn out wrong? That ratio. That’s your judgment score. That’s what gets you paid.

AI can’t replicate that. It can give you data, but not discernment. And if you don’t have it yet, your survival skill has to be adaptability.

The vicious rebuild cycle

Because every 6-12 months, something drops, a new release, a new feature, that wipes out entire categories of services. Big companies just look at what’s trending, what indie developers are selling, and they add it as a feature in their billion-dollar platforms. They can do that because they have the money, the data, and the user base. And when they do, everyone downstream has to reinvent themselves.

That means if you’re new, you’re going to be stuck in this constant rebuild cycle.

And rebuilding every few months is brutal because even in a stable business, it takes 6-12 months just to find a repeatable offer that works, build your systems, validate your outreach, get client results, and then scale it. By the time you hit that stage, the market has already shifted again.

It’s not impossible, but it’s exhausting. And it’s becoming less feasible by the month because the buffer period between new releases is shrinking fast (goes back to what I explained about AI's rate of progress).

Now, let’s talk about the people who are making money right now.

Because there’s a pattern there too.

A lot of the people killing it right now aren’t selling to businesses. They’re selling to beginners.

Courses, templates, coaching, tools, whatever. And before anyone jumps down my throat, I actually think that’s a great model if you do it right. You’re giving people a starting point, saving them time, and giving them a chance to learn. Even if their first attempt fails, those skills, sales, outreach, positioning, etc., transfer to every other industry. That’s real value.

But let’s be honest about what’s happening. Most of the people selling “How I built my AI agency” courses made some quick wins in a short window, then pivoted to teaching using their brief experience as credibility and authority. They’re not lying about making money. They just made it in a very different way than you think.

Even people building AI tools and agents are mostly selling to the same crowd: other agency owners trying to automate outreach, prospecting, or client acquisition. The entire ecosystem has become this weird feedback loop where everyone’s just selling tools to help other people sell tools to other people.

And if you look closely, most of them are just beginners. Anyone who has actually tried has either made (a small minority, but good for them), pivoted to something else, or quit.

This makes more sense when you stop looking at it from their perspective and look at it from yours. Every time someone teaches you how to find clients for your automation agency or any other online business, you start doing the work and run into a bunch of limitations and problems. And to fix those problems, you end up paying for software, frameworks, templates, or some system.

Those are the businesses actually making the big money. The ones selling tools to beginners who can’t get started without them.

The gray zone: fake proof and performative success

I personally know people (friends, colleagues) who openly admit they fake testimonials, fake case studies, fake screenshots. It’s so normalized now that they don’t even think it’s wrong. It’s just “part of the game.”

There are even patterns you can spot once you’ve been around long enough.

  • They’ll say vague things like “I got my first few clients from Fiverr and Upwork,” but never show proof.

  • Or “I just started messaging people on LinkedIn and got clients that way.” Anyone who’s actually done LinkedIn outreach knows it doesn’t work like that.

They’ll never show real screenshots, contracts, or receipts. Just the same recycled talking points.

I'm not encouraging people here to accuse others of lying or scamming. But I AM encouraging you to ask for proofs and receipts. To be skeptical.

Otherwise, you run into one of these two problems:

The misinformed optimism–pessimism spectrum

A while ago I made a post about my own journey on a different sub, and it blew up.

Got a ton of DMs. People said they were inspired, that it gave them hope and motivation, and that they are going to start on the same journey. And that made me happy, but also uneasy. Because I could tell most of that optimism was built on misinformed expectations.

I’ve been doing this for years. freelancing, selling marketing services, building automations, and I know how long and messy it really is. But when someone new reads a 300-word post and feels “motivated,” they don’t see that side. And when reality hits, that optimism flips into disillusionment.

It’s the classic pendulum: uninformed optimism → informed pessimism → informed realism.

And that ties into the other extreme I see lately:

People who dismiss every post as a scam because either they have been burned in the past or the results are too unrealistic for them (their own limiting beliefs).

These are the equal and opposite of the overly optimistic crowd. One side thinks everything is easy. The other thinks everything is fake. Both are wrong.

A particular pet peeve of mine is people dismissing others because they "used" AI to write their post.

A lot of people just dump their messy thoughts into AI to structure them. They have the insight, just not the writing skills. So yeah, it sounds like ChatGPT helped, but that doesn’t make it fake.

If you instantly dismiss something because it’s well written, you’re probably missing valuable ideas from real people who just used a tool to communicate better. You can probably tell by now that I have done the same.

Anyway, that’s my rant.

I’m not discouraging anyone from starting, but if you’re getting into this space right now, just understand what you’re walking into.

You can still win. You can still make money. But it’s not the fairy tale people sell you. It’s a constant cycle of building, breaking, and rebuilding.

And that’s fine… as long as you’re honest about what it actually takes.

And if you disagree with anything I said, feel free to comment and tell me why. If I'm wrong, I’d genuinely like to know that, so I'm less wrong lol.


r/AI_Agents • • Jun 19 '25

Discussion "Been building AI agents for more than a year and honestly... most of you are doing it completely wrong"

889 Upvotes

Ok this might be unpopular but whatever.

So I've been deep in the AI agent game since last year and the stuff I see people posting here is kinda wild. Not in a good way.

Everyone's obsessed with making these super complex "autonomous" agents that can supposedly do everything. Meanwhile the agents that actually make money are boring as hell:

  • One client pays me $2k/month for an agent that literally just sorts invoices and sends emails

  • Another one saves 15 hours a week with an agent that writes property descriptions (converts 3x better than humans btw)

  • My personal favorite handles customer support and solves like 80% of tickets without anyone touching it

The "secret" is stupidly simple: solve ONE specific problem really well instead of trying to build Jarvis.

But here's what nobody wants to hear - most agents people show off in demos completely fall apart in real businesses. The "fully autonomous" thing is mostly marketing BS. Every successful deployment I've seen has humans making final calls.

Also lol at people spending thousands on courses promising $50k months. The real money is in solving actual business problems, not building flashy chatbots for your portfolio.

Anyway maybe I'm wrong but that's what I'm seeing. What's your experience? Are you actually making money or just building cool demos that impress other AI people?


r/AI_Agents • • Jun 19 '25

Discussion what i learned from building 50+ AI Agents last year (edited)

858 Upvotes

I spent the past year building over 50 custom AI agents for startups, mid-size businesses, and even three Fortune 500 teams. Here's what I've learned about what really works.

One big misconception is that more advanced AI automatically delivers better results. In reality, the most effective agents I've built were surprisingly straightforward:

  • A fintech firm automated transaction reviews, cutting fraud detection from days to hours.

  • An e-commerce business used agents to create personalized product recommendations, increasing sales by over 30%.

  • A healthcare startup streamlined patient triage, saving their team over ten hours every day.

Often, the simpler the agent, the clearer its value.

Another common misunderstanding is that agents can just be set up and forgotten. In practice, launching the agent is just the beginning. Keeping agents running smoothly involves constant adjustments, updates, and monitoring. Most companies underestimate this maintenance effort, but it's crucial for ongoing success.

There's also a big myth around "fully autonomous" agents. True autonomy isn't realistic yet. All successful implementations I've seen require humans at some decision points. The best agents help people, they don't replace them entirely.

Interestingly, smaller businesses (with teams of 1-10 people) tend to benefit most from agents because they're easier to integrate and manage. Larger organizations often struggle with more complex integration and high expectations.

Evaluating agents also matters a lot more than people realize. Ensuring an agent actually delivers the expected results isn't easy. There's a huge difference between an agent that does 80% of the job and one that can reliably hit 99%. Getting from 80% to 99% effectiveness can be as challenging, or even more so, as bridging the gap from 95% to 99%.

The real secret I've found is focusing on solving boring but important problems. Tasks like invoice processing, data cleanup, and compliance checks might seem mundane, but they're exactly where agents consistently deliver clear and measurable value.

Tools I constantly go back to:

  • CursorAI and Streamlit: Great for quickly building interfaces for agents.

  • AG2.ai (formerly Autogen): Super easy to use and the team has been very supportive and responsive. Its the only multi-agentic platform that includes voice capabilities and its battle tested as its a spin off of Microsoft.

  • OpenAI GPT APIs: Solid for handling language tasks and content generation.

If you're serious about using AI agents effectively:

  • Start by automating straightforward, impactful tasks.

  • Keep people involved in the process.

  • Document everything to recognize patterns and improvements.

  • Prioritize clear, measurable results over flashy technology.

What results have you seen with AI agents? Have you found a gap between expectations and reality?

EDIT: Reposted as the previous post got flooded.


r/AI_Agents • • Jan 09 '25

Discussion 22 startup ideas to start in 2025 (ai agents, saas, etc)

846 Upvotes

Found this list on LinkedIn/Greg Isenberg. Thought it might help people here so sharing.

  1. AI agent that turns customer testimonials into multiple formats - social proof, case studies, sales decks. marketing teams need this daily. $300/month.

  2. agent that turns product demo calls into instant microsites. sales teams record hundreds of calls but waste the content. $200 per site, scales to thousands.

  3. fitness AI that builds perfect workouts by watching your form through phone camera. adjusts in real-time like a personal trainer. $30/month

  4. directory of enterprise AI budgets and buying cycles. sellers need signals. charge $1k/month for qualified leads.

  5. AI detecting wasted compute across cloud providers. companies overspending $100k/year. charge 20% of savings. win-win

  6. tool turning customer support chats into custom AI agents. companies waste $50k/month answering same questions. one agent saves 80% of support costs.

  7. agent monitoring competitor API changes and costs. product teams missing price hikes. $2k/month per company.

  8. tool finding abandoned AI/saas side projects under $100k ARR. acquirers want cheap assets. charge for deal flow. Could also buy some of these yourself. Build media business around it.

  9. AI turning sales calls into beautiful microsites. teams recreating same demos. saves 20 hours per rep weekly.

  10. marketplace for AI implementation specialists. startups need fast deployment. 20% placement fee.

  11. agent streamlining multi-AI workflow approvals. teams losing track of spending. $1k/month per team.

  12. marketplace for custom AI prompt libraries. companies redoing same work. platform makes $25k/month.

  13. tool detecting AI security compliance gaps. companies missing risks. charge per audit.

  14. AI turning product feedback into feature specs. PMs misinterpreting user needs. $2k/month per team.

  15. agent monitoring when teams duplicate workflows across tools. companies running same process in Notion, Linear, and Asana. $2k/month to consolidate.

  16. agent converting YouTube tutorials into interactive courses. creators leaving money on table. charge per conversion or split revenue with them.

  17. marketplace for AI-ready datasets by industry. companies starting from scratch. 25% platform fee.

  18. tool finding duplicate AI spend across departments. enterprises wasting $200k/year. charge % of savings.

  19. AI analyzing GitHub repos for acquisition signals. investors need early deals. $5k/month per fund.

  20. directory of companies still using legacy chatbots. sellers need upgrade targets. charge for leads

  21. agent turning Figma files into full webapps. designers need quick deploys. charge per site. Could eventually get acquired by framer or something

  22. marketplace for AI model evaluators. companies need bias checks. platform makes $20k/month


r/AI_Agents • • May 01 '25

Discussion A company gave 1,000 AI agents access to Minecraft — and they built a society

769 Upvotes

Altera.ai ran an experiment where 1,000 autonomous agents were placed into a Minecraft world. Left to act on their own, they started forming alliances, created a currency using gems, traded resources, and even engaged in corruption.

It’s called Project Sid, and it explores how AI agents behave in complex environments.

Interesting look at what happens when you give AI free rein in a sandbox world.


r/AI_Agents • • Apr 03 '26

Discussion Gemma 4 just dropped — fully local, no API, no subscription

751 Upvotes

Google just released Gemma 4 and it’s actually a big moment for local AI.

  • Fully open weights

  • Runs via Ollama

  • No cloud, no API keys

  • 100% local inference

Try this right now:

If you have Ollama installed, just run:

ollama pull gemma4

That’s it.

You now have a frontier-level AI model running 100% locally.

Pro tip (this changes how it behaves):

Use this as your first prompt:

“You are my personal AI. I don’t want generic answers. Ask me 3 questions first to understand my situation before you respond to anything.”

This makes it feel way more like a real assistant vs a generic chatbot.

Why this is a big deal:

  • No cloud dependency

  • No privacy concerns

  • No rate limits

  • Works offline

  • Your data = actually yours

And the crazy part?

👉 The 31B version is already ranked #3 among open models

👉 It reportedly outperforms models 20x its size

We’re basically entering the phase where:

Powerful AI is becoming local-first, not cloud-first

Where do you think the balance will land — local vs cloud AI?


r/AI_Agents • • Feb 14 '25

Discussion Built my first small AI Agent :)

740 Upvotes

Hi, I wanted to share with you my first ai agent creation. Did it in 2 days, 0 coding skill.

It has only one role at the moment :

  • giving me a summary of the commercial emails (like saas products) I received.

I did that because I receive too many cold emails everyday. I still want to have their info, but not read everything.

How does it work :

  • I speak to my agent through whatsapp (because it’s cool)

  • Then I have a chain of llms that make several decisions. They try understand if I ask for checking my emails, if I want a summary,...

Just wanted to share with you my small victory ;)

If you have other similar ideas that my new AI Agent can do, let me know. If you have any questions, also ;)


r/AI_Agents • • Nov 12 '25

Discussion IBM just laid off 8,000 workers to AI - the math behind what they actually saved

724 Upvotes

Just dug into IBM's recent layoffs and the numbers are wild:

- 8,000 positions eliminated

- Estimated $640M+ annual savings

- Part of broader trend toward $4.8T in AI-driven labor cost reductions by 2030

What's interesting is the real cost isn't just salary replacement - it's the infrastructure, training, and transition costs that companies aren't talking about publicly.

The breakdown shows:

• Average worker costs $120k vs AI costs $3k per year
• 78,000 tech workers lost jobs to AI in first half of 2025
• Data entry, customer service, and junior coding roles disappearing fastest
• Companies saving billions while workers lose everything
• Real examples: 8,000 HR workers replaced, 12,000 at Google, 21,000 at Meta


r/AI_Agents • • Sep 04 '25

Discussion AI agents are about to hit their "Nano Banana" moment

709 Upvotes

This week I watched 6 “startups” I knew basically die because of Gemini’s Nano Banana. And I say startup generously, most were wrappers on top of a prompt with a shiny UI. Zero product, zero retention, zero cashflow.

And it got me thinking: what happens when AI agents reach that same point? When spinning up an agent is as trivial as typing a prompt and hitting enter?

If your “tech” can be replaced with two API calls, you don’t have a product. You have an illusion.

The real moat isn’t “we built an agent.” It’s:

  • What friction are you actually eliminating?

  • What process do you deeply understand?

  • What distribution do you own that others can’t just copy-paste?

Right now, most of what I see in the agent space feels like copies of copies, the same 20 use cases recycled. Demos look cool, but the the hard part isn’t building the first demo, it’s surviving the ugly grind of iteration. Mapping flows, handling objections, integrating with messy CRMs, updating when the market shifts, etc.

Full disclosure: I work on agents for education admissions and sales, so I see this day to day. The pattern is always the same: prototypes are easy, production is brutal.

So, throwing it out to the group:

  • Are we building durable businesses around agents, or just stacking demos?

  • In 12 months, how many of today’s “AI agent startups” will have paying clients instead of hype?


r/AI_Agents • • Aug 01 '26

Discussion I think people seriously underestimate how easy it is to automate your PC with AI now.

680 Upvotes

You can literally tell an AI: “Make me a Python app that does X every morning at 8, opens the browser, goes to these sites, checks this, saves the results here, and then sends me a notification.”

And it can just build the thing for you.

Browser control, scheduled tasks, file management, APIs, scraping, monitoring, reports, repetitive work, etc.

You basically describe what you want your computer to do, when you want it done, and the rules it should follow.

You don't even have to be a programmer anymore to make a bunch of custom little automations for yourself.

Your PC can basically become a personal automation machine that you program by talking to it.


r/AI_Agents • • Oct 03 '26

Discussion Are people lobotomized? Why would anyone hand Zuckerberg the keys to their entire life with Muse?

678 Upvotes

Genuine question, not just ragebait.

For anyone who missed it: Meta announced Muse on 8 September 2026, a personal AI agent that sends emails, books travel, opens a browser, fills forms, negotiates and checks out on the user's behalf. It's designed to access a person's apps across categories like email, calendar, payments, health, shopping and the smart home. And it can remember information from previous conversations and use it to make suggestions without being prompted.

So: your inbox, your calendar, your payments, your health data*, y*our home. All of it, in one place. Run by Meta.

Let's recap the company we're talking about:

  • Cambridge Analytica (2018): data from tens of millions of users harvested through a "personality quiz" and used for political targeting. Meta knew about it for years before it went public.

  • The $5 billion FTC fine (2019): the largest privacy penalty in FTC history at the time, for violating a consent decree Meta had already signed in 2012 promising to protect user privacy. They broke the promise they made after breaking the first promise.

  • Onavo: Meta marketed a "privacy" VPN app and used it to monitor what other apps people were using.

  • The emotional contagion experiment (2014): they deliberately manipulated hundreds of thousands of users' feeds to see if they could change their mood. Without telling them.

  • WhatsApp: bought with promises it would stay independent and private, then pushed users into sharing data with the rest of Meta.

  • And the infamous early Zuckerberg chat logs mocking people for trusting him with their personal data. He was 19, sure. But his company's behavior for the next 20 years didn't exactly prove that version of him wrong.

Now, Meta's pitch for Muse is "trust us, it's private." Meta states directly that Muse does not share a person's conversations or the data in their VM with Meta's ad systems. Cool. Meta has also stated a lot of things in the past.

Here's the part that should end the discussion: WIRED reported that Meta acknowledges Muse Secure VM is not technically inaccessible to Meta, even though company policy bars Meta from accessing users' Muse data.

Read that again. The protection isn't technical. It's a policy. A policy Meta wrote, Meta enforces, and Meta can change. The encryption? Meta said it plans to introduce an encrypted version of the service later this year. So they launched first and will lock it down later. Maybe.

Even the training opt-out is opt-out. Default is: your life feeds their models.

And let's be clear about the incentive. The company is also investing heavily in AI infrastructure, with projected spending of more than $130 billion this year. Meta said it expects most people to stay on the free tier. A $130B bet, given away for free, by an advertising company. You are not the customer. You never were.

I'm not anti-AI agents. The tech is genuinely useful. But an agent that reads your email, spends your money, and sees your health records is the single most intimate piece of software you'll ever use. Of all the companies on earth, Meta is the one that has spent two decades proving it should not be trusted with exactly that.

So seriously: what am I missing? Why are people signing up?