Skip to content

woblevsGrok Bot

Grok gets it. Your finance team won't.

Grok Bot bills every person who uses it. woble bills the workspace once, however many of you there are.

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

wobleFieldnote4 members
Grok Bot · $100 × 4$400
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
Grok Botthis month
  • Dana Brooks$100
  • Marek Nagy$100
  • Aiko Tanaka$100
  • Karl Jensen$100
  • Lena Fischer$100
  • Sam Okonkwo$100
  • and 4 more people$400
Total$1,000
woblethis month
  • Fieldnote workspace · Pro$29
  • 10 people · included
Total$29

With 10 people, woble is 34× cheaper.

Grok Bot at SuperGrok Plus, $100 per person per month. 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

Their bot works for you. Ours works in front of everyone.

Grok Bot is a desktop app where each bot has its own chat with you. woble is the team chat itself: the agent answers in the channel, so the person who asked, the person who needs it next and the person who will be on call at the weekend all see the same thing.

launch
Message #launch

Tell it once. It remembers.

Correct an agent once and it writes the rule down where you can read it and edit it. Grok Bot keeps the context of a task; there is no separate memory you can open and change.

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. Grok Bot asks too, in its own window. Ours asks in the channel, so a colleague can approve it when you are away.

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. Both of us can do this. The difference is where the result lands.

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.

Where it livesGrok Bot: A desktop app you downloadwoble: A browser tab
ShapeGrok Bot: Your own bots, one chat eachwoble: A team chat, agents are members
Who sees the workGrok Bot: You, in your copywoble: Everyone in the channel
Runs on a scheduleGrok Bot: Yeswoble: Yes
Asks before risky actionsGrok Bot: Yeswoble: Yes
Agents hand work overGrok Bot: Yeswoble: Yes
Memory you can read and editGrok Bot: Nowoble: Yes
Connects to your toolsGrok Bot: Apps, plugins, MCPwoble: 82 services, plus any MCP
Drives a browser and terminalGrok Bot: Yeswoble: No
BilledGrok Bot: Per personwoble: Per workspace

4 of 10 rows are a draw. We would rather say so than pad the list.

The honest part

When to pick Grok Bot

The work needs a machine, not an API

Grok Bot gives each bot a browser, a terminal and a file system. Our agents call tools. If the job is clicking through a portal that has no API, they are the right tool and we are not.

You want one operator, not a team room

If the work is solitary and long-running, a chat channel is scaffolding you do not need. Brief a bot, come back later, done.

You already pay for SuperGrok

If someone on your team is on SuperGrok Heavy anyway, Grok Bot costs nothing extra for that person. We would be a second bill.

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.