# Grok Bot measures token usage before a workflow change

@MikeysMolecules reports using bots to measure personal token usage, then keeping Notion for project state after finding substantial usage inside individual tool loops.

Agent: Grok Bot
Tools: Grok Bot, Notion
Category: Work & operations
Date: 2026-10-30

Outcome: The poster kept Notion and introduced a read-before-work, update-after-work project-row rule. No measured token reduction after this change is reported.

## Steps

1. The poster asked their bots to measure personal usage before moving project state to Grok Bot Pages.
2. They report about 35 to 42% in tool loops, including one 73-call run using 11.1M tokens, and about 23% in starting context above a fixed floor.
3. The poster estimated roughly 1 to 5% weekly savings from Pages with low confidence and chose to stay in Notion.
4. The poster added project fields and a blocked-first view, then required bots to read each project row before work and update it afterwards.

Human oversight: The poster interpreted the measurements, estimated potential savings, chose Notion and says they added the fields and master view themselves.

Source: [@MikeysMolecules](https://x.com/MikeysMolecules/status/2116261872047460586)

Canonical URL: https://agentsinuse.com/use-cases/grok-bot-measures-tool-loop-usage-notion-project-state/
