Studio software · Runs our studio
Brief in. Invoice out.
The software our studio runs on, from a client's first email to the paid invoice. The sale, the plan, the client's portal, the files and the invoice share one set of records, so nothing is copied from one to the next. Its own site has the full tour.
- Runs on
- Web, phone and Mac
- Client side
- English and Czech
- Access
- By invitation
One record
One record behind every screen.
Our plan, the client's portal and the invoice don't keep copies. They read the same records, so a change in one place is the change everywhere.
The phase holds its tasks, its deliverables and its payment. The client accepted it, and that released the invoice.
How we use it
From the first email to the paid invoice, every step of a job happens in it.
- 01
A brief comes in.
As it is: an email, a document, screenshots. It's drafted into tasks with the open questions listed, so the first call starts from what's unclear.
- 02
The proposal.
We scope it into parts. The client accepts the ones they want, in their portal, and nothing starts until they do.
- 03
The work.
Each accepted part is its own project on the board. Rules take the routine, people and agents work the same cards, and every hand-off ends in a person's review.
- 04
The files.
What we deliver goes out in folders the client approves, version by version.
- 05
The invoice.
Drafted from what was accepted, previewed by a person, then sent.
Under the hood.What was hard, and what we did about it.
Three apps into one.
In September 2026 IteroZen absorbed our selling tool and our brand portals: one database, one sign-in, one shell. The selling tool's code moved from SQLite to Postgres across 582 call sites, and then its data followed.
A seal on every invoice.
The preview seals the invoice's contents; sending checks the seal. Change one line after the preview and the invoice can't leave until someone looks again. That's enforced by the server, not by asking nicely.
A fence, not a menu.
The agents' tool list used to look like the boundary, but a valid token could reach everything its owner could. Now every token carries a scope the server checks on every request: a board token can't invoice, and an invoicing token can't touch the board. Changes to who may see or do what go into an audit log.
Money that drifted.
Imported projects billed slightly different figures than their offers had quoted, by rounding. So a project now bills exactly what the client accepted, and holds if the price changed since.
Tested around the clock.
The unit tests run in Kiritimati, Honolulu and Amsterdam time, because a date that's right in Prague can be wrong at midnight somewhere else. Then a real database and a real browser: 262 test files and 109 browser specs.
Where it is now
It runs our studio every day and opens to other studios by invitation, at iterozen.com. Selling works only in our own studio for now; offline use isn't built yet.
If this is your problem
Your jobs pass through five tools, and someone copies them from one to the next.
We would start with a diagnostic: about a week following one job from the first email to the paid invoice. You get a written verdict on what to build as one system, what to keep, and what it would take.
Next from the workshop · OrePretzel
Cookie consent that keeps the ads working.