Use Claude Cowork, HubSpot, Clay, Slack, email, and call intelligence fields to turn recent closed-won deals into lookalike accounts and review-ready outbound sequences.
A weekly human-reviewed outbound system that finds lookalike accounts from new wins, enriches contacts, drafts sequences, and routes them to Slack for approval.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
7 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Closed-won deals contain the strongest outbound clues: real triggers, pains, objections, proof points, buyer roles, and account attributes. Most teams celebrate the win, update the CRM, and then fail to turn that learning into the next prospecting motion. This workflow operationalizes wins while keeping humans in the loop so automation creates better drafts, not unchecked spam.
Expected results
Lookalike accounts generated
10 per recent win
Ten accounts per win creates enough volume to be useful while keeping weekly human review realistic.
Contacts enriched
3-5 per account
This matches a practical multi-threading motion without overloading reps with low-fit contacts.
Time saved
6-12 hours per weekly run
The agent handles CRM review, enrichment setup, first-draft copy, and Slack routing while humans approve fit and messaging.
Quality control
Human-approved drafts only
The workflow intentionally stops before automatic sending so the team can protect brand, compliance, and account judgment.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
1-2 hours
1-2 hours
Set up: Start by giving Claude Cowork the reference material it will use on every run instead of letting it infer your market from one closed-won deal. Create four Markdown files or Google Docs named ICP, Personas, Messaging, and Product Facts, then include positive-fit traits, disqualifiers, buying committee roles, pain language, proof points, competitor context, security/compliance caveats, and claims to avoid.
Configuration: Open Claude Cowork, paste the prompt below, attach or reference the draft files, and ask it to turn them into a clean reusable skill pack with a short test section at the end.
Output: Save the final skill files in the shared folder Cowork can access and log the file URLs in Google Sheets.
Next action: QA check: ask Cowork to score three known good-fit accounts and three bad-fit accounts before you let it read live CRM data. Prompt handoff: open Claude Cowork, paste the prompt template below, attach or reference the inputs named in the prompt, and copy the output into Google Sheets before continuing.
Reusable ICP, persona, messaging, and product knowledge files with a QA test set for the outbound agent.
Do not build the agent first. Without reusable foundation skills, every downstream draft will drift toward generic outbound copy.
Open Claude Cowork and paste this prompt. Use the draft ICP, persona, messaging, and product notes as inputs, then save the cleaned skill files to {{skill_file_folder}} and log the final links in {{run_log_location}}.
Create a reusable foundation skill pack for a closed-won lookalike outbound agent.
Draft ICP notes:
{{icp_notes}}
Draft persona notes:
{{persona_notes}}
Draft messaging notes:
{{messaging_notes}}
Product facts and approved claims:
{{product_facts}}
Claims, audiences, or account types to avoid:
{{claims_and_accounts_to_avoid}}
Return:
1. ICP skill file
2. Persona skill file
3. Messaging skill file
4. Product facts skill file
5. Disqualifier checklist
6. Example good-fit account scores
7. Example bad-fit account scores
8. Questions that must be answered before the agent can run
Do not invent claims, customer names, metrics, or integrations. Mark unknowns clearly.60-90 min
60-90 min
Set up: Connect Claude Cowork to the smallest set of systems needed for this workflow: HubSpot for closed-won deal context, Clay for enrichment tables, Slack for approvals, and email for draft creation or export.
Guardrails: Restrict HubSpot access to deals, companies, contacts, associations, and the call-intelligence fields that describe pain, decision criteria, objections, and products purchased. In Clay, create a dedicated table for this workflow instead of letting the agent write into an active production outbound table.
Set up: Open Claude Cowork, paste the prompt below, and ask it to produce a permissions map, read/write boundaries, and a test procedure using one harmless closed-won deal. Save the permission map in Google Sheets and do not schedule the agent until the read/write test posts only a summary to Slack.
Output: Prompt handoff: open Claude Cowork, paste the prompt template below, attach or reference the inputs named in the prompt, and copy the output into Google Sheets before continuing.
A connected Cowork environment with documented permissions, test procedure, and safe read/write boundaries.
Pro workflow preview
Previewing 2 of 9 steps
Get the remaining 7 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Give the agent fewer permissions than you think it needs. You can always expand access later; cleaning up accidental CRM or email actions is harder.
Open Claude Cowork and paste this prompt. Use the system list and access policy below, then save the permission map to {{run_log_location}}.
Create the connection and permission plan for a closed-won lookalike outbound agent.
Systems to connect:
{{systems_to_connect}}
Required HubSpot objects and fields:
{{hubspot_objects_and_fields}}
Clay table name and allowed columns:
{{clay_table_spec}}
Slack review channel:
{{slack_review_channel}}
Email rules:
{{email_rules}}
Return:
1. Required connections
2. Read-only permissions
3. Write permissions
4. Actions the agent is not allowed to take
5. One-deal test procedure
6. Expected Slack test message
7. Rollback plan if the test writes to the wrong place
Do not create live outbound tasks or send emails.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A fast account brief with company context, likely initiatives, buyer roles, recent signals, and recommended first outreach angles.
A dynamic battlecard workflow with competitor snapshots, buyer objections, talk tracks, landmine questions, proof points, and review status.
A complete post-demo follow-up kit that helps reps move faster while keeping the buyer's priorities, objections, and next steps clear.