Skip to main content
You will end up with: a company table of closed-lost accounts with deal stage, amount, close date, owner, and loss reason on every row; a people table of decision makers at those accounts with the deal context beside each person; and, when you approve it, phone numbers. Before you start: HubSpot or Salesforce connected. Loading from the CRM and adding CRM columns are free. Finding new contacts and enriching phones cost credits.

​
Steps

1

Load the closed-lost deals

The companion loads the accounts behind those deals with the CRM IDs preserved, and the deal columns arrive automatically: Deal Stage, Deal Amount, Close Date, Deal Owner, deal name, and Loss Reason. A first load returns about a hundred; say “pull them all” for the full set.
2

Filter by what matters

Any deal property can be a filter, in your own words.
3

Decide who to call at each account

Two different asks. The people you already spoke with live in the CRM; new decision makers are net-new discovery.
4

Bring the deal context onto the people

Contacts built from a company table stay linked to their account, so the account columns can be copied down onto each person as “Account: Loss Reason”, “Account: Deal Amount”, and so on.
Now a rep sees why the deal was lost before dialing the person.
5

Approve phone enrichment, then export

The companion stops before spending credits on phones and states the row count.
Approve the card, then:

​
What happens behind the scenes

A deal-grain load resolves accounts through the deal or opportunity records and attaches the deal columns in the same pass, so there is no separate “loss reason” research step. Contacts found at those accounts are linked to their account row, which is what lets account columns be carried onto people. The companion refuses to auto-enrich phones; every paid step waits for your approval.

​
Prompts to try

​
Next

Build a look-alike list

Do the same starting from closed-won.

Winning skills

Save this as a monthly skill.