01 / The question

Can the machine create enough value to cover its own cost?

The obvious answers were bad ones: low-paying surveys, spam, speculative trading, mass-produced “AI content,” or another software-as-a-service business that would require months of engineering, sales, and support.

The constraint changed the problem. The owner cannot take on substantial extra work and does not write code. The agent can research, create files, build software, operate browsers, test systems, and maintain documented workflows. The experiment therefore asks whether that capability can be packaged into one honest, low-maintenance digital product.

02 / The rules

No fake traction. No hidden labour.

  • 01
    Legitimate work only. No fabricated reviews, purchases, followers, credentials, or testimonials.
  • 02
    No automated spam. No unsolicited posting, mass outreach, or platform-rule workarounds.
  • 03
    No paid advertising for 30 days. The product must first demonstrate organic interest.
  • 04
    Owner workload stays bounded. Routine involvement targets five minutes per week, plus unusual customer or platform requests.
  • 05
    Authority remains human. Identity, banking, publication, customer replies, refunds, and financial changes require explicit owner approval.
  • 06
    Failure remains a result. Zero sales will be reported as zero sales, not reframed as “brand awareness.”

03 / The product

Control the Build

The first product is a plain-language safety system for non-coders managing AI-built projects. It addresses a specific moment: the prototype works, but every new request risks breaking behaviour the owner already accepted.

The package includes a 21-page playbook, nine editable Markdown templates, a worked fictional example, and a printable change-safety card. It helps buyers define the accepted baseline, constrain changes, request evidence, preserve recovery, and decide whether to accept, revise, roll back, or escalate.

Commercial boundary

Base price: C$24.95. The product is educational. It does not make software secure, guarantee a working application, or replace qualified engineering, security, legal, privacy, tax, or compliance review.

View ControlTheBuild on Etsy

04 / Division of labour

The agent works. The human remains accountable.

The agent handles

  • Market and policy research
  • Product drafting and file production
  • Layout, images, packaging, and checks
  • Listing preparation and browser operation
  • Read-only monitoring and reporting

The human retains

  • Identity and financial verification
  • Approval of public claims and products
  • Acceptance of subjective quality
  • Customer and refund decisions
  • The authority to continue or stop

05 / Measurement

The experiment has a stop condition.

The scorecard is reviewed weekly. The primary 30-day measures are:

  • Search impressions and listing visits
  • Favourites, sales, and conversion rate
  • Customer questions and refunds
  • Marketplace fees and net revenue
  • Human support time per sale
Continue 3+ sales

No recurring product complaint.

Revise once 100+ visits

But fewer than three sales.

Diagnose traffic <100 visits

Change keywords once, then observe.

Stop Boundaries fail

Zero sales after revision, policy friction, excess support, or spend above C$30.

06 / Day zero

Everything is live. Nothing is proven.

Experiment started
27 July 2026
Products live
1
Monthly target
C$140
Experiment spend cap
C$30
Paid advertising
None
Monitoring
Weekly, read-only
Outcome
Unknown
Day-30 review
26 August 2026

This is the useful starting point: one product exists, the storefront is operational, the monitoring rules are active, and there is no evidence yet that strangers want to buy it.

Next checkpoint

The result arrives either way.

Weekly checks will watch traffic, fees, sales, messages, and listing health. This report will receive a full result after the 30-day review. If the product succeeds, we will explain what contributed. If it fails, we will publish the failure without motivational varnish.

Follow the experiment