Deal coverage board that pairs your pipeline with real calls

Build me a deal coverage board that my sales manager and reps open before every pipeline review. Each row is one open HubSpot deal lined up against the calls we have actually recorded in Fathom, so in one pass we can see which deals are genuinely being worked and which have quietly gone dark.

Deal data. Use HubSpot Search Deals to pull the open deals in the pipeline the app is configured to inspect, and Get Deal for each row's stage, amount, close date, owner and associations. Resolve the associated company with Get Company, since I need its name and domain for call matching, and the associated contacts with Batch Read Contacts, since I need their email addresses. Use List Owners to turn the deal owner id into a real person's name. Read the deal's stage-entered timestamp properties so the board knows when the deal last changed stage.

Call data. Use Fathom List Meetings to build each deal's real call history, matched to the deal by attendee email domain against the company domain and by company name. Each row shows how many calls have been recorded, the date of the most recent one, and who attended from the buyer side. Pull Get Summary for the most recent call only, so the row has real substance without hammering the API on page load.

Matching rules. Tolerate buyers who attend from personal email addresses such as gmail.com or outlook.com rather than dropping those matches. When an attendee's domain does not resolve, fall back to matching their name against the deal's associated contacts, or count the call when another attendee on the same call already matched the account. Mark those rows as a softer match so the reviewer knows the link is inferred rather than exact. Dropping a personal-address buyer would silently understate coverage on exactly the deals we most need to inspect.

Risk flags. Every row carries three flags. First, no recorded call in the last 21 days. Second, a close date inside 30 days with no recorded call since the deal last changed stage, which is the classic sign a deal moved forward on paper but not in conversation. Third, single threaded, meaning every recorded call on that deal had only one person from the buyer side. Sort the board by dollars at risk by default, computed from the amount on flagged deals, so the biggest exposed deals lead the review instead of getting skipped when the meeting runs long.

Settings stored in the app and editable from it: the staleness threshold, defaulting to 21 days; the large deal amount cutoff, used to escalate single threading and coverage gaps on the deals that matter most; and which pipeline is being inspected. Changing any of these re-evaluates the flags and the sort.

Every deal row has a Review this deal button that kicks off a background agent for that one deal. The agent reads the full transcripts of that deal's calls with Fathom Get Transcript, then writes a risk brief covering three things: what the buyer actually said they needed, with short quotes; the next step that was verbally agreed and by when; and which stakeholders are missing from the conversation, judged against who has actually appeared on calls. The finished brief lands back in the app next to that deal row, so it is still sitting there at the next review.

Two follow-on buttons act on a finished brief. One logs it onto the deal record with HubSpot Create Note, associated to the deal, so the thinking survives in the CRM rather than in someone's head. The other shares it to the revenue channel with Slack Send a Message for the deal owner to pick up, including the deal name, amount, close date, owner and the brief itself.

Two constraints to respect. Fathom allows 60 requests per minute, so fetch meeting detail per deal on demand rather than transcript-fetching the whole pipeline on page load, and cache what has already been fetched within the session. The Fathom API key is also user scoped, reaching only meetings the key owner recorded or that were shared to their team, so put an honest line on the board saying it covers the recorded calls the connected account can see. A deal with no matched calls must read as no recorded calls visible, never as proof that nobody spoke to the customer.

Framing. This board exists to answer the two questions a good pipeline review actually turns on: who else at the account have we spoken to, and what did the buyer do last. Standard inspection practice holds that a deal with no logged next step is stalling, that 21 or more days without buyer-initiated activity counts as stale, and that any deal above your average deal size sitting on a single contact needs a named second stakeholder reached this week. Keep the on-screen copy in that plain register, written for a sales manager running a meeting rather than for an analyst reading a report.