Work Orchestra
You shape the landscape
Pin the folders. Attach the files. Connect the tools. Capture the threads. You decide what belongs to this body of work — and what doesn't. No taxonomy meeting, no migration. Just point at what's relevant.
Closed beta · macOS + Windows · iOS coming soon
The user interface
for work.
Work Orchestra gives your files, web tools, AI, and agents one working surface — so you can open the work, understand what changed, and direct what happens next.
Works on the file servers you already use
Dropbox
OneDrive
Google Drive
SharePoint
NAS / fileshare
Local folder
The idea
Your work already exists.
It just doesn't have an interface.
Work Orchestra is the interface.
Why Orchestra
Real work has many parts. Direct them together.
Files. Folders. Tabs. Notes. Messages. Tools. AI. Agents.
The goal isn't to collapse them into one monolithic app — it's to coordinate them. Your files stay files. Your web tools stay web tools. Your AI stays AI. Work Orchestra gives you the interface to direct them together.
You stay the conductor.
The work starts moving.
The work starts moving.
Before and after
The old way is stitching. The new way is directing.
The old way
Stitch it together yourself.
- Find the right folder
- Open the spreadsheet
- Search Gmail for the thread
- Reopen the notes
- Dig through eight tabs
- Paste the context into AI
- Re-explain the project from scratch
- Copy the answer back into your tools
The Work Orchestra way
Open the surface. Direct the work.
- Open the working surface
- Files, web tools, notes, and history are already there
- AI and agents have the context
- Memory carries forward — the agent remembers what you discussed last time
- Tell the agent what needs to happen
- Watch it read, draft, update, and prepare
- You stay the conductor
How it works
One interface above what you already use.
Create a surface for a body of work, connect the folders and tools that belong to it, then use AI and agents inside that context.
Not a dashboard about the work. The interface where the work happens.
The foundation
Files, shared drives, cloud folders, web tools, inbox
stays as-is
The interface layer
Work Orchestra
one surface
What becomes possible
AI and agents that read, draft, update, and act
finally has context
How AI gets context
You define the landscape. We build the context AI can actually use.
Most AI tools sit and wait for you to explain the situation. Work Orchestra inverts the model. You shape the work landscape — the folders, files, tools, and threads that matter. We turn that into a structured map AI can consume natively. The AI doesn't guess what you meant. It reads the map you built.
We build the map
Files become readable artifacts. Folders become scoped containers. Notes become workspace memory. Tools become callable. AI gets a structured map of what exists, where, and how it relates — not a pile of pasted text.
AI acts in context
When you ask, the file is already in scope, the thread already loaded, the tool already authorized. No "let me paste the relevant bits." No re-explaining the project. The AI reads the map and works.
The result: AI you can trust to act — because the context didn't come from a guess, it came from you.
Adjacent, not the same
Other tools open things. We open the work.
Launchers
open apps.
Work Orchestra
opens the work.
Browsers
open websites.
Work Orchestra
gathers the web tools that matter.
File managers
show where files are.
Work Orchestra
turns files into a working surface.
Claude / ChatGPT
give you AI.
Work Orchestra
gives AI somewhere to work.
vs. Claude for Work
Claude is the intelligence. Work Orchestra is the interface.
The most common question we get: "Won't Claude just do this?" Claude is a powerful AI assistant. Work Orchestra is the working surface Claude needs.
Claude for Work
A powerful AI assistant for teams.
It helps users ask questions, generate content, analyze information, build artifacts, use skills, and connect to apps. Its center of gravity is the AI conversation.
Work Orchestra
The user interface for work.
It gathers files, folders, shared drives, web tools, context, AI, and agents into one desktop surface. Its center of gravity is the work itself.
Claude asks
"What can AI help you do?"
Work Orchestra asks
"Where is the work, and how do we give you one interface to direct it?"
Claude gives you AI. Work Orchestra gives AI somewhere to work.
Two bets behind Work Orchestra
What we believe, and why.
Bet One
Your file server is the source of truth — not us.
Most software companies want to become the place where your work lives. We make the opposite bet.
Your files already live somewhere. Your team already has a shared drive. That isn't a legacy problem to replace — it's the foundation.
The file server stays the source of truth. Work Orchestra is the interface above it.
Easier to trust. Easier to adopt. Harder to lose.
Bet Two
AI is most useful with context and tools.
A blank chatbot has neither. It waits for you to explain the situation, paste the relevant material, and translate the answer back into the tools where the work actually happens.
Work Orchestra changes the starting point. The files, web tools, notes, and history are already there.
AI can act from inside the work, instead of hovering beside it.
Lead with the interface. AI is what becomes possible because it exists.
Your files are not our hostage.
Your shared drive stays the source of truth. Work Orchestra points at the files and tools you already use, then layers an interface on top. If you stop using Work Orchestra, your files are still your files — same folders, same formats, same place they were before. No export, no migration, no contract holding your work captive.
What you actually get
What's in the working surface.
Five things, gathered in one place. Each is a real first-class citizen — not a feature pretending to be one.
Files
Pin folders, documents, spreadsheets, PDFs, and notes from your existing drives.
Web tools
Bring Gmail, Calendar, browser tabs, wikis, dashboards, and forms into the same window.
AI chat
Ask questions and give commands with the current work already in context.
Agents
Compare two versions of a file, summarize what changed, update a tracker, and prepare the follow-up — across the files and tools already open.
Plugins
Use built-in tools or add your own. The plugin SDK is open and documented.
What's unique
Four things, only together.
No single one of these is defensible alone. The combination is the product — and no other tool ships all four.
Files stay where they are
Built on your shared drive, cloud folder, NAS, or local files. Nothing migrates into our database.
Web tools in the same surface
Gmail, Calendar, browser, wiki, todo, RSS, DocuSign, and more — gathered into one window.
AI inside the work
Direct it in plain language. It reads files, drafts emails, runs multi-step work.
Portable working state
Your surface is described in JSON. Point another machine at the same files and the interface follows.
What's included
Built-in tools for the work you already do.
Twenty-eight first-class tools ship today. Use them as-is, or build your own.
Files
Email
Calendar
Browser
Wiki
Todos
Notes
Excel
Word
PowerPoint
RSS
DocuSign
AI Chat
Terminal
Stocks
…and a plugin SDK for whatever your work needs next.
Who it's for
Defined by behavior, not industry.
Anyone whose work is spread across files on a shared drive and tools on the web — and who wants one place to direct it all from.
People running many threads at once
Teams working from shared drives
Operators managing repeatable work
Researchers and writers with scattered sources
Analysts working across files and web tools
AI-native workers who want agents in the work
The pattern
They have many things going on at once — founders, operators, analysts, researchers, writers, lawyers, investors, consultants. Their source of truth is in folders. Their tools live on the web, their context scattered across tabs, files, messages, and AI chats. They wish AI could do the boring parts without making them paste the whole story into a blank box first. They are not looking for another empty system to maintain — they are looking for a better interface to the work they already have.
How we compare
Most tools own one piece. We're the surface above all of them.
A side-by-side look at where Work Orchestra fits versus the most common alternatives — including AI-first products like Claude for Work, where the center of gravity is the AI conversation rather than the work itself.
| Work Orchestra YOU | Notion / Obsidian | Raycast / Alfred | Claude for Work | File manager + tabs | |
|---|---|---|---|---|---|
| Files stay on your drive | ✓ Source of truth on your file server | ✗ Stored in their database | — Not a file tool | ~ Files referenced, not held | ✓ |
| Web tools in the same surface | ✓ Gmail, Calendar, browser, wiki, RSS, more | ~ Some embeds | ~ Quick-launch only | ~ Connectors, but inside chat | ✗ Each tool a separate window |
| AI with full context of your work | ✓ Files, tools, history all available | ~ Limited to their database | ✗ | ~ Per-Project context, not your environment | ✗ |
| Agents that act across tools | ✓ Multi-step work in your environment | ✗ | ✗ | ~ Skills + connectors, vendor's ecosystem | ✗ |
| Center of gravity | ✓ The work itself | ~ Their database | ~ App launching | ~ The AI conversation | ~ File hierarchy |
| AI provider flexibility | ✓ Use Claude, others, or local — your choice | ~ Their AI features only | — | ✗ Anthropic's models only | — |
| Works offline (your files) | ✓ Files are local; tools degrade gracefully | ✗ Cloud-only | ✓ | ✗ Cloud-only | ✓ |
| Portable across machines | ✓ JSON state, points at your drive | ✓ Their cloud sync | ~ | ✓ Their account sync | ~ |
| Extensible (write your own tools) | ✓ Open plugin SDK | ~ Limited API | ✓ Extension store | ~ Skills + MCP, in their environment | ✗ |
| If you stop using it… | ✓ Files unchanged, work intact | ✗ Export and rebuild | ✓ | ~ Projects, history, artifacts are theirs | ✓ |
In plainer terms
Our first competitor isn't a startup. It's the chaotic status quo.
Bookmarks & tabs
A folder of bookmarks, eight pinned tabs, and a ChatGPT tab open in the corner.
Works for a while. Falls apart fast. Work Orchestra is the surface, not the workaround.
Notion / Obsidian
Good for storing knowledge — in their database, in their format.
Work Orchestra leaves your work on the file server and gives it an interface.
Raycast / Alfred
Great launchers. They open apps quickly.
Work Orchestra opens the work itself — the right files, the right tools, in one window.
A file manager
Necessary, but inert. It shows hierarchy, not context.
Work Orchestra turns files into a working surface with the tools and AI to act on them.
A browser
Essential, but chaotic. Every tool becomes another tab.
Work Orchestra holds the relationships you currently keep in your head.
Claude / ChatGPT
Powerful intelligence. But the work still lives elsewhere — in files, folders, tabs, inboxes, and tools.
Work Orchestra is the interface where that work is gathered, so AI and agents can act with the context already in place.
where-am-i.docx
A note in a document, summarizing where you are. Honest. Hand-maintained.
Work Orchestra renders the document obsolete — your state is the surface.
A typical morning
One sentence in. The work moves.
Review the new files, update the tracker, and draft the follow-up.
Reading launch-tracker.xlsx · /shared/work/acme-launch
Compared against last revision · 12 cells changed
Updated weekly-update.docx · §3
Draft saved · "Acme launch — week 4 update"
Done. Weekly saved. Draft is in your outbox.
No app switching
It happened in one window — the same one you started in.
No context pasting
The AI already had the files, the inbox, and the history.
You directed
The work moved across files and tools — under your direction.
Stop reassembling. Start directing.
Your files stay where they are. Your web tools stay yours. Work Orchestra gives them one working interface, with AI and agents inside.