Your CFO wants a pricing model.
Six weeks later, a Streamlit deploy that breaks every time someone refactors. Or a Google sheet nobody trusts.
beta
Studio is in open beta — bring your team
The AI work surface for your team.
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
Works with
+ 9 more
The problem
Stop renting ten SaaS tools. Build them.
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 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
Five apps your team could ship this week.
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.
tool
Seats
120
Usage
2.4M
monthly revenue
$28,400
Pricing simulator
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
app
contract.pdf · 14 pages
Summarize a PDF
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
notebook
SELECT cohort, retained()
FROM events
GROUP BY 1
Customer retention notebook
An analysis page that shows how many customers stick around month over month. Code, charts, and notes side by side.
Workbook coming soon
app
cust_3f9a…
Mira Patelactive
4 orders · $2,840 LTV
Customer lookup
Type a name. See their orders, tickets, and recent activity. The internal tool your support team has been asking for.
Workbook coming soon
deck
Quarterly update
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
We hold the apps. Your team uses them.
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.
◫
Group libraries
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.
◉
Sign-in & take offline
Private apps need a sign-in to open. Take any of them offline in one click — the link stops working right away.
⌘
Keys out of the file
Your API keys and database URLs are added when an app loads, not when you save it. Rotate them later without rebuilding.
⌖
Run it from Claude
Claude (or Cursor, or Codex) can publish, retire, and list your apps for you. You just say what you want done.
Programmable agents
A hackable agent harness across your team.
Pick a problem. See the chat. See the workbook it built.
Every chat above is rendered by Studio's real chat panel.
Every artifact is a real .html file. Click around
— sort the table, page through the slides, tick off setup
steps. The interactions are real because the workbook is.
Why this works
A calculator and a dashboard are built from the same parts.
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.
my-workbook.html
<!-- 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
Use Workbooks from the AI tool you already work in.
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.
From any coding tool
→
your team's library
- list_groups — find what your team has built
- open_workbook — read code, data, or output from any artifact
- build — generate a new workbook from a prompt
- publish — push it to a group your team can see
- revoke — take any of it offline in one call
No config to copy. Each tool has a one-line install prompt in the docs.
Open source
Yours, even if we disappear.
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.
Start with one app this week.
Free during open beta. Bring your team. Ask Claude what to build first.
Open Studio
no card · cancel any time · run it on your own server if you'd rather