Bots Running the Work Week

A couple of weeks ago I started leaning hard on Grok Bot. This week a couple of those bots started carrying real weight in my ThreeWill work week — not by doing the work for me, but by keeping the busywork moving so I can spend my time on the parts that need me.

The pattern is the same for every bot: it drafts, I approve, and only then does anything get posted, filed or merged.

Willy, the roadmap bot

Willy maintains the codebase for ThreeWill's Operational Dashboard.

• Keeps the roadmap and backlog in sync with what the team decides, including a roadmap PDF with a requirement ID on every row and a "what changed" section, and waits for my review before anything goes to SharePoint
• Opens docs-only pull requests through a cloud agent so the repo's roadmap and backlog match what we published, with app code and store-frozen paths off limits; I review and merge
• Posts roadmap updates to the team, clearly labeled as Willy, only after I approve the wording
• Even trades notes with a teammate's own Grok Bot, which was a fun first

Rudy, the operations bot

Rudy handles the operational side of my week.

• Daily timesheets: every weekday morning Rudy drafts yesterday's time from my calendar, Cursor sessions, chats and work items, and builds a tentative plan for today; I adjust, and Rudy posts it after I OK it
• Retention scoring: we replaced a hand-run AI prompt with a transparent, documented formula for how likely each Managed Services client is to stay, and set up a monthly grooming routine that recommends changes, waits for my OK, writes them back, and updates a "clients at retention risk" scorecard measure
• A running to-do board with check-ins during the day, so nothing slips between meetings

Why it works

None of this is magic. It's small, repeatable routines with a human gate at the end. The bots are great at gathering evidence and drafting; I'm still the one who decides.