- Built and supported in Sydney
- Runs on Claude
Team work doesn’t belong in a private chat.Team work doesn’t belong in a single-user session.
Everyone on the team has their own AI. So the work happens where nobody else can see it.Everyone runs a private assistant. So the prompts, the context and the outputs stay where nobody else can see them.
69%of respondents said most AI-assisted work happens in private sessions rather than shared spaces.Miro, The State of Intelligent Collaboration: a survey of 9,500+ leaders and employees, September to October 2026
- “I asked the AI, then pasted the answer into the team chat.”
- “Who checked this before it went out?”
- “We pay for AI for everyone. I can’t see what it’s done for the team.”
One chat. Your people, Cora and her heroes.One thread. Your people, the orchestrator and specialist agents.
Everyone sees the work.Shared context by default.
Questions, drafts and results are in one place, as they happen.Questions, drafts and results live in one mission thread, as they happen.
Compare with a personal AIThe right person makes each call.Human-in-the-loop, routed by role.
Cora sends every decision to the person who owns it.Cora routes each decision to the person who owns it.
See how Cora worksCopy lead · today, 2:14 pm
It carries on while you’re off.Async by design.
Scheduled work runs in the cloud overnight. The results are waiting in the morning.Scheduled runs execute in the cloud sandbox overnight. The artifacts are waiting in the morning.
How the sandbox worksMeet Cora. She coordinates. You decide.Meet Cora. She orchestrates. Humans approve.
We know what it’s like when everyone has their own AI and the team is no better off. So we built an AI that works in the open, with the whole team, and asks first wherever you choose.We know what it’s like when everyone has a private assistant and the team is no better off. So we built an orchestrator that works in the open, in shared context, and waits for approval wherever you set Ask first.
“Tell me what you want done. I’ll coordinate the rest. You make the calls.”“Give me the objective. I’ll plan, delegate and report back.”
Has never said “oops, already sent”.
- She asks first.Write tools ask first.A tool set to Ask first waits for an approval card before it changes anything. Your admins, or the person who added the connection, choose which ones.A write tool set to Ask first waits on an approval card. Admins set this per tool.
- She never sees your passwords.Credentials never enter the model’s context.Logins stay in a vault. The AI uses them without reading them.Secrets stay in a vault. Agents refer to a key by its name; its value never reaches a prompt.
- She works in her own walled-off space.Isolated execution.A cloud sandbox, not anyone’s laptop.An isolated cloud sandbox, never anyone’s device.
Sent only to the site Daniel named · never shown againCora uses a key without seeing it. She sees only its name.
Invested in AI, but it never stuck?AI pilots stalled? We get agents into production.
Built and supported in Sydney. We set it up with you, write skills for your work and build custom connectors for bespoke and legacy systems.Built and supported in Sydney. Our team writes domain skills, builds custom connectors and MCP servers for bespoke and legacy systems, runs evals and tunes token use.
Three steps to your first missionThree stages to your first mission
Tell Cora what you want done.Give the orchestrator a goal.
Write the goal in your own words.A plain-language objective becomes the orchestrator’s context.
Approve the team she suggests.Approve the team the orchestrator proposes.
Your people and the AI heroes for the job. Untick anyone.People by role and specialist agents by capability. Untick any line before you approve.
Make the calls.Stay in the loop.
The heroes do the legwork. Anything set to Ask first waits for your yes.Specialist agents run the tasks. Write tools on Ask first wait on your approval card.
Meet the heroesDone in 2 minutes · checked the landing page, 3 fixesCalled in Nova
Done in 3 minutes · pulled last autumn’s numbersDaniel, start the ad campaign at A$1,500?Nothing is spent until Daniel says yes.ApproveNot nowArtifactsLaunch plan.mdFrom CoraLanding page fixes.mdFrom Kit, a hero
Build a hero once. Your team calls it in.Persistent specialist agents, shaped by your team
Your team decides what each hero knows, what it may use and who signs off its work. It stays on your team, ready for the missions you open it to.People stay in the loop: they choose each agent’s skills and connections, and the people who approve its work. Agents persist across missions and are called by handle.
- SkillsWhat it knows how to do, chosen and approved by your team.Domain skills: instructions and scripts for repeatable, predictable results. An admin approves each one.
- ConnectionsConnectors and MCPThe tools and accounts switched on for its mission, and nothing else.Connectors and MCP servers switched on for its mission. Write tools on Ask first wait for approval.
- MemoryWhat it has learned, kept as plain Markdown your team can read.Persistent mission memory, kept as Markdown your team can read.
- A walled-off workspaceSandboxYour organisation’s sandbox in the cloud, with a private folder for each call.Runs in your organisation’s isolated sandbox, with a private scratch folder per call.
- AI modelModelRuns on Claude, from Anthropic, matched to each job.Tasks are routed across Anthropic’s Claude Haiku, Sonnet and Opus.Choosing the model per hero: coming soonPer-agent model choice: coming soon
- Who decidesHuman approversThe people who must say yes, by role.Role-based approvers: the humans in the loop.
How Team Cora works
See how Cora worksTeam Cora is a shared workspace in your web browser. You open a project, which we call a mission, and say what you want done. Cora, the mission coordinator, plans the work and suggests who should be on it: the people on your team, and the AI specialists we call heroes. Each hero has its own job, skills and tools, set up once and shared with everyone. The work happens in one chat that the whole team can see. When something needs a decision, or a tool set to Ask first is about to change something, Cora asks the person who owns that call and waits. What the team learns is kept as plain documents you can read and download.Team Cora is a shared workspace that runs in the browser. You open a mission and state the objective. Cora, the orchestrator agent, plans the work and proposes the team: people by role, and the specialist agents we call heroes. Each hero has its own role, skills and connectors, configured once and shared across the organisation. The work happens in one mission thread that every member can read. When a decision is needed, or a write tool on Ask first is about to change something in a connected system, Cora routes an approval card to the person who owns that call and waits. What the team learns persists as Markdown artifacts you can read and download.
Questions teams ask
- Will it send something without asking?Can an agent act without approval?
- Not when it’s set to Ask first. A tool on Ask first waits for a person’s approval before it changes anything, and your admins, or the person who added the connection, choose which tools are on Ask first.Not on Ask first. A write tool on Ask first waits on a person’s approval card; admins choose which tools are on Ask first.
- Can it see our passwords?Do credentials reach the model?
- No. Logins stay in a vault, and the AI never reads them.Secrets stay in a vault. Agents refer to a key by its name and never read its value.
- Does it run on my laptop?Is there any local execution?
- No. It works in a walled-off sandbox in the cloud, with no way into your computer.Agents run in an isolated cloud sandbox, with no path to your devices.
- Is it only for marketing teams?Is it tied to one domain?
- No. Any team, any mission.Any domain, any mission. See seventeen examples.
- Do we need to be technical?Do we need engineers to run it?
- No. You write in plain English, and our Sydney team sets it up with you.Objectives are plain language, and our Sydney team handles set-up, skills and connectors with you.
- We already have an AI chat for everyone. Why this?We already have a single-user assistant for everyone. Why this?
- Keep it for your own work. Team Cora is for the work you do together.Keep it for single-user work. Team Cora is the shared, multi-agent workspace for the work you do together.
Pick a first mission
Any team, any mission. Choose one and see how Cora would run it with your people.Any domain. Pick one to see the plan, the human approvers, the agents involved and the artifacts it leaves behind.
Growth and launches
Sales and customers
Operations
Finance and legal
People and leadership
Here’s how we’d run launch a product:
- You set the launch date and who signs off what
- Cora writes the plan and drafts the announcement
- Kit checks the landing page before it goes live
- Cora asks the budget owner before any ad spend starts
Here’s how we’d run run an email campaign:
- You name the audience, the offer and the send date
- Cora drafts three emails for your copy owner to approve
- Nova pulls the last campaign’s results to set a target
- You share each send’s results, and Cora records what worked
Here’s how we’d run build a landing page:
- You say what the page is for and who it is for
- Cora drafts the structure and the words
- Kit opens the page in a browser in the sandbox and lists the fixes
- Your team approves the final version
Here’s how we’d run watch competitors each week:
- You list the competitors and what matters to you
- Cora schedules the check for every Monday morning
- Scout compares their prices and announcements
- Cora flags the changes and asks who should respond
Here’s how we’d run run a customer survey:
- You choose who to ask and what you want to learn
- Cora drafts the questions for your team to approve
- Echo reads the answers and pulls out the themes
- Cora writes the summary and the suggested next steps
Here’s how we’d run answer a tender:
- You share the tender in the mission and name who owns each section
- Scout lists every requirement and its deadline
- Cora drafts each answer and sends it to its owner
- Your sales lead approves the final response
Here’s how we’d run clean up the CRM:
- You say what “clean” means: duplicates, missing fields, old leads
- Cora works through your CRM connection and never sees its key
- Nova finds the records that need fixing
- With the CRM’s write tools on Ask first, every change waits for your approval
Here’s how we’d run write the weekly report:
- You say what the report should cover
- Cora schedules it for every Monday at 9 am
- Nova pulls the numbers and writes it up
- Cora asks you about anything that looks unusual
Here’s how we’d run plan an office move:
- You name the move date and the budget owner
- Cora builds the checklist and names who owns each task
- Scout compares three removal companies
- Cora asks the budget owner before anything is booked
Here’s how we’d run plan a team event:
- You set the date, the headcount and the budget
- Scout shortlists venues that fit
- Cora puts the shortlist to a team vote on a choice card
- The budget owner approves the booking
Here’s how we’d run close the month:
- You share the month-end checklist and name who owns each item
- Cora asks each owner for their item before the deadline
- Nova checks the reports you share against last month’s and lists what looks unusual
- Your finance lead signs off the close
Here’s how we’d run collect overdue invoices:
- You share the list of overdue invoices and say how firm to be
- Cora drafts a note to each customer, in your own tone
- Your accounts lead approves each note before it is sent
- You share the replies, and Cora keeps the list up to date
Here’s how we’d run get ready for tax time:
- You share the list of documents your accountant asks for
- Cora builds the checklist and names who owns each document
- Nova checks what has been shared against the checklist and lists the gaps
- Your accountant decides what goes in the return
Here’s how we’d run review a contract:
- You share the contract and your team’s own review checklist
- Scout reads it against the checklist, clause by clause
- Cora lists the questions and the clauses that differ from your usual terms
- Your contract owner or your lawyer decides what to accept
Here’s how we’d run onboard a new starter:
- You name the starter, their role and their first day
- Cora builds the first-week plan from your past onboarding notes
- Cora names the owner of each task: laptop, accounts, introductions
- Cora schedules a check-in for the end of week one and records what to improve
Here’s how we’d run hire for a role:
- You describe the role and who is on the hiring panel
- Cora drafts the job ad and the interview questions
- Scout researches salary ranges for the role
- Your panel chooses who to interview and who to hire
Here’s how we’d run prepare the board pack:
- You list the sections and who owns each one
- Cora asks each owner for their update before the deadline
- Nova pulls the numbers from your reports
- You approve the final pack
The heroes named here are examples. Your team builds its own, or our Sydney team builds them with you. Cora prepares and checks; she does not give legal, tax or financial advice, and your people and your advisers make those calls.The agents named here are examples. Your team builds its own, or our Sydney team builds them with you. Agents prepare and check; they do not give legal, tax or financial advice, and your people and your advisers make those calls.
Every plan has everything
Every connector, any MCP server, the cloud sandbox, vaults, schedules and heroes. Plans differ only in AI usage, people and support.Every connector, any MCP server, the sandbox, the vault, schedules and specialist agents on every plan. Plans differ only in AI usage, people and support.
Free for 14 days, then fromUS$49a month for 5 people
See pricingReady to start your first mission?Ready to run your first mission?
It’s your call. No card needed.Your approval. No card needed.CORA IS SCANNING YOU
NOT A NERD
Showing you Plain English.
Just for fun. Cora didn’t scan anything, and nothing was recorded.