Bot, meet humans.
The world's first multiplayer bot experience.
Watch
In use at
Point at the spike. Everyone asks why.
A bot keeps the growth dashboard. Someone circles Tuesday 4pm. One person knows an email went out then, one knows a creator reposted, one saw bot traffic last week. Each points to where the data lives. The bot connects to all three, tests each theory against the spike and adds a panel with the answer.
Start a dash bot →
Comment on the bad cell. It gets fixed.
A bot owns the month-end export. One analyst knows EMEA lands in a different system, one knows a refund was booked twice on purpose, one knows the Q3 dates were pushed a week. None of that is in the data. The bot fixes each at the source and rebuilds the sheet. Every fix is logged.
Start a sheet bot →
Review the spec together. Decide it in the doc.
A bot maintains the spec. One engineer knows two customers already use the old API, one knows why the last migration failed, the lead knows what was promised for the quarter. The bot checks each against the code and the tickets and writes the decision into the doc, next to the comment.
Start a doc bot →
The QBR deck, built by everyone who knows the account.
A bot drafts the QBR deck from the numbers. The rep knows what was promised on the last call, the solutions engineer knows which integration is actually live, the success manager knows which ticket the customer will ask about. The bot rewrites the slides around what they know. Nobody has to build the deck.
Start a deck bot →
Leave the meeting with the plan already on the board.
A bot runs the board. Paste in the standup notes. One engineer knows the vendor is late, one knows a review is blocked on someone's leave, the lead knows the launch date moved. None of it is written down yet. The bot reworks the plan around all three and tells the people it affects.
Start a board bot →
One bot.
- 01A bot can run 24×7.
- 02A bot can work on its own isolated computer, with a browser.
- 03A bot can build tools to connect to any API or database.
- 04A bot can create artifacts and apps.
Many users.
- 01Users can't ask the bot to access another user's data.*
- 02Users can edit and delete messages in the shared chat.
- 03Users can spawn private bots to do secret work and report back.
Start a bot. Invite a collaborator.
Spin up a bot and give it a responsibility or a goal. When it hits a wall, or has output worth sharing, bring someone in and keep things moving.
Real work, by team
Board deck
CEO · FinanceDraft it from last quarter's. Tell me what data you're missing and who in sales, finance, product you need to talk to for the narrative.
AI radar
CEO · ProductInfer from my sent emails which AI topics I should track. Suggest who else should add topics. Then run a twice-daily newsletter for the team.
Actionable bug from a customer report
EngineeringReproduce the issue or read our logs, find it in the code. Pull in the right engineer when stuck. Flag if it needs a product call.
Ad-hoc dashboard
DataSomeone asked for a dashboard. Build the basic version from our existing dashboards, then tag them to check it's what they actually wanted.
Dedupe metrics & dashboards
DataWe have multiple overlapping and conflicting dashboards and metric definitions. Find them and bring in the right folks so that we can document which ones are correct.
On-call
Engineering · OpsAlert in a service I don't know. Pull recent changes, similar incidents. Identify the right expert if stuck. Send them your hypothesis and what to confirm.
Meeting prep
SalesCall with [account] Thursday. Brief me on product things they asked last time. Get product to confirm shipped vs roadmap vs never. What can I commit to?
Security questionnaire
Security · SalesSplit the questions by who'd know: infra to engg, controls to security, DPA to legal. Reuse past answers; bring people in only for the rest.
Communicate a deliverable ETA
Product · SalesWhen does [issue] ship? Is it in a sprint, backlogged, or off the radar? Ask the owning engineer. Check what we've already told them. Draft my reply.
Clickable prototype
Product · EngineeringTurn this spec into wireframes I can click through. Get design to mark what's off and engineering to flag what's expensive. Iterate until it's decided.
Brand guidelines
MarketingDraft them from what we've actually shipped. Let design and the founders argue it out in the doc. Then hold every new asset, print or digital, to it.
Event kit
Marketing · OpsBooth, banners, one-pagers, swag for [conference]. Get specs and quotes from the vendors, brand sign-off from us, and track who owes what by when.
Website edits
Marketing · EngineeringFix the copy on [page]. Show me the diff, get product to confirm the claims, open the PR. Nudge me when it's live.
Flux analysis
FinanceRun this month's with last month's excel as baseline. Bring in the right people when you're stuck on getting data or to create the narrative.
Office pantry
Ops · HRHere are photos, $500 weekly budget. Ask the team what they want, figure out the order, place it on Instacart.
Pay only for the AI you use
Every user starts free. Pay only for users who need more in $40 increments, billed weekly.
- Shared context: knowledge, skills, semantic layer
Consumption based with a monthly minimum commit.
- No limit on users
- Shared context: knowledge, skills, semantic layer
- Single-tenant deployment
- BYOC or self-hosted deployment
- Bring your own models
- Dedicated forward-deployed engineers
What is a bot, exactly?
An agent you spin up for one thing: movie night, the quiz, the trip. It starts generic and becomes yours as you use it. What it learns, what it makes and what you told it all stay with it.
Do my friends need an account?
They need an invite from you, and during the beta each person gets a handful. Once they're in, they talk to the same bot you do, from whatever device they're holding.
What can it see?
What you give it, and nothing else. Connect a streaming account and it can check that account. Don't, and it can't. Your friends' connections stay theirs; the bot never uses one person's access to answer another. How that works →
Whose permissions does a bot use?
A bot has no access of its own. Each time it acts, it borrows the permissions of the person who asked: the data, apps and files that person can already reach, nothing more. If you ask it for a report, it can only pull from what you can see. If a colleague asks the same bot next, it switches to what they can see.
So a shared bot is not a side door. You can't ask it to fetch something a teammate can see and you can't, and neither can they. Access is decided by your organisation's permissions, not by who happens to be in the chat.
One thing to keep in mind: whatever a bot says in a shared chat is visible to everyone in that chat. If the question is sensitive, ask it in a private bot and share the result.
Where does it run?
On its own computer, with its own browser, around the clock. Nothing is installed on your phone or laptop, and it keeps working when you close the app.
Can I do something without the group seeing?
Yes. Spawn a private bot, do the work there, and share only the result: the surprise party stays a surprise.