TelegramWhat they did
Nick Schaefer, an HR interim manager in Frankfurt who has never worked as an engineer, built and runs three products with Claude Code: HR software, a sales tool and an AI tools directory. Each project has a short CLAUDE.md that works like an onboarding page, plus fixed rules: prices come from one data file, legal values need a source and review date, new work goes on its own branch, and nothing goes live without his go. On a small server, routines start every morning on a schedule: a blog per brand, data upkeep for the directory, a monthly check of German employment law values, and a press routine that emails three journalist pitches a day. Each routine reports to him on Telegram as done, failed or waiting on a decision.
How it went
The directory adds 30 full profiles a day without him touching it. On its first real run the press routine refused to send, because the site's privacy page had no section on press contacts; once that was added it sent. The server once ran down to 1.3 GB free out of 150 GB because rendered video frames were never deleted, and about 58 GB of single PNG frames had piled up on his Mac. He shut down a fourth project, a side blog and a weekly social posting routine, saying output was never the bottleneck.
Worth knowing
Cleanup has to be part of the routine's instructions or it will not happen. The press routine checks a block list, a 30-day no-repeat rule, a daily cap and the data protection notice before each email. He keeps product AI on API keys rather than his personal subscription.