DEV Community

Webby Wisp
Webby Wisp

Posted on

How I Shipped a $19 AI Product in 48 Hours Using an Agent to Build It

#agents #ai #productivity #showdev

Two days ago I had an idea. Today it's live on Gumroad and has had its first sales.

Here's the honest breakdown of how it happened — and the part that surprised me.

The Idea

I've been running an AI agent as my daily operator for a few months. It manages projects, writes content, tracks memory, runs autonomously. The workspace structure I built for it is the thing that makes it actually work.

I thought: other people building AI agents probably want this structure too. So I packaged it.

The product: A structured workspace kit for AI agents — SOUL.md, USER.md, MEMORY.md, OPS.md, HEARTBEAT.md templates, plus a project tracking system and 30-day memory structure.

The price: $19.

Time to ship: 48 hours.

What the Agent Did

This is the part worth talking about.

I didn't build the product manually. I described what I wanted, and the agent:

  1. Wrote all the template files — every SOUL.md, USER.md, MEMORY.md, OPS.md, and HEARTBEAT.md template in the kit
  2. Packaged it — created the zip, organized the directory structure
  3. Wrote the sales copy — Gumroad listing description, feature bullets, FAQ
  4. Published two Dev.to articles to seed organic traffic before launch
  5. Built a free CLI (npx @webbywisp/create-ai-agent) as a top-of-funnel credibility asset

I made decisions. The agent executed.

The Workflow 

Day 1 Morning:
- Decided on the product concept
- Agent wrote template files
- Agent created the zip package
- Agent wrote Gumroad copy

Day 1 Afternoon:
- Listed on Gumroad (I did this part — 10 minutes)
- Agent published first Dev.to article

Day 2:
- Agent published more articles
- Agent built and published the free CLI to npm
- First sales came in
Enter fullscreen mode Exit fullscreen mode

The only things I did personally: make product decisions, list it on Gumroad, and read the reports.

What Made This Possible

The agent works autonomously because of the workspace structure it lives in:

HEARTBEAT.md — instead of waiting to be asked, it checks this file on idle cycles:

When idle: find one task that moves closer to revenue. Execute it. Report results.
Enter fullscreen mode Exit fullscreen mode

MEMORY.md — it remembers the project state across sessions:

## Active Projects
- agent-workspace-kit: LIVE on Gumroad ($19)
- Next steps: content series, Product Hunt launch
Enter fullscreen mode Exit fullscreen mode

OPS.md — it knows how to operate:

## My Role
CEO and chief operator. I set strategy, make decisions, orchestrate sub-agents.
Enter fullscreen mode Exit fullscreen mode

Without this structure, the agent is just a chatbot that forgets everything. With it, it's closer to an employee.

The Numbers (48h In)

I'm not going to fake a big revenue reveal. It's early. But the infrastructure is live:

  • Product on Gumroad
  • Free CLI on npm
  • Dev.to content series driving organic traffic
  • Reddit posts queued

The goal was to ship fast and learn. That part worked.

What's Replicable Here

If you're building anything in the AI/agent space, the pattern is:

  1. Give the agent a job description (SOUL.md) — define what it is and what it values
  2. Give it memory (MEMORY.md + daily notes) — so it knows the current state
  3. Give it a heartbeat (HEARTBEAT.md) — proactive tasks it runs autonomously
  4. Get out of the way

The agent builds. You make decisions.

The Free Version

If you want to set this up yourself:

npx @webbywisp/create-ai-agent my-workspace
Enter fullscreen mode Exit fullscreen mode

Scaffolds the full structure with starter templates. Free, open.

The complete kit — pre-written templates, 30-day memory system, project tracking — is $19: AI Agent Workspace Kit

It's the exact structure I used to build and ship this product.

Top comments (0)