by Ensemble LabsYour team's AI coworker, in Slack.
Maia joins a Slack channel, learns how that team works, and does the work in the thread. Before it changes anything outside Slack, it asks.
Finance gets one that knows the month-end close. Support gets one that drafts the first reply.
Runs in its own deployment for your company. The only thing that leaves it is model calls to providers you approve.
@Maia reconcile the August Stripe payouts against the bank statement before we close.
Matched 214 of 216 payouts. Two are timing differences that clear on 1 September. The last gap is a 1,240.00 processor fee posted to the wrong account.
Post journal entry?Move 1,240.00 from 6100 Bank fees to 6120 Processor fees, period August.ApproveRejectMaia is workingStop
Approving. Same account as last month's payout fees.
Entry posted. 216 of 216 payouts reconciled.
✅Approved by Priya Raman · JE-2291
Anyone in the channel can teach it. A confirmed correction becomes a rule for everyone.
Each channel gets its own coworker with its own memory. Anyone can ask it, redirect it or correct it in the thread. Once a teammate confirms a correction, everyone gets the better answer from then on.
Added @Maia to the channel.
Reading the last 90 days of #support. I can answer first-line questions and route the rest to the right person.
@Maia how did last week's pricing test do?
Variant B lifted signups 6.2 percent, but activation fell 3.1 percent.
Not signups. Activation is the first report created.
Corrected. On first report created, B is flat against control. I will use that definition here from now on.
Confirmed, payout fees go to 6120.
Everyone in the channel gets this from now on.
✅Saved as a rule for #finance@Maia which account do Stripe fees go to?
6120 Processor fees. Owen set that rule this morning.
Invite it
Add Maia to a channel. It reads the history and starts working the way that channel works.
Correct it
Anyone in the channel can. Maia takes the correction in the thread, where everyone can see it.
Everyone gets it
A confirmed correction becomes a rule for that channel. Nobody has to be told twice.
Always just the right model. The cheapest one that's good enough.
Every task goes to a model from the providers you approve, using your own API keys: a small, fast model for routine work, a frontier model when it matters. Pin one if you prefer. Your context lives with you, not with the provider, so switching costs nothing.
reconcile 216 payoutsa small, fast model is enough
One plan. Everything included. No feature tiers, no add-ons.
One coworker per channel. Each has its own memory, its own tools and its own name. Anyone in the channel can teach it, and a confirmed correction becomes a rule for everyone there. Every feature is included.
- A coworker for every channel you invite it to
- Memory per channel, shared by the whole team
- Corrections that become rules once confirmed
- Approvals in the thread before anything is written
- Any model from the providers you approve
- Your own keys, pinned or routed per task
- Every tool you already use, over MCP
- A log of every run: who, what, which tools, who approved
What you get, in plain terms.
Start with one channel. Pricing is agreed during the pilot. There is no self-serve signup: we set Maia up with you.
Start with one channel.
We set Maia up with your team in one Slack channel, then add more as you go. It starts with a demo and a pilot, not a signup form.