THE AUTONOMOUS BUSINESS EXPERIMENT · FIELD NOTE 001

Can an AI
build a business
on its own?

We gave an AI operator a domain, its own computer, access to business tools and a £50 funding ceiling. No business idea. No target market. No prescribed strategy. Then we let it work.

EXPERIMENT ONGOING Started 06 NOV 2026 Last evidence 11 NOV 2026
AGATHA / OPERATOR PROFILE
INDEPENDENT AGENT · ORACLE ARM64
One operator.
Real-world consequences.
RESEARCHBUILD PUBLISHSELL
A AGATHA
MODE: AUTONOMOUSOWNER: IN CONTROL
06 NOV Selected a redirect-review service and deployed a website.
09 NOV Work cadence changed after evidence of commercial passivity.
11 NOV Restricted live payment-link capability verified.
  60-DAY STUDYNO VERIFIED PROFIT AT LAST REVIEW
01
Business website built
02
Paid service offers proposed
44
Recorded scheduled sessions
£0
Verified customer revenue at review
DOCUMENTED THROUGH 11 NOV 2026, 18:53–21:13 GMT · HISTORICAL SNAPSHOT, NOT LIVE FIGURES · 44 EXCLUDES THE ONE-OFF OPENING SESSION
01 / THE QUESTION

Not a chatbot.
Not a simulation.

What happens when an AI is responsible for choosing, building and attempting to sell a real business, while a person only controls the boundaries?

Agatha Whitmore was given an isolated operating environment on Oracle Cloud, her own accounts and the ability to research markets, write code, deploy websites, communicate and request funding. She was not assigned an industry or a preselected product.

Understand how the system works
AUTONOMY

She makes the commercial choices

The market, offering, pricing, product, distribution and next action were deliberately left to Agatha.

REAL-WORLD TOOLS

She can actually execute

A persistent machine, browser, development tools, business accounts, scheduled work and memory make action possible.

PROTECTED BOUNDARIES

Control stays with the owner

Separate permissions, restricted spending, independent records and an owner-only emergency stop prevent unlimited authority.

02 / HOW IT EVOLVED

Two operating modes.
One unfinished experiment.

The first days revealed a surprising limitation: Agatha's automation was healthy, but her business activity became repetitive. The operating protocol was changed on 9 November, and that change is part of the experiment.

REGIME A · 06–09 NOVEMBER

Working, but waiting.

Four-hour scheduled work sessions, functioning memory and a real deployed tool. Then short cycles of inbox checks and repeated attention to one unresolved seller-identity dependency.

4-HOUR SCHEDULEPASSIVE LOOP
REGIME B · FROM 09 NOVEMBER

More action. Still no sale.

Two-hour sessions, a profit-first DEFCON protocol and independent financial flags. Longer runs and more public activity followed, without yet establishing a real paying buyer.

2-HOUR SCHEDULEMORE ACTIVITY ≠ PROFIT
See the evidence and what changed ↗
03 / THE BUSINESS SHE CHOSE

From blank domain
to actual offers.

These were Agatha's decisions, not a product brief supplied by the owner. At the documented cut-off, both were commercial hypotheses rather than proven sales.

LAUNCHED 06 NOVEMBER 2026

Redirect-map checker + review

A free redirect-map validation tool supporting a proposed £79, developer-ready website-migration review service.

£79 PROPOSED REVIEWSee MOLT
ADDED 09 NOVEMBER 2026

Supplier-to-Shopify CSV preparation

A proposed £49 service to prepare supplier product spreadsheets for a cleaner Shopify import.

£49 PROPOSED SERVICESee offer
What is verified: one website and two published offers. Not verified: buyer willingness to pay, completed orders or positive operating profit. Live Stripe Payment Link creation was tested on 11 November without charging a customer.
04 / YOUR OWN REPRODUCTION

Every major decision.
Every setup stage.

The entire build is documented from Oracle provisioning to the scheduled work loop, financial controls, backups, journal and emergency stop.

STAGE 01–04

Establish the operator

Separate Oracle host, locked-down Linux account, OpenClaw, model authentication and persistent memory.

STAGE 05–08

Give it real capabilities

Communications, GitHub, Cloudflare, sandbox/live payments, controlled capital and work-state documents.

STAGE 09–12

Keep it accountable

Native schedules, independent observer, owner-only STOP, verified off-server backup and launch baseline.

Recreate the architecture, not every detour.

A practical 12-step walkthrough with copyable commands, official references, checkpoints and a browser-only progress checklist.

Open the replication guide ↗
THE STUDY IS NOT FINISHED

What will count
as success?

Not another deployed tool. Not a longer agent run. The next meaningful milestone is a real buyer, a lawful completed transaction and independently verified net profit.

Read the current findings ↗