13-minute read
The future of B2B sales is hybrid. Some reps work from home, closing deals on Zoom. Some reps work in the field, meeting customers in person. The best companies blend both motions: virtual efficiency at scale plus in-person relationship building for complex enterprise deals.
But hybrid teams face a specific data problem that enterprise teams rarely talk about: the inside reps look great in reports and the field reps look invisible.
Here’s why: Gong records every virtual call, transcribes it, and automatically populates deal records. Managers see rich conversation intelligence for inside rep activities. For field reps, there’s no Gong. There’s no recording of in-person meetings. There’s a check-in logged in SPOTIO showing that the rep was at the customer location, but zero conversation intelligence about what actually happened at that location.
The manager looks at weekly reports: inside reps have detailed deal notes, field reps have sparse notes. Inside reps appear more productive, more skillful, more valuable. Field reps appear disorganized or underperforming. But this comparison is completely unfair. The data quality isn’t equal. The intelligence capture isn’t equal. The system is biased toward virtual motions.
This creates retention problems, coaching inequity, and forecast inaccuracy. The good news: this problem is solvable. The bad news: it requires rethinking how field activity gets captured and reported.
Here’s the hybrid stack that modern sales teams are building. And here’s the universal capture layer that creates data parity across all selling motions. Learn what voice-to-CRM is and how it works — and why it’s the missing link for hybrid teams. Explore Hey DAN’s full capabilities to see how hybrid teams deploy it across inside and field motions.
Modern B2B sales is genuinely hybrid. Enterprise deals require in-person relationship building. High-velocity self-serve expansions close on Zoom. Territory expansion happens in the field. Account defense happens virtually. Strategic accounts require both motions.
The data richness is asymmetrical. Virtual calls get recorded by Gong. Conversations get transcribed. Intent signals get extracted. Deal progressions get tracked with precision.
Field visits get logged in a map app. A check-in proves the rep was there. A one-line activity note captures the meeting. The conversation intelligence—what was discussed, what objections arose, what was learned, what the next step is—requires manual entry after a full day in the field.
By the time that manual entry happens (if it happens), the context has degraded. The rep was in six meetings. The details blur together. The nuance gets lost.
The result: a hybrid sales org with two-tier data quality. Virtual motions are visible. Field motions are invisible. Management decisions reflect this bias. Resource allocation reflects this bias. Individual rep evaluation reflects this bias.
And it’s all based on a data capture disparity, not performance disparity.
What It Is
The universal CRM. One system of record for all selling motions: inside sales, field sales, enterprise reps, transactional reps, retention, expansion, everything.
Core Functionality
Salesforce and HubSpot both operate as pipeline management systems. Deals get created, moved through stages, tracked toward close. Team reporting shows pipeline value by stage, by territory, by individual rep. Forecast accuracy depends on the data in the system.
For hybrid teams, the CRM is the place where all selling activities should converge: virtual call intelligence from Gong, field check-ins from SPOTIO, deal progression notes from both rep types, forecast contributions from all motions.
The Limitation
The limitation isn’t the CRM itself. It’s the data quality feeding into it. The CRM is only universal if both rep types populate it equally.
In practice, inside reps have Gong capturing their Zoom calls and auto-populating deal records with conversation intelligence, objection handling, deal health signals, and next steps. Field reps have no capture system. They move through six customer meetings in a day. Each meeting contains critical intelligence. But each meeting also requires manual post-visit data entry when the rep gets back to the office.
The “universal” CRM becomes two databases: rich, detailed, AI-powered records for inside rep activities and sparse, manually-entered, two-line-note records for field rep activities. The CRM data entry challenge is structurally worse for field reps, who lack the automated capture that Gong provides for inside reps.
When a manager reviews the pipeline, they see this disparity. Inside rep deals look comprehensive and smart. Field rep deals look incomplete and concerning. The manager doesn’t consciously think “these are data quality problems.” They think “the inside reps are stronger.” It’s a structural reason why CRM adoption fails in hybrid organizations — not lack of effort, but lack of an equitable capture infrastructure.
What It Is
Gong is the intelligence layer for virtual selling. It records video calls, transcribes conversations, extracts deal signals, and auto-populates CRM records.
Core Functionality
Every Zoom call gets recorded and analyzed. Gong watches the conversation for keyword patterns: competitive mentions, pricing objections, authority questions, urgency signals. Gong scores deal health based on conversation signals. Gong populates Salesforce or HubSpot with the key intelligence extracted from the call.
A rep closes a Zoom call. Gong has already created a call record, transcribed the conversation, identified critical moments, and suggested the next deal stage. The rep reviews the auto-populated deal notes and confirms the stage change. The CRM record is now complete and accurate with zero manual entry.
For inside sales, this is transformative. Conversation intelligence automatically flows into the CRM. Deal velocity increases. Coaching becomes data-driven.
The Limitation
Gong is the inside rep’s superpower. Every virtual call recorded, analyzed, and structured into the CRM. But for field reps on the same team, Gong records nothing.
A field rep can have six customer meetings in a day and generate zero Gong data. The manager reviews the pipeline at week-end. The inside rep has seven new Gong records from the week showing conversations, deal progression, and next steps. The field rep has two new records showing “customer visit - discussed expansion opportunity.”
The manager sees dramatically different activity density and intelligence density between the two rep types. The false conclusion: the inside rep is more productive or more skilled. The true conclusion: one rep type has data capture infrastructure and one doesn’t.
This creates an unfair performance perception. High-performing field reps may appear as underperformers on paper. Over time, retention suffers.
What It Is
SPOTIO and Badger Maps are field management tools. They track where field reps are, optimize their routes, and log their activities.
Core Functionality
Field reps open the app each morning. Their day of customer visits is mapped out by territory and optimal drive time. They navigate between visits. At each location, they check in to log the visit.
The check-in proves the rep was at the customer location. It timestamps the activity. It creates an audit trail.
From a territory management perspective, this is valuable. The manager sees which areas are covered, which territories need more attention, where reps are spending time.
The Limitation
SPOTIO and Badger Maps prove presence. They don’t capture conversation. A field rep checks in at six locations on Tuesday. The manager sees six activity logs. That’s activity visibility.
But activity isn’t intelligence. The rep was at six locations. The manager doesn’t know what happened at those locations. Was a specific deal advanced? Did an objection come up? What integration requirement was discussed? What timeline was mentioned? What competitive alternative is the customer evaluating?
Those answers exist in the conversations. The conversations are happening. The intelligence is being gathered. But the capture layer doesn’t exist for field activities the way Gong exists for virtual activities.
A field rep has a 45-minute meeting where the customer reveals budget constraints, decision timeline, and a technical integration requirement. That intelligence is every bit as valuable as a Gong-recorded virtual call. But it has nowhere to go. It doesn’t auto-populate the CRM. It doesn’t get transcribed. It gets summarized in a one-line activity note: “Customer visit - discussed needs.”
The ideal hybrid workflow would look like this:
Inside rep’s day: 8 Zoom calls scheduled. Gong records and analyzes all eight. Conversation intelligence flows into Salesforce automatically. Deal records are complete and rich. The rep reviews and confirms stage changes. CRM is fully current by end of day.
Field rep’s day: 6 customer visits scheduled. The rep drives to location one, checks in on SPOTIO, meets with customer, captures conversation intelligence, moves to location two. By end of day, all six visits are logged in SPOTIO and all conversation intelligence is in Salesforce. CRM is fully current.
In reality, the inside rep’s experience matches this ideal. The field rep’s experience is: 6 visits logged in SPOTIO, zero conversation intelligence in Salesforce, manual data entry at end of day (if it happens), sparse notes recorded.
Picture a Monday morning team meeting in a hybrid sales organization:
The manager reviews the pipeline. Inside rep Sarah has seven new opportunities this week. Each one has detailed conversation intelligence: specific objections raised, competitive alternatives mentioned, budget range discussed, decision timeline established, key technical requirements identified. The deals look smart and well-qualified.
Field rep Michael has two new opportunities this week. Each one has a two-line note: “Customer visit - discussed expansion.” That’s it. The manager wonders: why does Michael only have two new opportunities when Sarah has seven? Is Sarah more productive? Is Michael underperforming?
The answer is neither. Sarah has Gong recording every conversation and auto-populating the CRM. Michael has his handwritten notes from the day. One rep type has infrastructure to capture intelligence. One doesn’t.
But the manager’s conclusion is performance-based, not data-infrastructure-based. And that false conclusion affects coaching, resource allocation, territory assignment, and ultimately, retention.
The forecast problem is worse. At pipeline review, the manager can see inside deals with detail and conviction. Outside deals look generic and questionable. The manager becomes more optimistic about inside pipeline and skeptical about field pipeline. But this forecast bias isn’t based on actual deal quality. It’s based on data capture quality.
When your team’s forecast is systematically biased toward one motion, your planning and resource allocation are systematically wrong.
Companies with successful CRM strategies treat data parity across motions as a first-class problem — not an afterthought.
Voice-to-CRM is the universal capture layer that creates data parity between inside and field selling motions.
Here’s how it works:
For inside reps: They have Gong handling virtual calls. Voice-to-CRM handles any in-person activities (client visits, off-site meetings, lunch meetings with prospects). Now the inside rep has complete capture infrastructure regardless of whether the conversation is virtual or in-person.
For field reps: Voice-to-CRM handles all post-meeting capture. Every customer meeting gets immediately followed by 90 seconds of voice intelligence: what the customer needs, what budget they mentioned, what timeline they’re working toward, what integrations matter, who else is evaluating, what the next step is.
Together: every rep on the team generates comparable CRM data quality. Virtual and in-person activities are equally captured. The inside rep’s Gong records don’t create a data advantage over field reps. Both motions are equally intelligent.
The manager benefits immediately: - Fair performance comparison: no more data disparity between inside and field reps - Consistent coaching: can coach from full data across all rep types - Accurate forecast: both motions equally visible - Territory planning: actual customer activity visible across all reps - Retention: high-performing field reps aren’t mistakenly perceived as underperformers due to data capture gaps
Scenario: 20-person team (10 inside, 10 field). $10M quarterly pipeline.
Without voice-to-CRM: - Inside rep data completeness: 85-95% (Gong) - Field rep data completeness: 30-40% (manual) - Team-wide forecast visibility: 60% (only inside motion is fully visible) - Field rep metrics are systematically suppressed due to data capture disparity
With voice-to-CRM: - Inside rep data completeness: 85-95% (Gong handles virtual) - Field rep data completeness: 85-95% (voice-to-CRM handles all field activities) - Team-wide forecast visibility: 90%+ (both motions equally visible) - Fair performance measurement across all rep types
Incremental revenue impact: - Field team improvement: data completeness 30% → 90% - Better data quality enables better follow-up, more intelligent territory planning, more accurate forecasting - 10 field reps × 10 deals/week = 100 field deals/week - Data quality improvement → 25% improvement in field deal conversion and velocity - At average deal size $50K: 2 additional deals/month closed by field team = $100K/month = $1.2M/year incremental - Cost of voice-to-CRM for 10 field reps: $18,000/year - ROI: 6,667%
Plus forecast accuracy: - $10M quarterly pipeline with 30% field visibility = $3M of pipeline uncertainty - Better field data visibility → 25% improvement in forecast accuracy - Better forecasts drive better resource allocation, better pipeline planning, fewer surprises at close
Retention value: - Top-performing field reps who appear to be underperformers due to data gaps may leave - Fixing data disparity improves retention of high-quality field talent - Cost of replacing a sales rep: $200K+ - Retaining two field reps per year due to fair measurement = $400K+ in direct replacement costs avoided
It’s Tuesday morning. The team has 10 inside reps and 10 field reps.
Taylor (inside rep): 8 Zoom calls scheduled throughout the day. Each one gets recorded by Gong. After each call, deal records in Salesforce are automatically updated with conversation intelligence: who was on the call, what objections came up, what competitive alternatives were mentioned, what the customer is trying to do, what the timeline is.
By 5 pm, Taylor’s pipeline in Salesforce shows eight new opportunities with rich, detailed information. No manual entry required. Gong did the work.
Jordan (field rep): 6 customer visits scheduled. First visit: 45 minutes with a prospect who’s considering upgrading from free to paid. Discussion covers: current usage patterns, team size, budget constraints, integration requirements, timeline to go live, who owns the decision.
Visit ends. Jordan speaks for 90 seconds while walking back to the car: “Team of 12 people, currently 4 using free. Want to integrate with their Slack workflow. Budget is $40K annually. Timeline to go live is 6 weeks. They’re comparing us with one competitor but we’re the preference. CFO approval required but they think that’s a formality. They want to see customer case studies from similar teams.”
That 90-second voice note hits Salesforce immediately. The deal record is populated: - Deal size: $40K - Team size: 12 - Current usage: 4 people - Key feature need: Slack integration - Timeline: 6 weeks - Competitive status: In eval, we’re preferred - Approver: CFO - Next step: Send case studies
Jordan completes five more visits. Each one generates a 90-second voice note. Each one populates Salesforce with complete intelligence.
By end of day, Jordan’s pipeline in Salesforce shows six new opportunities with intelligence equivalent to Taylor’s. Both reps have complete data capture. Both reps’ activities are equally visible.
End of week team review: The manager looks at the pipeline. Taylor’s eight deals and Jordan’s six deals all have comparable detail and richness. The manager can fairly assess relative performance, coach from actual data, and make resource decisions based on real activity intelligence, not data capture disparity.
One of Jordan’s field deals converts to a $40K expansion deal the following month. The forecast was accurate because the deal intelligence was complete.
Hybrid sales is the future of B2B. Inside reps close deals at scale. Field reps build relationships and close complex deals. Both motions matter.
But hybrid only works when both motions generate equal data quality. When one motion is captured at 90% completeness and the other at 30%, your organization is systematically biased. Forecasts are biased. Coaching is biased. Performance evaluation is biased. Retention suffers.
Voice-to-CRM is the equalizer. It’s the universal capture layer that makes inside and field selling equally visible in the CRM. It’s what transforms hybrid from a theoretical advantage into a practical one.
The three-tool stack works fine for either motion in isolation. But for hybrid teams, the stack breaks at the capture layer. Voice-to-CRM fixes it.
With voice-to-CRM, every rep on the team—inside or field, virtual or in-person—generates comparable CRM data. Your forecast is real. Your coaching is fair. Your team retention improves.
