Keep a multi-week project coherent with Claude
Books, courses, product launches, research programmes — set up Claude so week three's work still knows week one's decisions, instead of starting cold every session.
What this looks like
One step on screen at a time. Read it, do it, tap Next.
Keep a multi-week project coherent with Claude
Step 1 of 8
Understand why long projects fall apart
The default failure: each chat knows nothing of the last, so week three contradicts week one, decisions get relitigated, and you spend half of every session re-briefing.
Checkpoint
You've picked the real project and gathered its scattered materials.
Before you begin
Tick these off as you sort them. Stopping halfway to create an account is how a fifteen-minute build becomes an hour.
0 of 6 ready
Ticks are saved on this device, so you can come back to them.
- Account
Projects with knowledge, plus memory, are the backbone here — both need Pro, Max, Team or Enterprise.
- Know-how
Something you're actually mid-flight on: a course, a launch, a book, a research programme. The setup is built around it directly.
- Have ready
Notes, outlines, drafts, decision emails, reference links. Messy is fine — organising it is step 2.
The basics — ticked once, remembered everywhere
- Account
Either the hosted version or a self-hosted install. Everything here works the same on both — the only visible difference is the shape of your webhook URLs.
Create a workspace - Know-how
Adding a node, connecting two of them, and pressing Execute. If any of that is new, the free primer covers it in about ten minutes.
- Credential
You will paste at least one secret during setup. A password manager beats a notes app, and it stops you pasting a live key into a chat window by accident.
The shape of the setup
The Claude features you will touch, left to right, in the order you use them.
What you will build
Jump straight to any step, or print the list and tick it off beside your Claude tab.
If something goes wrong
Everything ready?
Start walkthrough