MQL to buying group reporting in HubSpot and Salesforce: the definitions, fields and dashboards

Most reporting projects start in the CRM and end in an argument about what the numbers mean. Start with definitions instead, agreed in writing by marketing, sales and RevOps. Our article on buying groups vs MQLs explains why the unit changes; this one covers how to report it.

Keep the first version simple. You can add opportunity types and role weights later; you cannot report anything until the basic rules exist.

Buying group reports fail on data, not on dashboards. Before building anything, run three checks: share of contacts linked to a company or account, share of open opportunities with two or more contacts attached in a role, and duplicate company records among your target accounts. If any of these is weak, fix it first. Our CRM for ABM setup guide lists the fields to create in each system; the reporting below assumes they exist.

According to HubSpot's documentation, the Buying role contact property shows the part a contact plays in the sales process; contacts can hold multiple roles, default options include Decision Maker, Budget Holder and Blocker, and you can add your own roles. ABM features require Marketing Hub or Sales Hub at the Professional or Enterprise level, and HubSpot provides a library of ABM dashboards and reports on the Companies data source.

HubSpot also documents a buying groups feature on company records, an org chart of the people involved in a purchase, available with Sales Hub or Service Hub Professional or Enterprise and marked beta when we checked. It helps sellers see gaps; it does not replace reports.

• Company report: target or ICP accounts by tier with count of contacts in each buying role.
• Company report: accounts with three or more engaged roles in the last 30 days, using a calculated property or workflow-set field.
• Deal report: open deals by stage with the number of associated contacts and their roles.
• Funnel: accounts reached, accounts with an engaged role, qualified buying groups, deals created, deals won, all counted by company.

Salesforce Help describes contact roles as specifying "the part that a person plays in an account, case, contract, or opportunity." In Lightning Experience they are available on opportunities, contracts and cases, and Salesforce notes that creating an opportunity from a contact makes that contact primary but does not automatically assign a contact role. That detail is why so many opportunities have no roles at all.

Make contact roles a required step at a defined opportunity stage, keep the role picklist aligned with the buying roles you agreed, and add a custom field or formula on the account for engaged roles in the last 30 days, usually fed by your marketing automation or ABM platform.

• Opportunity report with contact roles: open opportunities by stage and number of roles.
• Account report: target accounts by tier with engaged roles and last engagement date.
• Exception report: opportunities past the qualifying stage with fewer than three contact roles.
• Funnel: the same account and opportunity stages as above, with win rate by number of roles.

Reports and scoring must agree, or sales will receive leads under one model and be measured under another. Forrester's analysts recommend scoring that recognizes when signals occur across a group, so that several people each taking one action can surface an opportunity that single-person scoring misses.

In practice we keep a simple person-level score for routing direct hand-raisers, and add an account-level score built from fit, intent and the number of engaged roles. The account score drives the qualified buying group flag; the person score never creates an MQL target again.

1. Month 1: publish the definitions, fix the data gaps and build the new reports without changing targets.
2. Month 2: review MQL and buying group reports side by side in the weekly pipeline meeting; note where they disagree.
3. Month 3: compare win rate and cycle length for opportunities with one role against three or more roles, using closed deals.
4. End of quarter: move the headline target to qualified buying groups and opportunities; keep MQLs as a diagnostic.
5. After the switch: change scoring and routing so sales receives accounts with roles, not individual leads.

The parallel quarter matters for trust. Sales leaders who see the two views disagree, and see which one predicted opportunities, accept the change faster than those told to switch on a date. For the stage-by-stage rates to watch, see our article on ABM conversion rates by stage.

• Counting contacts in a role instead of companies with the role engaged.
• Letting the engaged window drift between reports.
• Leaving leads unconverted, so they never count toward an account.
• Building the dashboard before the role picklist is agreed with sales.
• Keeping MQL volume as a target "for now", which keeps the old behaviour alive.

The CRM work is a few weeks for most teams; the agreement is what takes time. We sit with marketing, sales and RevOps to settle the definitions, then build and test the reports in HubSpot or Salesforce.

Our RevOps team does this work for enterprise B2B companies, including the scoring and routing changes that follow.

If you want a read on how ready your CRM is, talk to our team and bring an export of open opportunities with their contacts.