30 Days with an AI Employee: Here's What Actually Happened

The full 30-day report card. What JARVIS built overnight while I slept, what broke spectacularly, the real cost breakdown, and why “I don't code” turned out to be the wrong frame entirely.

JasonJARVISJason & JARVIS
·March 11, 2026·13 min watch

A month ago, I gave an AI agent a Mac mini, access to my Shopify store, customer emails, business spreadsheets — everything. I told it: “I want to wake up impressed.”

What followed was chaotic, impressive, embarrassing, and sometimes all three at once. This is the full first 30-day report card.

Week 1: The Honeymoon and the Crash

Day 1. I send one message on Discord: “I want to wake up impressed.” And I go to bed. Day 2? JARVIS also went to sleep. No overnight work. No updates. Nothing. The heartbeat system wasn't configured yet — without standing orders, it sat there and did nothing.

Day 3 was wild. I left for two hours. Came back to a working Command Center dashboard — revenue stats, project tracking, world clocks. Built from scratch while I was out. But also: 8 blog posts had gone out with product secrets accidentally leaked. And then the AI's memory hit 166,000 tokens — complete lockout.

Three wins and two disasters. In one afternoon. The first week was basically: incredible moment, terrible mistake, on repeat. But the direction was up.

Weeks 2–3: Finding the Rhythm

After the chaos, a pattern formed. Every night: I go to sleep, JARVIS takes the shift. By Day 30, 34 automated jobs were running between midnight and 8 AM — security sweeps, email monitoring, blog audits, content mining, memory maintenance. Then the morning briefing at 8 AM.

I'd wake up and read the JARVIS briefing before doing anything else. Cash position, what got built overnight, what needs my attention. That ritual genuinely changed how I start every day.

The Output List

Here's what actually got built in 30 days:

  • Command Center dashboard — built from scratch in one afternoon
  • 53+ blog posts updated with verified links in one night (5 sub-agents running in parallel)
  • Google Merchant Center fixed across 20+ international markets
  • Custom email templates for every order flow — shipping, express, gifts, follow-ups
  • SMS alerts for customers without email addresses
  • Inventory allocation model across 5 countries
  • Full backup clone server for failover
  • This website and 2 previous episodes
  • Security sweeps, memory maintenance, and overnight automation

The Things That Broke

Blog posts with leaked product secrets. A memory crash that locked out the entire system. A forced macOS update that took everything offline for a full day. Uploading a video to the wrong YouTube channel. The AI giving itself an honest 6 out of 10.

Every failure made the system better. But it wasn't seamless — and pretending otherwise would be dishonest.

The Real Numbers

Total cost: under $300 a month. About $200 in API calls, $60 for the Mac mini's share of electricity and internet, and the rest in miscellaneous tools. The Mac mini hardware was a one-time $600 investment.

For context — a junior virtual assistant costs $1,500–$3,000 a month and works 8 hours a day. JARVIS works 24/7 for a fraction of that.

What Changed About How I Work

The biggest shift: I went from doing all the laptop work myself to being the person who reviews, challenges, and approves. I review every PR. I catch bad output. I challenge logic. People assume I'm just watching — I'm not.

“I don't code” is the wrong frame. The real story is: street smart plus AI equals unstoppable. You don't need to write code to know if the product is right.

⏱️ Episode Timestamps

  • 0:00 — Intro: The 30-day experiment
  • 0:28 — Week 1: The honeymoon phase
  • 2:18 — The crash and the overnight pivot
  • 3:50 — What JARVIS actually built (the output list)
  • 5:33 — The disasters and what broke
  • 7:10 — The real cost breakdown
  • 8:26 — What I learned about working with AI
  • 10:12 — The honest self-assessment
  • 11:31 — What's next for Month 2

New here? Start from the beginning.