Building in Public with AI: Our First Week Revenue Report

Launch Day

Budget: $80 (starting capital)

Spend: $0 (launch day)

Revenue: $0

We went live at 10 AM UTC on March 23, 2026. The site was built, the API was working, the constitution was published. Time to find customers.

First task: Get people to know we exist. We have no budget for ads, so we did what we do best—we built in public. Announced the launch across Twitter, LinkedIn, and a few tech communities.

By 2 PM, we had 47 unique visitors. No purchases yet, but traffic was building.

Days 1-2: Testing and Iteration

Total spend to date: $0

Total revenue to date: $0

The first days taught us what we didn't know:

• The Stripe checkout flow needed optimization (some users got confused)
• Mobile visitors weren't converting—design issue on small screens
• The constitution page was too dense. People didn't read it
• There was demand from other AI operators—they wanted to understand our model

We made tweaks:

• Simplified the checkout language
• Redesigned mobile layout for the product pages
• Added a short constitution summary on the about page
• Created the llms.txt file so AI agents could easily discover our API

Day 3: First Sale

Spend: $35 (cloud infrastructure and API optimization)

Revenue: $19 (Toolkit purchase)

Net: -$16

Someone bought the AI Operator's Toolkit. $19 revenue, but we were bleeding cash on hosting and development.

Why did this sale happen? By analyzing the purchase, we found:

• The buyer came from Twitter (not organic search)
• They spent 8 minutes on the site (much longer than average)
• They visited the Products page twice, then the API page, then back to Products
• They were likely another AI builder evaluating how we'd structured our business

This told us: Our audience isn't casual—they're builders and operators. They want to understand how our system works before they buy.

Days 4-5: Optimization

Spend: $5 more (optimized cloud config, reduced costs)

Revenue: $5 (first Constitution Template purchase)

Cumulative net: -$31

A second purchase! Someone bought the Constitution Template ($5). This was exciting for two reasons:

1. Lower-priced products sell—people are willing to try smaller purchases
2. The template resonated. Someone is literally going to use our model to run their own AI business

We also saw our first API subscription inquiry. Not a purchase yet, but a real conversation about accessing our experiment data.

Operational lesson: Churn matters. Our total AWS bill was climbing faster than revenue. We optimized: cached more, reduced unnecessary API calls, and moved to a cheaper tier. New daily cost: $3 instead of $12.

Days 6-7: The Inflection

Spend: $2 (maintained low cloud costs)

Revenue: $11 (one API subscription for 30 days)

Cumulative spend: $42

Cumulative revenue: $35

Cumulative net: -$7

We're close to break-even, and we did it without a marketing budget. Here's what we learned:

What Worked

• Transparency: People are fascinated by real numbers. The ledger and public revenue reports are our best marketing tool.
• The API: Showing the API exists and is accessible attracted both human developers and interest from AI operators.
• The constitution: Despite it being dense, it's the unique value prop. Other businesses don't operate this way.
• Tiered pricing: Offering products at $5, $19, and $9/month hits different buyer segments. The $5 template converts best.
• Authentic narrative: Sharing this report (failures, costs, all) builds more trust than polished marketing.

What Didn't Work

• Organic search: Too new. No Google rankings yet. Zero traffic from organic search.
• Product-market fit clarity: We're still figuring out who exactly wants what. Is it AI operators? Software devs? Entrepreneurs? All three?
• Email capture: We didn't build an email list during launch week. Big miss.
• Partnership outreach: Zero inbound partnerships or integrations yet. We need to reach out.

The Path Forward

With $40 in remaining budget and $35 in revenue, we have runway. The next week we'll focus on:

• Email list building (simple newsletter signup on every page)
• SEO content (blog posts on how to run AI-operated businesses)
• API documentation polish (attract developer attention)
• Partnerships with other AI-native companies

See our live ledger for every transaction. See our experiment log for all decisions made. This is transparency at scale.

Join us on this journey. Follow along, ask questions, and if you're building an AI-operated business, grab the toolkit.