prospect-deep-dive

star 2

Build a comprehensive multi-dimensional prospect deep-dive on a target company plus key contact — industry, product, ICP, business model, positioning, history, funding, investors, marketing, growth, competitors, stakeholders, LinkedIn, and AEO/GEO answer-engine visibility — into one Notion page with sales-ready Virio outreach angles. Use this skill whenever the user says "do a deep dive on [company]", "comprehensive analysis of [company]", "research [company] for me", "tell me everything about [company]", "build a profile on [company]", "account research on [company]", "full prospect workup on [name/domain]", or pastes a company URL plus a contact name/email and asks for analysis spanning more than one dimension. Trigger proactively when the request is broad and synthesis-oriented. For narrower asks use linkedin-content-analyzer (LinkedIn only), linkedin-competitor-benchmark (2+ competitors), or prospect-deck (post-discovery 2nd-call pitch deck).

miriamdong By miriamdong schedule Updated 5/7/2026

name: prospect-deep-dive description: Build a comprehensive multi-dimensional prospect deep-dive on a target company plus key contact — industry, product, ICP, business model, positioning, history, funding, investors, marketing, growth, competitors, stakeholders, LinkedIn, and AEO/GEO answer-engine visibility — into one Notion page with sales-ready Virio outreach angles. Use this skill whenever the user says "do a deep dive on [company]", "comprehensive analysis of [company]", "research [company] for me", "tell me everything about [company]", "build a profile on [company]", "account research on [company]", "full prospect workup on [name/domain]", or pastes a company URL plus a contact name/email and asks for analysis spanning more than one dimension. Trigger proactively when the request is broad and synthesis-oriented. For narrower asks use linkedin-content-analyzer (LinkedIn only), linkedin-competitor-benchmark (2+ competitors), or prospect-deck (post-discovery 2nd-call pitch deck).

Prospect Deep-Dive

What this skill does

Produces a single, comprehensive Notion page that gives Miriam everything she needs to walk into a sales conversation cold-prepped on a prospect. The page covers thirteen standard sections plus a TL;DR and recommended Virio outreach angles, drawn from web research, LinkedIn (company + personal profiles), CRM context, and any prior Virio notes.

The output is opinionated for a Virio sales context: every section ladders up to "is this a good fit for our content/ghostwriting service, and what's the strongest opening angle?"

When this skill is the right call (vs. neighbors)

  • Use this skill when the user wants the full picture across multiple dimensions — they're prepping for outbound, a first call, or evaluating a new account from scratch.
  • Use linkedin-content-analyzer when the user only wants LinkedIn content strategy on a single company.
  • Use linkedin-competitor-benchmark when the user is comparing 2–4 named companies side-by-side.
  • Use prospect-deck when the user has had a discovery call already and wants a personalized pitch deck for the 2nd call.
  • Use event-attendee-icp-scanner when the input is an event attendee list, not a single company.

When in doubt and the user has given you a company URL + a contact email/name, default to this skill.

Inputs to confirm

Before kicking off research, make sure you have:

  1. Company domain or URL (e.g., getwiq.ai, acme.com).
  2. Primary contact — name and/or email. Email lets you infer domain match; name lets you find them on LinkedIn.
  3. Use case (default: sales/outbound prep for Virio). Other valid contexts: competitive intel, partnership eval, investment eval. The framing of the TL;DR and outreach angles changes accordingly.
  4. Depth (default: deep dive). Light = top-line per section, no Virio angles; standard = all sections, brief; deep = all sections plus stakeholder LinkedIn audits and competitor positioning.

If any of these are missing or ambiguous, ask via AskUserQuestion before spending tokens on research. Underspecified runs waste effort and produce generic briefs.

Research workflow

Run as much as possible in parallel. The goal is to get to the Notion page quickly without producing a generic-looking output.

Phase 1 — Discovery (parallel)

Fire all of these in the same turn:

  • WebSearch — Three to five queries covering: (a) what the company does, (b) founders + funding history, (c) any recent press/launches in the past 12 months, (d) the contact's name + company for LinkedIn URL, (e) competitors in the named space, (f) "best [category] tools 2026" round-ups to test AEO presence.
  • Notion search — Look for any prior Virio notes on the company, contact, or domain. Pick up where past research left off rather than redoing it.
  • HubSpot search — Check if the company or contact already exists as a CRM record. If yes, pull deal stage, last activity, owner, and any notes — this dramatically changes the outreach angle.
  • Chrome MCP — Navigate to the company's about/team page and the contact's LinkedIn profile to get current state. While there, check [domain]/llms.txt, run a JS snippet to count JSON-LD blocks and <h1>/<h2> tags, and pull meta tags — these AEO/GEO signals only take one extra page load.

Phase 2 — Targeted follow-ups

Based on Phase 1 findings, fire follow-up searches for whatever is thin or surprising:

  • If the company is a rebrand/spinout, dig into the parent entity history.
  • If a Series A/B is recent, find lead investor + amount.
  • If the contact is the founder, get their personal LinkedIn follower count, posting cadence, and most recent post topic. The asymmetry between founder following vs. company page following is one of the strongest Virio outreach hooks — always capture both numbers.
  • If multiple co-founders, briefly profile the others (different products / different roles / now-departed all change the picture).
  • If SimilarWeb or other traffic data is connected, pull rough domain traffic to gauge marketing scale.

Phase 3 — Stakeholder map

For the named contact and 2–4 other key stakeholders (CEO if not the named contact, co-founders, head of GTM/marketing, board members from lead investor):

  • Role + tenure
  • LinkedIn signal: follower count, recent post recency, posting cadence if visible
  • Virio relevance: who's the likely economic buyer? Who's a content target? Who's noise?

Output format — Notion page

Create the page at the workspace level (parent omitted) so it lands in Miriam's private workspace. Use this exact section structure — the user has confirmed it as the canonical brief format:

  1. TL;DR — Why this is a strong (or weak) Virio prospect

    • 2–3 paragraphs synthesizing the headline finding and the strongest single angle. This is the only section the user may read in full before a call, so make it earn its place.
  2. Industry & Product

    • Industry framing in 1 line, then a structured product description (job-to-be-done, core loop, key features). Quote positioning lines verbatim where they're crisp.
  3. ICP Definition

    • Who they sell to: company size, industries, named functions/teams, regulatory or technical signals. Cite the source (their bio, their About page, their case studies) so it's verifiable.
  4. Business Model

    • SaaS tier, pricing posture (public vs gated), distribution channel, sales motion, partner stance. If they integrate with vs. compete with adjacent platforms, call that out.
  5. Positioning

    • Their category claim, core narrative (quote it), 4–6 differentiators, and a brief read on the strategic whitespace they could own.
  6. Company History

    • Year-by-year table of milestones: founding, key hires/departures, funding rounds, product launches, rebrands, pivots. Note anything unusual (parent entity, spinout-in-place, leadership transitions).
  7. Funding & Investors

    • Total raised, round-by-round breakdown, full investor roster (split institutional vs. angels), board members, and a 1–2 sentence read on what the funding pattern signals (e.g., bridge round vs. real B, runway, likely next raise window).
  8. Marketing Presence

    • Web/site (CTA structure, pricing posture, content depth), social channels with follower counts, founder-led content quality and cadence, press coverage, owned content (blog, podcast, newsletter), and the gap a Virio-shaped service would fill.
  9. Growth Signals

    • Headcount + hiring, recent launches, ecosystem partnerships, founder content velocity, anything that points to "this is a moment when they invest in content."
  10. Competitors

    • Group into direct, adjacent-incumbent, and adjacent-but-partner. Don't just list — say what whitespace the prospect could own that competitors don't.
  11. Main Stakeholders (table)

    • Person | Role | LinkedIn signal | Virio relevance. 4–6 rows. The named contact is always row 1.
  12. LinkedIn Presence Snapshot

    • Personal profile of the named contact (follower count, post recency, cadence, headline read, mutual connections with Miriam). Company page (followers, last post, engagement, cadence). Surface the asymmetry between founder following and company page following as a numbered ratio — this is one of the strongest single hooks for Virio outbound and it should be impossible to miss.
  13. AEO / GEO Presence (AI Answer Engine Visibility)

    • Whether the company shows up in AI-generated answers (ChatGPT, Claude, Perplexity, Google AI Overviews) for category-defining queries. Capture both technical and citation signals.

    Technical signals to check on their domain:

    • llms.txt and llms-full.txt (visit https://[domain]/llms.txt — 404 vs. present)
    • JSON-LD structured data (run document.querySelectorAll('script[type="application/ld+json"]').length in Chrome MCP — zero is bad)
    • Canonical URL set
    • Semantic HTML — count <h1> and <h2> tags. Sites built in Webflow / no-code tools often have zero, which destroys AI extraction
    • Meta description, Open Graph, Twitter card
    • Robots.txt directives for AI crawlers (GPTBot, ClaudeBot, PerplexityBot)

    Third-party citation surface:

    • Wikipedia / Golden / Crunchbase / MIT AI Agent Index entries
    • G2, Capterra, TrustRadius, Gartner Peer Insights pages — and whether they're active or stale
    • Chrome Web Store / app store listings
    • Inclusion in "best of" / "top X tools" round-ups for their category — search 2–3 category-relevant queries and see if they appear
    • Reddit / Hacker News / Indie Hackers discussion
    • Press coverage (TechCrunch, VentureBeat, etc.)

    Synthesize the read:

    • Will an AI answer engine recommend them today, yes or no? Why?
    • If they're a rebrand, does their old brand have AEO equity that the new brand is losing?
    • What 30-day quick wins (llms.txt, schema markup, semantic HTML, round-up pitches) would dramatically improve discoverability?

    For category-creation plays this is often the sharpest single angle: a company whose entire pitch is about being the smart layer for AI but who is themselves invisible to AI search has a deeply pitchable irony. Always look for that ironic mismatch — it can become the headline outreach hook.

  14. Recommended Virio Outreach Angles

    • 4–6 specific opening angles, each one tied to evidence from the research above. Avoid generic stuff like "thought leadership matters" — every angle should reference a specific signal (their funding stage, the founder/company-page asymmetry, a recent post, an ICP overlap with Virio's portfolio, or the AEO/GEO mismatch). The strongest single hook is often whichever finding is most ironic given the prospect's positioning.
  15. Sources

    • Bullet list of every URL referenced, as markdown hyperlinks. Always include LinkedIn (personal + company), homepage, About page, Crunchbase or PitchBook if pulled, and any press releases that grounded specific claims.

Style and tone of the brief

  • Write the way you'd brief a smart colleague before they walk into a meeting in 15 minutes. Punchy, evidence-backed, no filler.
  • Use specific numbers wherever possible (followers, $ raised, headcount, post date). Vague qualitative claims like "active on LinkedIn" are useless — write "11,727 followers, posted 1 week ago, 3-week average cadence" instead.
  • Quote the prospect's own positioning when it's crisp. Don't paraphrase what they say better than they do — let their voice through, then add your read.
  • The TL;DR earns the right to be the only section read. Spend time on it.
  • Sales-ready does NOT mean salesy. The brief should help Miriam pattern-match quickly, not pump up the prospect.

Edge cases

  • Company is a rebrand or has a parent entity: Capture the legal entity vs. brand structure explicitly. Note who's CEO of which entity. This is common in 2024+ AI rebrands and gets confusing fast.
  • Contact is not the founder: The "founder vs. company page" asymmetry hook may not apply. Lean instead on their team/role-specific content gap.
  • Company is stealth or pre-launch: Flag immediately and ask the user how to proceed — depth-3 deep dives on a stealth company are mostly wasted effort. Suggest a lightweight pass instead.
  • No LinkedIn presence at all: This is itself a finding — call it out as either (a) opportunity (they need help) or (b) red flag (founder isn't bought into content; Virio sale will be hard).
  • CRM record already exists with recent activity: Include the deal stage and last touchpoint in the TL;DR so Miriam doesn't accidentally re-cold-outreach a warm contact. This is a real risk and the skill should guard against it.

Process notes for the agent running this skill

  • Use TaskCreate to track progress through Phase 1 / Phase 2 / Phase 3 / Notion page. Long-running research drifts without a tasklist.
  • Don't ToolSearch one tool at a time — load the LinkedIn / Notion / HubSpot / WebSearch tool group in a single bulk call, then research in parallel.
  • The Notion page should be created at the workspace level (no parent) — team-space IDs return 404 as direct page parents.
  • Always end the chat response with a one-paragraph standout finding (the single most important thing) plus the Notion page link. Don't summarize the full brief in chat — the brief is on the Notion page; chat is for the executive read.
  • Cite Sources in chat using the markdown link format the WebSearch tool requires.
Install via CLI
npx skills add https://github.com/miriamdong/mstack --skill prospect-deep-dive
Repository Details
star Stars 2
call_split Forks 1
navigation Branch main
article Path SKILL.md
More from Creator