# Inside sales vs. outside sales: how to read a field rep and a desk rep in the same CRM

https://salesbond.app/blog/inside-sales-vs-outside-sales-crm-tracking/
Published: 2026-10-15 · Updated: 2026-10-26

Inside sales reps sell remotely, by phone, email and video, while outside sales reps travel to meet buyers in person. In a shared CRM the two should be read differently, because a field rep’s five visits and a desk rep’s sixty calls are not the same unit of activity. The numbers that are comparable across both roles are stage results and the freshness of the next step, not the count of touches.

## Two reps, one dashboard, wrong conclusion

Monday morning, activity report for last week. Take a made-up pair, with numbers for example only. Dana, who sells from the office, logged 58 calls and 41 emails. Tom, who covers the north of the state from his car, logged 5 meetings and 2 calls. Same pipeline, same report, same column. The manager reads it top to bottom and the first thought is the obvious one: Tom had a quiet week.

He didn’t. Four of those five meetings were on-site with two or three people in the room, one of them was a plant tour that took the whole afternoon, and between them sat about eleven hours of driving. Dana’s 58 calls were real too, but 31 of them went to voicemail, which the CRM counts as a call all the same.

The report is not lying. It is adding apples to miles of highway.

And once a manager has read Tom as “quiet” a few Mondays in a row, that reading starts to leak into one-on-ones, into the territory review, into who gets the next inbound lead. The fix is not a second CRM for the field team. It is deciding, in advance, which columns of the shared report mean the same thing for both reps and which do not.

## What inside and outside sales actually mean

The split is about where the selling happens and how the buyer is contacted. Inside sales is done remotely, from an office or from home, over phone, email and video. Outside (field) sales is done in person: the rep travels to the customer’s site, works trade shows and events, sits in the buyer’s conference room ( [Nutshell: inside sales vs. outside sales](https://www.nutshell.com/blog/inside-sales-vs-outside-sales)). Door-to-door selling is one form of outside sales, but plenty of field reps look more like Tom, driving to scheduled meetings.

That is all the definition carries. It says nothing about who is senior, who closes bigger deals, or who works harder. It also says nothing about where the lead came from, which is a different axis altogether. If you are sorting your team by lead source and direction rather than by place of work, that is the [inbound vs. outbound split](https://salesbond.app/blog/inbound-vs-outbound-sales-small-team/), and the two get mixed up constantly.

Nutshell adds two observations worth keeping. An inside sales cycle often closes faster, and many companies run both models side by side instead of picking one. Why faster? Our guess is simple: a remote rep can keep several deals moving at once, and the next contact is a dial away rather than a drive. The second point matters more here. A mixed team is normal, and a mixed team reports into one CRM. For the outside half, see [logging field sales visits in the CRM](https://salesbond.app/blog/field-sales-visit-logging-crm/).

## Where the day goes: calls and visits are not the same unit

Take a desk rep’s day. Nutshell describes inside sales as the more cost-effective model partly because a rep can make 60 or more calls a day and work multiple deals at the same time ( [Nutshell](https://www.nutshell.com/blog/inside-sales-vs-outside-sales)). Spotio, which sells field sales software and has an interest in the comparison, puts the inside rep at 40 to 60 touches a day against 3 to 5 meetings a day for the field rep, and estimates the cost at roughly $50 per call versus roughly $308 per field visit ( [Spotio](https://spotio.com/blog/inside-sales-vs-outside-sales/)). Those are Spotio’s figures, not ours. Nutshell, for comparison, talks about 3 to 5 in-person meetings a week, so even the sources don’t agree on what a normal field week looks like, and your own cost per visit depends on your territory. But the shape is right, and the shape is what matters here.

A call is a unit that takes minutes and can fail cheaply. A visit takes a morning, costs real money, and usually happens only after two or three remote touches have already set it up. One visit might contain a demo, a pricing conversation and an objection from the finance person who walked in uninvited. In the CRM it is one row.

So “calls per day” is a reasonable norm for Dana and a meaningless one for Tom. If you set Tom a target of 20 calls a week, he will hit it from the car, and the the calls will be worth exactly what calls made from a car are worth. If you set him 5 meetings a week, you need to know whether a meeting means a 20-minute coffee or a half-day on site, or the number tells you nothing either.

We think the honest position is this: activity volume is a norm you set per role, and it never goes on the shared comparison page. There is a longer argument about which activity numbers are worth watching at all in [sales activity metrics for a small team](https://salesbond.app/blog/sales-activity-metrics-small-team/). Here the only point is that the two roles should not share a volume target.

## What to log for each, and what to compare

The trick that makes a shared CRM work for a mixed team is small: give field work its own activity type, then compare the roles only on fields that both of them fill in the same way.

Each of the four CRMs we write for gives you some way to do the first part. Pipedrive lets an admin add custom activity types next to call, meeting and email. HubSpot lets admins add call and meeting types on its paid Sales Hub plans. Salesforce keeps tasks and events apart and has a Type picklist admins can extend. Zoho CRM splits activities into calls, meetings and tasks. In all four, an admin can set this up without a developer, as long as you are on a HubSpot plan that has it. The setup takes ten minutes; the discipline of using it takes a quarter.

What the desk rep logs is the obvious stuff: every call, connected or not, every email and video demo, each with an outcome and a date for the next activity. The field rep logs visits, on-site demos and events, with who was in the room and the next activity date. Add drive time if you want to know what a visit really costs you. “Visit” should be its own type, not a meeting with a note in it, because a filter on “meeting” will pull in Dana’s video calls and the whole exercise collapses.

Then there is what both of them fill in the same way. Deal stage, days in the current stage, whether a next activity is set and sits in the future, and conversion from one stage to the next. These four mean the same thing for Dana and for Tom, so they can sit side by side. So can overdue next steps and deals with no next step at all, which is the one rule that judges both roles identically: a deal with no scheduled next step is drifting, no matter who owns it.

Everything else stays on the rep’s own page. Calls per day, emails per day and touches per deal for Dana; visits per week, meetings per deal and time between touches for Tom. None of it goes in a column next to the other role.

One caveat on days in stage. It only works if both reps move deals on the same trigger, which means you write down what “Proposal sent” means and make the field rep move the deal from the parking lot, not on Friday afternoon.

![Diagram: a desk rep's many calls and emails and a field rep's few visits sit above four shared stage metrics that can be compared](https://salesbond.app/wp-content/uploads/2026/10/inside-sales-vs-outside-sales-crm-tracking-2.png)

What goes on the manager’s one page, then, is stage movement and next-step freshness per rep, and activity volume stays on each rep’s own view with it’s own norm. If you already run a short weekly dashboard, this is the same idea as the [six numbers a sales manager actually needs](https://salesbond.app/blog/sales-manager-dashboard-six-numbers/), with one extra rule: activity totals are never a column shared by both roles. Cycle length is a fair comparison too, as long as you compare each rep against their own role’s history rather than against each other.

## The hybrid team

In a team of five to ten, the usual pattern is two or three desk reps who qualify and book, and one or two field reps who go and close. The deal lives in one pipeline. The problem is the handoff, and it shows up in the CRM as a deal with two owners and no next step.

Here is how it goes wrong. Dana books a site visit for Tom on Thursday. In the CRM the deal is still hers, because nobody changed the owner, and the “meeting” activity is hers too, because she created it. Thursday comes, Tom does the visit, writes nothing because he is driving to the next one, and on Friday the report shows Dana with a completed meeting she never attended and Tom with nothing at all. By the Monday meeting the deal has an overdue next step that both of them think the other one owns.

The field we use for this is plain: who owns the next meeting. Not the deal owner, which stays with whoever gets credit, but the person responsible for the next physical step. In most CRMs this is the user the meeting activity is assigned to (in Salesforce, the Assigned To field on the event). The rule at handoff is that the desk rep creates the visit and assigns it to the field rep, in the same minute the buyer confirms. Doing it at creation also matters in Salesforce, where Assigned To becomes read-only once the event has other attendees. The desk rep’s work is done when the visit exists with Tom’s name on it. Tom’s work starts when it does.

A good handoff also carries three things in the deal, written by the desk rep before the visit: who will be in the room, what was already discussed about price, and what the buyer said they wanted to see. The field rep reads them in the parking lot. If they are missing the visit starts from zero, which is the expensive way to use a trip Spotio prices at around $308.

Territory is the other half of this. A field rep with a territory drawn around drive time behaves differently from one drawn around account size, but that is a separate piece of work, and the handoff rule above works with any map.

## The question to ask on Monday instead

Go back to Dana and Tom. The question that the shared report invited was “why did Tom do so little?” The better question is one you can ask both of them in the same breath: which of your deals moved stage last week, and which ones have no next step. Dana answers with three stage moves and one deal she has been avoiding. Tom answers with one stage move, a plant tour that is now at proposal, and two visits that need a follow-up he hasn’t scheduled. That is a conversation about the pipeline. The activity report, as it stood, was a conversation about who looks busy, and it was wrong about Tom.