What was used in the field
The Metadot channel motion, and the judgment that came from matching partner lists by hand.
Partner GTM Engine
Which accounts does this partner actually share with me, who owns them, and where is the whitespace — once the spreadsheets disagree?
Built with
Confirmed in the repository that renders this page. Planned tools stay in the case study and are not shown as logos.
What is not built
Domain matching, partner overlap, conflict review, and scored whitespace. Documented. Not deployed.
Where it stands
Designed. The Metadot channel program is history from that job. It is not usage of this design.
One fictional match on the case study. No spreadsheet upload, domain search, or CRM sync. Metadot's channel program is historical context, not a result of this design.
Illustrative account match
Domain missing, review open
Fictional account and partner. No real book of business is on this page.
- Account
- Northline Freight (fictional).
- Partner sheet
- Partner A sent “Northline Freight Inc” with no website column.
- Internal book
- A similar name exists. The domain on our side is northline.example.
- Match
- Uncertain. Name similarity is not a domain match.
- Human review
- Needs review. Do not auto-assign the account and do not export it back to the partner as a shared win.
- Joint action
- Ask Partner A for the website. If the domain matches, mark it a conflict and decide ownership. If it does not, leave it unclaimed.
Metric to test: a partner sheet with a missing domain is either matched to a cited source or left in human review, and a conflict view names who to call.