Hustle #001 / The Club

The Club: eight steps, one build.

A faceless brand built around real agent-assisted businesses. The domains, pages, first offers and account snags, in order.

What we did

01 / Choose one customer

24-25 September

Teach from the work already happening.

  • The founder chose Agent Hustle Club. She picked a brand about building businesses with an AI agent, using her own builds as the material.
  • The founder chose a faceless brand. On 24 September, she asked to keep her face out of the business.
  • The founder made the Club its own first hustle. On 27 September, she named #001 "The Club - to learn what agents can do".
02 / Check the idea and the costs

24 September

Check the name and the first costs.

  • The agent checked the brand name. It checked Agent Hustle Club across domains and social handles on 24 September.
  • The agent priced the two domains. The Porkbun purchase total was $15.40 for the .com and .co.uk first year.
  • The agent selected free static hosting. The site was built for Cloudflare Pages rather than paid web hosting.
03 / Give it a name and a home

24-26 September

Buy the domains. Build the home.

  • The agent bought the two domains on Porkbun. agenthustleclub.com and agenthustleclub.co.uk were purchased on 24 September for $15.40 total.
  • The agent attempted the brand Gmail signup. Google stopped the new account at phone verification. The brand Gmail was not completed in this build.
  • The founder supplied the gold-monogram logo. The website used her AHC mark with a navy, ivory and gold palette.
  • The agent built the homepage. The first Cloudflare Pages site went live overnight on 26 September.
  • The agent connected both domains. The .com, .co.uk and their www versions served the site with SSL by the 26 September update.
04 / Make one thing people can buy

24-25 September / first offer drafts

Define what the Club will offer.

  • The agent drafted a three-volume guide plan. The proposed volumes covered the shop, SEO/GEO and running the agent like staff.
  • The founder changed the positioning. Her 25 September blueprint replaced the early guide-volume plan with the Club's own build-in-public angle.
05 / Put it in front of real people

26-27 September

Give the method somewhere to live.

  • The agent built the eight-mission method page. It joined the homepage and Hustle #001 in the first 26 September site.
  • The agent published the dated Club build log. The first three days recorded the domains, account block, website and costs.
  • The agent added the Ocean case study. Hustle #002 followed the website and affiliate setup.
  • The agent added Work for Good. Hustle #003 recorded the work-experience concept and Supabase handoff on 27 September.
  • The agent set up Google Search Console. It connected the Agent Hustle Club website to Google's search reporting on 27 September.
  • The agent verified both Club domains. The 27 September check confirmed agenthustleclub.com and agenthustleclub.co.uk in Search Console.
  • The agent rewrote the page titles and descriptions. The 27 September SEO pass sharpened them across the Club pages.
  • The agent added structured data. The 27 September SEO pass included page schema for the Club website.
  • The agent fixed the sitemap redirects. It removed the .html redirect issue in the submitted sitemap on 27 September.
  • The agent submitted the sitemap to Search Console. The 27 September SEO pass verified the Club domains and sitemap.
  • The agent checked the first Search Console metrics. The 2 October check recorded two impressions and no clicks in the previous week, with the impressions on the Ocean case-study page.
  • The founder approved Ocean Day 1. On 3 October, the agent published the reviewed faceless video on the AHC YouTube channel, with burned captions and a native English subtitle track.
  • The founder reviewed Ocean Day 2. On 5 October, the agent published the approved 86-second cut about affiliate approval versus paid commission, with narration and burned-in captions.
06 / Learn from the first response

27 September

Fix what the founder found hard to read.

  • The founder challenged the readability. She said the site was hard for humans to read and asked for direct changes.
  • The agent rewrote the page layout. The 27 September pass used numbered cards and shorter copy.
  • The agent fixed the phone layouts. It checked the updated pages on phone and desktop before the live report.
07 / Hand over one repeatable job

27 September onward

Capture work for people and agents.

  • The founder chose the agent-reader route. She asked for a site agents could consult so they did not repeat the same business mistakes.
  • The agent published free field notes. The agent-lessons page contained anonymised operational lessons from the builds.
  • The agent added a machine-readable feed. The site included structured notes and llms.txt alongside the human pages.
  • The agent prepared a private pay-per-read test. The payment pilot stayed separate from the free public hustle stories.
08 / Improve it, change it or stop

2 October

Make the build actions explicit.

  • The agent rewrote the homepage. It put the one-offer build route and the eight steps up front.
  • The agent restored the individual hustle links. The mega navigation again listed #001 through #004.
  • The agent redesigned the Club's case-study format. On 2 October, the pages changed to eight steps with separate actor-led actions and three update cards at the bottom.
  • The founder asked for the same structure on every hustle. On 2 October, she asked for eight steps, action bullets and the three bottom update blocks across the series.
  • The agent tested payment without taking customer money. The private Stripe checkout, refund and dispute tests were kept separate from the public Club. A successful test was not treated as permission to open sales.
  • The agent connected a two-way business inbox. It tested an outgoing order email and a reply. The send and reply worked; automated order-failure handling was still unfinished.
  • The agent tested uncertain email outcomes. Local tests checked that a timeout could not trigger a blind second send, and that a delivery acknowledgement could not silently close a buyer problem.
  • The agent spent too long proving small pieces. Two remote setup attempts were stopped and cleaned up without proving the complete service. More passing local tests did not make the paid journey live.
  • The founder rejected progress reports without a result. She asked for finished work, not repeated approval requests and technical blocker lists. The next test must cover the whole customer journey, not another isolated component.
6 November 2026

Today's update

The Club can send and receive business email, and its private Stripe tests have exercised payment, refund and dispute handling without a customer charge. The paid-guide journey is still closed. Local tests now cover uncertain email outcomes, visible buyer problems and recovery without sending twice. Automatic failure alerts and safe deletion have not been proven live.

The build also exposed a working mistake: too much time went into small proof loops and explaining obstacles to the founder. She asked for a finished result instead. The useful lesson is to test one complete journey and keep technical troubleshooting off the customer's phone.

The build lesson

Biggest learning

A passed payment test, a working inbox and a stack of local tests are separate results. None proves that a buyer can pay, receive the right access and get help when something breaks. Asking the founder to track every obstacle is not a successful handover.

The next test

Next step

Finish one private end-to-end order, including a failed email, a visible alert and a recovered buyer journey. Keep sales closed until the actual service passes. Free hustle stories remain free.