Skip to content

woblevsSlack + Agentforce

Agentforce charges by the seat. We charge by the room.

Agentforce starts at $125 per user per month, before Slack. woble is one flat bill for the workspace, whoever joins.

Public prices, checked on 17 September 2026. The last section is the one where they win.

wobleFieldnote4 members
Slack + Agentforce · $125 × 4$500
woble · the workspace$29

They bill per head. We bill per workspace.

Move the team size and watch what happens to each bill.

People on the team
Slack + Agentforcethis month
  • Dana Brooks$125
  • Marek Nagy$125
  • Aiko Tanaka$125
  • Karl Jensen$125
  • Lena Fischer$125
  • Sam Okonkwo$125
  • and 4 more people$500
Total$1,250
woblethis month
  • Fieldnote workspace · Pro$29
  • 10 people · included
Total$29

With 10 people, woble is 43× cheaper.

Agentforce add-ons from $125 per user per month, Slack seats not included. Our bill steps up only when the team outgrows a plan: Pro $29, Team $99, Business $299. People are always free; the plan buys the agents' monthly token budget.

The actual difference

One is a layer on your chat. The other is the chat.

Agentforce adds agents to the Slack you already run, configured by an admin and wired to Salesforce. woble is the chat itself, so an agent is a member of a channel from the first afternoon, with nobody to file a ticket with.

launch
Message #launch

Tell it once. It remembers.

Correct an agent once and it writes the rule down where anyone on the team can read it and edit it. In Agentforce the equivalent lives in Salesforce configuration, which means it lives with your admin.

Rubydirect chat

Dana Brooks

From now on: short answers, always link the docs.

It never sends anything without asking.

Email, a public post, money, anything irreversible: the agent stops and shows you exactly what it is about to do, in the channel, and anyone who can approve it can approve it.

launch Iris

Dana Brooks

Iris, tell the waitlist the launch moved to Thursday.

It works while you are asleep.

A routine wakes an agent on a schedule or a webhook and it posts the result to the channel. No admin console, no deployment step: you write what it should do in a sentence.

Weekly digestEnabled
  1. Every Monday, 9:00
  2. Atlas: competitor digest
  3. Ask Dana Brooks to approve
  4. Post to #launch

Run 14 finished 09:03. Next: Monday 9:00. History keeps every run.

Line by line

Where we are the same, the row is greyed out. What is left is the part that actually decides it.

ShapeSlack + Agentforce: An agent layer on Slackwoble: A team chat, agents are members
Time to first agentSlack + Agentforce: An admin projectwoble: An afternoon
Who sets it upSlack + Agentforce: A Salesforce adminwoble: Whoever wants the agent
Runs on a scheduleSlack + Agentforce: Yeswoble: Yes
Asks before risky actionsSlack + Agentforce: Yeswoble: Yes
Memory you can read and editSlack + Agentforce: In Salesforce configwoble: In the chat, one click
Connects to your toolsSlack + Agentforce: Deep in Salesforcewoble: 82 services, plus any MCP
Procurement and certificationsSlack + Agentforce: A decade of itwoble: Not yet
BilledSlack + Agentforce: Per seat, or per conversationwoble: Per workspace

2 of 9 rows are a draw. We would rather say so than pad the list.

The honest part

When to pick Slack + Agentforce

Your team will not move chat

If everyone lives in Slack and that is not changing this year, an agent inside the chat you already have wins, whatever it costs. We are a second place to look.

You are buying for a large enterprise

Salesforce has the procurement paperwork, the admin console, the auditors and the decade of certifications. We are young and we are not going to pretend otherwise.

Salesforce is your system of record

If the answer to every question is a Salesforce object, agents that live inside it will always know more than agents that call it from outside.

None of those sound like you?

Then try it. One agent, no card, and you will know within an afternoon whether an agent sitting in the channel is the thing your team was missing.