by Audra Carpenter

Draft the weekly recap email to a client

Have Grok Bot write the weekly recap email to a client, then clean it up, as the author says he does.

What the agent did

Source-reported example · as described by Derek Riggs (@DerekatQuango), co-owner and account manager at Quango, a two-person web-first creative studio (per his X profile and Quango's site)

The author, Derek Riggs, co-owner and account manager at the web and advertising studio Quango, posted on X that he has Grok Bot write his weekly recap emails to one of his clients. He says the emails used to take him 30 to 45 minutes each week.

He says Grok Bot "has all the info it needs" and that it tends to already do most of the tasks for this account, or is at least aware of everything that goes on with them. He now cleans up what his Grok Bot sends.

The post gives no setup, steps, example email or prompt, and does not say what the recaps contain, how Grok Bot gets its information, or whether the email goes to him or straight to the client.

He says this saves him about 2 hours a month: the weekly email went from 30 to 45 minutes to "closer to 7-8 minutes a week" (his own figures; he does not say how they were measured).

Limitations

Short post with no setup details, steps, example or prompt. The times are the author's own estimates. It covers one client's weekly recap only.

The post does not say what the recap contains, how Grok Bot knows what happened on the account, whether Grok Bot sends the email itself or hands it to him, or what "clean up" involves, so we cannot say whether a person approves every email before the client sees it.

The model is not stated. One reply to the post exists and was not readable.

Try it in your business

What you'll need

Grok Bot with enough access to, or notes about, the week's work for the client (the post does not say which); your usual recap format or an earlier recap to follow; your own read-through and clean-up of each draft before it goes to the client.

The post says Grok Bot already knows what is going on with the account, which suggests it can see the account's work, but it does not say how. The label is our reading, not something the author states.

Starting prompt

The author didn't publish their prompt (read the full note_tweet text; no prompt or instruction is quoted; the one reply was not retrievable), so this is our adaptation.

How ours differs from the original setup: Same execution agent (Grok Bot). The author published no prompt, so this is our starting prompt based on his one-paragraph description. Where Grok Bot gets the week's information is a blank you fill in, because the post does not say.

It adds 'check' marks for anything uncertain and an explicit no-send, review-first instruction, because the post does not say whether the author reviews every email before the client sees it.

Our suggested starting prompt — not the author's original · untested
Draft this week's recap email to [client name]. Cover what we did for them from [date] to [date], what is in progress and what we need from them next. Use [where the week's work is recorded: notes, a task list or a folder I give you] and my last recap, [paste or attach], as the format and tone to follow. Where you are unsure whether something happened, mark it 'check' instead of stating it. Do not send anything to the client; give me the draft to review and edit.

Replace the [bracketed] parts with your own files and tools.

Get examples like this every Tuesday and Friday

Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.

Unsubscribe any time. Privacy policy

Report a correction

Related use cases

Check local prospects' email security and draft personalized outreach for your approval

Have Grok Bot research local businesses' public email-security records and draft personalized first-touch emails for your approval, the work the author says his AI team did.

Grok Bot · Sales · Custom development · Source: Eddy Kawira, runs a one-person local tech services business in South Bend, Indiana (Eddy Services); infrastructure engineer and writer of the eddykawira.com blog (per the post, his About blurb and his services site) · October 11, 2026

Triage customer support tickets and prepare fixes or replies for your approval

Have Codex triage incoming customer support tickets and prepare a reply or a proposed fix that waits for your approval before anything goes out.

Codex · Customer service · Custom development · Source: Hacker News user mike_hearn (full name not stated in the source), describing his own part-time side business; his Hacker News profile lists Hydraulic, maker of Conveyor · September 30, 2026

Build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive

Have Grok Bot build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive, as the author says he did to replace his construction-management software.

Grok Bot · Operations · Connected apps · Source: Pawan (@puvsandhu), owner of several companies; X bio: "Real estate. Property development. Construction." (surname not stated publicly) · November 6, 2026