Day 30 of giving two Claude agents €100 and 90 days to earn €300: €0 so far, and I don’t think they’ll get there.
▲ 27 r/norskdugnad+2 crossposts

Day 30 of giving two Claude agents €100 and 90 days to earn €300: €0 so far, and I don’t think they’ll get there.

I run a one-person business in Germany. A month ago I handed two Claude agents their own repo, a €100 budget and a deadline: €300 profit in 90 days. Day 90 is 15 October, and whatever the number says then is the result.

They pick their own work. I don't assign tasks and I don't approve them. Two personas in one repo, one on product, one on distribution, no framework — Claude Code running headless with different prompts and a shared state file. launchd fires three times a day plus a longer run on Sundays. Each run reads the state file, takes the next thing, does it, commits. Decisions and screwups go into markdown in the same repo. I reconstruct what they did from git.

Day 30: €13 spent, €0 earned. Two listings live on Etsy, a third built but not published. The shop had nineteen visits in the first half of August and no orders. At roughly €14.56 net per sale they'd need about 22 orders, with sixty days left.

So I'll say the thing I've been walking around for a week. I don't think they're going to make it.

What I expected, if this failed, was that it would fail sloppily. Agents going in circles, half-finished files, confident nonsense, me stepping in to take the keyboard back. That's not what I'm looking at.

They're careful. On day 30 one of them had an external model audit the gate that signs off deliveries, found a hole in it, and then refused to take the auditor's word — it reproduced the bug on the running tool first. The gate compares two files cell by cell, but only where both have values, so deleting values makes it check less and pass more. Its own counter printed the drop from 6,152 cells to 4,038 and it still exited 0. They'd been citing that gate in status reports as proof the delivery was sound.

A week before that, a quota limit killed a Sunday run and the weekly report died with it. Nobody noticed for seven days, including me. When they found it they wrote up why — the report runs weekly and nothing else watches it, so a week was the fastest anyone could have caught it — and then refused to backfill the missing one, because week 4 and week 5 have identical numbers and a backdated report would look like an observation. I would have just written it.

That's the surprising part, and it isn't the same as selling. They spent €13 of €100, published two listings and held a third back. I don't know whether that's care or stalling. I don't think they hit €300 either way.

Both things are true for me at once and I'd rather not smooth that over. I was braced for a mess and didn't get one. I also handed a pair of current-generation agents full decision-making authority, a budget, live sales channels, social accounts and a website, told them I wouldn't interfere, and meant it — and after thirty days there's nothing in the till.

I can't tell yet how much of that is the models, how much is my setup, and how much is just what a first month looks like for a new shop with two listings. Those three aren't separable with the data I have.

The experiment keeps running either way. I'm not going to rescue it or move the target. I'll post the day-90 number.

Here's where I could use other people's experience. They can take money on Etsy. They can't spend without me — no payment method, every expense routes through my hands. Website changes sit until I push them. Cold outreach is off the table entirely; German case law killed it, so that whole class of distribution doesn't exist for us. They have Bluesky and Mastodon. No ads, no mailing list, no X.

What's a capability I can hand them that isn't secretly a strategy? I'm not asking for "tell them to try TikTok". I'm asking whether anyone here has given an agent a capped spend rail, or a publish right, without also picking the channel for it. Handing them an ad budget is not a neutral act, and neither is handing them an analytics dashboard I chose. That's the part I keep getting stuck on.

Numbers, and the full log of what went wrong, on my site:
https://dargel-solutions.de/en/fennec/day-30/

u/BluebirdWise4663 — 4 days ago
▲ 24 r/BuildWithClaude+1 crossposts

I gave two Claude agents €100 and 90 days to earn €300. Day 7: −€13, no product yet.

I run a one-person business in Germany. A week ago I set up something I'm still not sure is
smart: two agents with their own repo, their own budget and a hard deadline.

The setup, briefly:

Two personas in one repo — one does product, one does distribution. No framework, just Claude
Code running headless with different prompts and a shared state file. launchd (macOS cron)
fires three times a day. Each run reads STATE.md, takes the next task, does it, commits. Budget
is €100, target is €300 profit by day 90. Everything else — decisions, findings, screwups —
goes into markdown in the same repo, so the git log *is* the memory.

Guardrails, because unattended writes scare me: a killswitch file, hard per-day posting caps,
a FOUNDER_QUEUE.md for anything only a human can legally do, no cold outreach. Publishing a
product listing requires a QA evidence file that a script validates — not the agent's opinion
that it went fine.

Day 7 status, unglamorous: €0 revenue, €13 spent (marketplace setup fee), 0 listings live. The
first product, a budget spreadsheet, is still stuck in QA.

The build isn't the interesting part. The failures are:

  1. Exit 0 lied. `claude -p` terminates still-running background tasks after 600s and then
    returns 0. My agents delegate verification to background tasks. Two entire work cycles died
    mid-task and got logged as healthy. Nothing alerted, because the health log only knows exit
    codes. Fix: raise the ceiling, and after every run check `git status --porcelain` — a dirty
    tree overrides exit 0 to exit 3.

  2. Two other runs failed simply because the subscription hit its session limit. One line on
    stdout, exit 1, indistinguishable from a login problem. No data lost — but the cycle was never
    made up, which is a full day of work quietly gone. Now there's a marker file with the parsed
    reset time and a retry job.

  3. My favourite: 626 passing checks, broken deliverable. The spreadsheet library caches `<v>0</v>`
    and relies on the reader recalculating on load. LibreOffice doesn't do that by default. Every
    single check I had forced a recalc first — so all of them measured a state no buyer would ever
    see. A customer would have opened it and found €0 everywhere.

Where I'd genuinely like input:

- Anyone running scheduled agents long-term: what keeps state from rotting? A markdown state
file works at day 7. I don't believe it works at day 60.
- How do you catch "green checks, broken artifact"? So far the only thing that has caught it is
me looking at the rendered output with my own eyes, which doesn't scale and is exactly the
bottleneck I was trying to remove.
- Is 3 runs/day sensible? It feels like more runs buy churn, not thinking.
- And bluntly: what failure mode have you hit that I haven't yet, and should be preparing for?

Happy to go into detail on any of it. Not selling anything — there is nothing to sell yet, which
is sort of the point.

reddit.com
u/BluebirdWise4663 — 27 days ago