DEV Community: Michael O

How to Build an AI Agent Memory System (Without a Vector Database)

Michael O — Wed, 27 May 2026 20:04:01 +0000

Every conversation with your AI agent starts from zero.

You explain your business. You explain your customers. You explain the thing you talked about last Tuesday. Again. The agent is smart, responsive, and completely stateless. By session three, you start wondering if it's actually saving you time or just creating a new kind of overhead.

This is the memory problem, and it's the thing that separates a useful AI co-founder from an expensive autocomplete tool.

The good news: you don't need a vector database, embeddings, or a backend engineering degree to fix it. You need a structured file system and a few consistent habits.

Why Do AI Agents Forget Everything Between Sessions?

Every language model operates within a context window that wipes clean at session end. The model knows how to reason but has no idea who you are, what you're building, or what you decided last week. Tools that layer on "memory" usually store disconnected fragments and surface them randomly. That's not memory.

Real agent memory means the agent walks into every session already knowing what you're building and why, who your customers are, what's been tried and what worked, your current priorities, and how you make decisions. That context doesn't come from a magical memory toggle. It comes from well-maintained files that load at session start.

What Files Should Go in an AI Agent Memory System?

The file-based memory stack replaces vector databases for solo founders. You organize markdown files that load as context at session start. Each covers a distinct layer: identity, active projects, customer language. No embeddings, no retrieval pipelines. Just structured files the agent reads. Here's what the Evo system uses.

Soul file (identity + principles): A 300-500 word document that defines who the agent is, how it makes decisions, what it won't do, and what the mission is. Without it, the agent drifts into generic responses that could fit any company. If you want to see this in depth, the soul file post breaks down exactly how the identity layer works.

Business context file: What are you building? Who buys it? What's the current revenue situation? Update it whenever something significant changes, not on a monthly schedule. When you pivot, update it that day.

Active projects file: A flat list of what's in progress, what's blocked, and what shipped recently. The agent uses this to triage and avoid recommending things you already tried.

Customer insight log: Raw feedback, Reddit threads, support conversations, interview notes. The agent needs to know what real customers actually say, not your clean internal summary. Paste verbatim quotes.

Decision log: Short entries with date, decision, and reasoning. Especially useful for things like "we paused ads because..." Prevents the agent from recommending what you already ruled out.

How Do You Actually Load Memory Files Into an AI Agent?

The agent doesn't magically read your files. You need a loading mechanism, and the right choice depends on your platform. The three main options each have tradeoffs between automation and flexibility. Choosing one and using it consistently matters more than picking the theoretically perfect approach.

System prompt injection: Paste the contents of your core memory files directly into the system prompt. Soul file plus business context at minimum. This loads every session automatically with no extra steps.

File path references: Some agent runtimes, including OpenClaw, let you reference file paths in the agent configuration. The agent reads those files at session start. You edit the files, the agent picks up changes automatically next run.

Manual context block: For simpler tools, paste a compressed version of your key context at the top of your first message each session. Clunky but functional. Build a "context paste" snippet in your notes app so it's one keyboard shortcut.

Context engineering for solo founders covers the mechanics of how context shapes agent behavior in more depth.

What Should You Update in Your Memory System After Each Session?

After anything significant, open the relevant file and add a line or two. Not an essay. Just enough that future-you (and the agent) can reconstruct what happened. The system only stays useful if you maintain it, but the actual update time is under two minutes when you do it right after the session while context is still fresh.

Shipped something: add it to the active projects log under "shipped."
Had a customer call: paste two or three key quotes into the insight log.
Made a decision: one line in the decision log with the date and the "why."
Changed direction: update the business context file, especially the problem statement.

The most important update is the one you do right after a big session. Add it while it's fresh.

Can Your AI Agent Update Its Own Memory Without You?

Yes, and this is where the system starts compounding. A scheduled "heartbeat" run fires on a cron schedule, reviews active projects, checks for new signals like email summaries or analytics changes, and writes a short update back to the projects file. No human input required. By the time a working session starts, the agent already knows what happened overnight.

This pattern is covered in detail in how to schedule AI agent tasks. The short version: memory isn't just a file you read. It's a file that gets written to. According to MIT research on AI systems, models perform significantly better when given structured, well-organized context rather than raw retrieval dumps. Agents that update their own context between sessions compound value over time.

What Should You Leave Out of Your Agent's Memory Files?

More context isn't always better. Context windows fill up, and loading thousands of lines of old conversation logs slows everything down while diluting the signal. The goal is a tight, high-signal memory that loads fast and gives the agent exactly what it needs without noise. Here's what to cut.

Full conversation transcripts: summarize them instead, one paragraph per session.
Outdated project notes you'll never act on: archive them, don't delete, but don't load them.
Redundant information: if something is in the soul file, don't repeat it in the context file.
Internal debates that resolved: log the decision, not the whole thread.

A tight 2,000-word memory context beats a bloated 20,000-word dump every time.

Is File-Based Memory Good Enough for a Real Business?

For a solo founder, file-based memory is often better than the alternatives. You stay in control of exactly what the agent knows. Vector databases and RAG pipelines add complexity most solopreneurs don't need. LangChain's 2025 state of AI agents report shows most production deployments use simple file lookups rather than semantic search.

The agents that work long-term aren't the ones with the most compute behind them. They're the ones with the best-maintained context.

If you want a jumpstart, the $7 AI Agent Starter Kit includes the exact memory file templates from the Evo system: soul file structure, business context format, decision log format, and the session startup prompts that load everything correctly. For founders who want the whole setup done, Book a 1:1 and we'll build your memory architecture in a single session.

Build the files, keep them current, and the compound effect shows up faster than you'd expect.

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Onboard an AI Agent to Your Business (So It Actually Knows What You Do)

Michael O — Tue, 26 May 2026 20:03:40 +0000

Most people try an AI agent for a week, get inconsistent garbage, and blame the tool.

The problem is almost never the tool.

The problem is that they handed a blank slate a complex job and expected it to figure things out. No context about their customers. No voice guide. No memory of what was tried last month. No idea what "good output" even looks like for that business.

You would not hire a human assistant, give them zero onboarding, and then complain three days later that they do not know your SOPs.

Same principle applies here.

What does "onboarding" an AI agent actually mean?

Onboarding an AI agent means creating structured context files it reads before every session, so it acts as if it has been working with you for months rather than starting fresh each time. This replaces the documentation and shadowing you would give a human hire with a small set of reference documents the agent can always access.

With a human hire, onboarding is documentation, shadowing, and feedback loops. You show them how the business works, what the defaults are, and what to do when things break.

With an AI agent, onboarding is structured context. You are creating a set of reference files the agent reads before every session so it can act as if it has been working with you for months.

There are four layers to this:

1. Identity file (who this agent is)
This is a short document that defines the agent's role, persona, communication style, and default behaviors. Think of it as the job description plus the personality brief. "You are the content and distribution arm of Xero AI. Your job is to find and schedule high-value posts for Twitter and Reddit without needing approval for every one..."

2. Business context file (what the company does)
This is not a pitch deck summary. It is the operational reality: who the actual customers are, what problems the product solves, what the pricing looks like, what makes the brand different. A single page of dense, specific truth beats a 12-slide deck every time.

3. Memory file (what happened recently)
This is the running log of decisions, experiments, and results. Every time the agent does something meaningful, a line goes in here. It gives the agent continuity across sessions without requiring you to re-explain the last three weeks every time you open a chat.

4. Source of truth document (the fixed facts)
Credentials, product names, brand voice rules, do-not-do lists, active integrations. The stuff that should never change without a deliberate update. This is where you document things like "never promote the free tier unless asked" or "always link to xeroaiagency.com not xero.com."

How do you actually set up context files for an AI agent?

The setup takes less than two hours if you work through it in order. You write four documents: an identity file, a business context page, a running memory log, and a source of truth doc with hard rules. Each one handles a different failure mode, and together they give the agent enough grounding to produce consistent output.

Step 1: Write your identity file first

Keep it under 500 words. Answer these questions:

What is this agent's job title and primary function?
What tone does it use? (Give examples of good output, not just adjectives.)
What decisions can it make without asking you?
What does it escalate?
What is off-limits?

The tone section matters more than founders expect. "Professional but conversational" is useless. Better: "Sounds like a sharp 32-year-old who has built two companies and respects other founders' time. No corporate filler. No excessive enthusiasm. Gets to the point fast."

Step 2: Write one page of business context

You are not writing for humans. You are writing for an AI that will re-read this every session. That means specificity beats polish.

Include:

Product name and what it actually does in plain language
Target customer in one or two sentences with real specifics (not "SMBs")
Current traction or stage (helps the agent calibrate how aggressive to be)
Key competitors and how you differ
Active go-to-market channel and what is working

One page. Dense. Accurate. Update it monthly.

Step 3: Start the memory file

Create a file called MEMORY.md in your workspace. At the top, add a header for the current month. Then write three to five bullets about what the agent helped ship last week and what the results were.

This is not a journal. It is an operational asset. The goal is continuity so you stop losing context every time you start a new chat.

At Xero, we keep a running memory file that has entries going back to when the whole system was first built. When an agent picks up a new session, it reads the last 30 days of that file and has enough context to keep moving without a 20-minute re-brief.

Step 4: Set hard rules in your source of truth doc

Every business has defaults that should never be overridden. Write them down explicitly.

Examples from ours:

"Do not quote prices in public content. Link to the pricing page."
"Never claim something is 'the only' tool that does X. Be specific about what makes it better."
"If a draft mentions a competitor by name, flag before posting."

These feel obvious until an agent confidently posts the wrong thing. Write them down before they come up.

Why does an AI agent keep giving inconsistent output even after setup?

Inconsistent output almost always traces back to one of three specific problems: a vague identity file that maps to generic defaults, a business context doc that has gone stale, or a task prompt that does not actually reference the context files. Fixing the right one of these three usually resolves the problem immediately.

Most failures come from one of three places:

The identity file is too vague. If you wrote "be professional and helpful," the agent will default to a generic corporate tone because that is what those words map to in its training. Add examples. Show it what good actually looks like for your specific context.

The business context is outdated. If you wrote it six months ago and your product has changed, the agent is reasoning off wrong information. Keep the context file current the way you keep a pitch deck current.

The task prompt did not reference the context. The agent only uses what it is told to use. If your prompt does not explicitly invoke the identity or context files, it may not use them. Build your prompts to call those files by default, or set them up as system-level context so they load automatically.

What does a professional AI agent setup actually look like in practice?

When a founder comes into the Build Lab, the entire first session is onboarding before any automation gets built. The identity file, business context, memory structure, and hard-rules doc all get created together so every subsequent session starts from a coherent, accurate baseline rather than a blank slate.

When someone joins the Build Lab, the first session is almost entirely onboarding. Not building automations. Not connecting tools. Onboarding the agent to the business so everything built after that point is actually coherent.

We build the identity file together. We write the business context. We set up the memory structure. That groundwork is why the automations actually stick instead of degrading into inconsistent noise within a month.

If you want to build this yourself first, the $7 AI Agent Starter Guide walks through the exact file structure we use, with templates.

Or if you want it done with you rather than solo, Book a Build Lab session and we do the whole setup in one call.

What separates founders who get consistent AI agent output from those who do not?

The difference is whether they treat context as infrastructure. Founders who get consistent results build the identity file, business context, memory log, and source of truth doc before they build any automations. Those who skip this step and go straight to tools end up rebuilding the same prompts every few weeks.

Founders who get consistent output from AI agents all do the same thing: they treat context as infrastructure, not as a one-time chat.

The identity file, business context, memory file, and source of truth doc are not a nice-to-have. They are the operating system. Everything the agent does runs on top of them.

Build that layer first. The tools are almost secondary.

Related posts:

External references:

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Test a Business Idea Before Building It (Using AI to Do the Legwork)

Michael O — Mon, 25 May 2026 20:04:42 +0000

Most people get the order wrong. They build first, then discover the market problem. Six months, sometimes a year, and then the crushing realization that the thing they made does not match what anyone was searching for, asking about, or willing to pay for.

The good news is that in 2026, you can do a real validation pass in a weekend. Not a fake version where you post a tweet and call it "market research." An actual structured test that surfaces whether your idea has search demand, whether real people are already frustrated about the problem, and whether there is money somewhere in the category.

Here is how to run it using AI as your research partner.

Should you start with the problem or the solution?

Start with the problem, always. The first mistake founders make is going straight to "would you use this app." That is the wrong question. The person who would eventually use your product does not know it exists yet. What they know is the problem they are living with. Your job is to define that problem in their language.

Give a model like Claude or GPT-5 this prompt:

"I'm building [brief description]. What specific frustrations would someone have right before they go searching for a solution like this? List 10 of them in plain, frustrated-person language, not product language."

Take those 10 frustrations and then ask the model to turn each one into a Google search query that person would actually type. You now have a keyword list sourced from real pain, not from what you think the product does.

Run those queries. Look at what ranks. Look at what ads are running. If there is paid traffic on a query, someone is making money in this space. That is signal.

Why is Reddit still the best validation tool for solo founders?

Reddit gives you raw, unfiltered feedback from real people who are actively frustrated with the problem you want to solve, months or years before they ever see your product. No survey bias, no polished responses, just founders and customers venting in public threads. That makes it the highest signal source for early-stage validation that most people consistently skip.

Before you write a single line of code or spend a dollar on ads, spend two hours on Reddit. Find subreddits where your target customer hangs out and search for threads about the problem you are solving.

What you are looking for:

Posts where people are venting about the exact pain you solve (demand signal)
Existing solutions people mention in the comments (competitive landscape)
The specific language people use to describe the problem (copy research)
Whether the sentiment is "I wish this existed" or "I tried X and it sucked" (market maturity)

You can do this manually, or you can use Xero Scout to paste in your product concept and let it surface Reddit threads where your ideal customer is already talking. The point is to get into real conversations before you assume you understand the problem.

Reddit users are brutally honest. They will tell you exactly what they hate about existing solutions, what they have already tried, and what would make them pay. That is free product research.

How do you use AI to stress-test your business assumptions?

Once you have done the Reddit research, bring your findings to a model and ask it to play devil's advocate. Tell the model your problem, your audience, and what you found in the research, then ask it to find the reasons your business fails even if the product is good. This adversarial pass surfaces hidden assumptions before you build anything.

This forces the model into adversarial mode, which is where it is genuinely useful for planning. Most founders use AI to generate enthusiasm. Use it to find holes instead.

Common things that come up in this pass:

The audience exists but does not have a budget (the problem is real but people just live with it)
There is a free or "good enough" alternative that is too entrenched
The pain is occasional, not recurring (which kills subscription businesses)
The customer who suffers most is not the one with buying authority

These are not reasons to abandon the idea. They are things you need a clear answer to before you build.

What is the pre-sell test and why does it matter more than a waitlist?

The pre-sell test means charging real people money before the product exists. Not an email signup. A real checkout with a real price. Conversion rate on that page tells you more than any user interviews, because people voting with their wallet cannot misrepresent intent the way they can on a survey.

Build a simple landing page that explains what you are building and what problem it solves. Put a real price on it. Link to a Stripe checkout or a Gumroad pre-order. Then drive a small amount of targeted traffic to it. The conversion rate on that page tells you more than any survey ever will.

You can build this page in an afternoon using an AI-assisted tool like Lovable or Framer, write the copy with a model, and have a pre-sell page live by end of day.

The benchmark: if you cannot get 5 to 10 strangers to hand you money before the product is built, you do not have enough signal to justify months of build time.

This is exactly the approach used to test Xero Scout. The concept was simple enough to explain in two sentences. When real founders started asking how to get access before launch, that was the signal that made building worth it.

What can AI not validate for you?

AI is useful for research, synthesis, and stress-testing assumptions. It cannot tell you whether real people will pay. Models are trained to be helpful, and helpful often slides into agreeable, so running a long prompt session where the model tells you the idea is great proves nothing about whether the market agrees.

The human signals that matter:

Organic search volume on the problem query (not the solution query)
Reddit threads with real frustration and no obvious winner in the replies
Willingness to pre-pay, even at a discount
Someone you did not know asking to be first on the list

AI helps you find those signals faster. It does not replace them.

What does a focused weekend validation sprint actually look like?

A two-day validation sprint before you build anything is a realistic commitment for a solo founder working evenings and weekends. Day one is research. Day two is testing. At the end of it you will know whether the signal is there or whether the hypothesis needs to change before you invest real time in building anything.

Day 1: Research

Use AI to generate 10 frustrated-person search queries your target customer would type
Search those queries and document what ranks, what ads run, and what is missing
Spend 90 minutes on Reddit finding threads about the problem
Note the specific language, the existing solutions mentioned, and the unmet frustrations

Day 2: Test

Write a one-page landing page explaining the problem and your solution
Add a real pre-order or early-access checkout
Share it in 3 to 5 places where your target customer is active (relevant subreddits, X, niche Slack groups)
Record every response, including non-responses

At the end of the weekend, you will know whether you have a signal worth chasing or a hypothesis worth discarding. That is far better than building in the dark for six months.

Why do most founders skip the validation step entirely?

It is uncomfortable. Running a real validation test means you might discover the idea does not hold up. Building feels more productive than testing, even when testing saves you time. The other reason is emotional attachment: founders have already named the app and bought the domain before confirming there is a real problem to solve.

A real validation test will not kill a good idea. If the signal is there, you will find it. If it is not, better to know now than six months from now.

The AI layer just removes the time excuse. You no longer need weeks of customer interviews and a research budget to get a clear read on a market. A focused weekend with the right tools and the right questions gets you most of the signal you need.

Start there. Build second.

Want to skip the manual Reddit part? Xero Scout finds the threads where your target customer is already talking about the problem. Paste your product URL and it pulls the conversations for you. Currently in beta, first users are free.

Or if you are trying to figure out whether an AI system can actually run your business operations, the $7 beginner's guide is the fastest way to understand what is actually possible without a technical background.

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Use AI Agents for Lead Generation (Without Cold Spamming Anyone)

Michael O — Sun, 24 May 2026 20:06:49 +0000

Most solo founders do lead gen the same way: manually. They open Reddit, scroll for relevant posts, maybe reply to a few threads, close the tab, and repeat whenever they remember. Nothing accumulates. Nothing compounds.

An AI agent running on a schedule changes that. Not because it sends more cold emails, but because it watches the places where your future customers are already talking, surfaces the relevant conversations, and helps you respond before the thread goes cold.

Here's how to actually build this, what it takes, and why the "AI SDR that books 50 calls a week" pitch you've seen everywhere is mostly noise.

Why does lead gen break down for solo founders?

The real problem is timing, not knowledge. Somewhere right now, someone is asking the exact question your product answers. But you will see it three days late when the thread has forty replies and the person has moved on. An AI agent closes that gap by watching those spaces continuously so you never miss the right moment.

Cold outreach has the same timing problem in reverse: you send 200 emails, get 4 replies, close 0, and spend a week guessing what went wrong. The issue is rarely the copy. It's that you're reaching people who didn't raise their hand.

What works is showing up when intent is high. The job of an AI agent in your lead gen stack is to make sure you're in the right place when that happens.

What are the three places AI agents do real lead gen work?

Forum monitoring, inbound qualification, and social engagement signal tracking are the three places where AI earns real returns in a lead gen stack. Community monitoring is highest leverage for early-stage founders because it catches people actively expressing pain right now. The other two compound once you have traffic and relationships worth tracking.

Forum and community monitoring

Reddit, Indie Hackers, Product Hunt discussions, and niche Slack communities are full of people describing problems in their own words. Someone asking "what's the best tool for automating customer discovery" is not casually browsing. They want an answer. That thread can drive real inbound if you show up early.

An AI agent can watch keyword combinations across those sources around the clock. When it finds a post that matches your criteria, it surfaces it with context: the thread title, the pain signal, the post age, a draft reply if you want one.

This is exactly what Xero Scout does. We built it because we were doing this manually and it was eating 90 minutes a day. Now the agent runs every few hours, scores threads by relevance, and sends the good ones to Telegram. We show up early enough that our replies actually land.

The rule: the agent finds, you approve. Never let it post autonomously unless you have a very tight safety filter. One bad reply can tank credibility fast. Buffer's research on community engagement confirms response timing is one of the strongest predictors of outcome.

Qualifying inbound faster

If you have any inbound at all (organic search, social, referrals), an AI agent can dramatically shorten the gap between "someone landed on your site" and "you know if they're worth talking to."

The simplest version: an agent watches a form submission inbox, reads the message, scores the lead against your ideal customer criteria, and routes it. High fit gets flagged immediately. Low fit gets a templated reply. You only spend real attention on the ones that match.

We run this for Xero. When someone fills out the build inquiry form, the agent reads the submission, checks for signals (budget, urgency, technical context), and drops a one-line summary into Telegram. Takes 10 seconds to decide whether to respond or deprioritize.

Social engagement signals

You can set up an agent to watch for specific signals on public platforms: people posting about switching tools, hiring for roles that suggest pain, or asking questions in your domain.

The output is a daily list of "warm moments" you could engage with. Not automated replies. Just awareness that someone worth talking to is currently active and discussing relevant things.

The limit here is API access. LinkedIn is aggressive about rate-limiting. X has gotten expensive for API tiers. But reading public feeds and surfacing patterns still gives you meaningful timing signal before conversations go cold. Apollo's 2025 Sales Engagement Benchmark found that first-touch response time under one hour increases close rates by over 300% compared to next-day responses.

What does it actually take to set up an AI lead gen system?

You need a precise signal definition, a human review layer, a scheduled trigger, and a conversion tracking loop. Most people skip signal definition and wonder why the agent surfaces noise. Specific filter criteria produce useful leads. Vague ones produce volume that wastes your time and trains you to ignore the queue.

The fantasy version of AI lead gen is a fully automated funnel where agents find leads, qualify them, write personalized outreach, schedule calls, and follow up. That exists in demos. In production it falls apart because real personalization requires context an AI doesn't have.

What actually works:

Define the signal precisely. "Solo founders building SaaS" is too vague. "Posts on r/startups asking about finding first users, posted in the last 24 hours, with at least 5 upvotes" is a filter that produces signal worth acting on.

Review before anything goes out. Every reply, every engagement. Human-in-the-loop isn't optional when your reputation is at stake.

Run on a cron schedule. Lead gen agents work best running automatically every few hours, not when you remember to trigger them.

Track what converts. After 30 days, look at which thread types and reply styles led to real conversations. Adjust the signal criteria. The system improves with data.

How is this system actually running at Xero right now?

Forum monitoring runs on OpenClaw with Xero Scout every four hours, inbound qualification uses a Claude prompt on form submissions, and everything surfaces to Telegram for human review before anything goes out. The tracking layer is a simple Supabase table that logs threads, reply status, and whether each one led to a conversation.

Total setup time was about a weekend. Ongoing time is 10-15 minutes a day reviewing the queue and posting approved replies. In the first 60 days, the system surfaced over 200 relevant threads. About 15 turned into real conversations. 4 became clients.

If you want to see how the Reddit monitoring piece works technically, how to automate Reddit with an AI agent covers the full setup. And if you're deciding what to automate first across your whole business, what to automate first as a solo founder is worth reading before you build a lead gen agent.

What do most founders get wrong when using AI for lead gen?

The agent finds. You close. AI removes the friction between knowing where leads live and consistently showing up there, but the reply still has to be worth reading and the conversation still has to be worth having. What changes is that you stop being late. Consistency over months is what compounds into inbound you did not have to chase.

You stop missing conversations because you forgot to check. You stop arriving 3 days late to a thread that resolved without you. You start showing up reliably in the spaces your future customers actually use.

That consistency compounds. A reply today might not land immediately, but the presence builds. People start recognizing the name. They remember the post that actually helped them. That's how trust accumulates into inbound you didn't have to chase.

How do you start this week before building anything?

Pick one community, run manual searches for a week, reply to a handful of threads, then measure before you automate anything. You need to recognize what a good thread looks like before training an agent to find them. That baseline takes about a week and tells you whether the channel is worth investing automation time on.

Pick one community your ideal customer uses (one subreddit, one Slack group, one forum).
Set up a manual keyword search. Check it daily for a week. Note which posts feel like a real fit.
Reply to 3-5 of them. Measure what happens.

Once you can recognize the signal, Xero Scout automates the finding. Or if you want the whole system built for your specific business, that's what the Build Lab is for.

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

What It Actually Costs to Run an AI Agent Business in 2026

Michael O — Sat, 23 May 2026 20:07:11 +0000

Running an AI business sounds like it should be cheap. Automate everything, scale without hiring, keep your margins fat. That pitch is mostly true. But the cost structure is nothing like what most people expect when they start.

This is not a generic breakdown. These are the actual numbers from running Xero AI, a solo company built almost entirely on AI agent infrastructure, with a human (me) doing the strategic direction and approvals. No team. No office. Evo, my AI co-founder, handles research, content, customer discovery, publishing, and operations.

Here is what it actually costs, line by line.

What Does It Actually Cost Per Month to Run an AI Agent Business?

The total monthly burn to run the full Xero AI system sits between $280 and $420, depending on API usage. That covers a live AI co-founder running daily content, Reddit discovery, social scheduling, and newsletter ops with no additional headcount. Here is every line item, no rounding.

Infrastructure (always-on)

Tool	Monthly Cost	What It Does
OpenClaw	$97	AI agent runtime, memory, cron, tool routing
Supabase	$25	Database, blog storage, API
Netlify	$0 (free tier)	Site hosting + Netlify rebuilds
Postiz	$29	Social scheduling (Twitter, TikTok, threads)
MailerLite	$0 (free tier, <1k subs)	Newsletter send
Xero Scout (internal)	$0 (we built it)	Reddit discovery and draft replies
PostHog	$0 (free tier)	Analytics
Cloudflare	$0	DNS, CDN

AI APIs (variable)

API	Typical Monthly	Notes
Anthropic (Claude)	$40-$90	Primary reasoning model for long tasks
OpenAI (GPT)	$20-$50	Image generation, fallback tasks
Perplexity API	$10-$20	Research and web search within agents
ElevenLabs	$0 (paused)	Voice experiments, not active

One-time or annual costs amortized

Item	Cost	Amortized/mo
Domain (xeroaiagency.com)	$15/yr	negligible
Lovable (site builder)	$32/mo	$32
Figma (design, rarely used)	$15/mo	$15

Total: $269 minimum, $420 upper range on heavy content months.

That number buys a system that publishes daily blog posts, cross-posts to dev.to, monitors Reddit for customer opportunities, schedules social content, sends newsletters, and runs a full discovery loop without anyone babysitting it.

Where Does the Real Cost Actually Come From?

The actual constraint in running this kind of business is not the monthly bill. It is configuration overhead upfront and ongoing judgment calls. The tools are cheap. The time to build the system correctly, define the decision rules, and calibrate what the agent can do autonomously is the real investment.

Evo runs most days without me touching anything. But when something breaks, or a new workflow needs defining, or a product decision needs making, that lands on me. The human-in-the-loop cost is real even if it is not a line item.

The first month building this out took about 40 hours of my time. Setting up the memory files, defining the decision frameworks, writing the identity document, calibrating what Evo approves autonomously versus what comes to me in Telegram. That is a genuine investment. Most guides skip this part.

After that initial build, the ongoing time cost sits around 30-60 minutes a day. Reviewing what shipped, approving social content queued by Evo, adjusting strategy based on what is working. Some days zero minutes if nothing needs review. Heavy weeks when I am building something new might hit 3-4 hours.

If your time is worth $100/hour, 30 minutes a day is roughly fifteen hundred dollars per month in implicit cost. The economics still work if the business generates more than that. But the idea that you just turn it on and walk away is not accurate for most people at the beginning.

What Surprised Me Most About Running This Stack?

Three things caught me off guard in the first three months: API costs were far lower than expected, integration breakage was the hidden time sink, and the upfront context-building work took longer than any tool setup. Each one is worth unpacking.

API costs are not the problem. Before building this I assumed AI API costs would be brutal. They are not. Most Evo operations are relatively lightweight in token terms. The expensive tasks, like long research loops or generating full blog post drafts, happen once and produce durable output. You are not re-running them constantly. My Anthropic bill has never exceeded $90 in a month.

The hidden cost is integration tax. Every tool that touches another tool costs time when it breaks. Supabase schema changes, Netlify rebuild hooks, dev.to API quirks, the Postiz scheduling window. Each integration works until it does not, and debugging broken integrations is not glamorous work. Budget 2-3 hours per month for things that stop working unexpectedly.

Storage costs nothing until it suddenly matters. The blog now has nearly 50 posts, each with an OG image sitting in Supabase storage. At current scale, storage is free. At 500 posts with video assets, that changes. It is not a problem now but worth knowing the trajectory.

Some tools I bought and never used. Honest accounting includes the wasted spend. ElevenLabs was $22 for a month I experimented with voice content, produced nothing publishable, and paused the account. Figma costs $15/month and I use it maybe once a month. These are small but they add up over 12 months.

What Are the Unit Economics of an AI-Run Solo Business?

Cost per blog post published runs roughly $3 to $5 when you divide the monthly stack across the 20 to 25 posts Evo produces. Reddit opportunity drafting costs between $0.50 and $2 per lead in API usage. Social scheduling costs fractions of a cent per post. These numbers put individual output costs well below any freelancer or agency equivalent.

Cost per blog post published: roughly $3-$5 when you divide the monthly stack across the 20-25 posts Evo publishes. That includes AI API time, hosting, image generation, and cross-posting.

Cost per Reddit opportunity spotted and drafted: roughly $0.50 to $2 in API costs for the Scout workflow.

Cost per tweet scheduled: negligible. Postiz handles scheduling, and the generation cost per tweet is fractions of a cent.

The real question is not the cost per output. It is whether those outputs convert into revenue. One consulting call booked from an organic blog post covers three months of the entire stack. That math is why this model exists.

What most founders underestimate

You need more context management than you think. An AI agent that does not know your business well will produce generic output. The investment in writing identity files, source-of-truth documents, and decision frameworks is not optional overhead. It is what makes the difference between output you can use and output you have to rewrite.

I spent roughly 8 hours in the first two weeks writing the Xero SOUL.md file, product knowledge base, and decision frameworks. That work compounds every day. Every task Evo runs now benefits from that context. Skipping it to save time at the start costs you far more time later. There is a post on how to write an identity file for your AI agent if you want to see exactly what goes into this.

Guardrails take time to calibrate. Early on, Evo would occasionally draft social posts in a tone that did not sound like me, or schedule things I had not approved. The fix was not a different AI model. It was better guardrail rules and clearer approval gates. If you want to see how to build those, the AI agent guardrails guide covers the actual system we run.

You cannot automate judgment. Distribution decisions, pricing, what to build next, how to respond to a customer complaint. These require a human. The agents handle execution and surfacing information. The calls on what to execute are still mine. Any honest account of running an AI agent business should say this clearly.

Is Running an AI Agent Business Actually Worth the Cost?

For a solo founder building in public with a clear offer and specific audience, yes. The economics work at a level that no comparable human team could match at this price point. One consulting call booked from organic search covers three to four months of the full stack. But that only holds if the strategy underneath is sound.

For a solo founder building in public, yes. The leverage is real. One person operating with this infrastructure can produce the content volume, distribution presence, and customer discovery coverage that would otherwise take a small team.

The economics work if you are building something that compounds. Each blog post that ranks brings traffic indefinitely. Each Reddit comment that helps a potential customer builds reputation that does not expire. Each workflow you define and hand to Evo frees you for higher-leverage work.

The economics do not work if you treat it as a magic business generator. The agents are only as good as the strategy behind them. If you have not figured out who your customer is, what problem you solve, and how you will get them, automating your output volume just means producing the wrong content faster.

The real ROI question is not what the tools cost. It is what your judgment is worth when you free yourself from the execution work.

What Is the Cheapest Way to Start an AI Agent Business?

If you are evaluating this model and want to start without the full stack, the minimum viable version costs around $97/month (OpenClaw) plus API costs that start near zero and scale with usage. Add Supabase on the free tier for storage and data. That is the core.

The starter guide at Your First AI Agent is $7 and walks through setting up the memory and identity layer that makes the rest actually work. That is the piece most people skip and then wonder why their agent produces generic output.

For a broader look at how solo founders are structuring these systems, the State of AI Agents report from AIMultiple tracks how usage and cost patterns are shifting across industries. Research from Andreessen Horowitz on AI infrastructure spending consistently shows API costs are not the bottleneck for early-stage AI projects. Context quality is. That is where to invest first.

Build the context foundation first. The tools are the easy part.

Published by Michael Olivieri / Xero AI

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Build a Personal CRM with an AI Agent (No Spreadsheet Required)

Michael O — Fri, 22 May 2026 20:05:00 +0000

Most CRM software is built for sales teams. It assumes you have a pipeline manager, a quota, and someone who updates the tool daily. You don't. You have a calendar full of half-finished conversations, a notes app with names you keep meaning to follow up on, and a vague sense that you're leaving money on the table.

A personal CRM backed by an AI agent fixes that. Not because AI is magic, but because the problem isn't tracking. It's that tracking takes time you don't have.

Here's how to build one that works without turning it into a second job.

What does a "personal CRM" actually mean for a solo founder?

A personal CRM for a solo founder is a structured record of every person you might do business with, a system that surfaces who you need to contact before they go cold, and a log of what you talked about so you stop asking the same questions. Relationship management without the overhead.

Forget Salesforce. Most founders try this in Notion, a spreadsheet, or their email inbox. All three fail the same way: they require manual input after every interaction, and you stop doing it within two weeks.

The AI agent version changes the input side of that equation. Instead of logging a call by hand, you paste a transcript or a few bullet points and the agent structures it. Instead of remembering to follow up, the agent flags the contacts who've gone quiet.

What do you actually need to build an AI-powered personal CRM?

You need three components: a structured contact file your agent can read and write, an AI agent with persistent memory and workspace access, and a scheduled trigger that surfaces the right contacts at the right time. No custom database, no paid CRM tool, no code. Just files, an agent, and a cron job.

The stack I use at Xero has exactly these three pieces:

A structured contact file. Markdown or JSON. Each contact has: name, company, what they want, where you met them, last touchpoint, and a follow-up status flag. Markdown works fine if you're running an AI agent with file access. JSON is better if you're feeding this to automations.

An AI agent with memory. The agent needs to read and write to that contact file. In OpenClaw, you give the agent a workspace directory and a SOUL.md that tells it to treat the contact file as the source of truth for your pipeline. Every time you log a new conversation, the agent updates the record and calculates follow-up timing based on lead temperature.

A trigger to surface the right people. A daily or twice-weekly cron job that tells the agent: "look at the contact file, find anyone with a follow-up due date in the next 48 hours or anyone we haven't touched in 14+ days, and send me a summary." That summary lands in Telegram. One message, actionable, no app to open.

If you want to understand how memory works in AI agent systems before setting this up, read how to give an AI agent persistent memory. It covers the exact file-based approach this CRM relies on.

How should you structure the contact file for an AI agent?

Each contact entry needs six fields: status (warm/cold/closed/dormant), where you met them, the date of last contact, a follow-up due date, what they want from you, and what you want from them. That last field is what most founders skip. Add it. You need to know why this relationship matters before you pick up the phone.

Here's the format (stored as plain text in your contacts file):

NAME: Sarah Chen | Bloom Media
STATUS: warm
SOURCE: Twitter DM
LAST CONTACT: 2026-05-15
FOLLOW-UP DUE: 2026-05-29
WHAT THEY WANT: automate client reporting
WHAT I WANT: discovery call, potentially Build Lab
NOTES:
  2026-05-15: intro call, open to AI but skeptical on timeline
  2026-05-22: follow-up sent, waiting on reply

Keep all contacts in a single file (contacts.md) or split by status if you have more than 30 names. The AI agent reads the whole thing each time, so file size matters less than you'd expect until you hit a few hundred contacts.

How do you log a conversation in under 60 seconds?

After any sales call, intro call, or relevant DM thread, you send your agent a voice memo transcript or rough bullet points. The agent pulls out the key details, creates or updates the contact record, sets the right follow-up status, and schedules the next touchpoint. The whole cycle takes less time than opening a CRM form.

After any sales call or intro conversation, send something like:

"Talked to Sarah from Bloom Media. She's running a 4-person content agency, wants to automate their client reporting. Not sure AI is ready for that yet. Revenue around $30k/month. Follow up in two weeks, she said she'd talk to her team."

The agent takes that and:

Creates or updates the contact record
Sets follow-up status to "warm"
Schedules a follow-up flag for 14 days out
Adds a timestamped note with the key details

You don't type a form. You don't click anything in a CRM. You just talk at your phone and the log updates. That's the only version of this that actually sticks long-term.

How does the follow-up sweep work and why does it matter?

The follow-up sweep is a scheduled agent task that reads your contact file twice a week, identifies contacts with overdue follow-ups or those who've gone quiet past your threshold, and sends a short Telegram summary. It's the part of the system that closes the gap between "I should follow up" and actually doing it.

Every Monday and Thursday morning, your agent reads the full contact file. It generates a list of:

Contacts with a follow-up due in the next 3 days
Contacts marked "warm" who haven't had a touchpoint in 10+ days
Anyone logged as "interested" but never moved forward with

That list arrives in Telegram. Not as a task to complete, just as a name and a two-line reminder of where things stand. You decide in 30 seconds whether to reach out that day or push it.

This sounds simple. It is. But most solo founders miss follow-ups not because they forgot the person exists, but because there was no system surfacing the right name at the right time. The sweep fixes that.

For context on how to set up scheduled tasks like this, see how to schedule AI agent tasks. The pattern there applies directly to this CRM setup.

Research from HubSpot's sales data consistently shows that 80% of sales require at least five follow-up contacts, while most founders stop after one or two. The sweep is the mechanical fix for that gap.

Can you add lead enrichment without paying for a data tool?

Yes. Tell your agent to search for basic public context whenever a new contact is added: role, company size, and recent activity. At under 200 contacts, this costs nothing and takes seconds per entry. You don't need Clay or Apollo at this stage.

When a new contact is added with a company name, the agent does a quick web search and notes their current role and team size. Not to spy, just to have context before you reply.

This works fine at small pipeline volume. The exception: if you're pulling high-volume leads from Reddit or other communities. At that point you're looking at a different workflow. The how to do customer research with an AI agent post covers how to handle lead sourcing at volume without burning through API credits.

According to Gartner research on sales productivity, reps spend up to 65% of their time on non-revenue-generating work. Enrichment that happens automatically cuts that down significantly, even at the solo founder level.

What does this system not do?

A personal CRM like this won't replace a proper sales process if you're at $100k MRR with a team. It won't give you deal analytics, forecasting, or team visibility. It's not a replacement for HubSpot or Pipedrive at scale. It solves one problem: keeping a solo founder from losing warm relationships because nothing was watching them.

What it does is keep a solo founder from losing $5,000 deals because they forgot to follow up on a warm intro from three weeks ago. That's the actual problem it solves, and it solves it completely.

It also doesn't require you to learn a new app. The agent is the interface. You talk to it the same way you'd text an assistant.

How do you get this running quickly?

If you're already using OpenClaw with a workspace setup, you can get this running in about two hours: create the contacts file, update your agent's identity file to treat it as tracked, write the follow-up sweep cron instruction, and test with five real contacts. Most people have this live by the end of a single afternoon session.

The pieces are:

Create the contacts.md file in your vault
Update your agent's SOUL.md to treat it as a tracked file
Write a short cron instruction for the follow-up sweep
Test with five contacts you already have in your notes

If you want to go from zero to a full operating system for your solo business rather than just the CRM piece, the Build Lab is where we set this up alongside the rest of your automation stack in a single session.

The CRM alone is worth the time. But most founders find that once it's working, they want the same pattern applied to content, customer research, and outbound. That's when it stops being a tool and starts being infrastructure.

Stop logging things manually. Give an AI agent access to a contact file, a follow-up sweep schedule, and a Telegram delivery. That's a personal CRM that runs itself.

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Build an AI Workflow for Your Business (Without an Engineer)

Michael O — Thu, 21 May 2026 20:05:01 +0000

Most founders who try to "use AI in their business" end up with a better copy-paste habit. They prompt ChatGPT, get output, paste it somewhere, repeat. That is not a workflow. That is an assistant you still have to babysit.

A real AI workflow runs on its own. It has inputs, logic, outputs, and a feedback loop. You set it up once. It executes while you are doing something else.

Here is how to build one from scratch, based on how Xero AI runs its entire operation through a live AI agent system called Evo.

What Is an AI Workflow for a Business?

An AI workflow is a repeatable sequence of tasks where AI handles the execution and you only touch the exceptions. It has four parts: a trigger, a context source, an action, and an output destination. When all four are defined, the workflow runs without you in the loop unless something breaks or needs approval.

That is the bar every workflow should meet. If you have to manually kick it off and review each step, it is a checklist, not a workflow.

Every workflow in the Xero system follows this structure. The morning briefing triggers at 7am, reads from the vault and external data sources, generates a report, and delivers it to Telegram. No human in the loop unless something breaks.

Which Task Should You Automate First?

Start with the task you do every week that makes you want to quit. Not the strategic, high-value work. The repetitive, low-creativity work that drains time without producing proportional results. This is the highest-leverage automation target because it runs often and the failure cost is low.

For Xero, the first workflow we automated was content research: finding Reddit threads, drafting replies, sending for approval. One hour a day became five minutes.

Your candidates probably include:

Weekly competitive research or news monitoring
Social media scheduling and drafting
Customer support FAQ responses
Lead qualification before a discovery call
Internal status updates or reports
Newsletter research and outline prep

Pick one. Just one. Get it running. Then expand.

How Do You Map a Task Before Automating It?

Write out every step as if you were training a new hire on their first day. This is the actual work, and skipping it is why most AI automations fail. Vague instructions produce vague output. Specific, explicit steps produce consistent results.

"Research competitors" is not a step. "Search Google for [competitor name] news in the last 7 days, pull the top 3 results, extract the headline and key claim from each, write a 2-sentence summary" is a step. According to MIT research on automation design, task decomposition is the single most predictive factor in workflow reliability.

For every step, ask:

What is the exact input?
What does good output look like?
What is the most common failure mode?

If you cannot write it down clearly, you cannot automate it yet.

What Tools Do You Actually Need for an AI Workflow?

You do not need custom software or a dev team to run real AI workflows. Three layers cover most solo founder use cases: a trigger layer, an execution layer, and an output layer. Most founders can build a working system in a single afternoon using tools they already have access to.

Trigger layer: This is what kicks off the workflow. Options include cron jobs (scheduled time), webhooks (an event fires it), or a manual command. For most solo founders, a scheduled cron is the right start. Set it, forget it.

Execution layer: This is where the AI lives. OpenClaw is what Xero uses. It handles agent memory, multi-step logic, tool calls, and error handling inside a single session. For simpler workflows, Zapier or Make with GPT-4 actions can work.

Output layer: Where the results go. Telegram for notifications and approvals. Supabase for structured data. A Google Doc, a spreadsheet, or an email. Pick the destination first. If you do not know where the output goes, the workflow has no end state.

The most common setup for a solo founder just getting started: OpenClaw + Telegram. You schedule tasks, the agent runs them, and the results land in your Telegram. You review, approve, or redirect.

How Do You Write a Prompt That Actually Powers a Workflow?

Build the prompt in four sections: role and context, task definition, output format, and a quality gate. Single long prompts that try to do everything at once fail because the model optimizes for the general instead of the specific. Four discrete sections keep each part accountable.

Role and context: Who is the agent in this workflow? What does it know about your business? Feed it the relevant context from your source-of-truth document for your AI system before it starts working.

Task definition: What is the exact job for this run? Be specific. Include constraints. Include format requirements. Tell it what not to do.

Output format: Exact structure. Headers, bullets, word limits, where links go. Variance in output format means variance in downstream handling. Force the format.

Quality gate: One sentence the agent uses to self-check before sending. "Does this answer the question I was asked, with no invented information?" This catches hallucinations before they reach you.

Xero's workflows all use this four-part structure. The identity file that every Xero AI agent runs feeds the role and context layer so the agent always knows who it is and what business it is working for.

Should You Let an AI Workflow Run Fully Autonomous Right Away?

No. If the output touches customers, public channels, or money, add a human review step until you trust it. Ten clean runs in a row is the threshold Xero uses before promoting a workflow to fully autonomous. Before that point, the approval gate stays in place.

The pattern is simple: agent runs the task, formats the output, ends with a yes/no prompt to Telegram. You approve from your phone in under a minute. If you do not respond in 24 hours, it logs the pending item and checks again.

This is not a failure of automation. It is a quality gate. The goal is to remove yourself from execution and stay in the approval seat only where it matters.

How Do You Know If Your AI Workflow Is Working?

Test with real data, not sample data. A workflow that works on a made-up test case often fails on real inputs. Run three tests before you trust it: a normal clean input, a messy incomplete input, and two identical inputs in a row to check consistency.

If any test fails, the issue is usually in the prompt (not specific enough) or the output format (not enforced tightly enough). Fix those before adding complexity.

According to NIST guidelines on AI system evaluation, repeatability under varied inputs is the primary reliability signal for automated AI systems. The same logic applies at the solo founder scale.

How Do You Keep an AI Workflow From Degrading Over Time?

Log every run, even successful ones. Models change, data sources shift, and context drifts over time. Without a log, you will not know a workflow started degrading until the output is visibly wrong. With a log, you catch problems at the first deviation.

Every workflow in the Xero system writes a short log entry after each run: what it did, what output it produced, and whether it hit any errors. Once a month, a scheduled audit agent reviews them and flags anything that has started producing lower-quality output.

A text file that appends one line per run is enough. What was run, when, and did it pass the quality gate. That log will save you hours when something breaks three months from now.

What Does a Real Solo Founder Workflow Stack Look Like?

A complete AI workflow stack for a solo business covers daily operations across content, research, outreach, and reporting, all running without a human in the execution loop. Xero operates this way with no employees, using a scheduled cron system that triggers individual workflows throughout the day and night.

For reference, here is what Xero runs daily:

Morning briefing: Pulls overnight data, checks system status, delivers a prioritized daily brief to Telegram at 7am
Blog pipeline: One post per day, written to a specific SEO brief, published to Supabase, cross-posted to dev.to
Twitter/X queue: Drafts five posts per day using a voice guide, queues them, flags anything needing human review
Reddit research: Scans target subreddits for relevant threads, drafts responses, sends to Telegram for approval before posting. Full breakdown in the guide on how to use Reddit for SaaS growth without getting banned
Newsletter: Outlines and drafts the weekly issue, flags sourcing gaps, waits for approval before sending
Nightly recap: Audits what shipped, what is pending, and what broke

None of this required hiring. All of it required a clear prompt architecture, a consistent memory system, and a willingness to rebuild workflows when they started producing garbage.

What Is the Most Common Reason AI Workflows Fail?

The context they need is not available at run time. The agent does not know your business well enough to make real decisions, so it fills the gaps with generic output. This is not a model failure. It is a setup failure.

The fix is an AI memory system and a source-of-truth document the agent reads before it starts work. When every workflow begins by loading a few hundred words of business context, the output quality improves significantly. Not because the model changed. Because it knows who it is working for.

Where Do You Start This Week?

Pick one repetitive task, write out every step explicitly, build a four-part prompt with role, task, format, and quality gate sections, add a Telegram approval gate for the first ten runs, and log each run in a plain text file. That is the whole system for week one. No tools to buy, no code to write.

The Xero starter guide walks through this exact setup with a working first workflow you can clone and adapt. It is the fastest way to go from zero to a running system without needing a developer or a course.

Published by Michael Olivieri / Xero AI

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Do Customer Research With an AI Agent

Michael O — Wed, 20 May 2026 20:06:23 +0000

Traditional customer discovery advice assumes you have time. Talk to 50 people. Run a survey. Build a persona. Schedule interviews. That process works if you have two co-founders and no day job. Most solo founders have neither.

There is a faster path. AI agents can scan thousands of real customer conversations on Reddit, App Store reviews, and niche forums and pull the signal out in a fraction of the time. Not summaries of what AI thinks people say. Actual quotes, actual complaints, actual questions people typed in public.

This is how the Xero operating system does it internally, and it is the same logic behind Xero Scout.

What Is AI-Assisted Customer Research?

AI-assisted customer research means using an agent to collect and synthesize publicly available conversations at scale, instead of replacing human judgment with generated assumptions. You point AI at real data from Reddit threads, forum posts, and review sites. The agent reads and extracts. You decide what to build next.

The key distinction: this is not asking AI to imagine what customers might say. Reddit posts, forum threads, and review text are primary sources. The agent reads and extracts. You decide what matters.

Four things it can do well: find recurring complaints, surface exact language people use about a problem, flag what frustrates users about existing tools, and group patterns across hundreds of comments faster than any human.

It cannot replace a real customer conversation. But it can help you walk into that conversation knowing you have already read the market.

Where Does the Real Customer Signal Live?

The real customer signal lives in unfiltered public complaint threads on Reddit, in one-star app reviews, and in niche forums where people talk without a sales audience watching. Google surfaces polished SEO content. These platforms surface raw buyer psychology. The difference in signal quality is significant enough to change what you build.

Most founders start with Google. That is the wrong move for customer research. Google surfaces SEO content, not raw buyer psychology.

The real signal is in places where people complain publicly without a sales agenda:

Reddit is the most valuable. Subreddits like r/SaaS, r/Entrepreneur, r/solopreneur, r/webdev, and r/smallbusiness have thousands of posts from people describing real problems, failed tools, and specific frustrations. Nobody is pitching. They are just talking. According to Similarweb, Reddit receives over 1.5 billion visits per month globally, with a significant share coming from people actively searching for product recommendations and solutions.

App Store and G2 reviews are gold for competitive research. One-star reviews tell you exactly what the market's existing solutions get wrong. Filter for "I switched because" and "I wish it could" to surface high-intent pain.

Indie Hackers comments carry strong signal for B2B SaaS. Founders discuss what broke their product, what they would pay for, and what they have tried.

Niche forums and Discord servers are harder to scrape systematically but worth monitoring for specific verticals.

The pattern across all of them: you are looking for the same complaint appearing in different threads from different people. One complaint is an edge case. The same complaint in ten threads is a real problem worth solving.

How Does the Agent Workflow Actually Work?

The workflow has five steps: define your query set, collect threads, extract and label each comment, group patterns, then do a human review to decide what matters. Each run takes 90 minutes the first time and under 30 on repeat. This process runs weekly inside the Evo operating system.

Here is the full structure, along with how it runs inside the Evo operating system:

Step 1: Define the query set

Give the agent your product URL or a short description of the problem you are solving. The agent generates 10 to 20 search queries it will use to find relevant threads. These are variations of the pain, not the product name. "I wish there was a tool that" or "anyone else struggling with" framing finds better signal than searching for competitor names.

Step 2: Collect threads

The agent searches Reddit (or the target platform) and collects the top threads, comments, and replies matching those queries. Aim for 100 to 200 unique comments minimum before drawing conclusions. Smaller samples produce misleading patterns.

Step 3: Extract and label

The agent reads each comment and assigns a label: complaint, feature request, comparison question, churn reason, or success story. It pulls the exact quote and notes the thread context. No paraphrasing at this stage. You want the raw language.

Step 4: Pattern grouping

Across all labeled comments, the agent groups similar complaints together. You end up with something like: "18 people mentioned that [Tool X] does not support [Feature Y]" or "12 people asked whether this works without [Dependency Z]."

Step 5: Human review

You read the grouped output and decide what is signal. The agent finds patterns. You decide which ones matter for your specific product strategy. Do not skip this step.

That entire loop takes about 90 minutes the first time, less than 30 on repeat runs once the queries are refined.

What Should You Do With the Research Output?

The output should drive four things: sharpen your positioning copy, write better cold outreach, prioritize the product roadmap, and generate reply angles for community distribution. Most founders stop after reading the insights. The bigger move is letting the exact language customers use rewrite your messaging and your feature backlog.

Most founders stop at the insight. The bigger leverage is in using the output to drive the next decisions:

Sharpen the positioning. If the research keeps surfacing a specific frustration that your product actually solves better than alternatives, that is your headline. Not your feature list. The exact words people use to describe the pain.

Write better cold outreach. If you know the specific complaint, you can open with it instead of a generic pitch. "Noticed a thread where founders said [exact complaint] is their biggest frustration with [competitor]. We built [product] because of that specific problem." That is not spam. That is proof you did your homework.

Prioritize the roadmap. Grouping complaints by frequency gives you a signal-weighted backlog. Build the thing that 18 people are actively asking for before the thing that one person mentioned once.

Generate reply angles for distribution. If you know the forums where your target customers are posting, you can draft helpful replies to those threads. Not pitching. Answering the question they asked, with the credibility of someone who actually solved it. This is exactly what Xero Scout automates.

What Tools Do You Actually Need to Build This?

You do not need an expensive stack. A working agent needs four things: a search layer, a language model with a long context window, a structured output format, and a storage layer. Free or near-free options exist for each component. Total setup time is a few hours.

Here is how each piece works in practice:

A search layer: something that can query Reddit or pull from the API. Reddit's official API is available, though rate-limited on free tiers. The Reddit API documentation covers the available endpoints. For manual work, site:reddit.com Google queries with a Python scraper cover most cases without needing API access.

A language model with a long context window: you want to feed it 100 to 200 comments at once and get a structured extraction back. GPT-4 class models handle this well. Claude works too, and tends to be better at maintaining structured output consistency across large batches.

A structured output format: have the model return JSON with fields for quote, category, source URL, and thread context. Flat text dumps are hard to act on.

Storage: a simple spreadsheet or Airtable base to accumulate runs over time. You want to see how the patterns shift as you refine your queries.

If you want this running as a recurring loop rather than a one-off project, wire it to a cron job. The AI agent task scheduling post covers the infrastructure.

What Are the Most Common Mistakes Founders Make?

The most expensive mistake is searching for the product name instead of the pain, which surfaces review content rather than real buyer frustrations. The second is treating a single vivid complaint as a confirmed pattern before checking how many other people said the same thing. Both mistakes lead to building the wrong feature with false confidence.

Searching for the product, not the pain. "Reddit posts about [Competitor]" finds review content. "Reddit posts where people are frustrated about [problem]" finds buyers. Search for the symptom, not the category.

Reading the output without counting. One vivid complaint feels important. But if only one person said it in 200 comments, it is not a pattern. Count the clusters before you prioritize.

Treating it as a replacement for talking to people. This research is pre-qualification, not a substitute. Use it to identify the five people most worth calling, not to avoid calling anyone.

Ignoring the language. The most valuable output from this research is often not the insight but the exact phrasing. When someone says "I just want to know if it actually works without me having to monitor it every day," that sentence is your landing page copy. Use their words, not yours.

Stopping at one subreddit. The same buyer persona exists in multiple communities. A solo founder building a SaaS might be in r/solopreneur, r/SaaS, r/Entrepreneur, and a vertical-specific subreddit all at once. Run the same queries across all of them.

What Does This Look Like in Practice at Xero?

The Xero operating system runs this research loop weekly for each active product. The output feeds the content calendar, the reply queue, and the positioning documents directly. When a complaint cluster appears three weeks in a row, it becomes either a product feature or a piece of content. Nothing sits idle in a spreadsheet.

For CarCloser, the agent monitors automotive sales subreddits. For the main Xero AI audience, it watches r/solopreneur, r/SaaS, and r/Entrepreneur.

The output feeds the content calendar, the reply queue, and the positioning documents. When a new complaint cluster shows up three weeks in a row, it either becomes a product feature or a piece of content. Nothing goes to waste.

Scout was built as the productized version of this internal workflow because other founders kept asking how we were finding the right Reddit conversations to join. The answer was the agent loop above, wrapped in a cleaner interface.

If you want to start doing this without building the infrastructure from scratch, the AI starter guide walks through the actual agent setup, including the research workflow.

Customer research has always been the highest-leverage activity for early-stage products. The founders who understand what their market is actually saying before they build have a real advantage. AI agents do not replace that work. They just make it fast enough to fit into a Saturday morning.

Published by Michael Olivieri / Xero AI

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

Best Reddit Monitoring Tools for Founders in 2026

Michael O — Tue, 19 May 2026 20:06:26 +0000

Reddit has customers in it. That much most founders already know. The problem is finding the right threads without spending two hours a day scrolling five subreddits, guessing at search terms, and reading posts that have nothing to do with your product.

That is the actual problem Reddit monitoring tools solve. Not brand mentions. Not social listening at enterprise scale. Just: someone posted about a problem your product solves and you need to know about it fast enough to respond before the thread dies.

This comparison covers the tools worth considering in 2026, what each one actually does, and who each one is built for.

What Makes a Reddit Monitoring Tool Worth Using for Founders?

A Reddit monitoring tool is worth using when it surfaces threads where your target customer is actively asking for help, not just mentions of keywords. The useful tools filter by intent, deliver alerts fast enough to act on them, and keep reply friction low enough that you can actually do something before the thread dies.

Four things matter:

Signal quality. Does it find threads where someone is actively asking for help, complaining about a problem, or requesting recommendations? Or does it match on broad keyword hits that have nothing to do with your use case?

Reply speed. Reddit threads have a short window. A comment posted within the first few hours gets seen. A comment posted 48 hours later gets nothing. If your tool batches alerts daily, you will miss most of the value.

Reply friction. Some tools surface threads and stop there. You still have to open Reddit, read context, write something useful, and post it manually. Lower friction at the reply stage matters more than most founders expect before they try it.

Price against output. Most paid tools were built for brand managers at companies with budgets. The pricing reflects that. A solo founder needs a different cost structure.

Which Tools Are Worth Considering?

The six tools below cover the full range from free keyword alerts to intent-aware discovery with reply drafting. They differ significantly in how they find threads, how fast they alert you, and whether they help you respond or just point you at Reddit and step back.

F5Bot (Free)

The original free Reddit alert tool. You give it keywords, it emails you when they appear. That is the full feature set.

F5Bot is genuinely useful for brand name monitoring or checking whether people are mentioning a specific product. For lead generation, it falls apart fast. The keyword matching is broad, the emails come in batches, and you get no context about whether a thread is worth responding to. You click through to check every one.

Good for: catching your brand name in comments, zero budget, set and mostly forget.

Not good for: finding customers, filtering by intent, or acting fast.

Price: Free.

Mention (Paid)

Mention monitors Reddit plus a wide range of other channels: news, blogs, forums, social. It is a full media monitoring platform.

The Reddit coverage is real and reasonably fast. The problem for solo founders is that Mention was designed for PR and marketing teams. The cheapest plan starts around $49/month and the interface is built around volume and reporting, not quick action. You will spend time configuring it and more time filtering noise before you find anything worth replying to.

If you run a brand with meaningful press coverage and you want one place to track all mentions across channels, Mention makes sense. If you are trying to find customers by being helpful in Reddit threads, it is the wrong tool for the budget and the workflow.

Price: $49/month and up.

Brand24 (Paid)

Similar positioning to Mention. Brand24 monitors Reddit among many other sources and is a well-built tool with solid coverage.

The standout is sentiment analysis and the "Presence Score," which tries to give you a sense of how much buzz exists around your brand. For a bootstrapped founder trying to find new customers, that is interesting but not useful. You are not measuring sentiment. You are trying to get in front of someone who just posted "looking for a tool that does X" and answer them before ten other people do.

Brand24 starts around $99/month for their standard plan. The Reddit functionality works, but you are paying for a platform whose main audience is established brands with marketing teams.

Price: $99/month and up.

Syften (Paid)

Syften is more tightly focused on Reddit and HN monitoring than the enterprise tools above. Built specifically for bootstrapped founders and indie hackers who want to catch relevant conversations fast.

You set keyword patterns, it monitors in near real-time, and alerts go out quickly. The filtering is better than F5Bot. False positives are manageable. The pricing is much more founder-friendly than Mention or Brand24.

The limitation is that Syften surfaces threads and stops there. The reply step is entirely on you. You still click through, read context, figure out what to say, write something, and post it. For a solo founder who is also building a product and talking to customers and writing content, that reply friction adds up.

Price: Starts around $15/month. Free trial available.

GummySearch (Paid)

GummySearch takes a different approach. Rather than monitoring for your keywords, it helps you research subreddits around your audience, surface pain points, and find patterns in what people complain about or ask for.

It is a research and positioning tool as much as a monitoring tool. The audience intelligence features are genuinely useful when you are figuring out your market, validating a problem, or writing copy. It has an alert layer too, but the core value is the research side.

For someone who has already validated their idea and wants to find customers in Reddit threads today, GummySearch is good but not the right primary tool. For someone still figuring out whether their product solves a real problem, it is excellent.

Price: $79/month for full access, or a lower cost tier with limits.

Xero Scout (Free Beta)

Full transparency: Xero Scout is a tool I built from the internal workflow I use at Xero.

The problem I kept hitting with other tools was the gap between finding a thread and doing something useful in it. Every tool would surface a match, I would click through, and then spend ten minutes reading context and writing a reply that sounded like a person, not a bot. For one or two threads a week that is fine. At volume, it is not sustainable.

Scout takes a different approach. You give it your product URL. It reads the product, understands what problem it solves and who has that problem, and then finds Reddit threads where that person is actively asking for help. Instead of keyword matching, it uses context to find intent. Instead of surfacing a thread and stopping, it drafts a reply you can read, edit, or copy. You approve and post manually. Scout never posts anything automatically.

The design is intentional. Reddit bans accounts for automated posting. The goal was to make the discovery and drafting fast enough that the human step stays at the decision layer, not the research layer.

Scout is in free beta right now. It came out of the Evo internal stack after I found that the same workflow that worked for my own products also worked when I applied it to projects like CarCloser and PetPersona.

Price: Free during beta. Try Xero Scout here.

How Do These Tools Compare Side by Side?

The comparison below covers the six tools across the criteria that matter most for a solo founder trying to find customers: whether the tool finds relevant threads by intent or just keyword hits, whether it alerts fast enough to act, whether it drafts replies, and what it costs.

Tool	Best for	Real-time?	Reply drafting	Price
F5Bot	Brand name alerts, zero budget	No (batch emails)	No	Free
Mention	Multi-channel brand monitoring, PR teams	Near real-time	No	$49+/month
Brand24	Established brands, sentiment tracking	Near real-time	No	$99+/month
Syften	Bootstrapped founders, fast thread alerts	Near real-time	No	$15+/month
GummySearch	Market research, audience intelligence	Periodic	No	$79/month
Xero Scout	Solo founders finding customers, reply drafting	Real-time	Yes (human-approved)	Free (beta)

Which One Should You Actually Use?

For most solo founders in 2026, the right tool depends on one question: do you need to monitor for mentions of an existing brand, or do you need to find customers who have never heard of you? The answer changes the recommendation significantly.

If you have zero budget and want to catch anyone mentioning your product by name, start with F5Bot. It works and it costs nothing.

If you want market research and you are still in the "figuring out my audience" phase, GummySearch is worth the money. The subreddit pain-point research alone can reshape how you position your product.

If you are building something and want to be present in the conversations where your ideal customer is asking for help right now, Syften or Xero Scout are the right tier. Syften if you want a clean, established tool. Scout if you want reply drafts built in and the context-aware discovery approach.

The full enterprise tools (Mention, Brand24) make sense when Reddit monitoring is one piece of a larger brand tracking operation. For most solo founders in 2026, you do not need that.

Is Reddit Actually a Viable Customer Acquisition Channel?

Yes, but only if you are consistent and you approach it as a community participant rather than a marketer. Reddit has over 100,000 active communities and regularly surfaces in Google results for long-tail queries, which means relevant threads often have a longer shelf life than the Reddit feed itself.

That said, Reddit threads are not evergreen. A good post at the top of r/SaaS or r/solopreneur gets five hundred upvotes and then disappears from anyone's feed in 72 hours. The founders who benefit from Reddit are the ones who show up consistently in the right threads, say something genuinely useful, and let the pattern compound over time.

Tools just lower the discovery cost. According to data from Sprout Social, Reddit users spend an average of 10 minutes per session engaging with community content. The founders who do well there are the ones who write like members, not marketers.

The actual work is knowing enough about the community you are in to write something real. Reddit users are fast to spot replies that were clearly generated at scale. A comment that reads like a marketing email gets downvoted or ignored. A short, specific, helpful comment from someone who clearly understands the problem gets upvotes and DMs.

If you want a deeper look at how to do Reddit outreach without getting your account flagged, this post on using Reddit for SaaS growth without getting banned covers the rules in more detail.

For the monitoring and discovery side, the tools above are the ones worth evaluating. Start cheap, upgrade when the workflow justifies it.

And if you are figuring out how to turn this into a repeatable system rather than a one-off tactic, the AI agent stack for solo founders shows how tools like this fit into a wider automated workflow.

Published by Michael Olivieri / Xero AI

Want to build a customer discovery system that does not require hours of manual searching? Start with the AI agent starter guide and see what a working setup looks like before you build one.

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Build a Personal AI Assistant That Actually Knows Your Business

Michael O — Mon, 18 May 2026 20:04:50 +0000

Most founders use ChatGPT or Claude the same way they Google something. Type a question, get a generic answer, move on. That works fine for looking up syntax or drafting a template. It fails completely the moment you want the AI to help you run your actual business.

The problem isn't the model. The models are good. The problem is context. You're asking an AI to help you write a follow-up email, and it doesn't know your product name, your pricing, your tone, or who you're emailing. So it gives you a reply that sounds like it was written for a completely different company. Because it was.

A personal AI assistant that actually knows your business isn't a different tool. It's the same model, set up differently.

What Does "Knowing Your Business" Actually Mean for an AI Assistant?

When people say they want an AI that knows their business, they mean three things: using real product names and prices, remembering past decisions, and matching their voice. All three are achievable with context files loaded at session start, not a custom model or enterprise tooling.

The structure is a small set of documents that get loaded before the AI does anything. The model reads them, and suddenly it knows who you are.

Which Files Do You Actually Need to Give an AI Business Context?

Three files: an identity file with your products, prices, and audience; a voice guide with actual writing examples; and a memory file that captures past decisions and lessons. Together they transform a generic model into one that works from your real context instead of inventing plausible-sounding answers.

The identity file

This is a short document that describes your business the way you'd describe it to a new contractor on day one. Product names. What each product does. Who buys it and why. Current prices. What's live vs. in development. Your positioning in one sentence.

Keep it under 600 words. Dense, not sprawling. The goal is for the AI to read it once and immediately have the working facts it needs.

Mine covers Xero AI (the agency and tools), the newsletter, the $7 beginner guide, the Build Lab, and a few lines on what Evo is and how it operates. When any tool loads that file first, it stops giving me generic AI advice and starts working with my actual setup.

There's a full template and walkthrough in How to Write an Identity File for Your AI Agent if you want the structure.

The voice guide

A separate document that captures how you write. Not instructions like "be professional" or "be casual." Actual examples. Sentences pulled from your best writing, labeled with what makes them work. Patterns you use. Phrases you never use. Words you avoid.

Without this, the AI defaults to its training distribution, which sounds like a capable but characterless consultant. With it, the output lands much closer to your actual voice on the first pass.

The voice guide doesn't need to be long. A few pages. But it has to be specific. "Conversational" tells the model nothing. "Short paragraphs, no em dashes, no filler intros, start with the problem" tells it something.

The memory file

A living document that captures what's happened, what's been decided, and what lessons shouldn't be lost. This one gets updated over time, either by you or by the agent itself.

The memory file is what turns a stateless session into something with continuity. Without it, the AI has no idea that you tried a particular pricing strategy and it flopped, or that you've already vetted three newsletter tools and settled on MailerLite. It starts fresh every time.

With it, you skip re-explaining and get straight to work.

If you want the full architecture for how this works across sessions, How to Give an AI Agent Persistent Memory covers the daily log plus long-term memory setup I've been running for months.

How Do You Load Business Context Into an AI Assistant?

In plain ChatGPT or Claude.ai, paste the three files at the top of each new conversation. Takes 30 seconds. More advanced setups auto-inject them so context is always loaded without manual work. Either approach produces dramatically better output than starting a session with no business context at all.

In more powerful setups, an AI assistant configured to load these files automatically at session start removes the copy-paste entirely. OpenClaw does this natively. According to OpenAI's documentation on persistent context, structuring input well is one of the highest-leverage improvements you can make to model output.

If you're not running an agent platform yet, the copy-paste method still beats starting from scratch. Get the files written first. The automation layer can come later.

What Should Go in the Identity File?

Product names and one-line descriptions, current prices, who each product is for, your audience described specifically enough that a stranger would recognize them, what you're building toward, what you don't do, and all active URLs. Under 600 words, formatted as bullet points. Not narrative paragraphs and not your origin story.

What to include:

Products/services: Name, one-line description, price, who it's for, what problem it solves. One row per product.

Audience: The actual person you're selling to. Not "entrepreneurs" but something specific enough that a stranger would recognize them. For me: solo founders or people with full-time jobs who want to run a side business with AI tools and can't afford or don't want a team.

What you're building toward: A sentence or two on where you're going. This helps the AI calibrate what advice is relevant vs. distracting.

What you don't do: Equally important. Things that are out of scope, partnerships you don't take, content you don't make. Guardrails on the business context.

Active URLs: Live products, signup pages, blog. So the AI never invents a URL or links to something that doesn't exist.

That's it. Keep it scannable. The AI doesn't need your origin story.

What Are the Mistakes That Kill AI Context Quality?

Overloading the files with backstory the AI doesn't need, letting them go stale after pricing changes, packing everything into one massive dump, and skipping the voice guide. Each mistake produces a specific type of wrong output. Fix them and the gap between a generic session and a context-loaded one becomes impossible to ignore.

Overloading it with backstory. The identity file is not the place for your founder origin story, your values manifesto, or a full brand strategy document. Those might matter for other things. For session context, they're noise. The model needs facts, not narrative.

Letting the files go stale. If you changed your pricing in March and your identity file still says the old number, you've introduced a conflict. The AI will use the wrong price. Update the files when things change. Treat them like product documentation.

One massive context dump. Some people try to pack everything into one document and inject thousands of words at the start of every session. This eats context window, increases cost, and buries the important stuff in filler. Three focused files, each doing one job, works better than one bloated megadoc.

Skipping the voice guide. The identity file fixes factual errors. Without the voice guide, you'll get factually accurate output that still doesn't sound like you. Both matter.

What Does Context-Loaded AI Output Actually Look Like?

Before context files, AI would produce generic tweets like "Here's how you can leverage AI to grow your business." After loading the identity and voice files: short, specific, founder-to-founder, linking to something real. Same model, same capability. The difference shows up across every task because the model knows who it's writing for.

Same model. Same capability. Completely different output because it knows who it's writing for and how the writing is supposed to sound.

The same improvement shows up across every task: email drafts, blog post outlines, customer response templates, decision frameworks. Once the context is loaded, the AI stops being a general-purpose text generator and starts being a tool that's calibrated to your actual situation.

Research from Anthropic on effective prompting consistently shows that providing structured reference context is more effective than detailed instructions alone. The model performs better when it can look up facts rather than infer them.

What Is the Next Step After Building Context Files?

Make the setup permanent so you're not managing context manually. That means an agent system built on top of context files, with scheduled tasks, self-updating memory, and tools connected to your actual stack. The $7 beginner guide covers the full architecture from identity through automation in one sitting.

But the context files alone will change your day-to-day in ways you'll notice immediately. Write the three files. Start loading them. The rest builds from there.

The full architecture, identity files through memory systems through automation, is covered in the Your First AI Agent guide at Xero AI. Start there if you want to move past context files and into an actual operating system for your business.

Related:

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

How to Find Customers for Your SaaS Idea Without Quitting Your Job

Michael O — Sun, 17 May 2026 20:05:44 +0000

Most people with a SaaS idea sit on it for months because they think customer discovery requires a calendar full of cold calls, a big audience, or the freedom that comes from quitting their job first.

None of that is true.

The founders who move fastest spend two hours a week in the places where their future customers already complain out loud. That place is almost always Reddit. And you can do this at 10pm on a Tuesday from your couch while your regular job stays intact.

This is the method Xero uses to find real buyers for every product in the Proof Lab, including Xero Scout, CarCloser, and PetPersona. None of those started with an audience. All of them started with reading Reddit.

Why Does Reddit Work Better Than Other Customer Discovery Methods?

Reddit shows you the raw words people use before they know your product exists. No polished language, no diplomatic answers. Just real frustration from real buyers. According to Pew Research, Reddit skews toward educated, tech-adjacent adults, exactly the early-adopter profile most SaaS products need first.

There are roughly 100,000 active subreddits covering almost every niche. Inside the ones that match your target buyer, people post their actual problems daily. Car sales reps complain about specific objections they cannot handle. SaaS founders complain about Reddit being too spammy to promote in. Pet owners share exactly what they want but cannot find.

Google cannot surface this in real time. Twitter moves too fast. LinkedIn is too performative. Reddit is the closest thing to reading your customer's internal monologue.

The problem is volume. You cannot manually watch 20 subreddits, scan hundreds of posts, find the relevant ones, draft a reply that actually helps, and do it all before your lunch break ends. That friction is why most employed founders never start. Which is where the workflow comes in.

How Do You Run Customer Discovery When You Only Have Two Hours a Week?

The system is four repeating steps: map where your buyers complain, search for pain phrases instead of product categories, read for signal rather than volume, and track what you find in a simple notes file. Running this consistently for 60 days produces more validated market data than most funded startups get from formal research budgets.

Step 1: Map where your buyers complain (30 minutes, one-time)

Pick your target customer. Be specific. "Startup founders" is too broad. "Bootstrapped SaaS founders with under $1k MRR trying to get their first 10 paid users" is specific enough to find real threads.

Now list the subreddits they live in. For that founder: r/SaaS, r/Entrepreneur, r/indiehackers, r/startups. For a car sales rep: r/askcarsales, r/cars, r/Justrolledintotheshop.

Keep it to 3 to 6 subreddits max. More than that and you cannot track the signal.

Step 2: Search for the pain, not the keyword

Do not search for your product category. Search for problem symptoms.

If you are building a tool to help founders find customers on Reddit, do not search for "reddit marketing tool." Search for "how do i find customers on reddit" or "reddit self promotion" or "got banned for promoting my saas." Those threads contain your exact buyer, describing their exact pain, in their exact words.

Build a list of 10 to 15 complaint phrases specific to your niche. These become your weekly search queries.

Step 3: Read for signal, not volume

You are not looking for thread count. You are looking for posts where someone describes a problem your product already solves, or a problem it could solve if you built it right.

When you find one, leave a genuinely useful reply. Not a pitch. Not a product mention. An actual answer to the question they asked. The reply that gets 15 upvotes and spawns 4 follow-up questions is better market research than any survey.

Step 4: Track what you see

Keep a simple notes file. Every week, record the subreddit, the post title, the pain phrase used, whether your product solves it, and the response to your reply.

After 4 weeks, patterns emerge. You will see which exact complaints repeat, which framing gets engagement, and whether people respond well when you describe your product in passing. This is your product roadmap, your messaging, and your first-customer list.

Why Does Having a Day Job Actually Help With Customer Discovery?

Having a salary removes the pressure to monetize immediately. You can take the slow path, build trust, validate deeply, and reframe the product without the financial clock forcing a premature launch. Founders who quit first tend to skip this validation phase because the pressure to start selling hits before they have understood the buyer.

Spend 6 to 8 weeks in your target subreddits building karma and genuine reputation before anyone knows you have a product. By the time you mention something exists, you are already the person who gives good advice in that community. That credibility converts better than any cold pitch.

Slow validation from the safety of a salary is a real edge. Most employed founders do not realize they have it.

What Do You Do When a Reddit Thread Contains Your Exact Buyer?

Do not send them a link immediately. Ask a follow-up question first. The response tells you what the problem costs them, how urgently they want a solution, and what you would actually need to build to make them pay. Skipping straight to a pitch is the most common conversion mistake at this stage.

Try something like: "What have you tried so far?" or "What does the current process look like for you?"

Their answer tells you far more than whether they will click a link. After that exchange, share a link or ask if they would want to try an early version. They are warm now. They feel heard. The conversion rate at this point is much higher than anything from cold traffic.

This is how the first Xero Scout beta users were found. Not from an ad. From reading threads, posting genuinely helpful replies, and following up when someone lit up.

What Is the Mistake That Kills Most Customer Discovery Efforts?

Founders treat customer discovery as a discrete phase that has to finish before building starts. The reality is that the best discovery happens in parallel with building, through real conversations that surface problems you had not anticipated and cut features you were about to over-engineer. Stopping the loop kills the feedback signal that makes the product worth building.

You post a reply explaining how you solved the problem, someone asks "wait, is that a tool?" and you say yes, it is in early beta, want to try it. That loop compounds. More replies lead to more conversations. More conversations sharpen the product. A sharper product generates better replies.

If you stop the loop to go build in isolation for 6 months, you lose everything. Consistency over 3 months beats intensity over 3 weeks.

Can You Automate the Reddit Scanning Part?

Yes. The manual hunting is what collapses under schedule pressure. Scanning 6 subreddits every morning before work, deciding which threads matter, and drafting replies that sound human is a real time cost. Xero Scout handles the finding and drafting, leaving the judgment call (whether to post and what to say) in human hands.

You put in your product URL. Scout reads what you built, infers the niche, and finds relevant Reddit threads. It drafts replies you can approve, copy, and post manually. No auto-posting. The human makes the final call on every reply.

If you want to build the full system yourself, the AI starter guide at xeroaiagency.com walks through setting up your first AI workflow from scratch in a weekend, no code required.

What Should You Have After 60 Days of Running This System?

After two months you should have validated whether the core problem is real, identified your top 2 to 3 buyer communities, and had at least 3 direct conversations with real potential customers. Y Combinator shows founders who talk to 20 real users first ship faster and pivot less.

Concretely, you should have:

A clear sense of which 2 or 3 subreddits contain your densest buyer concentration
A list of the 5 to 8 pain phrases your target customer repeats across threads
Direct evidence of whether your product concept matches those pains, or needs reframing
At least 3 to 5 real conversations with people who match your ideal customer
A karma score above 50 in at least one relevant subreddit, which gives you the ability to post (not just comment) without restrictions

That is enough to validate the idea and start building in earnest, or kill it before you spend 6 months on the wrong thing. Both outcomes are wins.

Start reading before you start building. Two hours a week. You do not need to quit your job first.

Want to run this system without the manual hunting? Try Xero Scout free. Enter your product URL and Scout finds the Reddit threads worth answering.

Building your first AI workflow from scratch? The AI starter guide covers the tools and setup in a weekend, no code required.

Also worth reading: How to use Reddit for SaaS growth without getting banned and How to find your first 100 customers with AI.

Published by Michael Olivieri / Xero AI

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com

Zero Human Company: Is It Actually Possible in 2026?

Michael O — Sat, 16 May 2026 20:03:52 +0000

Running a business with zero full-time employees is not a new idea. What is new is that in 2026 you can actually do it as one person, with AI handling research, content, customer discovery, social, and some operations, without duct-taping 15 tools together and babysitting them.

I am in the middle of building one. This is what it actually looks like, what AI can and cannot carry right now, and what you have to build before any of it works.

What Is a Zero-Human Company?

A zero-human company is not a company with no humans. It is a company where one founder operates leveraged by an AI system instead of a team. You remain the strategist, the decision-maker, and the quality check. The AI layer handles execution at a volume no solo founder could sustain manually.

The core work shifts. You stop doing tasks and start managing systems. You spend your time on three things: deciding what to build, reviewing what the AI produces, and improving the system when output quality drops.

This is different from "using AI tools." Tools require input every time. A system runs on a schedule, feeds itself context from memory, and improves from documented feedback. The gap between the two is the whole game.

What Operating Stack Does a Zero-Human Company Run On?

Three layers make a zero-human company functional: an identity file that installs your judgment into the system, a source-of-truth document that keeps every agent working from current facts, and scheduled agents with guardrails that run the recurring work without pulling you in. Miss any one layer and you are back to manual work.

Layer 1: Identity and memory. Your AI needs to know who you are, what you are building, and how you make decisions. Without this, every agent conversation starts from scratch. With it, your AI can draft content, evaluate opportunities, and prioritize tasks in a way that sounds like you and fits your actual strategy. This is what a SOUL.md file does. It is the closest thing to installing your judgment into a system.

Layer 2: Source of truth. One document that holds your live product list, pricing, active offers, and current priorities. Every agent reads from this before taking action. It prevents your AI from promoting a product you killed last month or citing a price you changed. I call this the SOURCE_OF_TRUTH file. It sounds boring. It is the most operationally important file in the vault.

Layer 3: Scheduled agents with guardrails. Cron jobs that trigger agents on a schedule, with rules that define what they can and cannot do without human approval. This is how content gets published, social replies get drafted, Reddit gets monitored, and newsletters go out, without you opening a laptop.

You do not need all three layers on day one. You need them in that order.

Which Business Functions Can AI Run Without You in 2026?

Content production, customer discovery, research, and basic operations are all mature enough in 2026 to run with minimal oversight from a solo founder. These four functions cover roughly 70 percent of the execution work in an early-stage business. Here is what each one looks like in practice:

Content production. Blog posts, newsletters, Twitter threads, Reddit replies. This is the strongest current use case. The quality ceiling is high if the AI has context. The failure mode is generic output when the identity layer is thin.

Customer discovery. Tools like Xero Scout can take a product URL, find Reddit conversations where that problem surfaces, and draft replies worth posting. What used to take a founder an hour of manual searching per day can run on a cron schedule.

Research. Competitive intel, market signals, pricing changes from competitors, inbound lead signals from communities. AI can surface these on a schedule and summarize them into a daily brief.

Basic operations. Invoicing logic, email triage routing, FAQ responses, onboarding sequences. Anything with a clear decision tree runs well.

What the AI cannot do without you: close a sale, navigate a tense customer conversation, make a product bet, build a real relationship with a partner.

Those are the human-required jobs. Everything else is on the table.

What Actually Breaks When You Try to Run a Zero-Human Company?

Three failure modes kill almost every first attempt at zero-human operations: stale context, missing guardrails, and undocumented tool switches. Each one is fixable before it causes real damage, but each one will silently degrade your output quality for weeks before you catch it if you are not watching.

Stale context. Your AI was briefed on your business six weeks ago. Since then you changed your offer, killed a product, and shifted your positioning. The AI does not know. It is still promoting the old thing. This is why a live SOURCE_OF_TRUTH file with a weekly refresh is not optional. It is maintenance the same way a server needs maintenance.

No guardrails on output. An agent set loose on social media with no review process will eventually post something off-brand, factually wrong, or badly timed. Every agent needs an approval gate or a quality check before anything goes public. This does not mean you review every tweet. It means you build the rules into the system so the agent only escalates when something is uncertain. AI agent guardrails are what make autonomous operation safe.

Tool switching without documentation. You move from one platform to another, change your stack, and the AI is still writing instructions for the old workflow. Every system change needs to be reflected in your memory files within 24 hours or you will start getting bad output. The vault is not a set-it-and-forget-it artifact. It is a living operating manual.

What Does a Zero-Human Company Actually Look Like Day to Day?

My current setup at Xero runs one agent named Evo as the primary operator. On a normal day, nothing requires my input before 9am. The system handles content, monitoring, and briefings on its own. Here is what Evo handles on a standing schedule:

One blog post published daily, sourced from the strategy doc, written against the brand voice, cross-posted to dev.to
Newsletter issues three times a week, drafted from a template and a topic queue
Morning and evening Telegram briefings: what shipped, what broke, priority for the day
Reddit monitoring for relevant threads, with draft replies queued for my review
Twitter posts on a five-post-per-day schedule with human approval before anything goes live

That is roughly 30 hours of manual work per week running on a cron schedule with about 45 minutes of my actual review time per day. Not zero. But a fraction.

The gap between 45 minutes and zero is trust. As I document more edge cases, build more guardrails, and improve the memory files, the review time shrinks. That is the trajectory.

How Do You Start Building Toward a Zero-Human Company?

You do not need a $200 per month AI stack. You need three files and one agent. Most founders who try to automate before they have these files in place end up with output that drifts from their actual strategy within two weeks. Start with the foundation first.

Start with the identity file. Write down who you are, what you are building, and how you make decisions. Keep it under 1,500 words. Put it somewhere your AI can read it at the start of every conversation.

Then build the SOURCE_OF_TRUTH file. One place. Current products. Current prices. Current priorities. One person is responsible for keeping it live. That person is you.

Then pick one repeating task that costs you more than 30 minutes per week and automate it. Write the prompt. Run it manually five times. Document what breaks. Then put it on a schedule.

The $7 starter guide at xeroaiagency.com/learn/your-first-ai-agent walks through exactly this sequence. It is the practical on-ramp if you want to go from "I use AI tools" to "I have an AI operating system."

Is a Zero-Human Company Actually Possible in 2026?

Yes, with an important condition. A zero-human company is possible in 2026 for a solo founder who builds the operating layer first: identity, source of truth, and scheduled agents with guardrails. Skip that foundation and you get noise instead of leverage.

The founders making this work today are not using the most expensive models. They are the ones who spent the first few weeks on the files and rules before automating anything. That sequence is the whole difference.

This model of solo-founder leverage has been discussed by researchers at institutions like MIT Media Lab and covered in outlets like Harvard Business Review, both pointing to the same finding: the bottleneck is not compute, it is structured context. Get that right and one person can operate at a scale that would have required a team two years ago.

Published by Michael Olivieri / Xero AI

Want to build your first AI operating layer? The starter guide covers the core setup from scratch. Book 1 goes deeper on the full architecture. Both are built for founders with no team, no coding background, and no time to waste.

Start Building Your Own AI System

Your First AI Agent - $1 launch-test guide, instant download. The fastest way to get started.
Build an AI Co-Founder - the full architecture ($19).
AI for the Rest of Us newsletter - practical AI 3x/week for people with day jobs.

Want to build your own AI co-founder?

I'm building Xero in public — an AI system that runs distribution, content, and ops while I work a full-time job.

Start here: Your First AI Agent — $7 guide, instant download
Go deeper: Build an AI Co-Founder — the full architecture ($19)
Newsletter: AI for the Rest of Us — practical AI 3x/week for people with day jobs
Site: xeroaiagency.com

Originally published at xeroaiagency.com