After-Hours Global Prospecting and Outreach

Purpose

Use this skill when the user wants productive outbound work to continue outside their local working day by targeting prospects in other time zones that are currently in business hours.

This skill should:

• identify the current user's company, offer, ICP, and selling context from saved knowledge and connected systems
• find ICP-matched companies in geographies outside the current user's local timezone
• prioritize companies where the local time is likely within normal business hours
• find verified decision-makers or likely champions at those companies
• write concise, human outbound emails that optimize for replies, not premature meeting asks
• send or draft the outreach when the user asks for execution

Owner-Aware Behavior

This skill must be reusable across different users and companies.

• Never hardcode one company's ICP, positioning, CRM, or tech stack as a permanent default.
• Start with the current user's saved knowledge, company profile, and other durable context to infer the right ICP.
• If the current user has rich saved context, use that as the primary source of truth.
• If the current user has limited saved context, inspect connected systems such as CRM, LinkedIn, and available data sources to infer likely segment, buyer roles, target-account patterns, and market focus.
• If a clear ICP still cannot be inferred, ask the smallest possible question before running a large search.

For Moe / Expertise AI

When the current user context indicates Expertise AI, bias toward Expertise AI's actual ICP and positioning already available in saved knowledge and company context.

That means the skill should naturally favor patterns such as:

• HubSpot-first B2B companies
• B2B SaaS, tech, fintech, and professional-services teams with meaningful inbound traffic
• buyers in sales, marketing, RevOps, growth, or revenue leadership depending on the segment
• problems tied to weak website conversion, low-quality chatbot outcomes, missed after-hours demand, or poor website-to-pipeline performance

Use this only when the current user's own context supports it. Do not force Expertise AI assumptions onto other users.

System-Agnostic Requirement

This skill must stay connector-agnostic and stack-agnostic.

• It should work whether the user relies on HubSpot, Salesforce, Salesloft, LinkedIn, email, spreadsheets, or only saved knowledge plus enrichment.
• Use whichever connected CRM, LinkedIn account, and signal sources are actually available for the current user.
• If multiple systems are connected, use them together when that improves targeting or personalization.
• If a specific system is not connected, do not fail just because that stack is absent. Fall back to the best available combination of saved knowledge, enrichment, and connected tools.
• Do not assume one fixed CRM or one fixed outbound system.

Default Assumptions

Unless the user says otherwise:

• treat the user's own timezone as the exclusion anchor
• exclude prospects in the same country as the user only if the user frames the task as truly international; otherwise exclude only same-timezone targets
• prioritize English-speaking or English-friendly business markets first when language preference is unknown
• prefer decision-makers or strong functional owners most likely to care about the user's offer
• optimize the first touch for a reply rather than a calendar ask
• keep email copy direct, specific, and short

Workflow

1. Resolve the current user's ICP.

• Start with saved me and company knowledge.
• Then use connected CRM, LinkedIn, and other available systems for additional evidence.
• If enough context exists, proceed immediately.
• If not, ask the smallest possible question needed to identify target company type, buyer role, and geography constraints.

2. Translate the ICP into search filters.

• Use structured company filters first: industry, keyword tags, geography, headcount, revenue, funding, hiring signals, technology stack, CRM usage, and other relevant signals.
• Avoid stuffing a long ICP into keyword search.
• When the user wants "perfect ICP," bias toward narrower filters and quality over volume.

3. Enforce timezone logic.

• Build a country or region set outside the user's timezone.
• Prefer countries where the local time is currently within a normal workday, roughly 8:00 AM to 6:00 PM local time.
• If the user's goal is overnight coverage, favor markets that are active while the user is offline.
• If needed, explicitly rank candidates into: in-hours now, near start of day, and deprioritized due to local time.

4. Find companies first.

• Start with company discovery.
• Present verified companies directly.
• If the search returns fewer strong results than needed, broaden geography before weakening ICP quality too much.
• Where possible, avoid accounts already active in the user's CRM unless the user wants expansion or re-engagement.

5. Find the right people second.

• Search for likely buyers, champions, or owners at those companies using role and seniority filters.
• Enrich candidates before presenting them as usable contacts.
• Exclude unresolved or unverified people from final outreach-ready lists.
• If CRM or LinkedIn context suggests better entry points, use that signal.

6. Write outreach with judgment.

• Keep the first email concise and commercially relevant.
• Lead with a credible reason for reaching out tied to company fit, likely pain, or visible trigger.
• Avoid generic filler, hype, or "checking in" language.
• Default to one clear idea per email.
• Prefer a soft CTA that invites a response.
• Tailor the angle to the current user's offer and buyer context rather than one fixed playbook.

7. Execute based on user intent.

• If the user asked to build a list, return the best prospects with contact details that were actually returned.
• If the user asked for drafts, prepare send-ready emails.
• If the user asked to send, send the emails one recipient at a time using the connected sending channel that fits the current user.

Email Writing Rules

Good first-touch email qualities:

• short enough to read on a phone
• tailored to likely business context
• clear why this person
• clear why now
• one easy reply path

Default structure:

• short opener tied to fit or trigger
• one sentence on the problem or missed opportunity
• one sentence on relevant outcome or angle
• simple reply-oriented close

Good vs Bad

Bad:

• broad blasts with weak ICP fit
• contacting people whose details were not verified
• sending to prospects in the same working window when the task is specifically after-hours global coverage
• generic copy like "wanted to reach out" or "would love to connect"
• asking for a meeting too early without context
• presenting availability signals as if they were actual email addresses
• assuming every user sells the same thing or uses the same CRM

Good:

• narrow ICP filters, then widen only if needed
• verified contacts only for outreach-ready output
• region selection based on time-zone advantage and current local work hours
• concise outreach tied to likely relevance
• reply-first CTA such as interest, ownership, or priority check
• owner-aware positioning based on the current user's business and systems

Output Expectations

For list-building requests, return:

• company name
• domain
• country or region
• reason it fits the ICP
• contact name
• title
• verified work email only if actually returned
• local-time relevance note when useful

For outreach requests, return:

• recipient
• subject line
• email body
• why this angle was chosen

For larger runs, summarize:

• how many companies were searched
• how many verified companies were found
• how many usable contacts were found
• which regions were prioritized and why
• any shortfall or data gaps
• which available systems informed targeting, if relevant

Safety Boundaries

• Never guess email addresses, phone numbers, LinkedIn URLs, CRM state, or technology usage.
• Use only returned verified contact details for outreach-ready output.
• If the ICP is under-specified, ask before doing a large search.
• If the user asks for high volume, maintain quality guardrails rather than pretending weak matches are ideal.
• Keep claims in outreach grounded in known context. Do not invent personalization.
• Stay stack-agnostic. Adapt to the current user's systems instead of requiring one fixed toolset.

Example Triggers

• "Find fintech prospects I can work while North America sleeps"
• "Build me an after-hours outbound list in EMEA"
• "Prospect ideal customers outside my timezone and draft emails"
• "Who should I email tonight in Europe or APAC?"
• "Run global follow-the-sun prospecting for my ICP"

Decision Standard

This skill should behave like a disciplined outbound operator, not a list hoarder. Precision first, timezone leverage second, volume third.