client-discovery

You can generate a discovery call script by feeding a prospect's website URL and meeting history into the skill, which synthesizes intelligence from sources like LinkedIn to produce tailored questioning frameworks. It automates pre-call research aggregation to build a comprehensive briefing.

The best way to prepare qualification frameworks is to map prospect intelligence directly to GTM primitives like positioning, ICP, and competitive landscape. This approach ensures your discovery questions are structured around high-impact qualification cues rather than generic prompts.

Yes, you need integration with research MCPs like Exa, Firecrawl, and Apollo. These dependencies are required to fetch real-time data from company websites and LinkedIn, ensuring the output is data-backed and completely non-hallucinated.

Yes, you can build pre-call briefings by aggregating data from company websites, LinkedIn profiles, and prior meeting history. The skill compiles this multi-source data to create a comprehensive intelligence briefing before your high-stakes discovery call.

Automated prospect intelligence prevents hallucinations by requiring integration with research MCPs like Firecrawl and Apollo to fetch live data. It synthesizes actual website content and recent funding news into the discovery script instead of relying on generated assumptions.

The main limitation is the strict dependency on external research MCPs; without integrations like Apollo or Exa, the skill cannot ensure data-backed output. Additionally, the quality of the generated agenda depends entirely on the availability of recent prospect data and website content.