- Form submit
- Fetch company site
- Claude scores fit
Auto-qualify inbound leads before a rep sees them
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
An hour before each discovery call, get a one-page brief on the account, the attendee and recent news, saved to Salesforce.
Account executives either walk into discovery calls cold or burn 20 minutes per meeting clicking through LinkedIn, the company blog and old CRM notes. With six or seven calls a day, prep is the first thing that gets skipped. The result is generic opening questions and missed signals like a recent funding round or a new executive hire.
Create a Make scenario on a 30-minute schedule with a Salesforce "Search Records" module for Events where Type = Discovery and StartDateTime falls in the next 60 minutes. Add a Make data store keyed on Event ID so each meeting is briefed only once.
For each Event, pull the related Account (industry, employee count, website), the last five Activities and any open Opportunity. Flatten them into one text block with a Text Aggregator module.
Call the Perplexity API (sonar model) through an HTTP module with the research prompt below. Keep the returned citations so the rep can check anything surprising before repeating it on the call.
Send the CRM block and the Perplexity answer to the Anthropic Claude module with the brief prompt. Cap the output at about 350 words; anything longer will not get read in the five minutes before a call.
Create a Salesforce Note linked to the Event and Account, then email the same text to the meeting owner with the account name and start time in the subject. Add an error handler route that posts the failed Event ID to Slack or email so nothing drops silently.
Research {{company_name}} ({{company_website}}) and {{attendee_name}}, {{attendee_title}}, ahead of a sales discovery call.
Find, from the last 12 months only:
1. Funding, acquisitions, layoffs or leadership changes.
2. New products, pricing changes or market expansion.
3. Open roles that hint at priorities (for example, several RevOps or data hires).
4. Anything {{attendee_name}} has published or said publicly about their work.
For each finding, give the date and the source URL. If you cannot find something, write "nothing found" rather than guessing.You are preparing an account executive for a 30-minute discovery call.
CRM history: {{crm_context}}
Web research with sources: {{research}}
What we sell: {{product_one_liner}}
Write a brief under 350 words with these headings:
- Company in two sentences
- What changed recently (cite sources inline)
- Who they are meeting (role, tenure, likely priorities)
- Our history with them (past calls, open deals, objections raised)
- Five discovery questions tied to the findings above
Do not invent numbers. Mark anything inferred rather than sourced with "(inferred)".Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
A CrewAI crew checks 50 competitor pages, changelogs and news sources every week and sends a short brief covering only what changed.
Score every new Greenhouse application against your role scorecard with Claude, so recruiters start each day with a ranked shortlist.