See which open deals are still reading your website

Build me a deal engagement board I open before every pipeline review. It answers the one question I always ask: which of my open HubSpot deals are actually still reading our website, and which ones have gone completely quiet.

Loading the data. When the app opens, pull my open deals from HubSpot with Search Deals, filtering out anything already closed won or closed lost, and use List Pipelines so I see readable stage names instead of stage IDs. For each deal, get its associated company with Search Companies so I have the company name and the company domain. Separately, resolve my Leadfeeder account with List Accounts, then fetch the last 90 days of identified companies in a single List Leads call, passing explicit start_date and end_date since Leadfeeder requires both. Cache that 90 day lead set for the session instead of refetching it per deal: Leadfeeder is rate limited and the lead list is the expensive call. Pull per deal visit detail on demand with List Visits For Lead when I expand or act on a row, and use Get Lead when you need the lead's full company and visit summary attributes.

Matching. Join on company domain. Normalize both sides before comparing: lowercase, strip the protocol, strip www, drop any path or trailing slash. A deal is matched when its company domain equals a Leadfeeder lead domain in the cached window.

The row. One row per deal showing deal name, company, stage, amount, close date, visits in the last 14 days, days since the last visit, and the last page viewed. Expanding a row loads the recent visit list for that account: date, page path, and time on site.

Two tabs split the board. Heating up holds matched deals whose visit count in the last 14 days is higher than the 14 days before that, and shows both counts plus the change so I can see how much it moved. Gone quiet holds matched deals with no site activity for 30 or more days. Both tabs sort by deal amount descending by default so the biggest risk sits at the top, and I can re-sort by days since last visit or close date.

Unmatched deals get their own group, visible rather than hidden, and the design has to make the reason obvious. These are deals whose company Leadfeeder has never identified in the window. Visitor identification typically resolves only 15 to 35 percent of business web traffic, so an unmatched deal usually means the visitor was never resolved, not that nobody visited. Say that in plain words in the group header or empty state, style the group as unknown rather than as bad news, and sort it by deal value like the others. If a deal has no associated company, or the company record has no domain, put it in this group with the reason shown on the row instead of silently dropping it.

Actions on every row. Create a HubSpot follow-up task with Create Task, associated to the deal, with the subject prefilled from the company and the signal and fields for due date and priority. Log the visit evidence onto the deal with Create Note, writing out the pages viewed, the visit counts for both 14 day windows, and the dates. Post the deal to a team channel with the Slack Bot Send a Message operation, with a channel picker and a prefilled summary I can edit before it sends.

Prep this deal. Every row has a button that starts a background agent. The agent reads the HubSpot deal record and its associated company, pulls the full visit history for the matched Leadfeeder lead with List Visits For Lead and Get Lead, and writes a short call prep brief covering three things: what pages they are researching, how broadly the company is engaging based on the spread of visits and sources, and what changed since the last touch. It files the brief onto the deal as a HubSpot note with Create Note, and the app shows the same brief inline on the row so I can read it without opening HubSpot. Show a clear running state per deal while the agent works, and keep the most recent brief with its timestamp so I can see whether it is stale.

Small things that matter. Put counts for each group and the date window currently in use in the header. Give me a refresh control that re-pulls both sides. Keep the whole board readable at a glance: this is something I scan for two minutes before a meeting, not a report I study.