Work/Life 2.0

Showroom

What the lab has built

Bring an idea, build the digital co-worker your life needs. Each experiment here is led by a person, and AI agents do the digital work.

About $3,200,000 of work as an AI prices it, across 60 days worked. How both numbers are made.

Filter:

The lab's own work

Members' projects

Build yours here

Tell us your idea. One sentence is plenty.

Ask for a seat

Where these numbers come from

The amounts are rough AI estimates, in US dollars, of what it would cost to have each project made. The full method below explains their limits.

The full method

Older estimates without a manifest (a record of which files the model read) leave it unknown which files they covered. Lab and RevenueLab were priced again after their old estimates were shown to cover the wrong files. Manifests were recorded for those new estimates; they say nothing about the older ones.

With review-contiguous-v1, source files too large to read at once are cut into consecutive stretches of characters. Every character is kept, but code and the context around it can be split at a cut. Estimates for parts can be off in either direction. These are rough AI estimates of what it would cost to commission the work, not quotes and not money earned.

Days worked counts calendar days with at least one saved change, not how long the project has existed, and not how many hours anyone sat at a desk. Three changes in one afternoon count as one day. The total at the top counts a day on which anything here moved, so a day that four projects worked on is still one day.

Lines written counts the text of the project as it stands today. Images, fonts and machine-generated lock files are left out, because their size says nothing about the work.

Design work is counted in pieces instead. A logo has no lines, so counting them would price a year of drawing at nothing. A design project is measured by the finished pieces it delivers, and its days and start date are read from each piece's own history, including the ones still filed with the project they were drawn for, so a piece is dated from when it was made, not from when it was catalogued. The money question changes with it: the model is asked what a studio would charge to deliver this list of pieces, and it is given the list (formats, sizes, what each one is for), not the artwork itself, because a wordmark has the name written in it.

What it would cost to have built is not our figure. An AI model is given the project's source code, a short description of what it does, and its size in files and lines. The project's notes and lock files are left out, and its name, its lead's name, dates written like 2026-10-15 and words like "AI" and "agents" are replaced. Comments in the code can still mention a date written another way, or how long something took. The model keeps its usual tools, but the question tells it to judge only the material it is given, and never says how quickly the work was made. A model told "this took three days" would price three days of work. It is asked how many hours a competent independent developer or small studio would need to build it and at what hourly rate, and the figure is those hours times that rate. It is asked to be conservative and to estimate low when unsure. It can still read some things from the code itself, for example that one person uses it.

A project too large to read at once is read in parts, normally split along folders, with whole files in one part. The range method above handles oversized individual files. Each part is told that it is one part of a larger project and which one, is priced on its own, and the parts are added up. Its page says so.

The estimates move. Asked the same question twice, the model does not give the same figure. So it is asked three times, and the page shows the middle answer, rounded to two digits, with the lowest and highest next to it. A project is priced again only when its code has changed, and then at most once a week; its page says when it was last priced. Until 15 Oct 2026 these figures came from a different method, which was shown a short description and a list of file names instead of the code; they are not comparable.

What it is worth to own is the same model's answer to a different question, and it is usually small. Most of these have no users and earn nothing, however much they cost to build. We show both because showing only the first would be a sales pitch.

These are estimates, and we would rather they were too low than too high. If you think a number is wrong, we would like to know: olaf@paradaice.info.

Measured 16 Nov 2026.