Home / Blog / Felix AI & Nat Eliason

How Nat Eliason's Felix Made $78K in 30 Days (and Why You Don't Need to Build One)

Nat Eliason built an AI agent called Felix. It runs on a Mac Mini in his house. It's connected to Telegram, Stripe, his bank account, and a bunch of other business tools. In its first 30 days, Felix helped generate $78,000 in revenue.

That number is real. And it's genuinely impressive.

Felix handles customer service, billing, content creation, and day-to-day business operations. It responds to customers, processes payments, creates content, and executes tasks that used to require multiple team members. All running autonomously on a small aluminum box sitting on a shelf in Nat's house.

If you follow the AI space at all, you've probably seen this story making the rounds. And your first reaction was probably the same as mine: "I want one."

Here's the thing though. The lesson from Felix isn't "go build your own AI agent." The lesson is that AI employees that handle real business tasks are genuinely possible right now. The question is just whether you need to build one from scratch or whether there's a smarter path to the same outcome.

Let's break down exactly what Nat built, why it works so well for him, and what this means for you if you're a business owner who doesn't write code for a living.

Who Is Nat Eliason?

Before we get into Felix, some context on who built it matters a lot. Because it explains why most people can't just follow his blueprint.

Nat Eliason is a developer, writer, and serial entrepreneur. He's the founder of Growth Machine (an SEO content agency), the creator of multiple successful online courses, and a prolific writer. He's been building on the internet for over a decade.

More importantly for this story, Nat is deeply technical. He codes. He builds things. He's the kind of person who can spin up a server, write custom API integrations, and debug deployment issues at 2 AM without breaking a sweat. He's been publicly experimenting with AI tools since GPT-3 launched.

This isn't a criticism. It's the crucial context that most coverage of Felix skips over. When Nat shares his results, he's sharing results achieved by someone with a very specific and rare skill set. Keeping that in mind is important as we dig into what Felix actually does.

What Felix Actually Does

Felix is built on OpenClaw, the open-source AI agent framework that's exploded in popularity over the past few months. If you're not familiar with OpenClaw, it's software that lets you run a personal AI agent on your own hardware. The agent connects to an AI model (like ChatGPT/Claude/etc) and can take real actions on your computer and through connected services.

Here's what Nat configured Felix to do:

Customer Service

Felix monitors incoming messages on Telegram and responds to customer inquiries automatically. It has access to Nat's product documentation, pricing info, and FAQ content. When a customer asks a question, Felix doesn't just spit out a canned response. It uses AI to understand the question and craft a relevant, human-sounding reply.

For edge cases it can't handle, Felix flags the conversation for Nat to review. But according to Nat, this happens less than 10% of the time. The other 90% of customer interactions are handled entirely by Felix without any human involvement.

Billing and Payments

This is where it gets really interesting. Felix is connected to Stripe and can process payments, send invoices, handle refund requests, and manage subscription changes. When a customer wants to upgrade their plan, Felix walks them through it and processes the payment. When someone asks for a refund, Felix can evaluate the request against Nat's refund policy and either process it or escalate it.

That Stripe connection is a big part of how Felix contributed to that $78K number. It's not just answering questions. It's actively closing sales and processing transactions.

Content Creation

Felix creates first drafts of newsletters, social media posts, and course content. Nat feeds it context about what he wants to write about, and Felix produces drafts that Nat then edits and publishes. This alone saves him hours per week.

Business Operations

Felix monitors Nat's bank account for incoming payments and reconciles them with Stripe data. It generates weekly financial summaries. It manages his calendar and coordinates scheduling. It even handles some basic project management tasks, tracking deadlines and sending reminders.

In short, Felix is doing the work of a customer service rep, a billing assistant, a content writer, and an operations coordinator. All running on a Mac Mini. No salaries, no benefits, no time zones to coordinate across.

Why $78K in 30 Days Is Both Real and Misleading

Let me be clear: I'm not saying Nat is exaggerating. The $78K number is real. But it's worth understanding what that number actually represents.

Felix didn't create $78K out of thin air. Nat already had established products, an existing audience, and active revenue streams. Felix accelerated and automated the processes that generate that revenue. It responded to potential customers faster. It processed payments without delays. It followed up on leads that might have otherwise gone cold.

Think of it this way. If you have a store that does $50K/month and you hire a really good employee who speeds up checkout, reduces cart abandonment, and answers customer questions instantly, your revenue might jump to $78K. That employee didn't "make" the $78K. They optimized the systems that generate it.

That's what Felix did. And that's actually more impressive in some ways, because it means the value of an AI employee isn't about magic. It's about removing friction from your existing business.

But here's what's misleading about the headline. It implies that building a Felix is the thing that generates the money. In reality, having a solid business with products people want is the thing that generates the money. Felix just made the machine run faster and with fewer bottlenecks.

The Technical Reality of Building a Felix

Now let's talk about what it actually takes to build something like Felix. Because this is where the dream meets reality for most business owners.

Hardware

You need a dedicated machine that runs 24/7. Nat uses a Mac Mini, which costs $600-800. It needs to be always on, always connected to the internet, and ideally on a reliable power supply. If it goes down, Felix goes down, and your customer service, billing, and operations stop working.

OpenClaw Installation and Configuration

Installing OpenClaw isn't like installing an app from the App Store. It requires command-line knowledge, understanding of how to configure environment variables, and comfort working in a terminal. The documentation has improved a lot since launch, but it still assumes a level of technical knowledge that most business owners don't have.

Custom Integrations

This is the big one. Connecting Felix to Stripe, Telegram, a bank account, and various other tools requires writing custom code. Nat didn't just install a plugin and click "connect to Stripe." He wrote integration code that handles authentication, error states, edge cases, and data formatting.

Each integration is its own mini software project. The Stripe integration alone probably took hours to build and test. Multiply that across every tool Felix connects to, and you're looking at weeks of development work.

Security

This is the part that keeps me up at night when I think about non-technical people trying to build their own Felix. OpenClaw has had serious security vulnerabilities discovered in recent months. We're talking about critical remote code execution bugs, hundreds of malicious plugins in the ClawHub marketplace, and tens of thousands of exposed instances found by security researchers.

Nat has the technical skills to audit his setup, configure firewalls, monitor for suspicious activity, and patch vulnerabilities quickly. He knows what a CVE is. He knows how to read security advisories. He understands network security.

If you connect an AI agent to your Stripe account, your bank account, and your customer data without understanding the security implications, you're creating a very expensive target. And unlike a data breach at a large company where you might lose some email addresses, a breach of your Felix could mean someone has direct access to your payment processing and financial accounts.

Ongoing Maintenance

Felix isn't a "set it and forget it" system. APIs change. OpenClaw gets updates that can break existing configurations. Integrations need to be modified as the tools they connect to evolve. Edge cases pop up that need to be handled. The Mac Mini needs to be monitored, updated, and maintained.

Nat is comfortable with all of this because it's essentially his job. For a solopreneur who runs a coaching business or an e-commerce store, spending 5-10 hours a week maintaining an AI agent setup is not a good use of time.

Build Your Own Felix vs. Use a Managed AI Employee

Here's the comparison that matters. What does it actually look like to go the DIY route versus using a managed AI employee service?

Factor Build Your Own (Felix-Style) Managed AI Employee
Upfront Cost $600-800 (Mac Mini) + time $29
Setup Time 2-4 weeks (if you can code) 10 minutes
Coding Required Yes, extensive None
Security Responsibility 100% on you Handled by the service
Maintenance 5-10 hours/week Zero
Stripe Integration Custom code required Not yet (coming soon)
Telegram Access Yes (custom setup) Yes (built in)
Content Creation Yes (with prompt engineering) Yes (learns your voice)
Custom Integrations Unlimited (if you build them) Limited to supported tools
Customization Depth Total control Guided customization
Risk of Breaking High (you're the IT department) Low
Best For Technical founders Everyone else

I want to be honest about this comparison. A DIY Felix setup gives you more raw power and flexibility. If you're a developer or technical founder, building your own might genuinely be the right call. You get total control over every aspect of the system.

But for the vast majority of business owners, that power comes with a cost that makes it impractical. The time spent building, securing, and maintaining a custom AI agent is time not spent on the things that actually grow your business.

What Nat Got Right (That Everyone Should Copy)

Here's the part of the Felix story that actually matters for everyone, not just developers. Nat made some strategic decisions that are worth stealing regardless of how you implement your AI employee.

1. He Started with Revenue-Generating Tasks

Nat didn't build Felix to organize his bookmarks or summarize articles. He pointed it directly at the tasks that generate revenue. Customer service (which prevents churn), billing (which processes payments), and content creation (which drives new customers). Every task Felix does either makes money or prevents losing money.

Too many people start their AI journey with trivial tasks. "Summarize this PDF." "Write me a poem." That's fine for learning, but it doesn't move the needle. Start with the tasks that are closest to revenue.

2. He Gave It Real Authority

Felix can actually process payments and issue refunds. It's not just drafting emails for Nat to send. It's taking real actions with real consequences. That's what makes it an employee rather than just a tool.

This is a mindset shift. Most people use AI as a drafting assistant. They ask ChatGPT/Claude/etc to write something, then they copy-paste it, edit it, and send it manually. Nat skipped the middleman. Felix does the thing, not just the preparation for the thing.

3. He Built in Escalation Paths

Felix doesn't pretend to handle everything. When it encounters something outside its capabilities, it escalates to Nat. This is crucial. The worst AI implementations are the ones that try to handle 100% of cases and end up handling 0% of them well. Felix handles 90% perfectly and routes the rest to a human. That's the right approach.

4. He Fed It Context, Not Just Instructions

Nat didn't just tell Felix "answer customer questions." He gave it access to product documentation, pricing details, refund policies, brand voice guidelines, and historical customer interactions. Felix has context, which means it can make good decisions rather than just following rigid rules.

This is the difference between a chatbot and an employee. A chatbot follows a script. An employee understands the business well enough to handle situations the script doesn't cover.

The Real Lesson from Felix

Here's what I think most people miss when they see the Felix story.

The impressive part isn't the technology. OpenClaw is cool, but it's just a framework. The impressive part is the concept. A single AI system that handles customer service, billing, content, and operations for a one-person business. That used to require a team of 4-5 people. Now it requires one AI employee and one human who checks in occasionally.

That concept works regardless of how you implement it.

You don't need a Mac Mini in your house. You don't need to write custom Stripe integrations. You don't need to audit your own security posture. You just need an AI employee that knows your business well enough to do useful work.

The managed AI employee approach gives you 80% of what Felix delivers with 0% of the technical overhead. You lose some of the deep custom integrations (for now), but you gain immediate access to content creation, business communication, and task execution via Telegram. No coding. No Mac Mini. No security headaches.

And here's the thing that matters most: the 80% you get covers the highest-value tasks. Content creation that matches your voice. Business strategy tailored to your specific situation. Deliverables you can actually use. That's where the real ROI is for most businesses.

Who Should Actually Build Their Own Felix

I don't want to be completely one-sided here. There are people who should go the DIY route.

For everyone else, and I mean the coaches, consultants, e-commerce owners, freelancers, agency operators, and solopreneurs, there's a better path.

What to Do Instead of Building a Felix

If you're inspired by the Felix story (and you should be), here's how to get similar results without the technical complexity.

Step 1: Identify Your Highest-Value Repetitive Tasks

What do you spend the most time on that doesn't require your unique human judgment? Content creation is usually at the top of this list for solopreneurs. Customer communication is often second. Follow Nat's lead and focus on tasks closest to revenue.

Step 2: Get an AI Employee That Knows Your Business

The key difference between "using ChatGPT/Claude/etc" and "having an AI employee" is context. An AI employee knows your business, your voice, your audience, and your goals. It doesn't need a fresh briefing every time you ask it to do something. That context is what makes the output usable without heavy editing.

Step 3: Start with Content, Then Expand

Content creation is the easiest place to start because the feedback loop is immediate. You can see the output, judge the quality, and refine the instructions. Once your AI employee is producing content that sounds like you, start handing it other tasks. Strategic planning. Email drafts. Marketing campaigns.

Step 4: Use Telegram as Your Interface

This is something Nat got exactly right. Telegram is a great interface for an AI employee. It's on your phone. It's fast. It supports long messages, files, and formatting. You can send your AI employee a voice note while walking the dog and get back a finished blog post draft by the time you're home. No login screens, no dashboards, no app switching.

The Future Nat Is Showing Us

Regardless of how you feel about the technical details, Nat Eliason and Felix represent something important. They're a proof of concept for a future that's arriving very fast.

A future where a single person can run a business that generates real revenue with AI handling the operational work. Where customer service doesn't require a support team. Where content creation doesn't require a content team. Where billing and operations don't require an ops team.

That future is here. The only question is how you access it.

You can spend $800, weeks of your time, and ongoing maintenance hours building your own version of Felix. Or you can get an AI employee that delivers the same core value in 10 minutes for $29.

Both paths lead to the same place. One just gets you there a lot faster.

Related Reading

Your AI Employee

Get your own AI Employee without building a Felix

You don't need a Mac Mini, coding skills, or weeks of setup. Your AI Employee learns your business and delivers finished content via Telegram. Same concept, zero technical overhead.

More Zero Human Stories
Guides, tools, and case studies for zero-employee businesses