Claude Can Build Your Office a Mini App. Here Is What It's Good For, and Where It Stops.
Describe a checklist or a calculator in plain English and Claude builds a small working tool your team can click through. No code. Here is how to pick the first one, and the limits to know before anyone relies on it.
By John Martines · October 22, 2026 · 6 min
Claude's artifacts can be small interactive tools: a new-caller checklist, an estimate range calculator, a job board. Here is what they do well, what they can't do yet, and a safe way to build your first one this week.
The person who answers the phones at a six-truck plumbing company keeps a sticky note on the edge of her monitor. Eight questions to ask every new caller. The address. Is water running right now? Where is the shutoff? Any pets? The best number to call back. New hires forget half of them, and the plumber finds out at the door.
One afternoon she types into Claude: "Make me a checklist screen for a new call. These eight questions, a notes box, and a three-line summary at the bottom I can paste into our job system." A minute later a small working tool opens beside the chat. Boxes to tick, a place to type, a summary that fills itself in. Nobody wrote any code.
That's an artifact. I call this kind a mini app, and it's one of the most useful things Claude does that most offices haven't tried.
An artifact is anything Claude makes for you to use outside the conversation. It can be a document, a slide deck or a design. In Anthropic's own words, it can also be one of the "small interactive tools." That last kind is the mini app: a screen with boxes, buttons and results that does one job.
You describe it in plain English. Claude writes the code, and the tool opens next to your chat. You use it by clicking and typing. You change it by asking: "add a box for the gate code," "make the buttons bigger," "put urgent calls in red."
A mini app can also do three more things:
- Remember. It can save text, up to 20 MB per artifact, text only. The person who builds it decides what each user keeps privately and what everyone shares.
- Use Claude. A tool can call Claude itself, for example to turn rough notes into a clean summary. Anthropic says no API keys are needed, and each person's use counts against their own plan.
- Read your apps. It can connect to the apps you've connected to Claude. Each person uses their own connections, not yours.
Saving and connecting to your apps need a paid plan: Pro, Max, Team or Enterprise.
How it got here:
- June 21, 2024: Anthropic introduced Artifacts on Claude.ai.
- July 25, 2025: Anthropic let people build, host and share AI-powered apps in Claude, in beta for Free, Pro and Max. Team and Enterprise followed on July 31. At launch the apps couldn't save anything.
- June 12, 2026: you could highlight part of a draft and have Claude change just that part.
- September 16, 2026: Anthropic changed how artifacts work, so you can ask for a design, deck or document in any conversation. Artifacts made before that date became "legacy": they keep working and can still be shared, but new ones are made the new way.
- October 8, 2026: Docs, Slides and Design came out of beta on every plan, including Free.
Most small offices run on a handful of jobs that happen every day and live in someone's head. The new hire asks the same questions. The estimate depends on who picks up the phone. The closing checklist is a laminated sheet nobody looks at.
A mini app turns one of those jobs into a screen everyone uses the same way. Good first ones:
- A new-caller checklist, like the plumber's above.
- An estimate range calculator for one service, built from your own price list, for staff to use on the phone. It gives a range. A person still writes the quote.
- An opening and closing checklist for a shop, with a shared list of what's been done today.
- A one-page job board. Paste in this week's job list and see it grouped by day and status.
None of these replaces your real software. They fill the gap between "ask Claude a question" and "buy a new program," and that gap is where a lot of office time goes.
Know these before your team relies on one.
Everyone who opens it needs a Claude account. Anthropic is plain about it: people without one "can't open a shared artifact, even with the link." The only exception is an older legacy artifact that was published from a chat. So a mini app is a tool for your staff, not a calculator for your website. If you want customers to use a tool inside ChatGPT or Claude, that's a different thing, which we covered in [MCP Apps, Explained](/articles/mcp-apps-explained).
Saving needs a paid plan. On Free you can build and use a tool, but it can't save data.
Shared means shared. With shared storage, everyone who uses the tool sees the same data. Claude asks you to confirm the first time. Keep customer details to what the job needs, and never put card numbers, passwords or health information in a mini app.
Tools that use Claude or your connected apps can't go out by public link. On Team plans, any "anyone with the link" sharing also needs an owner to turn on external sharing, or to allow that one artifact.
Don't count on version history. Anthropic's help pages don't describe one for artifacts, and its Claude Design page says Design doesn't have one yet. Keep your own copy of the request that built the tool, so you can rebuild it.
It can get things wrong. If a tool breaks, Claude offers a "Try fixing with Claude" button, and Anthropic says success isn't guaranteed. Test before you trust it.
1. Pick one repeated job. Something done five or more times a week, by more than one person, where mistakes come from a forgotten step.
2. Write the recipe. One paragraph: who uses it, what they type in, what it shows, and what it must never save. Keep that paragraph in your own document. It's your backup and your instructions in one.
3. Build it in a chat. Paste the recipe and ask for the tool. Then ask for changes until it fits. Short, specific requests work best.
4. Test it on three real past cases. Use made-up names. If it's a calculator, check the result against what you actually charged. If it's a checklist, ask the person who does the job whether anything is missing.
5. Decide what it saves. Start with nothing saved. If it needs to remember, use private storage before shared.
6. Share it inside the business only. On a Team plan, share it with your organization and leave external sharing off. On individual plans, invite only the coworker who'll use it, and keep the first tool simple: Anthropic says the parts that use Claude or connected apps don't work for people invited from outside an organization.
7. Give it an owner and a review date. One person fixes it when it breaks. Look at it again in 90 days.
- Did it get three real past cases right?
- Does every price, rule or step in it come from your own documents, written into the recipe?
- What does it save, and who can see that?
- Does it say plainly when a number is an estimate, not a quote?
- Who owns it, and where is the recipe kept?
For a lot of small offices, the first custom software they ever own will be a checklist or a calculator that someone on staff built in an afternoon. That's a good thing, as long as you treat it like any other tool in the building: one owner, a written recipe, a test before it's used, and a person who makes the final call on anything that goes to a customer or touches money. Start with one. The sticky note on the monitor is a fine place to look.
---
Sources (checked October 21, 2026). Artifacts launch: "Introducing Claude 3.5 Sonnet" (Anthropic, Jun 21, 2024). AI-powered apps, plans and launch limits: "Build and share AI-powered apps with Claude" (Claude blog, claude.com/blog/claude-powered-artifacts, Jul 25, 2025, with the Jul 31, 2025 update for Team and Enterprise). Editing drafts in place and the new artifacts in any conversation: Claude release notes (Anthropic Help Center, entries for Jun 12, 2026 and Sep 16, 2026). Docs, Slides and Design out of beta on every plan: "Build live dashboards and animate explainers with Claude" (Claude blog, Oct 8, 2026). Small interactive tools, the 20 MB text storage limit, personal and shared storage, artifacts that use Claude, connected apps, legacy artifacts and "Try fixing with Claude": "What are artifacts and how do I use them?" (Anthropic Help Center, support.claude.com/en/articles/9487310). Claude account requirement and link-sharing rules: "Share artifacts" (Anthropic Help Center, support.claude.com/en/articles/9547008). Version history in Claude Design: "Get started with Claude Design" (Anthropic Help Center, support.claude.com/en/articles/14604416). External sharing for Team plans: "Artifacts admin guide for Team and Enterprise plans" (Anthropic Help Center, support.claude.com/en/articles/16994751).