Business Analysis Case Study: Solving Diverse Sales Workflows with Flexible Dialer Options in HubSpot
One of the most common assumptions in software development is that a single solution can satisfy all users. In reality, users performing the same job often work in very different ways. While analyzing the calling experience available through the JustCall-HubSpot integration, I encountered a problem that appeared simple on the surface but revealed a deeper workflow challenge.
Sales teams wanted to make calls directly from HubSpot. The obvious response was to provide a dialer within the CRM. However, after examining how different sales representatives worked, it became clear that the real challenge wasn’t enabling calls; it was enabling productivity.
This case study explores how stakeholder analysis, workflow evaluation, and solution assessment led to the availability of multiple dialing options within HubSpot.
Business Context
HubSpot serves as the primary workspace for many sales teams. Representatives spend their day:
- Managing contacts
- Reviewing activities
- Updating opportunities
- Tracking follow-ups
- Communicating with prospects
As sales organizations scaled, users increasingly requested the ability to make calls directly from HubSpot rather than switching between multiple platforms. The initial business request appeared straightforward:
“Allow users to make calls from HubSpot.”
However, business requests rarely tell the full story. In this case, the goal was not simply to enable calling functionality within HubSpot. The real objective was to improve sales productivity by reducing context switching, streamlining workflows, and ensuring sales teams could communicate with prospects more efficiently without leaving their CRM environment.
Problem Statement
How can sales representatives place and manage calls from HubSpot while supporting different working styles, minimizing workflow interruptions, and maintaining accurate activity tracking?
Business Analysis Approach
To better understand the problem, I approached the initiative through a structured analysis process.
Activities Performed
- Reviewed existing calling workflows
- Identified key stakeholder groups
- Analyzed user behavior patterns
- Evaluated workflow bottlenecks
- Assessed solution alternatives
- Defined business requirements
- Documented expected outcomes
The goal was to identify the root problem rather than immediately implement a solution.
Stakeholder Analysis
Several stakeholder groups were directly impacted.
Sales Representatives
Sales representatives wanted to initiate calls quickly without unnecessary navigation or switching between applications.
Success Criteria
- Faster calling experience
- Reduced context switching
- Improved efficiency
Sales Managers
Managers required consistent activity logging and visibility into communication activities.
Success Criteria
- Accurate reporting
- Reliable activity tracking
- Better performance visibility
Revenue Operations Teams
Operations teams focused on deployment, maintenance, and user adoption.
Success Criteria
- Easy configuration
- Minimal support overhead
- High adoption rates
Product Team
The product team needed a solution that could accommodate a wide variety of customer workflows.
Success Criteria
- Scalability
- Flexibility
- Long-term usability
Workflow Investigation
To understand user behavior, I examined how sales representatives interacted with HubSpot during active customer conversations. The analysis revealed that not all users worked the same way. Some representatives remained focused on a single contact record throughout the call.
Others continuously navigated across:
- Contact records
- Company records
- Deals
- Tasks
- Notes
- Email conversations
The calling experience needed to support both groups.
Key Findings
Finding 1: Users Had Different Definitions of Productivity
User research revealed two distinct workflow preferences. Some users valued simplicity and preferred an embedded calling experience within HubSpot, as it felt intuitive and efficient to manage calls without leaving their CRM environment. Others prioritized flexibility, needing the ability to continue navigating different HubSpot records, updating information, and performing tasks while remaining engaged in an active call. Supporting both workflows became a key consideration in the solution design, ensuring the integration could accommodate different working styles without compromising productivity.
A single workflow would not satisfy both user groups.
Finding 2: Embedded Calling Simplified Adoption
The HubSpot Native Dialer provided a seamless calling experience directly within HubSpot.
Benefits
- Familiar interface
- Minimal setup
- Easy adoption
- Reduced learning curve
For many users, this experience was sufficient.
Finding 3: Advanced Users Required Greater Flexibility
Research showed that power users frequently multitasked during calls, often reviewing notes, updating records, opening deals, and navigating across multiple CRM objects while speaking with customers. For these users, a fully embedded dialer could introduce workflow limitations by restricting their ability to move freely within the CRM. To maintain efficiency and support their dynamic work patterns, they required a more flexible calling experience that allowed them to continue working across HubSpot without disrupting active conversations.
Solution Evaluation
Several options were considered.
Option 1: Native HubSpot Dialer Only
Advantages
- Simple implementation
- Consistent user experience
- Faster onboarding
Risks
- Limited flexibility for power users
- Workflow restrictions during active calls
Option 2: Chrome Extension Only
Advantages
- Greater flexibility
- Independent calling interface
- Enhanced multitasking
Risks
- Additional setup requirements
- Increased onboarding effort
Option 3: Multiple Dialer Options (Recommended)
Provide both:
- HubSpot Native Dialer
- JustCall Chrome Extension
Allow organizations and individual users to choose the workflow that best aligns with their working style.
Benefits
- Supports diverse user preferences
- Reduces workflow friction
- Improves adoption
- Accommodates future growth
After evaluating stakeholder requirements and workflow patterns, this option delivered the highest overall business value.
Recommended Solution
The recommended approach was not to force users into a single calling workflow. Instead, users should be able to choose between:
HubSpot Native Dialer
Best suited for:
- Users who primarily operate within HubSpot
- Teams seeking a simple experience
- Organizations prioritizing ease of adoption
JustCall Chrome Extension
Best suited for:
- High-volume sales teams
- Power users
- Representatives who multitask extensively during calls
This approach balanced simplicity and flexibility while supporting a broader range of customer needs.
Business Requirements
The analysis produced several key requirements.
Requirement 1
Users must be able to initiate calls directly from HubSpot.
Business Objective: Reduce application switching.
Requirement 2
Users must be able to choose a dialing experience that aligns with their workflow.
Business Objective: Increase adoption and productivity.
Requirement 3
Call activities must be captured consistently regardless of dialing method.
Business Objective: Maintain reporting accuracy.
Requirement 4
The solution must support future scalability and evolving customer workflows.
Business Objective: Reduce future operational constraints.
User Stories
User Story 1
As a Sales Representative, I want the ability to place calls directly from HubSpot so that I can communicate with prospects and customers without leaving my CRM workflow. By eliminating the need to switch between multiple applications, I can save time, maintain context, and focus more effectively on building customer relationships and advancing sales opportunities.
Acceptance Criteria
- Calls can be initiated from HubSpot.
- The calling experience is accessible from contact records.
- Activity logging occurs automatically.
User Story 2
As a Sales Representative, I want flexibility in how I make calls so that I can choose the workflow that best supports my daily activities. Whether I prefer an embedded calling experience within HubSpot or a separate calling interface that allows me to navigate freely across CRM records, I need a solution that adapts to my working style and helps me remain productive throughout the sales process.
Acceptance Criteria
- Multiple dialing options are available.
- Users can select their preferred method.
- Calling functionality remains consistent.
User Story 3
As a Sales Manager, I want communication activities to be captured consistently across all customer interactions so that I can accurately monitor team performance, track engagement levels, and gain reliable insights into sales activities. Consistent activity logging ensures better visibility into the sales pipeline, supports data-driven decision-making, and helps maintain accountability across the team.
Acceptance Criteria
- Activities are logged automatically.
- Reporting remains accurate.
- Call history is visible.
Risks Identified
Risk 1: User Confusion
Providing multiple options could increase complexity.
Mitigation
- Clear documentation
- Guided onboarding
- Feature education
Risk 2: Inconsistent Adoption
Different teams might adopt different workflows.
Mitigation
- Standardized reporting
- Consistent activity tracking
Risk 3: Increased Support Requirements
More options can create additional support scenarios.
Mitigation
- Knowledge base documentation
- Self-service resources
- Product guidance
Success Metrics
The effectiveness of the solution could be measured through:
Adoption Metrics
- Dialer usage rate
- Feature adoption rate
- User activation rate
Productivity Metrics
- Reduction in application switching
- Time saved per representative
- Increase in call activity volume
Operational Metrics
- Activity logging accuracy
- Reporting consistency
- Reduction in support requests
Key Business Analysis Takeaways
This initiative reinforced an important lesson: users rarely ask for flexibility directly. Instead, they describe symptoms such as inefficiency, friction, or inconvenience in their daily workflows. The role of a Business Analyst is to look beyond these symptoms, identify the underlying need, and understand the real problem that users are trying to solve.
In this case, the challenge was not simply enabling calls inside HubSpot. The real challenge was recognizing that productivity looks different for different users and designing a solution that supports multiple working styles rather than forcing everyone into a single workflow.
Conclusion
This project demonstrated that successful product decisions are often driven by workflow analysis rather than feature development.
By examining stakeholder needs, identifying user behavior patterns, evaluating solution alternatives, and aligning recommendations with business objectives, the team was able to provide a more flexible calling experience that accommodated a broader range of customer workflows.
The result was a solution that balanced simplicity, flexibility, adoption, and operational efficiency: delivering value not only through functionality but through a better user experience.
Disclaimer: I originally authored the product documentation for this feature as part of my Technical Writer responsibilities at JustCall. This case study builds on the research, workflow analysis, and product understanding developed during that process and reinterprets the feature from a Business Analyst perspective.
Original help article: https://help.justcall.io/en/articles/11293671-available-justcall-dialer-options-within-hubspot
