Claude Code briefs twenty consulting engagements

Dave Zille starts by asking Claude Code to draft communications for one consulting client. The working system grows into daily briefs for more than twenty engagements, using local Markdown rather than a new hosted CRM.

Two repositories retain the original material: one for Help Scout conversations and one for Basecamp posts. A third organises each client’s profile, current context, recent activity and billing history. Global indexes identify actionable threads and map source IDs to files, so the agent can open the underlying conversation when a short summary is insufficient.

Scheduled runs leave a fresh brief of outstanding tickets, replies waiting on Zille and overnight changes. The same skill produces a focused client update on demand. Source repositories synchronise independently; aggregation files reference them rather than duplicating every thread. This makes it possible to investigate why a ticket remains open without discarding its history.

Zille keeps internal and shareable views separate and reviews consequential edits, sends and publication. Credentials and sensitive contracts stay outside both views. The account demonstrates an operating consultancy workflow, without an independently measured time saving. Its flat-file approach also depends on one operator’s curation; the author explicitly says it would not provide the roles and shared audit controls needed for thousands of accounts.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Blog · Dave Zille