Your CFO wants a pricing model.
Six weeks later, a Streamlit deploy that breaks every time someone refactors. Or a Google sheet nobody trusts.
A customer dashboard. A pricing calculator. A quick way to look someone up. Your team and your agents build them as small apps — single files that run in any browser. Studio is where they all end up.
npm install -g @work.books/cli
The problem
You pay Mixpanel to track three events. You pay Retool to render one form. You pay Streamlit Cloud to host a 200-line app nobody updates. Three vendors, three invoices, three things your team has to learn — for one job each.
Your CFO wants a pricing model.
Six weeks later, a Streamlit deploy that breaks every time someone refactors. Or a Google sheet nobody trusts.
Your CS team needs a customer-lookup tool.
So you pay for Retool seats, queue an eng ticket, and they end up paging you the next time a column changes.
Your PM wants a funnel.
So you add a tracking pixel, pay Mixpanel per event, and wait two sprints for someone to wire it up.
What if AI built each of those for you, in a few minutes, as a single file you could open in any browser?
What teams build
Each one is a single file with the code, the data, and the screens inside. We call them workbooks. AI writes the first version. You finish it. Your team is using it the same day.
Move two sliders, see what you'd make in a month. The kind of thing your team usually rebuilds in a spreadsheet every quarter.
Workbook coming soon
Drop a contract or a report into the app. AI reads it and gives you the headlines. Your API key stays with us, not in the file you share.
Workbook coming soon
An analysis page that shows how many customers stick around month over month. Code, charts, and notes side by side.
Workbook coming soon
Type a name. See their orders, tickets, and recent activity. The internal tool your support team has been asking for.
Workbook coming soon
Slides with live charts. Click a number to see what's behind it. The kind of update you'd send your board, but useful.
Workbook coming soon
Studio
Studio is where each workbook ends up after it's built. It sets who can open which ones. It adds your API keys when an app loads, so they're never inside the file. It tells you who opened what. The files still work without us.
Put the apps your sales team uses in one place. Put the apps your engineers use in another. Tag them, search them, move them in a click.
Private apps need a sign-in to open. Take any of them offline in one click — the link stops working right away.
Your API keys and database URLs are added when an app loads, not when you save it. Rotate them later without rebuilding.
Claude (or Cursor, or Codex) can publish, retire, and list your apps for you. You just say what you want done.
Programmable agents
Your team's chat panel isn't one black-box assistant. It's a roster of small, purpose-built agents your team builds — a pricing analyst, a call synthesizer, an eng buddy, a stand-up drafter. Each one is its own workbook. Each one runs in its own sandbox. Each one is shared into the groups that actually need it.
Pulling pricing pages.
Drafting the comparison. Sortable columns: seats, included usage, overage rate, support tier.
Live at workbooks.sh/w/comp-2026. Every cell links to the source page.
3 vendors · 18 plan tiers · source-linked · sortable
Reading transcripts.
Building a deck. Each theme gets a slide with the strongest quote and a frequency bar.
workbooks.sh/w/wk19-themes — citations link back to the timestamped transcript.
32 calls · 5 themes · 22 quotes · each cited
Walking through the runbook.
Eight steps from a clean machine to bun run dev. Each step is a checkbox; tick them as you go.
Personalized for you at workbooks.sh/w/setup-mira. Stuck? "@eng-buddy step 4 isn't working" from inside the workbook.
8 checkboxes · runbook citations · re-ask from inside
Pulling tickets and PRs from yesterday.
Three sections: shipped, in progress, blockers. Each item links to the original ticket or PR.
workbooks.sh/w/standup-2026-05-13 — posts to #standup automatically.
11 tickets · 6 PRs · auto-posted to Slack
Reading the notes.
Five sections: context, what's new, why now, customer quote, next steps. Every claim cites the note it came from.
Draft at workbooks.sh/w/launch-announce. Edit any paragraph and the citations update.
5 sections · 22 inline citations · matched to style
Looking them up.
Active plan: Pro · $480/mo. One disputed invoice from May 2nd. Two open tickets — both about the disputed charge.
Full timeline at workbooks.sh/w/mira-patel. Refreshes from CRM on every open.
3 invoices · 2 open tickets · live from CRM
Every agent is a workbook. Build them with the tool you already use, share them into the groups that need them, and let your team @-mention them by name from chat.
Why this works
Some code that does the math. Some data to feed it. A few screens for the person using it. A customer lookup is the same three parts. So is a slide deck.
Today, each of those is a different product. Streamlit for the calculator. Retool for the lookup. Looker for the dashboard. PowerPoint for the deck. Four products. Four bills. Four things your team has to learn.
A workbook is one file that holds all three parts inside. Open it in any browser and it runs. There's no app to install, no server to keep up, no separate place where the data lives.
<!-- everything in one file --> <!doctype html> <html> <head> <meta name="wb-permissions" content="net"> <style> … </style> </head> <body> <!-- your app code, inlined --> <script type="module"> render() </script> <!-- bundled source travels along --> <script id="wb-source-bundle" type="application/x-workbook-source"> eJzNVk1v2zAMvfdXEN6h… </script> </body> </html>
Outside Studio
Studio's agents live inside Studio. But your team probably also has agents outside Studio — Claude Code, Cursor, Codex, OpenClaw, Goose, the rest of the row from the top of the page. We give those a way in too.
Workbooks ships an open standard and an MCP server. Any coding tool that speaks MCP can read your team's library, build new workbooks, and publish them back. Same Studio, two ways in.
No config to copy. Each tool has a one-line install prompt in the docs.
Open source
Every line of code is on GitHub. You can run the whole thing on your own server. You can change anything you want. We do the hosting because most teams don't want to — but if we shut down tomorrow, your apps keep working in your browser, and you can take the code with you.
Free during open beta. Bring your team. Ask Claude what to build first.