# Uber driver uses Grok Bot to generate a daily one-page drive plan and take/avoid rules from historical offer data

Grok · X (Twitter) · Amount undisclosed (time-saving case, not a revenue case; author reports about one day to set up and about 30 seconds of daily use)

## Business summary

Independent Uber driver Levi Spires has a custom Driver Grok Bot that, before he wakes, builds a one-page drive plan from his own 12,291 Uber offers, heat maps, GigU acceptance floors, that day’s flights, road work, and local events. It converts this into take/avoid rules and staging locations. Setup took about a day; daily use about 30 seconds. Readers can reuse the pattern of feeding personal ops data to an Agent for daily executable rules.

## Business value

Independent Uber driver Levi Spires has a custom Driver Grok Bot that, before he wakes, builds a one-page drive plan from his own 12,291 Uber offers, heat maps, GigU acceptance floors, that day’s flights, road work, and local events. It converts this into take/avoid rules and staging locations. Setup took about a day; daily use about 30 seconds. Readers can reuse the pattern of feeding personal ops data to an Agent for daily executable rules.

## Workflow

Import personal historical Uber offers data, heat maps, and GigU acceptance floors into Grok Bot context

Aggregate daily external signals (flights, road work, local events) and generate a one-page drive plan

Convert the plan into specific take/avoid rules and staging locations

## Preparation and limitations

Results and time claims are as reported by the original post author. Workflow details, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. No income claimed. Grok Bot subscription amount undisclosed; exact data access method and vibe-code details not shown. Some $/hour figures at the bottom of the first attached image were partly obscured and were not used.

## Starter prompt

````text
You are my Driver Ops Agent. Generate today’s one-page drive plan from the materials I provide:
- Historical offer data summary (at least date, zone, duration, earnings or offer count)
- My acceptance floor (e.g. minimum hourly or accept rate)
- Today’s external signals (flights, road work, events list; mark missing if none)

Task: 1) Summarize high- and low-value zones; 2) Give 3-5 take/avoid rules; 3) Suggest 2 staging locations.
Output format: Markdown one-pager with zone table, rules list, staging suggestions.
If data is missing or conflicting, list the gaps explicitly and give only conservative advice based on available info. Do not invent numbers.
Before suggesting any send, booking, or external action, list it and wait for my confirmation.
This is an untested AgentFlow reconstruction prompt.
````

## Costs and pitfalls

Results and time claims are as reported by the original post author. Workflow details, freePrompt, and trial I/O are AgentFlow reconstructions and were not live-tested here. No income claimed. Grok Bot subscription amount undisclosed; exact data access method and vibe-code details not shown. Some $/hour figures at the bottom of the first attached image were partly obscured and were not used.

## Source and attribution

Levi Spires (@LeviSpires)
https://x.com/LeviSpires/status/2118329151304106419
2026-11-05
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
