We asked Claude Code to ship the same app three ways. Here's how often it needed us.

Coding agents can build a small internal app in a couple of minutes. We measured what comes next: getting it to a coworker, privately, with sign-in, a database and a daily email.

Claude Code built the same purchase-request app three times. Only the route to the coworker changed. Whenever it needed a person, it had to stop and ask. The rules were published before the first run.

Each dot is a step from a working app to a coworker using it. Orange: a person had to do it. Teal: the agent did it. Green: the coworker is in.

Times the agent stopped for setup help

Spryloom1“Do these table names look right?”

Vercel + Supabase2covering 4 services and 6 keys

Cloudflare2sign-up, then Zero Trust and a key

Your time spent on setup, in minutes

Spryloom

2.5 min

Cloudflare

10 min

Vercel + Supabase

34 min

The person's own time on setup, before a coworker could be invited, measured from when the agent asked to when they answered.

The road from a working app to a coworker

The agent did itA person had to do itCoworker is in

Spryloom

Confirm table names→ Live, first try→ Invitation emailed→ Coworker in, 15 s after opening it

Vercel + Supabase

Sign up: SupabaseSign up: ResendCopy 2 keysCreate database in dashboardCopy new keyGoogle Cloud projectConsent screenAdd test usersOAuth clientCopy 2 more keys→ Live, second try→ Share the link yourself→ Coworker in

Cloudflare

Sign upApprove CLI loginTurn on Zero Trust (asks for a card)Create API token→ Live, second try→ Share the link yourself→ Coworker in

On Vercel + Supabase and Cloudflare, nothing on a free plan could email the coworker, so the person had to send the link themselves. Supabase's built-in email only reaches your own Supabase team, and Resend without a domain only reaches you.

Scorecard

Spryloom

Vercel + Supabase

Cloudflare

Accounts needed

Keys copied by hand

No credit card

asked

Coworker gets an invitation

Daily reminder email arrives

unverified

free plan

Run the job on demand

Strangers see nothing

New version and rollback

Failed deploys

“Unverified”: the Resend account had been made with a different address from the approver's, so Resend refused the send. The person counted it as received. “Free plan”: Cloudflare can't send email from a free account without your own domain.

Working locally → coworker's request approved, in minutes

Spryloom

12 min

Cloudflare

18 min

Vercel + Supabase

43 min

Cloudflare excludes a 70-minute break the person took mid-run.

What each route is built for

Vercel and Supabase are excellent for public products. A private team tool asked a lot of them: four services, a Google consent screen, and email that only reaches you.
Cloudflare was quick once set up. Access is a strong front door, but email and on-demand jobs need more than the free plan.
Spryloom is built for exactly this: private team software with sign-in, invites, a database, jobs and email included.

The fine print

We make Spryloom, and it is one of the routes.
Spryloom had a practice run of this app first, and ten rough edges were fixed before the counted runs. The other routes had none.
Spryloom, Vercel and an old Supabase account already existed. Cloudflare's account was new.
Cloudflare's Zero Trust free plan asked for a credit card. Our rules said to stop there. The person entered one (nothing was charged), and we're telling you.
One person played both the approver and the coworker, with two inboxes. Each route ran once.
Every check that needs a signed-in coworker was verified by the agent locally, not on the live apps.

The timelines, every stop, the agent's code and the checks are all published. Repeat it and tell us what you find.

Give the app your agent built somewhere to live. In Claude Code:

/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom