/ 01Guided entry

Pick the file that matches your problem.

Three dossiers, each an ordered route through the archive. Open one, work it in order, ignore the rest until it is done.

Select a path
/ indexFive tracks
  • Models are commodity. The leverage is in how you wire them into a repeatable process you actually run every week.

    • Choosing one model per job instead of chasing releases
    • Prompt files that live in your repo, not in your head
    • Where AI quietly makes work worse — and how to spot it
  • A week that ships looks boring from the outside. Here is the scaffolding that makes it boring.

    • The two-list system: what is running vs what is waiting
    • Cutting a project to something you can finish in nine days
    • Reviews that take twenty minutes and change the month
  • Automate the boring middle, never the judgement. Breakdowns of the flows worth building and the ones that break.

    • Intake → triage → draft: the three-step spine
    • Why most automations die at the error handling
    • Manual first, script second, automate third
  • Offers built from what you already do. No launch theatre, no funnel cosplay — just the shortest line to paid.

    • Pricing a first product without a launch
    • Turning a saved workflow into a sellable asset
    • The four revenue shapes a solo builder can hold
  • One idea, worked properly, becomes a month of output. This is the pipeline behind the feed.

    • Capture → sharpen → publish → recycle
    • Writing the post before you build the graphic
    • How to keep a backlog that never runs dry
Keep the thread

Each week I send the next piece of the map.

One send a week. Systems, breakdowns, and what actually worked. Leave any time.