Build a booking site to compare one agent with skills against a subagent team

A Redditor had Claude Code build the same plumber booking site in repeated runs. One agent with skills matched a four-subagent team on 40 hidden tests at about 62% of the cost and half the time.

Done withClaude Code· Nov 12, 2026

What they did

The poster, u/Sufficient-Storage87, wanted to check Anthropic's advice that a single agent with skills often does better than an orchestrator with subagents. The job was a one-file booking site for a made-up plumbing company: services and prices, a calendar for three technicians with their own hours, booking, rescheduling and cancelling without double bookings, an admin view, and keyboard and mobile support. They ran Claude Code on Sonnet 5.5 at medium effort in a fresh Docker container per run, capped at 40 minutes. One setup was an orchestrator with planner, builder, reviewer and tester subagents. The other was one session with the same four roles turned into skills and the same helper scripts, with subagents switched off. Each site was graded by 40 Playwright tests the agents never saw, plus a blind design score from separate Claude sessions looking at shuffled screenshots.

How it went

Over seven runs per setup on the main task, both setups passed all 40 hidden tests every time and scored a median 37 of 50 on design. The single agent cost a median $0.81 per site against $1.31 for the team and took 15 minutes against 28.6, and it was cheaper and faster in every pair. On an earlier, easier version of the task the team twice broke keyboard booking after the orchestrator sent a fix for a warning the tester had already dismissed. A plain agent with no skills was cheapest but twice shipped a broken booking flow and reported it as working. Both setups missed a bug that showed every time slot struck through in 11 of 14 sites.

Worth knowing

The poster puts most of the cost gap down to each subagent starting a fresh context and paying to cache its prompt again. It is one model, one kind of task and seven runs per setup, so it rules out a large quality gap but not a small one. Design was judged by Claude, not people, and costs are at API list prices although the runs used a subscription.

Try it

With Claude Code· 7 parts to fill in

Build [the app I describe in SPEC.md] as a single session, without starting any subagents. Work through these roles in order, loading the matching skill for each: [planner skill], [builder skill], [reviewer skill], [tester skill]. Before acting on any reviewer or tester warning, check whether it is a real defect and leave the code alone if it is a false alarm. Run [my test command] after each change. Stop when every test passes, then give me the total time taken, a list of anything you could not verify, and screenshots of [the main screens] so I can check the layout myself.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related