@HeyBob pull this month's pipeline from HubSpot and make the deck for Friday's review.
Your AI employee in Slack
Give Bob the job.
Give Bob the job.
Get back the finished work.
Mention @HeyBob in Slack. He works across your connected tools, asks before sensitive changes, and returns the result with a receipt showing what it cost.
$100 in credits · about 150 typical tasks · 14 days · no card · Microsoft Teams in early access
What happens after you click?
- 1. Review accessSlack shows every permission before you approve anything.
- 2. Add BobHe joins your workspace like any other Slack app.
- 3. Give him a jobMention @HeyBob with a task your team actually needs done.
- 4. Connect as neededAdd another tool only when that task calls for it.
Not the person who installs apps? Send this to your admin
Adding Bob takes a Slack admin about a minute, once. Here is the note to send them.
Review Slack access first
Approval before sensitive writes
Every completed run receipted
Remove anytime
3,200+ connected apps
# pipeline-review
One @mention. Bob pulls the numbers, reuses last month's format, posts the finished deck, and itemizes the work, all in Slack.
Built like a coworker
What Bob does that software usually doesn't.
None of this is magic. It's just what happens when an AI has its own computer, its own memory, and a receipt printer.
# finance-ops•••
Finished work, receipted
Bob hands back the finished report, the fixed spreadsheet, the closed ticket, plus a receipt of exactly what it cost. Not a wall of suggestions to go execute yourself.
# weekly-ops•••
No app-switching required
Native connectors, 3,200+ apps, any OpenAPI or MCP server, and a real browser for the rest. If it has a login, Bob can probably reach it.
# pipeline•••
Runs on repeat, and knows when to stay quiet
Tell Bob once, in plain English, and it's a schedule. A check that finds nothing worth saying posts nothing.
# product-metrics•••
Remembers so you don't have to
Bob keeps a workspace memory of the decisions and definitions your team has already made, so nobody explains "active user" twice.
# support•••
Acts on events, not just clocks
Ask Bob for a webhook and point any system at the URL: "when a ticket closes, tell the channel." He only speaks up when the event actually matters.
Hand Bob the task you keep carrying into tomorrow.
Add Bob to Slack, start free
Bob vs. a standalone chat
A good answer is not the same as finished work.
Standalone chat is useful for thinking through a task. Bob is built for the part after the answer: working across your tools, asking for approval when needed, and returning the result in Slack. Pick a task below.
Standalone chat
You paste the numbers in. It explains reconciliation, beautifully, in bullet points. You still open QuickBooks yourself.
Bob
Matches 293 payouts against QuickBooks, flags the 2 that don't line up, and fixes them the moment you tap Approve.
Standalone chat
It summarizes the call nicely. The action items, the follow-up emails, and the CRM updates are still sitting on your to-do list.
Bob
Creates the tasks, sends the follow-ups, and updates the CRM. The meeting is actually over when Bob's done.
Standalone chat
It drafts a nice email about whatever numbers you copy-paste in. You're still pulling those numbers from four different dashboards.
Bob
Pulls the numbers itself, builds the report, and posts it every Monday at 8. You ask for the schedule once, Bob keeps it running.
Rule-based automation
It runs the rules exactly as you wrote them, and rewrote them, and debugged them, last Saturday.
Bob
Ask once, "every Monday at 8", and Bob turns it into a schedule, confirmed in plain English. Runs stay quiet unless there's something worth saying.
How it works
Bob can be working in minutes.
No setup project or onboarding webinar. Add him where your team already talks, connect only what he needs, and hand him the job.
Add Bob to Slack
He shows up like a new teammate, ready for an @mention in a channel, thread, or DM.
Connect only what he needs
Give Bob access to the CRM, ledger, or drive for the task. Credentials stay encrypted and out of his sandbox.
Give him the job
The result, files, and receipt land back where you asked. Sensitive writes still wait for your approval.
Control & spend
Full autonomy, zero surprises.
Let Bob own the work without giving up control. The important decisions stay visible, specific, and inside Slack.
- You approve sensitive writes.CRM, ledger, and document changes pause with the exact action Bob wants to take.
- You set the budget.Once recorded monthly usage reaches your workspace cap, Bob blocks new runs while work already in progress finishes. Every completed run ends with a receipt.
- You decide what runs quietly.Set schedules and quiet hours in plain English. Broken recurring work pauses instead of spamming the channel.
# finance-ops•••
I’m ready to update 2 QuickBooks entries. Approve this write?
2 records · QuickBooks · logged either way
Sandboxed agent runs
OAuth vault, encrypted at rest
Receipts on every completed run
No training on your data
Self-host in your VPC
SOC 2 · in progress
See the exact Slack permissions before you install
Slack shows and asks you to approve these 15 bot scopes during installation:
app_mentions:readchat:writechat:write.public
files:writefiles:readchannels:history
channels:readgroups:historygroups:read
im:historyim:readim:write
users:readcommandsreactions:write
They let Bob receive mentions and DMs, read the Slack context available to him, identify who asked, and post messages, files, and reactions. Other business tools stay disconnected until someone authorizes them separately.
The receipt
No mystery. Just the numbers.
Every completed run posts its own receipt beside the finished work, right in the Slack thread.
Bob's receipt
# daily-metrics•••
The result, the time, and the work behind it stay together. No separate usage dashboard to reconcile later.
Cost One readable total in credits.
Time How long Bob’s sandbox was working.
Tool calls How much outside work the run needed.
Why receipts? Because I've been on the other end of AI invoices that just say "usage." Bob is built on one bet: a team will hand real work to an AI employee only if the finished result, the approval moments, and the cost stay visible. That's the product; the rest is engineering.
MatthewFounder · [email protected]
Pricing
Start free. Scale when Bob earns it.
Your first $100 in credits are free for 14 days, with no card. Paid workspaces start at $99/month with flat workspace pricing and no per-seat fees.
The hour you get back
Buy back the hour.
If the all-hands deck normally takes an hour of $100/hr work, Bob changes the math.
Build it yourself
~60 min
~$100 of team time
Hand it to Bob
1m 11s
14 credits · about $0.69
The point isn't cheaper slides. It's getting the hour back.
Most teams start here
Flex
One bill and zero model setup. Credits cover models, tools, and sandbox time.
$99/mo
Task estimates use about 13 credits per completed run; actual usage varies with the work. Pick any volume from $99/mo. Change it whenever; it takes effect at your next renewal, never mid-cycle.
- Slack & Microsoft Teams (early access) surfaces
- Native connectors + 3,200+ apps
- Schedules, approval policies, spend caps
- OpenAPI & MCP connectors
- Unused paid-plan credits roll over one month
Your VPC · own model key · custom volume
Enterprise
Bob in your VPC, or on your own model key, with the paperwork bigger teams need.
Custom pricing
- Self-hosted in your VPC
- Bring your own model key at your negotiated rates
- Security review, DPA, and a subprocessors walkthrough
- The same Slack approvals, schedules, and receipts as Flex
- Offline license verification, so an expired license stops new runs and never bricks the deployment
- No training on your data, on any tier
Workspace credits, not per-seat
Your whole team draws from one pool. No per-seat licenses, no per-user minimums as you add people.
Every run comes receipted
Total credits, duration, and tool calls appear right beside the finished work.
Rollover, plus top-ups
Unused paid-plan credits roll over one month; purchased top-up packs do not expire. Running hot? Sliding your volume up is usually the better deal.
What is Bob, exactly?
An AI employee that lives in Slack, with Microsoft Teams in early access. He has his own sandboxed computer in the cloud, uses your connected tools, and browses the web to finish real work, then reports back in the channel with the result and a receipt. Not a chatbot; a coworker with paperwork.
Will Bob touch my CRM without asking?
No. External writes pause for an Approve/Deny button by default. You decide, per tool and per action, what's automatic and what needs a human tap, and the decision stays visible in the Slack thread.
Can Bob do things on a schedule?
Yes, just tell him. "Post the pipeline summary every weekday at 7:30" is enough; no cron syntax, no dashboard. He confirms the schedule in plain English with the next run time, and pausing, resuming, or cancelling it is just as conversational. Any completed task also gets a "Make this recurring" button if you'd rather not type it out.
Will scheduled tasks spam my channel?
No. A check-in that finds nothing worth saying posts nothing, with no "no updates" noise. The receipt still exists: ask what ran this week and Bob reports every firing, what it found or why it stayed quiet, and what each one cost. You can set quiet hours per schedule, and if a schedule fails repeatedly, Bob pauses it and tells you why instead of continuing to run a broken task.
Can Bob react to things outside Slack?
Yes. Ask Bob for a webhook and he hands you a URL. Point any system at it and Bob acts when it fires: "when a ticket closes, tell the channel." Same rule as scheduled runs: he only posts when the event is actually worth mentioning.
Does Bob learn our preferences?
Yes, and over time, two ways. Workspace memory holds the definitions, decisions, and conventions your team has already agreed on, so every run starts with the context that doesn't need re-explaining. Per-user memory holds each person's individual working style: how YOU like summaries, what shortcuts YOU take, which threads YOU want skimmed, so the next run by the same person picks up where the last one left off. Both are inspectable and editable; neither is used to train anyone else's model.
Do my credits expire?
Paid-plan credits roll over for one month, then expire. Trial credits expire after 14 days. Purchased top-up packs do not expire.
How do I know what a task cost me?
Every completed run ends with a compact receipt showing total credits, duration, and tool-call count. It posts with the work, so the cost is visible at the moment you get the result, not four weeks later on an invoice.
Can Enterprise use our own model key?
Enterprise customers can connect their own model API key, so the token bill goes straight to their model provider at their negotiated rate; we charge for the desk, not the brain. Enterprise pricing is custom and can also include deployment inside your own VPC. Email [email protected].
What if Bob makes a mistake?
If Bob gets a run wrong, you can rerun that task once without being charged for the redo. Each original run can receive one no-charge rerun, up to 10 per workspace in any rolling 30-day period. Risky writes still wait on approval, and the receipt shows what the original run cost.
Can I run Bob in my own cloud?
Yes. The Enterprise tier ships as containers for your own VPC, with offline license verification that degrades gracefully: an expired license stops new runs, it never bricks your deployment.
$100 in credits, free for 14 days
Give Bob the job you keep putting off.
Add him to Slack, hand him real work, and get back the finished result and the receipt. You have $100 in credits and 14 days to decide if he belongs on the team.
No card · Installs in minutes · Remove anytime
- Finish real work inside Slack
- Approve sensitive writes in the thread
- See a receipt for every run
- Turn good work into a schedule
- Keep unused paid credits next month
Early-access bonus
Start paid and book 20 minutes with Matthew. We’ll add $300 in credits to your workspace.