Get a demo
Personalize outboundSkill

Prospect One Account

Prep outreach for a single target company domain

Turns a company domain into a ready to review outbound package: CRM activity, public signals like hiring or funding, the 3 to 4 decision makers who own the buying decision with verified emails, and a personalized three email sequence per contact. Drafts only, nothing is sent.

Luca Prando
Luca Prando

GTM Ops at Clay

About this Skill

When to use it

Use this Skill when you need to prepare outreach for a specific company and want to know who to contact and what to say. It is ideal for situations where you need to prospect an account, build cold emails, or research a target company. This Skill is not suitable for bulk account processing or sending emails directly.

What it delivers

The Skill produces a package of drafts that includes an engagement summary, third-party signal analysis, and a list of 3-4 key decision-makers with verified emails. It unlocks the decision of who to contact and what to say, while respecting the boundaries of not sending emails or modifying CRM records.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

Prospect the account for acme.com and prepare outreach.

Other ways to ask

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • Company domain
    • The domain to prospect, e.g. acme.com
    • required — nothing runs without it.
  • Product context
    • Your product's name, a one-line value proposition, and 2–3 canonical use cases teams buy it for
    • required — the emails cannot be written without it.
  • Buyer functions
    • Which functions buy or own your product, e.g. Revenue, Sales, Marketing, RevOps
    • defaults to Revenue/Sales/Marketing/RevOps/Growth if missing.
  • Title keywords
    • The job-title keywords for people search, matched with 'contains'
    • defaults to a C-level → VP → Head of → Director ladder if missing.
  • Title exclusions
    • Title words that disqualify, e.g. junior, assistant, intern
    • defaults to the exclusion list if missing.
  • Seniority floor
    • The lowest seniority worth contacting
    • defaults to director if missing.
  • Regions
    • Which regions to search for people in
    • no filter is applied if missing.
  • CRM connection
    • Which CRM you run and the name of your connected account in Clay
    • the CRM half is skipped if missing.
  • CRM account fields
    • Which fields on your account object carry account fit, owner, and engagement summaries
    • those lines drop from the account context if missing.
  • Email providers
    • Which email finder/validator providers are connected in your workspace, and the waterfall order
    • defaults to Findymail → Prospeo → Wiza if missing.
  • Sender name
    • The name to sign the emails with
    • emails end with just the sign-off word if missing.
  • Spending cap
    • The most you want this run to spend, in credits or dollars
    • you are asked at the gate in Step 3.

Outputs

  • Contact ListA ranked list of 3-4 decision-makers at the target company, including their titles and reasons for selection.
  • Email DraftsThree personalized email drafts for each selected contact, tailored to their role and the company's current situation.
  • Engagement SummaryA concise summary of the account's recent engagement level and activities, providing context for outreach.
  • Third-Party Signal AnalysisAn analysis of public signals indicating the company's current needs, including hiring, funding, and leadership changes.

Representative output

ContactTitleWork emailProviderWhy pickedSubjectEmail 1Email 2Email 3
Avery NorthVP Revenue Operationsavery@northwind.exampleFindymailOwns the RevOps function; CRM shows a stalled 2025 oppScaling outbound after the raise(90–120 word intro draft)(80–110 word use-case draft)(under-40-word bump)
Jordan ColeDirector Sales Developmentjordan@northwind.exampleProspeoRuns the SDR team the hiring signals point toYour five new SDR openings(draft)(draft)(draft)

Plus an account context block: domain, the CRM account it matched (ID and owner), engagement level and summary, and the third-party signal analysis and tier.

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

1
Check the platform, and say where the work runs

Say the posture out loud before anything runs: this skill reads your CRM and public data, writes nothing anywhere, and its output is drafts in this conversation. Then check the platform to ensure you are signed in.

2
Collect the definition (interview; do not guess)

Collect the necessary definitions by asking for the domain, product context, CRM details, and any other required inputs, ensuring to note any defaults used.

3
Normalize the domain (free)

Normalize the domain by stripping protocol and 'www.', ensuring it is valid before proceeding.

4
Price the run and get one yes (spend-approval)

Fetch the live per-call price of each function this run will use and ask for the spending cap before proceeding. The run stops and waits for spend approval before continuing.

5
Enrich the company

Enrich the company by running the Clay action with the normalized domain and verifying the company name and LinkedIn URL.

6
Read the CRM (three lookups, read-only)

Read the CRM to gather recent activities, opportunities, and engagement summaries for the account.

7
Judge first-party engagement (no external lookups)

Judge first-party engagement based on the CRM data to produce an engagement summary and level.

8
Research third-party signals (budgeted web research)

Research third-party signals to identify any recent public indicators that suggest the company may need the product now.

9
Find the people

Find the people at the company using the LinkedIn URL and specified title keywords, ensuring to verify the results.

10
Pick the 3–4 people to prospect (no external lookups)

Pick the 3-4 people to prospect based on decision-making authority and engagement analysis.

11
Find and verify emails (waterfall)

Find and verify emails for each selected contact using the specified email providers in the defined order.

12
Write the emails (no external lookups)

Write the emails for each contact based on the account research, ensuring to follow the specified structure and tone.

13
Deliver the package

Deliver the package of drafts and account context in the conversation, summarizing the run and offering to save the answers.

Connections required

email finder/validator providersRequired connection

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 2From submitted SKILL.mdCurrent

Related Skills

Prepare Job ApplicationFinds open postings and matching recruiters for a list of target companies, then drafts a resume tailored to each job's own wording plus a short LinkedIn note to send. You get a reviewed draft folder per role, ready for you to check and send yourself.View Skill →Specificity RewriteWrites one short sentence per row that anchors a cold email to something a specific company actually sells, so the offer reads as written for them instead of a mass list. It leaves the row blank when no honest anchor exists, rather than guessing.View Skill →Value First Cold EmailThis Skill writes value first cold email drafts for a prospect list, with first lines built on verified signals like new roles, hiring, funding, or company news within a set time window. It also produces a matching four touch follow up sequence per persona and signal.View Skill →

Related searches

Personalize outbound skillsemail finder/validator providers skills