About 40 Hours a Week of a Construction President's Work: His Grok Bot Rules, From One Bot per Job to Draft-Only Email
- Level Beginner
- Setup~30 min (estimated)
- Evidence Anecdotal
- CostNot stated in source
- No-codeYes
What did they do with Grok Bot?
The president of a small commercial construction company says Grok Bot does about 40 hours a week of his work and is rolling it out to his directors. His chief-of-staff bot wrote down their rules: one bot per job (email, bidding, invoices, pay apps), routines for anything that repeats, drafts only and nothing paid or sent without OK, quick corrections saved to memory, an email voice learned from his sent mail, and repeat processes saved as skills.
How it went
X post by @Josh_C_Lyle (Nov 7, 2026 UTC): about 40 hours/week of work (self-estimated); rollout to 3 directors; rules list. The 40 hours is his own estimate; start with one or two bots before rolling out to staff
Worth knowing
- X post by @Josh_C_Lyle (Nov 7, 2026 UTC): about 40 hours/week of work (self-estimated); rollout to 3 directors; rules list.
- The 40 hours is his own estimate; start with one or two bots before rolling out to staff.
Prompt
Cleaned version rewritten from the source — not a direct quote.
Help me set up my bots like a team. Propose one bot per job for: [email, bidding, invoices, etc.], each with a one-paragraph job description. List which tasks should be routines. Every bot drafts and never sends, pays or deletes without my OK. Write the rules into each bot's instructions.
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (Email) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in Claude, ChatGPT Agent, OpenClaw.
Set it up
Tools: Email · Stack: Grok Bot
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
X post by @Josh_C_Lyle (Nov 7, 2026 UTC): about 40 hours/week of work (self-estimated); rollout to 3 directors; rules list. The 40 hours is his own estimate; start with one or two bots before rolling out to staff (as of 2026-11-07)
Source: X · 2026-11-07 · Verified by us: not yet · Report broken or outdated