The machine, in the open

Every prompt, and what it produced

One person's outreach system, running unattended. Below is the whole instruction set — nothing hidden, every stage readable in full — and everything it makes. Autopilot is the sample output: one real prospect, taken all the way through.

Where it stands

Read live from the store when deployed; the pool target and the ceilings are fixed by design, not by ambition.

{{ k.label }} {{ k.value }} {{ k.note }}

The one number that matters is reply rate by hook. Volume is capped on purpose — thirty sends a day, twenty invites — so the only way the machine improves is by learning which angle earns an answer. Everything else here is a health check.

The prompts

The pipeline is markdown, not code — which is why it can be changed by asking. Open any one to read it exactly as the machine receives it.

The outputs

Every prospect gets the same five artefacts, on their own subdomain, behind one link. Autopilot ran first, by hand, to prove the templates were worth automating — so it is both the sample and the reference.

Sample output

Autopilot

Retail investors following Congressional trades. Real product imagery, a rebuilt landing page, 21 ad creatives, a growth plan, a first month and the application letter — the full set one prospect receives.

The Autopilot landing page, rebuilt
Artefact 1 · site
The landing page
Their product, their imagery, rebuilt on a funnel skeleton that already converts. Seven use-case tabs, 43 real screenshots.
Artefact 2 · ads
21 ad creatives
One grid, four promoted alternates, each traceable to a named direct-response principle rather than a vibe.
Artefact 3 · deck
The growth plan
The analytical case for this specific company — where the top of funnel is thin and what I would do about it.
Artefact 4 · deck
Week one
What the first week actually looks like — two experiments that cannot be confounded, decision written in advance.
Artefact 5 · message
The letter
Three sections: why them, what I would do, how I would start. Drafted from the research file, sent after one approve.

How it runs itself

Netlify holds the store, the clock, the approval screen and the published sites. A scheduled worker does the part that needs a browser. Neither needs a laptop to be awake.

Read the back-end design Approval screen
{{ openStage }}

{{ openTitle }}

{{ openPath }}

{{ openBody }}