Claude Code
You describe what you want. It writes and changes files on your computer. Point it at an empty folder first.
goesai
Claude Code, GitHub, Cloudflare, and one API key. That is the whole stack. Here is what each one does, in normal words.
Start with one annoying task, not a big idea.
describe it · build it · use it tomorrow
the stack
Most people stop because nobody explains what these tools actually do.
You describe what you want. It writes and changes files on your computer. Point it at an empty folder first.
Your save history. Every version is kept, so you can go back to yesterday when something breaks. Do not skip this one.
Where your tool lives. It gets a web address, and other people can open it. You can add a login there too.
Lets your tool ask Claude questions on its own. That is what turns a page into a useful tool. Set a spending cap on day one.
start small, then put a spending cap on the API key
what you can make
Four small tools I built with this stack. Every one replaced something annoying.
ad-sales crm
No more spreadsheets that stopped agreeing with each other.
coaching log
Simple login, one clear record, no messages to search through.
money dashboard
The useful numbers, without opening the spreadsheet nobody liked.
content planner
The owner plans both versions herself and can see what is missing.
none of these became a startup. all of them gave somebody time back.
before you start
What happens: the first thing takes longer than expected, but it works. The second one takes an afternoon.
By the fourth, you stop being impressed and start being useful. That is the point.
the short version
The playbook gives you the exact words to paste at every step.
Everything on this page, in the order you actually need it, with the words to paste at each step.
English and German, as a web page and as a PDF you keep. About forty minutes to read. You can do the first hour of it the same day.
It gets updated as the tools change, and your link always gets you the current version. No extra charge for that, ever.
or do it together
The playbook covers the general case. Forty-five minutes on video covers yours - your systems, your one real task, and the parts you are not allowed to break. The playbook is included.
You pay, then I email you within a day to find a slot. Nothing to book here.
who is writing this
I run a design and architecture media company during the day. Over the past year, I have built about ten small tools with the stack on this page.
I broke a few along the way. One careless command wiped out a full day of work.
I still cannot code most of this by hand, but I can usually tell when Claude is getting it wrong.
The playbook is the setup I use now.
Based in Zürich, working in English and German. I answer emails.