No code required

Claude for Marketers & Business Owners


Zero programming. For the operator who wants the three-week jobs to become afternoon jobs, and does not care how it works underneath.

  • [PLACEHOLDER: platform: self-hosted, Udemy, or Coursera]
  • [PLACEHOLDER: course price]
  • [PLACEHOLDER: Claude for Marketers: course length, lesson count, format, and how enrolment works]

Afterwards

The recurring work stops eating your week.

Not everything. The specific jobs that are repetitive, well-defined and currently expensive.

You run marketing, or operations, or the whole business. You have made peace with not being technical and you have no intention of changing that. You keep hearing that AI should be doing half your job and you cannot work out which half, because every demo you have seen was either a toy or aimed at engineers.

This is the half. It is the recurring, well-specified work: the weekly report, the research nobody has time for, the fourth version of the same landing page, the summary of a call, the content calendar that gets written every month from scratch. Those become afternoon jobs. The judgement, the relationships and the decisions stay exactly where they were.

  • Build repeatable workflows for content, research and reporting
  • Automate the recurring work without hiring or learning to code
  • Know precisely where AI output still needs a human before it ships

Fit

Who this is for, and who should not bother.

This is the course with no code in it. That is a design decision, not a simplification.

  • Take it if

    You run something and the recurring work is winning

    Marketers · founders · business owners

    Marketing, operations, or the whole business. You are not going to learn to program and you should not have to. You want the three-week jobs to become afternoon jobs and you do not particularly care how it works underneath. This is the group I came from, so it is the one I can be most useful to.

  • Skip it if

    You want to ship software

    Builders · technical founders

    There is deliberately no code in this course, which means there is no software at the end of it either. If what you want is a product rather than a workflow, take Claude Code for Founders; it is free, and it is the one that ends with something running.

Syllabus

Six modules, each one ending in a workflow you keep.

You bring your own recurring job to the first module and work on that one throughout.

  1. 01

    Choosing the first job

    Pick the recurring job you resent, not the impressive one. What makes a task a good candidate (repetitive, well-defined, currently expensive, low blast radius if it is wrong) and the two categories that look ideal and are not.

  2. 02

    The brief, for work that is not code

    The same discipline, none of the vocabulary. Audience, constraints, the sources it is allowed to use, what it must not say, and what finished looks like. This is where the difference between a throwaway answer and something you would send shows up, and it is the module people come back to.

  3. 03

    Your voice, written down once

    Most output reads generic because nobody ever described the voice. Style, register, the words you never use, the claims you are not allowed to make, and worked examples of good and bad. You write this file once and every workflow afterwards points at it.

  4. 04

    Research you can stand behind

    Where to get sources, how to require them, and how to catch the confident invented citation before it is in a deck in front of a client. The failure here is not that the model is wrong. It is that it is wrong in the register of something correct.

  5. 05

    Making it repeatable

    Turning one good result into a workflow somebody else on your team can run without you standing behind them. Where to keep it, how to version it when it drifts, and how to hand it over so it survives the handover.

  6. 06

    The human gate

    What never ships unreviewed: numbers, claims about results, anything about a named person, anything a regulator would care about, and anything where a disclosure belongs. The gate is short on purpose, because a checklist nobody completes is worse than no checklist.

Nothing in the six modules requires you to write or read a line of code.

What comes with it

  • A workflow library for the recurring jobs: content, research, reporting, and the weekly summary nobody wants to write
  • The brief template in a version with no technical vocabulary anywhere in it
  • A brand-voice file you fill in once and point everything else at
  • The human gate as a one-page checklist, including where a claim needs checking before it goes out
  • Examples of output that looks finished and is not, annotated with the tells

Built to work with whatever you already use. Nothing here asks you to move your team onto a new tool.

The limit

It will not write your marketing for you.

It will do the draft, and the draft is most of the hours. The judgement stays with you, and so does the responsibility: the work that gets somebody into trouble is always the work nobody read. Module six exists because that is the failure this makes easier, not harder.

It also will not make you more interesting than you are. If the positioning is vague, faster output produces more vague positioning. That is a strategy problem, and no workflow fixes it. If you suspect that is your actual problem, book the free call instead of buying a course, and I will tell you straight.

Not open yet. The waitlist is the newsletter, and you will hear from me when there is something real to buy.

[PLACEHOLDER: course price]

[PLACEHOLDER: Claude for Marketers: course length, lesson count, format, and how enrolment works]

The refund position

[PLACEHOLDER: refund policy for the paid courses: how many days, and whether it is unconditional]

Before the waitlist

The three questions operators ask.

I am genuinely not technical. Does no code really mean no code?
It does. Nothing in the six modules requires you to write or read a line of code, and none of the examples assume you have ever seen one. That is a deliberate constraint on the course rather than a marketing line: the moment a lesson needs a terminal, it belongs in the founders course instead, and it gets moved there.
Can I not just ask ChatGPT and save the money?
You can, and for a one-off you should. What you will get is what everyone gets from a one-line request: something that reads plausibly and is generic, which is fine until you try to make it repeatable or put your name on it. The difference this course teaches is the brief and the gate, and both are portable: they work with whichever assistant you already pay for. If you want to test that claim for nothing, take the free course first.
My team will use this to publish rubbish at volume.
That is the real risk and it is the honest reason module six exists. Volume is not the point of this and the course says so repeatedly: a workflow that produces ten mediocre pieces where you used to publish one good one has made your week worse, not better. The gate, the voice file and the review checklist all exist to stop exactly that, and if your team culture already rewards output over judgement, a course is not the intervention you need.

Not open yet

Nothing to buy yet, and no countdown.

The syllabus above is the course. When it has a price and a place to live, the newsletter is where I will say so, and it will be one email rather than a five-day launch sequence.

P.S. The free course has a terminal in it and this one will not, but the first two lessons are the same idea. If you can tolerate six copied commands, you do not have to wait for this one.