As of 13 August 2026, AI can only partly research a prospect before a demo.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the prospect's company website, professional profile and any relevant public news or filings, and copy the URLs into a working document.
   2. Open your CRM record and gather the prospect's role, previous contact notes, stated needs, existing products and the agreed purpose of the demo.
   3. Paste the public links, CRM notes and your product description into the prompt, removing unnecessary personal or sensitive information.
   4. Ask the chatbot to produce the briefing and keep confirmed facts, inferences and unknowns in separate sections.
   5. Open every source link in the briefing and compare the cited facts, dates and job details with the original pages, deleting anything unsupported or stale.
   6. Send the checked briefing to a colleague who understands the account, then revise the discovery questions and demo plan to remove assumptions they cannot support.
   7. Use the final questions in the demo to test the remaining unknowns rather than presenting inferred priorities as facts.

   Prompt

   Research this prospect and account before a sales demo. Use only the information I provide and publicly accessible sources that you can link to. Do not invent facts, job responsibilities, business priorities, recent events or buying intent. Separate confirmed facts from reasonable inferences and unknowns.
   
   Account: [COMPANY NAME]
   Company website: [URL]
   Prospect name and job title: [NAME AND TITLE]
   Prospect or company profile URL: [URL]
   Known CRM notes: [PASTE NOTES OR WRITE NONE]
   Our product and target customer: [DESCRIBE PRODUCT, CUSTOMER AND MAIN USE CASE]
   Demo objective: [WHAT YOU WANT TO ACHIEVE]
   
   Return a concise briefing with these sections:
   1. Confirmed account facts, with a source link for each important claim.
   2. Confirmed prospect facts relevant to the meeting.
   3. Likely business priorities, clearly labelled as inferences and linked to the evidence behind each one.
   4. Relevant recent developments, with the publication or page date and source link. If you cannot establish that something is current, say so.
   5. Possible problems our product may address, without claiming that the prospect has those problems.
   6. Three discovery questions that test the most important assumptions without sounding scripted.
   7. Likely stakeholders or departments to ask about, only where supported by the evidence.
   8. A short meeting plan that uses the confirmed facts, avoids unsupported personalisation and states what I still need to verify before the demo.
   
   End with a table containing: claim, source, confidence, and what I should verify with the prospect. Keep private or sensitive personal information out of the briefing unless I explicitly provide it and it is necessary for the meeting.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.