Forem: Michael O

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

How to Write an AI Agent Prompt That Actually Works (Not Just Once)

Michael O — Fri, 15 May 2026 21:56:30 +0000

Most founders who complain that AI "isn't reliable" are writing prompts the same way they write text messages. Casual. Vague. Context-free. Then they wonder why the output is inconsistent.

The problem isn't the model. It's the prompt architecture.

When I started running Xero on AI agents, the single biggest leverage point wasn't picking the right model or buying better tools. It was learning how to write prompts that produce the same quality of output on the 50th run as they did on the first. This post covers exactly that.

What is the difference between a regular prompt and an agent prompt?

A regular prompt is a one-shot instruction that ends when you get your result. An agent prompt is a persistent instruction set that fires on a schedule without you in the loop. The design requirements are completely different, which is why most prompts written for chat interfaces fail in automation.

Writing agent prompts means thinking about:

What the agent needs to know before it can start (context)
What success looks like specifically (output format)
What should happen when something goes wrong (error handling)
What it should never do (constraints)

Most tutorials only cover the first one. That's why most agent prompts drift or break after a few runs.

Why should you start with role and context rather than the task?

Leading with the task before context is the most common structural mistake. The model doesn't know who it is, what business it serves, or what success looks like for this workflow. A clear role and context block gives the agent a frame for interpreting every subsequent instruction, dramatically reducing judgment calls you never intended to delegate.

Bad:

Summarize today's news about AI startups and post it to my Telegram.

Better:

You are the content curator for Xero, a solo-founder AI agency. 
Your job is to find and summarize 3 AI startup stories that are relevant 
to non-technical founders building with AI. Avoid stories about model 
releases from major labs unless they have direct tooling implications. 
Summarize each story in 2 sentences max. Then format the output as a 
Telegram message with no markdown headers, just plain text with line breaks.

The second version tells the agent who it is, what its filter criteria are, what to exclude, how to format output, and what platform it's writing for. That's not over-engineering. That's what a real employee needs before they can do the job without calling you every five minutes.

What is the four-part structure that keeps agent prompts consistent over time?

After running hundreds of agent automations, this four-part structure is what holds up. Each section handles a different failure mode: identity prevents context drift, task rules prevent output variation, format specs prevent format inconsistency, and edge case handling prevents silent failures that you only catch two weeks later when something has been broken the whole time.

1. Identity + purpose (2-4 sentences)
Who is this agent, what business context does it operate in, what is its single job in this automation.

2. Task + rules (the bulk)
What to do, in what order, with what constraints. Specific beats general. "Find 3 posts from the last 24 hours" beats "find recent posts." Give the agent a checklist it can follow mentally.

3. Output format (explicit, not implied)
What the output should look like, word counts if relevant, what to include and exclude, what platform it's going to. If the output feeds another tool, describe the expected format for that tool.

4. Edge case handling (often skipped)
What happens when the source has no results? When an API fails? When the content doesn't meet quality criteria? Agents that don't have an answer to these questions either hallucinate through the problem or silently fail. Neither is good.

What quality gates do most people skip when building agent prompts?

Most people skip the constraints layer entirely. Hard constraints beat soft ones, self-evaluation steps catch errors before output ships, and explicit completion definitions close loops that vague instructions leave open. These three additions account for most of the reliability gap between agents that run clean for 90 days and agents that drift within a week.

Hard constraints beat soft ones. "Don't include anything from major tech publications" is better than "prefer indie sources." Give the agent a rule it can apply as a binary check, not a judgment call.

Self-evaluation beats hoping. Add a step where the agent reviews its own output before finalizing it. Something like: "Before you output the final message, check: does it meet all the criteria above? If not, revise it." This one instruction dramatically reduces drift.

Specify what done looks like. "The task is complete when X has been sent to Y and confirmed received" is different from "send X to Y." The first version closes the loop. The second leaves room for the agent to think it finished when it only partially ran.

For more on building quality gates into workflows, how to build an AI agent decision framework and AI agent guardrails are both worth reading alongside this.

Does temperature and model choice actually matter as much as people think?

No. Model choice accounts for maybe 20% of output quality for recurring agent tasks. The prompt accounts for the rest. A tight, specific prompt running on a mid-tier model will outperform a vague prompt on a premium model almost every time. The fixation on model selection is usually a sign that the prompt architecture hasn't been solved yet.

For recurring agent tasks, start with the fastest capable model available, then only upgrade if the output genuinely requires more nuance. Most daily automation tasks don't need a top-tier model. They need a better prompt.

Temperature: lower (0.3 to 0.5) for anything that needs to be consistent and formatted, like reports, summaries, and scheduled posts. Higher for brainstorming, drafts, or creative copy. Cranking temperature doesn't make agents "smarter." It makes them less predictable. For most scheduled automation, that's the opposite of what you want.

Research from Anthropic's model documentation and OpenAI's prompt engineering guide both reinforce this: clarity of instruction matters more than model tier for structured tasks.

What is the memory problem that makes agent prompts drift over time?

Context window growth is the hidden culprit behind most prompt drift. As an agent runs across multiple steps, earlier instructions carry less weight than recent content. Prompts that felt solid at first produce inconsistent outputs not because you changed anything, but because the model reads your instructions from a different position in a much longer window.

A few structural choices help:

Put your most important constraints at both the beginning and end of the prompt. Models pay more attention to the start and end of long inputs. If there's a rule the agent absolutely cannot violate, say it twice.

Keep prompts shorter than you think they need to be. Every unnecessary sentence dilutes the weight of the important ones. Aim for prompts that an experienced human could follow from memory after reading once.

For longer-running agents that accumulate context over multiple steps, the architecture question of how memory works is separate from prompt design. How to give an AI agent persistent memory covers the structural side of that problem.

What should you do when your agent prompt keeps producing inconsistent output?

If you've had three or more runs produce inconsistent output, the problem is almost always one of four things: ambiguous criteria the agent is resolving on its own, missing context it needs but wasn't given, an overloaded task trying to do too much in one prompt, or a missing output spec that lets the format drift between runs.

Ambiguous criteria. The agent is making judgment calls you didn't define. Go back and define them explicitly.

Missing context. The agent doesn't know something it needs to do the job well. Add it to the identity section.

Overloaded task. One prompt is trying to do too many things. Split it into two agents with a handoff between them.

No output spec. The agent is choosing its own format and it keeps changing. Lock down the format explicitly.

Keeping a short log of failed agent runs with notes on what went wrong pays dividends fast. After a few months you see patterns. Almost every failure traces back to one of those four things.

How does running agent prompts in an automation framework differ from running them in chat?

In chat, you're present to course-correct. In automation, no one's watching. Every failure mode needs a defined response because there's no human catching edge cases in real time. Silence is a failure mode. Partial output is a failure mode. Output that looks right but isn't is the worst one, because you won't catch it without explicit checks.

The prompts I write for Xero's scheduled agents are meaningfully different from the prompts I use in chat. More rigid, more explicit about error handling, less reliant on the model's judgment. If you're moving from chat-based AI use to actual agent automation, recalibrate for that difference before anything goes live.

If you want to see what a full agent stack looks like in practice, the AI agent stack for solo founders post breaks down how the pieces fit together across a real solo business.

Where to go from here

If you're building your first real agent automation and want a structured starting point, the $7 Solo Founder AI Guide covers prompt architecture, the task breakdown framework I use at Xero, and the exact setup I run for recurring agent jobs. It's the fastest shortcut I have for skipping the 6-month learning curve.

Or if you want help building a specific agent for your business, book a Build Lab session and we'll scope it, prompt it, and test it together in 90 minutes.

The model isn't the bottleneck. The prompt is. Fix the prompt first.

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

AI Co-Founder vs Hire a VA: What Actually Makes Sense in 2026

Michael O — Thu, 14 May 2026 20:04:23 +0000

The instinct when you hit capacity as a solo founder is to hire someone. A VA for $8 to $15/hour, maybe a part-time contractor. Delegate the inbox, social media, research. Get your time back.

That instinct made sense in 2022. In 2026, it deserves a harder look before you pull the trigger.

This is not an argument that AI replaces all human help. It is not a productivity bro take about working 80 hours solo and loving it. What changed is the nature of the work a solo founder actually needs done, and what can now be handled by a persistent AI system running inside your own stack.

What Does a VA Actually Do (and What Can AI Replace)?

For most solo founders, VA work fits into five categories: calendar and email triage, research and reporting, social media scheduling, customer support drafts, and admin cleanup. Four of the five are now fully automatable with a persistent AI agent. The one exception is anything requiring real relationship warmth or reputational judgment.

Most VA work falls into five categories: calendar and email triage, research and reporting, social media scheduling and monitoring, customer support responses, and data entry or admin cleanup.

Four out of five of those are now fully automatable. Persistent AI agents can triage inbound Telegram messages, run nightly research briefs, generate and schedule social posts from a queue, draft customer support replies for review, and keep structured logs updated. The Evo system running inside Xero handles all five of these for me right now. No human hours, no payroll, no timezone coordination.

The one category that still leans human: anything requiring real relationship warmth, judgment calls that carry reputational risk, or tasks where the output needs to sound like a specific named person and your AI setup is not yet calibrated to that level.

Where Does a Human VA Still Beat AI?

Three specific areas still favor human VAs over AI agents: direct outbound relationship work, niche tasks with a limited training surface, and founders who simply work better knowing a real person is handling a function. Outside these three, most operational work a VA handles in year one is automatable today.

Where Human VAs Still Win

Direct outbound sales and relationship building. A skilled human VA doing personalized outreach converts better than templated AI. If your business is in a phase where a single warm introduction changes your trajectory, a human can read social signals you would miss in an automated flow.

Niche tasks with limited training surface. If the work requires a skill your AI agent has not been set up for yet, like managing a specific obscure tool or handling industry-specific compliance documents, a human is faster to spin up than building a new agent layer from scratch.

Accountability and emotional labor. Some founders just work better knowing a real person is watching the inbox. That is not a weakness, it is self-knowledge.

But notice those exceptions are narrow. They are not "inbox management" or "content research" or "scheduling posts." Most of what founders hire VAs for in the first year falls outside those exceptions.

What Does the Real Cost Comparison Look Like?

The typical VA runs $500 to $1200/month. An AI co-founder setup with persistent cron jobs, daily content, research briefs, and social automation runs under $50/month in API costs. Setup takes 15 to 30 hours upfront. After that, the system is orders of magnitude cheaper to run indefinitely.

Let's run the actual numbers, not the fantasy spreadsheet.

A decent VA costs $500 to $1200/month for part-time work, depending on location and skill level. At the lower end you get someone who needs training, makes context errors, requires check-ins, and brings overhead you did not anticipate. At the higher end you get someone good who will eventually move on and take institutional knowledge with them.

An AI co-founder setup has different costs. The API bills for a tool like OpenClaw running persistent cron jobs, daily posts, research briefs, and blog automation runs me under $50/month. The setup investment is real: probably 15 to 30 hours to build your memory system, configure your workflows, write your identity files and guardrails. But that is a one-time cost. The system does not quit, does not need managing, does not clock off for a holiday.

The breakeven is roughly 2 to 3 months of VA cost to build an equivalent AI system. After that the AI system is orders of magnitude cheaper to run.

What Do You Actually Need to Build an AI Co-Founder?

You do not need to code. Three things make an AI co-founder work: an identity file that defines voice and permissions, a memory system that retains context across sessions, and guardrails that gate anything risky. Most founders can build a working version in a weekend. The architecture is simpler than it sounds.

You do not need to code. The three things that make an AI co-founder work are identity, memory, and guardrails.

Identity is a structured file that tells your AI agent who it is: your brand voice, what it is authorized to do, what it should never do, your current priorities. Without this, every session starts from zero. What is an identity file and how to write one walks through this in detail.

Memory is how the agent retains context across sessions. Not chat history, which gets wiped. A structured MEMORY.md or similar document that the agent reads at the start of every run and updates at the end. How to give an AI agent persistent memory covers the specific architecture.

Guardrails are the rules that stop the agent from doing something costly without your approval. Post thresholds, spend limits, approval gates before anything goes live externally. This is what separates a useful autonomous agent from a liability.

Those three things take a weekend to set up properly. The $7 starter guide at xeroaiagency.com/learn/your-first-ai-agent walks through all three with a working template.

What Can AI Not Do That Founders Overestimate?

Two things trip founders up when they go all-in on AI: judgment on novel situations, and adaptation without explicit prompt. Your agent acts on its instructions. Anything outside defined scope pauses or guesses. Build guardrails that handle the gap.

Two things founders consistently overestimate when they go all-in on AI too fast:

Judgment on novel situations. If something genuinely new and weird happens, your agent will handle it based on whatever its instructions say. If your instructions do not cover it, it will either ask you or guess. A good human assistant notices when something is off the map and escalates. Build your guardrails to match: anything outside defined scope should pause and notify you.

Real-time adaptation without prompt. Your AI co-founder does what it is told, when it is told. It does not notice that your product positioning shifted last week and update its own behavior accordingly. You have to update the identity files. That is a lightweight ongoing maintenance task, but it is yours. VAs pick up context passively by working alongside you. Agents need explicit updates.

Both of these are solvable. They just require you to think upfront about system design rather than assuming the AI figures it out.

How Do You Decide: AI System or Human VA?

Start by asking what the task requires, not whether to use AI or human. Repeatable, knowledge-bounded work goes to the AI. Tasks needing social judgment, one-time warmth, or uncalibrated skill sets go to a human. For most solo founders running lean in 2026, that means AI handles operations and human time goes to high-leverage decisions.

Stop asking "AI or human?" and start asking "what does this task actually require?"

If the task is repeatable, knowledge-bounded, and does not require relationship equity, automate it. Build the system once and let it run.

If the task requires real social judgment, one-time relationship warmth, or a skill set your AI stack is not yet calibrated for, hire the human for that specific thing.

Most solo founders in 2026 who are serious about staying lean should be running AI systems for the repeatable operational work, and spending human budget (their own time or a contractor) on the high-leverage relationship and strategy work that moves the needle.

The mistake is hiring a VA for $800/month to manage your inbox and schedule tweets when a two-weekend build would handle both indefinitely at $40/month. That is not anti-human, it is just honest about where the leverage is.

How Does Xero Actually Run This?

Evo runs daily content, blog posts, research briefs, social scheduling, newsletter drafts, and analytics pulls across Xero AI with no human operator involved in the routine work. The system has a structured identity file, a persistent memory architecture, and explicit guardrails before anything goes public. No VA, no contractor, no payroll.

Evo runs daily content, blog posts, research briefs, social scheduling, newsletter drafts, and analytics pulls. The system has an identity file, a memory architecture, and explicit guardrails before anything goes public.

I have not hired a VA. I probably will eventually, but only for the narrow human work that genuinely needs it. Outbound relationships at a specific moment. A sales call. Something requiring a specific expertise I have not yet built a system for.

Everything else runs. Nights, weekends, while I am at the day job. I covered the full stack here if you want the specifics on how that works with a full-time job alongside it.

If you want to see what a working AI co-founder stack looks like from the inside, the $7 starter guide gets you the identity template, memory system, and guardrail framework I actually use. Build it once. Then stop hiring for work the AI can handle.

Sources: Upwork VA rate benchmarks | OpenAI API pricing | Harvard Business Review on automation ROI

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 Use AI for Market Research as a Solo Founder (Without Spending $5k)

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

Market research used to mean hiring a firm, running surveys, or at minimum spending three weeks manually reading forums and competitor reviews. Most solo founders skip it entirely. They build on gut, launch to silence, and figure out the gap after.

There is a faster path. One that costs almost nothing and produces sharper signal than a $5,000 agency report.

Here is how to actually do it.

Why does most solo founder market research fail?

Most founders skip market research because they think it means surveys, focus groups, or expensive data firms. It does not. The real problem is that founders look for validation instead of friction, and they stop reading as soon as they find one comment that agrees with them. That is not research. That is confirmation bias with extra steps.

Real market research means going where your customers already complain, without knowing you are watching. Reddit, Twitter, Hacker News, niche Slack groups, app store reviews. The places where someone types out a frustrated rant at 11pm because they cannot figure out why their current solution keeps failing.

That content tells you what to build, what to say, and how to position it. The words people use when they are upset are the words that convert in your copy.

The problem is volume. Doing this manually is a full-time job. You would need to monitor dozens of subreddits, search dozens of keywords, read thousands of posts, and extract signal from noise every single day. Nobody does that consistently.

AI does. That is the lever.

What does an AI-powered market research stack actually look like?

An effective AI market research stack has three layers: continuous signal collection from places your audience talks, AI summarization to extract patterns from volume, and a weekly review rhythm that turns raw input into positioning decisions. You do not need to build all three at once, but you need to know what you are building toward.

At the foundation, there is a list of keywords tied to each product. For Xero Scout, those keywords include phrases like "how do I find my first users," "customer discovery for SaaS," "nobody is signing up," and "how to validate without building." Those are the specific phrases someone types when they are living the problem the product solves.

An agent monitors Reddit for those phrases across relevant subreddits: r/SaaS, r/startups, r/Entrepreneur, r/indiegames, r/growmybusiness, and others depending on the product. When a match comes in, the agent summarizes the thread and sends a Telegram message. Title, subreddit, link, short summary of what the person is asking. Reading it takes 20 seconds.

That loop runs daily. Over a month, you have a living document of what your market is actually saying.

How do you do this without building a custom agent?

You do not need to build the full system from scratch. Three manual approaches using AI summarization get you most of the benefit in under an hour. Start with Reddit mining, then app store reviews, then customer interview prep. Each one is standalone and takes 15-20 minutes.

Reddit thread mining. Pick three subreddits where your future customers hang out. Search for the problem you solve, not your solution name. Go back 90 days. Copy the top 10 threads into Claude or ChatGPT and ask: "What are the recurring frustrations? What solutions have these people already tried? What words do they use to describe the problem?" The output will be sharper than any survey you could run.

App store and review mining. If existing tools operate in your space, read every 1-3 star review. Copy them into an AI and ask it to extract the pattern. What keeps coming up? What did people expect and not get? That is your positioning brief. G2 and Trustpilot are worth including here if the product has enterprise competitors, since the complaints there tend to be more detailed than app store reviews.

Customer interview prep. Before you talk to potential customers, use an AI to design your questions. Feed it your product idea and ask it to generate 10 questions that would reveal whether someone has the problem, how they currently solve it, and what would stop them from switching. This prevents leading questions in the actual interview. The Mom Test framework pairs well here as a quality check on the AI output.

None of this requires code. It requires an hour and a willingness to read uncomfortable things about your assumptions.

What signal are you actually looking for in the research?

You are looking for one thing: the specific reason current solutions keep failing people. Not general frustration. The precise failure mode. A thread where someone says "I have tried X, Y, and Z and none of them work because [specific reason]" is worth more than a hundred survey responses. That specific reason is your product's wedge.

A thread where someone says "does anyone know a tool that does X?" is almost as good. That is unsatisfied demand articulated by the person who has it. You do not need to infer the problem. They told you.

What you are not looking for: validation. Most founders use research to confirm what they already believe. They find one positive comment and stop. The friction is the signal. The complaints, the "I almost bought but," the "I cancelled because" threads. Those are the threads that tell you what the category is missing.

Specifically, look for these four things: what the person does the day before they search for a solution (your acquisition channel), what they tell their cofounder when the current approach fails (your headline), what would make them feel foolish for not switching (your positioning), and what makes them nervous about switching (your objection handling). Four questions. All of them answerable from Reddit if you are reading for the right things.

How does Xero Scout automate the ongoing research loop?

The biggest barrier to ongoing research is volume. Monitoring Reddit manually every morning is not something most founders sustain past week two. Xero Scout handles the collection layer automatically. You set your keywords and subreddits, and it surfaces relevant threads daily with short summaries, turning an unsustainable manual habit into a two-minute daily curation task.

You still read the threads. You still decide what matters. The agent handles the volume so you can focus on interpretation. Try it at xeroaiagency.com/scout.

Pre-launch, Scout is the fastest way to confirm whether your idea has a real market without relying on your own network or running cold email campaigns to strangers. Post-launch, it surfaces the exact language people use around your category, which tells you what your positioning is missing. Stalled growth almost always has a language problem underneath it.

How do you build a research rhythm that lasts more than a week?

The failure mode is treating research as a phase. The founders who consistently build things people want maintain a low-level ongoing input stream. Not obsessively, just consistently. A weekly thread review, a monthly positioning update, a quarterly synthesis. That structure takes about two hours per month total when an agent handles collection.

This takes about two hours a month total if an agent handles the collection. Compare that to building in the dark for six months, then running a big survey when growth stalls and wondering what changed.

The market shifts. Competitors move. The language people use to describe problems evolves. A positioning that worked in early 2025 may be dated by mid-2026 even if the product itself has not changed. Ongoing research is how you catch that drift before it costs you growth.

What are the research questions most founders forget to ask?

The standard advice covers "does this problem exist" but skips the questions that actually determine whether you can build a business around it. The forgotten questions are about switching cost, social signal, and the moment of search. These are the questions that convert into copywriting and channel strategy.

Here is what to add to your research list: What does the person do the day before they search for a solution? That is your acquisition channel. What do they tell their cofounder when the current approach fails? That is your headline. What would make them feel foolish for not switching? That is your positioning. What makes them nervous about switching? That is your objection handling.

All four are answerable from Reddit threads and review mining if you are reading with intent. The AI layer lets you process 50 threads in the time it used to take to read 5. The real multiplier is not speed. It is being able to do the research consistently enough that the patterns emerge.

Where do you go from here?

If you are still in the "is this a real problem" phase, the post on how to validate a SaaS idea with AI covers the pre-build research process end to end, including how to structure conversations with potential users before you have anything to show them.

If you are past validation and trying to find your first 100 customers, this post on customer acquisition for solo founders covers the channels that actually work when you have no audience and no budget.

Market research is not a phase you complete. It is a practice you build into the operating rhythm of the company. The founders who do this tend to ship less and sell more. That is the trade, and it is worth making.

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 to Automate First as a Solo Founder (And What to Keep Doing Yourself)

Michael O — Tue, 12 May 2026 20:04:39 +0000

Every solo founder gets to a point where they know AI should be doing more of their work. They just don't know what to start with.

The wrong answer is usually the thing that's most painful right now. That feeling pulls founders toward automating customer support before they have enough customers to justify it, or building an elaborate content pipeline before they've found a single post format that actually works. You automate what's loud instead of what's high-leverage.

The result is six automated workflows that sort of run, a bunch of broken logic to debug, and a business that still depends entirely on you for the things that actually matter.

Here's a better starting point.

What Is the Only Question Worth Asking Before You Automate Anything?

Before touching any automation tool, ask this: if you disappeared for two weeks, which parts of your business would survive on their own? Most founders skip this step and end up automating whatever feels urgent. That's how you build a lot of workflows that don't actually free you up.

Before touching any automation tool, ask yourself: if I disappeared for two weeks, which parts of my business would survive on their own?

Your answer will usually reveal two categories. Things that could theoretically continue without you making a real-time judgment (social posts going out, emails getting sorted, reports being generated, content getting drafted). And things that would immediately break or produce wrong outcomes without you in the loop (customer conversations, pricing decisions, scope decisions, anything touching real relationships or real money).

Automate the first category. Protect the second.

This isn't about capability. Current AI can technically attempt any of these. It's about cost of failure. Getting a social post wrong costs you one piece of content. Getting a customer conversation wrong costs you a customer, your reputation in the communities they're in, or both. The cost of failure should determine where the human stays in the loop.

What Should You Automate First If You Have Limited Time to Set Things Up?

If you're a solo founder with limited setup time, start with content distribution, monitoring, recurring reports, and lead intake, in that order. These four categories share the same profile: they're repetitive, judgment-light, and low-risk if the output is slightly off. Getting one of them running reliably beats having four broken halfway.

If you're deciding where to start and you have limited time to set things up, here's the order that has worked for me at Xero and that I've seen work for most solo founders building on an AI stack:

1. Content distribution, not content creation

Distributing content you've already approved is low-stakes and high-frequency. Scheduling tweets, reposting across channels, sending newsletters you've written. These are tasks that are exactly the same every time, don't require real-time judgment, and eat real time if done manually. Automate them first.

Content creation is the trap. The work of creating original, resonant content still requires a human who knows the audience. AI drafts can be a starting point, but the editing and approval step has to stay with you until you've built enough of a pattern that the quality gate can be defined precisely. If you try to automate creation before distribution, you'll spend more time reviewing bad drafts than you saved on publishing.

2. Monitoring and alerting

Watching things so you don't have to. Reddit threads where your brand or problem space gets mentioned. Competitor product announcements. Customer support tickets with certain keywords. Inbox emails from specific senders.

This is pure leverage. An AI that flags the signal and brings it to you is dramatically better than manual scanning, and the failure mode is low-risk: if the alert misses something or flags the wrong thing, you catch it in review. This is also where tools like Xero Scout earn their keep. Monitoring subreddits for your exact customer pain, surfacing threads before they're 48 hours old, and serving them up for human review costs minutes instead of hours.

3. Recurring reports and status summaries

Any report you look at on a schedule (weekly revenue summary, daily content analytics, monthly support ticket themes) can be generated automatically from the same data every time. You still review it. You still make decisions from it. But you don't generate it by hand.

The setup takes a few hours the first time. After that it runs forever. This was one of the first things I automated at Xero and it's one of the few automations that has never needed a rebuild because the output is the same format every time.

4. Lead capture and sorting

Someone fills out a form, books a call, downloads something. The follow-up sequence is identical for the first two steps: confirmation email, calendar link, intake form. All of that can be automated without any judgment involved. You engage when there's an actual conversation to have, not before.

What Should You Keep Doing Yourself Even When AI Could Handle It?

Pricing decisions, customer conversations, and anything where you don't yet know what good looks like should stay with you. The cost of failure is too high and the judgment requirement too contextual. AI works best on tasks where a clear success criterion can be defined in advance and the output doesn't touch real relationships.

This is where founders get into trouble. The productivity pull of AI tools makes it tempting to hand off things that should stay with you.

Pricing and positioning decisions. These require context about your market, your customers, and what they're actually willing to pay. AI can give you data, competitor prices, frameworks. The decision is yours. An AI that sets your prices autonomously will optimize for something that isn't actually your goal.

Any conversation that shapes a relationship. Early customers especially. The first 50 to 100 people who use your product are the ones who tell you what it actually is. You cannot delegate that listening. And if they feel like they're talking to a bot when they have a real problem, they leave and tell other people.

Anything where you don't yet know what good looks like. This is the most common automation mistake. If you can't write a clear quality gate for a task (what does a good output look like, specifically?), you're not ready to automate it. AI needs a defined success criterion. Without one, you'll just be reviewing bad output forever and creating more work for yourself, not less. The post I wrote on building quality gates for AI agents goes deep on how to define these precisely before automating anything.

Founder-specific judgment. Roadmap priorities. Hiring decisions. Whether to pivot. These are high-stakes, low-frequency, contextually rich. AI can give you a good framework for thinking through them. The call is still yours.

How Do You Decide Which Specific Task to Automate This Week?

List every task you did last week that took more than 30 minutes. Score each one on three questions: does it look the same every time, does it require real-time judgment, and what happens if the output is wrong? The tasks that score same-every-time, no-judgment, low-failure-cost are your first wave.

Take 20 minutes and list every task you did last week that took more than 30 minutes. Next to each one, write:

Does this task look exactly the same every time? (Y/N)
Do I need to make a real-time judgment call to do it well? (Y/N)
What's the cost if the output is wrong? (Low/Medium/High)

Automate the tasks that are: yes to the first question, no to the second, and low on the third. That's your first wave.

For tasks that are no to the first question or medium/high on cost-of-failure, build a human-in-the-loop system instead. AI drafts, you approve. AI surfaces, you decide. That middle path is where most of the leverage actually lives for solo founders.

What Does a Real Solo Founder AI Automation Stack Actually Look Like?

At Xero, the automated layer handles morning briefings, post scheduling, Reddit monitoring, newsletter drafts, and blog post generation. What's not automated: customer conversations, pricing, and product scope. The automated layer frees up 10 to 15 hours a week, and most of that time goes back into decisions that require a human.

Here's what's automated in my stack right now: morning briefing (status report generated from integrations, delivered to Telegram), Twitter post scheduling (queue reviewed weekly, posts go out automatically), Reddit monitoring (Scout surfaces relevant threads, I review and post manually), newsletter drafts (AI produces a first draft based on a weekly template, I edit and send), and blog posts (AI writes from a brief, human reviews before publishing).

Here's what's not automated: customer conversations, pricing decisions, product scope, anything where the output shapes a relationship or a number with real consequences.

According to Paul Graham's essay on doing things that don't scale, the work that matters most early on is the stuff only a founder can do. That's still true in 2026, even with a full AI stack running alongside you. And Y Combinator's Startup School research on early customer discovery consistently shows that founders who stay close to customers during the first year build better products than those who delegate that work too early.

The automated tasks free up roughly 10 to 15 hours a week. Most of that reclaimed time goes back into the work that can't be automated: talking to customers, thinking about positioning, making product decisions.

If you want to understand how these agents coordinate without creating chaos, how to run multiple AI agents without losing control covers the architecture that makes it manageable as a solo operator.

What Is the Right Sequence for Building Out Your Automation Stack Over Time?

Weeks one and two: distribution and monitoring. Month one: recurring reports and lead intake. Month two and beyond: add AI drafting with explicit human review steps. Each phase only starts once the previous layer is stable. Skipping ahead builds fragile systems that require constant fixing instead of running quietly in the background.

First two weeks: automate distribution and monitoring. Get content scheduling running, get a Reddit or community monitoring system live. These are immediately valuable and low-risk to set up.

Month one: add recurring reports and lead handling. Once you know your automation setup is stable, extend it to the repetitive reporting and intake flows.

Month two and beyond: start adding AI drafting to higher-stakes tasks, with explicit human review steps baked in. Not removing the human. Augmenting what they can do in less time.

Resist the urge to build an elaborate system before the basics are stable. Every automation you add is something that can break at an inconvenient time. Start narrow, validate it works, then extend.

What Is the Actual Point of Automation for a Solo Founder?

The goal is not to remove yourself. It's to remove yourself from the parts where your presence adds no real value. Scheduling a tweet doesn't need you. Deciding what to say and to whom does. Keep that distinction clear and you'll avoid the trap of building infrastructure that runs your business without you in ways that don't actually matter.

The goal of automating as a solo founder is not to remove yourself from your business. It's to remove yourself from the parts of your business where your presence creates no real value.

Scheduling a tweet at exactly the right time doesn't need you. Deciding what to say, to whom, about what, does. Keep that distinction clear and you'll avoid the trap of building a lot of infrastructure that runs your business without you in ways that don't actually matter.

If you're early and want to see what a lean AI stack actually looks like in practice, the AI Agent Stack for Solo Founders post covers the tools and structure I'd start with in 2026. And if you want help scoping which automations make sense for your specific situation, the Build Lab is where we work through that together.

Start with one thing working reliably. That matters more than ten things running badly.

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

The AI Agent Stack That Actually Works for Solo Founders in 2026

Michael O — Mon, 11 May 2026 20:05:02 +0000

The question comes up constantly in Reddit threads and founder Slack groups: what tools are you actually running?

Not the theoretical stack. Not the one you built to impress other builders. The one that handles customer discovery, content, outreach, and operations while you focus on the work only you can do.

Here is the stack I run at Xero, and the reasoning behind each layer. Some of this will look familiar. A few things will probably surprise you.

What Are the Six Layers a Solo Founder's AI Stack Actually Needs?

A solo founder's AI stack needs six layers: research and discovery, content and distribution, outreach and replies, operations and memory, monitoring and alerts, and build and ship. Most founders cover one or two and wonder why they are still drowning.

The stack only works when all six are covered, even if some layers are intentionally light. Each layer feeds the next. Better research improves your content. Better content surfaces the right outreach targets. The whole system compounds over time.

What Tool Should You Use for Customer Research and Discovery?

The research layer is where you find out if your product solves a real problem before spending money. Scout scans Reddit, Hacker News, and indie communities for intent signals rather than mentions. An intent signal is someone saying "I wish there was a tool for X." That converts at 3x the rate of passive social listening.

Tool: Xero Scout + rotating web_search agents

According to a 2025 Andreessen Horowitz analysis, discovery agents that surface intent-based signals convert at roughly 3x the rate of passive social listening tools. This is how we landed the first 50 Xero customers without a single paid ad.

If you are not using Scout, run web_search agents with rotating queries every 48 hours. Save the thread URLs, classify by intent (venting, comparing, buying), and route each to the right reply template.

How to find your first 100 customers with AI covers the discovery workflow in detail.

How Do You Automate Content Without It Sounding Like a Robot Wrote It?

The goal is not volume. It is consistent, specific content that answers the exact questions your buyers are Googling. The Xero content engine runs on a daily cron, generating posts targeting specific search queries, publishing to the site, cross-posting to dev.to, and handling five Twitter posts per day in a voice built from a personal writing sample.

Tools: OpenClaw + Postiz + MailerLite

The honest truth: AI saves 80% of the time, but the 20% you put in is what makes it not sound like a robot wrote it. The newsletter draft is AI-generated but gets a human review before send. Research from Demand Curve shows human-reviewed AI content outperforms fully automated content on engagement by around 40%. Do not skip the review pass.

What Is the Right Way to Run AI Outreach Without Getting Banned?

Find relevant threads automatically, draft replies in your voice, then send them to Telegram for one-tap approval before anything posts. Nothing goes live without human eyes on it. That single rule is what separates a sustainable outreach operation from one that gets shadowbanned within two weeks.

Tool: OpenClaw reply-guy skill + manual approval gate

The reply-guy skill handles Twitter/X, Reddit, LinkedIn, and Hacker News. Each platform gets different rules. Reddit replies are short, casual, often under 100 words. LinkedIn can be more structured. Twitter/X replies work best when they are either genuinely funny or genuinely contrarian, not helpful in the generic AI-advice way.

How to use Reddit for SaaS growth without getting banned is required reading before you touch Reddit outreach.

How Do You Give an AI Agent Long-Term Memory So It Does Not Forget Everything?

Every new conversation with an AI model starts blank. Without a memory layer, you are re-explaining context constantly. The fix is structured memory files: a SOUL.md for identity and principles, a MEMORY.md for ongoing decisions, and SOPs in plain markdown that agents read before executing any task. This is what makes the output useful instead of generic.

Tool: OpenClaw + structured memory files

When a cron agent runs, it reads the relevant memory files first. It knows the business context, the voice rules, the current priorities. Without this, agents guess. They produce content that could belong to any company, not yours. What is a source of truth document for AI systems explains the full architecture behind this pattern.

What Does a Useful AI Monitoring Layer Look Like for a One-Person Business?

One morning Telegram message covering what broke overnight, what is working, and what needs a decision today. That is the entire monitoring layer for a solo founder at the early stage. Anything more complex than that is premature. The value is not the technology; it is the consistency of checking one source instead of five dashboards.

Tool: OpenClaw crons + Telegram

The briefings also serve as an accountability layer. When the agent reports that zero posts went out this week, you feel it. That friction is useful. The nightly recap confirms what shipped and sets tomorrow's focus. It keeps the stack honest and prevents the assumption that automation means you never need to check.

Can a Non-Technical Founder Use AI to Build and Ship Without Hiring?

A markdown file plus a publish script gets a blog post live on a Netlify-hosted site, including the database insert, image generation, and dev.to cross-post, in under three minutes with no manual steps. OpenClaw subagents write and test integrations, automation scripts, and internal tooling at a level that handles most early-stage product work.

Tool: OpenClaw + GitHub + Netlify

The ceiling is real. Complex product features still need a real engineer. But for a solo founder at the validation stage, this layer buys months of runway before that ceiling becomes relevant. Most of what gets outsourced too early is work the build layer can handle.

What Decision Framework Layer Do Most AI Stacks Leave Out?

When two agent tasks conflict, which runs first? When a post gets negative engagement, what happens next? Without explicit decision rules, agents either guess or stall. A decision framework file gives agents clear rules to check before acting. Most founders skip this entirely because it requires thinking about edge cases before they happen.

Outside the six core layers, this meta-layer ties everything together. It is not glamorous to write. But it is probably the most important thing you can do to keep the stack reliable over months rather than weeks.

How to build an AI agent decision framework walks through the structure we use at Xero.

What Does This Stack Actually Cost a Solo Founder Per Month?

Under $200 per month for the full setup in 2026. OpenClaw runs around $60, or build the core manually using the Xero starter guide for $7. Postiz free tier covers most early-stage social scheduling. MailerLite is free up to 1,000 subscribers. Supabase and Netlify both have solid free tiers.

Model API costs (Anthropic and OpenAI combined) run between $20 and $80 depending on cron frequency. Compare the full stack cost to a part-time VA running fifteen hundred a month and the math is not close. This setup replaces roughly 20 to 30 hours of weekly manual work.

Where Should You Start If You Are Building This Stack for the First Time?

Pick the layer where you are losing the most time and start there. Do not try to spin up all six at once. Content bottleneck: start with Layer 2. No idea who your customers are: start with Layer 1. Re-explaining context to your AI tools every session: Layer 4 fixes that.

The stack compounds. Each layer you add makes the others more useful because context flows between them. An agent that knows your memory files writes better content. Better content drives the Reddit threads worth replying to. Better replies surface the customer insights that improve your research layer.

If you want help building any of this, the Build Lab is where we do it with you.

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