Claude Code
You say what you want in normal sentences and it writes the files on your own computer. It can read and change your folders, which is what makes it useful and also the reason you point it at an empty one first.
goesai
You don’t need to learn to code.
You need four accounts
and an afternoon.
Claude Code, GitHub, Cloudflare, and one API key. That is the whole stack. Below is what each of them actually does, in normal words.
the stack
Four tools. Here is what each one is actually for.
Nobody explains these in plain language, which is most of the reason people stop before they start.
GitHub
A save history. Every version of your work is kept, so you can always go back to how it was yesterday. This is the one people skip, and it is the one that saves you.
Cloudflare
Where the thing you made actually lives, so it has a web address and someone else can open it. Also where you put a login in front of it, in about five minutes.
An API key
A key from Anthropic that lets the thing you built ask Claude questions by itself. That is the difference between a page and a tool. Put a spending cap on it the same day.
none of this needs a credit card except the last one, and that one you cap
what you can make
Small things, used every day.
Not a business that runs itself while you sleep. That is what gets sold to you on Instagram and it is not what this is.
These are things I have built with exactly the four tools above. Some for work, some at home. Every one of them replaced something annoying.
- An ad-sales CRM for a family member, replacing a stack of spreadsheets that had stopped agreeing with each other
- A coaching log for two trainers, with a login their clients use to see their own notes
- A household finance dashboard that replaced a spreadsheet nobody wanted to open
- A marketing site the owner edits herself, without asking anyone for anything
- A content planner for a small herbal brand, working in German and Italian
- A reader for one issue of a local newspaper, built in an evening because I was curious
None of these made money directly. All of them gave somebody a few hours a week back, which turned out to be the better trade.
before you start
What I am not going to tell you.
- You can fire your developer
- Passive income in thirty days
- You will never need to understand anything
- It works the first time
What actually happens: the first thing you build takes longer than you expected, and works. The second one takes an afternoon.
By the fourth you stop being impressed and start being useful. That is the whole arc, and it is a better outcome than the one being advertised to you.
the short version
Your first hour.
- Pick one thing you do every week that annoys you
- Make three accounts: Anthropic, GitHub, Cloudflare
- Buy a test domain. About CHF 15 a year, and it can be nonsense
- Make an empty folder with nothing important anywhere near it
- Describe the annoying thing, and let it ask you questions before it builds
- Use the result tomorrow. That is the only test that counts
The playbook is the long version, with the exact words to paste at every step.
free while it is
The GoesAI Start Playbook
Everything on this page, in the order you actually need it, with the words to paste at each step.
- Setting up the four accounts, click by click
- How to pick a first project that cannot break anything
- Seven projects to build, each with the prompt ready to paste
- A prompt library: connecting a tool, checking what you gave it, getting unstuck
- One master prompt that turns Claude into a patient guide instead of an eager builder
- Twelve things I got wrong first, so they cost you nothing
English and German. About forty minutes to read. You can do the first hour of it the same day.
On its way.
Check , including the spam folder, because that is where new domains land at first. Or just open it now:
Open the playbookwho is writing this
I’m Timo.
I run a design and architecture media company during the day. Alongside that I have spent the past year building about ten small tools with exactly the stack on this page.
Several of them had to be rebuilt. One lost a day of work to a single careless command. I am not a developer and I still could not write most of that code by hand - I got good at describing what I wanted and at knowing when to stop.
That is the part worth passing on, and it is what the playbook is.
Based in Zürich, working in English and German. I answer emails.