Sales and Go-To-Market
Sales teams lose their best hours to preparation and admin — researching accounts, assembling context, updating records, writing the same email in slightly different words. This track recovers those hours without crossing the line that matters: customers can tell when they are talking to automation, and trust does not survive it. Claude prepares; the seller sells.
Workflow patterns
Account and call preparation
The pattern from the Foundation Lab, now at full strength. Combine approved account notes, public research, prior interactions, and opportunity context into a brief — with a source beside every material claim:
Prepare a call brief on Helios Manufacturing for tomorrow's renewal call.
Use only the attached notes, ticket summary, and their latest press page.
Include: current priorities with the evidence behind each, open risks,
stakeholder map, and three call objectives. Cite the source next to every
claim. List what we do not know under "Unknowns" — do not fill gaps.
The "Unknowns" section is where the value hides: it becomes the first three minutes of the call.
Pipeline and deal-risk review
With an approved CRM connection through MCP, Claude can sweep a pipeline and summarize what changed, which fields are missing, which deals have stalled, and which risks reps have recorded. Hold it to one discipline: recorded fact versus inference, always labeled. "No activity logged in 21 days" is a fact. "This deal is losing momentum" is an inference — useful, but the rep judges it. Any CRM write-back stays behind defined permissions and review.
Personalized outreach
Generic AI outreach is spam with better grammar. The workable pattern inverts it: start from a genuine account signal — a support milestone, a new integration, an expansion hire — and have Claude draft two or three thoughtful variants grounded in that signal and a relevant value proposition. The account owner checks the claim, the tone, the timing, and the permission to contact. Nothing sends itself.
Async deal review
Deal reviews consume meeting hours mostly on assembling context. Use an approved Slack workflow to collect a fixed packet per deal — objective, stage, evidence, blockers, next action, owner, deadline — and let Claude structure and summarize the thread. The team's time goes to the decision, which is the part that needed the team.
Track lab
Build one of these with your own materials:
- A source-grounded account brief
- A deal-risk summary from approved CRM fields
- An outreach workflow with a human send gate
- An async deal-review template
Test it on one typical case, one incomplete case, and one high-risk case. Score it against the answer key you brought in your workflow packet.
Guardrails
- Never invent account facts, relationships, or customer intent.
- Keep confidential customer and commercial data in approved systems.
- A person reviews before anything external is sent or any record changes.
- Measure preparation time and quality — not message volume. More outreach is not the goal; better conversations are.
Definition of done
The workflow produces a brief or summary a rep would actually bring to a call, shows its evidence, says what it does not know, and has a named commercial owner.