Your HubSpot CRM Has the Data. But Can Your Sales Managers Actually See the Problem?

We recently worked with a B2B technology company that had:

  • 18 Sales Representatives

  • 4 Sales Managers

  • Nearly 12,000 Companies

  • Approximately 38,000 Contacts

  • More than 3,500 Active Deals

Their HubSpot CRM contained a significant amount of sales data.

  • Marketing was generating leads.

  • Sales representatives were updating deals.

  • Managers were reviewing reports.

  • Executives were looking at dashboards.

  • Yet quarterly targets were still being missed.

  • The most interesting part?

  • The problem was not a lack of CRM data.

  • The problem was that managers could not quickly see what required attention.

  • Pipeline reviews were taking almost three hours.

  • Managers were exporting data into Excel.

  • Deals were remaining untouched for weeks.

And by the time a problem became visible in a report, the opportunity was sometimes already lost.

This was when we started looking closely at one HubSpot CRM feature that many teams treat as simply a different way to view their pipeline:

HubSpot Board View.

At first glance, it looks like a visual version of the traditional deal table.

But when implemented correctly, it can change how sales managers monitor opportunities, identify bottlenecks and conduct pipeline reviews.

The important phrase is:

When implemented correctly.

Simply switching from Table View to Board View does not fix a broken sales process.

Here is what we changed.

Why Table View Was Not Enough for This Sales Team

Table views are useful when you need to analyse individual records.

But during a sales manager's daily pipeline review, the questions are usually different:

  • Which opportunities have not moved recently?

  • Which deals are approaching their expected close date?

  • Which salesperson has too many stalled opportunities?

  • Where are most deals accumulating?

  • Which high-value opportunities need management intervention?

A table can contain all of this information.

But managers often need to open multiple records, apply filters or export data before they can understand the situation.

That creates friction.

HubSpot Board View gives sales teams a visual representation of deals grouped by pipeline stage.

Instead of reviewing a long list of records, managers can see the distribution of opportunities across the pipeline and focus their attention on specific deals.

HubSpot's current Board View supports features such as pipeline-based board views, filtering, record previews, configurable card information and bulk actions. Exact functionality can depend on the HubSpot account, object and subscription configuration, so the live product interface and account permissions should always be verified before publishing screenshots or making a specific feature claim.

Step 1: We Did Not Start by Opening Board View

This is where many CRM implementations go wrong.

The first step was not:

  • “Let's configure the HubSpot Board View.”

The first step was:

  • “What does each pipeline stage actually mean?”

We interviewed the teams involved in the sales process and found several problems.

Different sales representatives interpreted the same stage differently.

Some stages were skipped.

Some opportunities were moved forward because an activity had taken place—not because the customer had actually reached the next buying milestone.

So before configuring the Board View, we standardised the pipeline around meaningful sales milestones:

  • Qualification

  • Discovery

  • Product Demo

  • Proposal Sent

  • Negotiation

  • Legal Review

  • Closed Won

  • Closed Lost

The exact stages will differ by business.

The principle does not:

A Board View is only as useful as the process it represents.

If your stages are unclear, your visual pipeline will simply make the confusion easier to see.

Step 2: We Customised the Information Visible on Deal Cards

One of the most important implementation decisions was deciding what information should be visible without opening every deal.

A deal card showing only:

  • Company Name

  • Deal Amount

It does not provide enough information for effective sales management.

We configured the board around the questions managers needed to answer quickly.

The relevant deal information included:

  • Deal value

  • Expected close date

  • Deal owner

  • Last activity

  • Lead source

  • Priority

  • Industry

  • Next scheduled task

The goal was not to display every available property.

The goal was to display the properties that helped managers decide:

“Does this opportunity need attention?”

This is an important distinction.

More information does not automatically create better visibility.

The right information creates better visibility.

Step 3: We Used Filters to Turn the Board Into a Management Workspace

A sales manager does not need to review 3,500 opportunities every morning.

They need to see the opportunities relevant to their decisions.

Using HubSpot's filtering capabilities, managers could narrow their view by relevant criteria such as:

  • Deal owner

  • Pipeline

  • Deal stage

  • Close date

  • Deal size

  • Industry

  • Other available CRM properties

For example, a manager could focus on:

“High-value deals expected to close this month with no recent activity.”

That is far more useful than simply asking:

“How many deals are in the pipeline?”

Step 4: We Used the Board to Find the Bottleneck

Within the first few weeks of reviewing the pipeline more visually, one pattern became difficult to ignore.

A significant concentration of opportunities was accumulating in the Proposal Sent stage.

The initial reaction could have been:

“Sales representatives are not closing deals quickly enough.”

But the Board View helped the team ask a better question:

“Why are these opportunities accumulating here?”

After reviewing the process, we found that several deals were waiting for internal pricing approvals.

  • The bottleneck was not necessarily customer interest.

  • It was an internal approval process.

  • This is where a CRM feature becomes more valuable than a simple interface improvement.

  • The Board View helped make the pattern visible.

  • The sales process analysis helped explain the pattern.

  • The management team could then act on the actual problem.

Step 5: We Used Bulk Actions to Reduce Administrative Work

Pipeline hygiene is important.

But if maintaining the CRM requires managers to open every record individually, adoption becomes difficult.

Where appropriate, bulk editing can help teams update common information across multiple records more efficiently.

This is particularly useful when:

  • A process changes

  • Multiple records require the same update

  • A manager needs to correct a common data issue

  • A team needs to update a shared property

However, bulk editing should be used carefully.

Speed should not come at the cost of data quality.

Before making bulk changes, teams should confirm:

  • The correct records are selected

  • The correct property is being changed

  • The change is appropriate for every selected record

One incorrect bulk update can create a much bigger data problem than manually updating a few records.

This is exactly why CRM implementation requires more than simply knowing where a feature is located.

Step 6: We Changed the Pipeline Review Conversation

Before the implementation, the weekly pipeline review looked something like this:

CRM → Export → Excel → Manual Analysis → Meeting → Follow-up

The review could take approximately three hours.

After improving the pipeline structure and using Board View as the operational workspace, the review became more focused.

Instead of asking sales representatives to explain every opportunity, managers could focus on exceptions:

  • Why has this deal not moved?

  • Why is there no next activity?

  • Why is this opportunity still in the same stage?

  • Why are multiple deals waiting for the same approval?

  • Which high-value opportunities require intervention?

The review became less about reading the pipeline.

It became more about managing the pipeline.

That is the real value of the feature.

What changed for the client?

Board View was one part of a broader CRM improvement initiative.

The implementation also included:

  • Pipeline redesign

  • Stage standardisation

  • CRM data cleanup

  • Better activity visibility

  • Manager adoption

  • Sales process alignment

Therefore, we would not attribute every business outcome to Board View alone.

That would be an inaccurate conclusion.

The more honest conclusion is:

  • HubSpot Board View became more effective because the underlying sales process was also redesigned.

In the broader implementation, the client observed improvements in:

  • Pipeline review time

  • Visibility into stalled opportunities

  • CRM adoption

  • Manager oversight

  • Forecasting discipline

If you are publishing specific numerical results, these should be supported by a clearly defined baseline, measurement period and methodology.

For example:

Before: Weekly pipeline review required approximately three hours.

After: The redesigned review process was completed in approximately 20 minutes.

The more context you provide around a result, the more credible the case study becomes.

The HubSpot Board View mistakes we see most often

1. Switching to Board View without fixing the pipeline

A visual interface cannot fix unclear sales stages.

2. Showing too much information on each card

If every property is displayed, the board becomes difficult to scan.

3. Showing too little information

If managers must open every deal, the board loses much of its operational value.

4. Moving deals based only on sales activity

A call, email or meeting does not necessarily mean that a deal has progressed.

The customer milestone should determine stage movement.

5. Not defining stage exit criteria

Every stage should answer:

“What must be true before this opportunity moves forward?”

6. Using bulk actions without proper validation

Bulk editing can save time.

It can also create widespread data problems if used incorrectly.

7. Treating Board View as a reporting tool

A report tells you what happened.

A well-configured Board View helps managers decide what needs attention next.

Our implementation checklist for HubSpot Board View

Before configuring the board, we recommend asking:

✓ Are the pipeline stages based on real customer milestones?

✓ Does every stage have clear exit criteria?

✓ Can a manager identify stalled opportunities quickly?

✓ Is the most important information visible on the deal card?

✓ Are filters configured around real management decisions?

✓ Are opportunities reviewed based on age and activity?

✓ Does every active deal have a clear next action?

✓ Are managers actually using the Board View during pipeline reviews?

✓ Are bulk actions being used with proper data controls?

The feature is powerful.

But configuration is only the beginning.

The biggest lesson from this implementation

The biggest lesson was not that HubSpot Board View looks better than a traditional table.

The lesson was that the right CRM view can change the way managers interact with sales data.

When the right information is visible:

  • Managers can identify problems earlier.

  • Sales representatives receive more specific coaching.

  • Pipeline reviews become more focused.

  • Bottlenecks become easier to investigate.

  • And the CRM becomes more than a database.

  • It becomes part of the daily operating rhythm of the sales team.

  • But there is one important caveat.

  • A visual pipeline does not automatically create better sales performance.

It works when the following elements work together:

Clear process + clean data + defined stages + manager adoption + the right CRM configuration.

HubSpot Board View can provide visibility.

Your sales process determines what that visibility means.

Now I want to hear from HubSpot users.

What is your biggest challenge with your current HubSpot sales pipeline?

A. Deals remain stuck in the same stage

B. Managers still depend on Excel for pipeline reviews

C. Sales representatives do not consistently update the CRM

D. The pipeline looks healthy, but the forecast is still unreliable

Comment with A, B, C or D.

We may use the most common answer to create our next practical HubSpot CRM implementation guide.