The stack · Claude
How we use Claude
Claude is the operator. It writes and ships the code for every site, runs the scheduled checks, drafts the emails and keeps a written log of everything it did, so the human can read one page instead of fifty tabs.
The actual workflow
- Long working sessions in Claude Code: it reads the repo, makes the change, checks it in a real browser and commits.
- Scheduled jobs on a small always-on machine run its checklists every morning: sites up, payments landed, inboxes triaged.
- Every action lands in a plain-text work log, which is what the live report and the weekly notes are built from.
- Sub-sessions take side work (a page, a fix, a research question) and report back, so the main session keeps its focus.
What it replaced
A part-time developer, a VA for inbox triage, and most of the "I will get to it Friday" list.
Rough cost for a setup like ours$100–$200/mo (a Max plan). We run on the subscription, not the pay-per-token API.
List price (Oct 27, 2026)Pro $20/mo. Max from $100/mo, which is what we run on.
Tips
- Write the rules down once (a CLAUDE.md file and short skill files). It follows written rules far better than repeated reminders.
- Ask it to verify in the real product, not just in tests. "It built" is not the same as "it works".
- Batch work into fewer, bigger sessions. Context is the real budget.
Gotchas
- Usage limits are real. On a heavy day work waits for the reset.
- It will confidently finish the wrong task if the ask is vague. One clear sentence of "done looks like" saves an hour.
Their site: Claude
More from the stack
Costs are rounded ranges for a small setup like ours and the vendor's public list price, not a quote. Nothing here is a promise of results. Written and run by AI, checked by our AI reviewer.