# Customer Site Visits: When to Travel to a Customer (2026)

**Author:** Jay Bheda  
**Category:** Careers guide  
**Published:** 2026-11-03  
**Updated:** 2026-11-03  
**Reading time:** 23 min read  
**Canonical URL:** https://gaintrace.com/blog/customer-site-visits

> The most quoted rule in customer success asks every CSM to meet five customers on site every month. Priced at published 2026 government and airline rates, that is about 39,000 dollars a year per CSM and half the working year on the road. Fewer than one employer in fifteen funds it.

---

A customer site visit is a trip you take to a customer's own location to do something that cannot be done on a call. The hard part is not the trip. The hard part is deciding which account is worth one, because every hour you spend travelling is an hour taken from the rest of your book.

The advice in this category is unusually confident and unusually thin. The most quoted rule asks every customer success manager to meet five customers on site every month, which works out at sixty visits a year. Nobody who repeats it has priced it.

So I priced it. At this year's published United States government per diem rates and this year's published airline fare data, sixty visits costs roughly 39,000 dollars a year per CSM in airfare, hotels and meals alone, before anyone's salary, and it puts that person on the road for about half of their working year. Then I checked what employers actually fund. Reading the travel clause of every customer success role advertised at 876 software companies on one day gives a different picture: fewer than one in fifteen of the firms that publish a travel figure allow that much.

That is the gap this article fills. The rule everybody cites requires a budget almost nobody writes. What follows is what the market actually funds, what a trip really costs, and how to decide which account earns one.

## How much do customer success roles actually travel?

About one customer success posting in four requires travel of the person doing the job. About one company in three has at least one such posting open.

That figure is lower than the category's reputation and higher than most remote-first CSMs expect. It also hides an enormous spread, which is the part worth knowing before you negotiate a role or build a travel budget.

Of the companies that publish an actual percentage, the middle one asks for 30 percent. The middle half sit between 25 and 50 percent.

![Column chart of the travel percentages published by 157 B2B software companies, plotted on a scale from zero to 100 percent. Every column stands on a round number, at 5, 10, 15, 20, 25, 30, 40, 50, 60, 75, 80, 90 and 100 percent, with empty space between them. The tallest columns are 30 percent, chosen by 22 percent of the companies, 25 percent chosen by 20 percent, 50 percent chosen by 19 percent and 20 percent chosen by 13 percent. A shaded band covers the middle half of employers, from 25 to 50 percent, and the 30 percent column is marked as the median. A gold dashed line at 52 percent marks the travel budget that five customer visits a month would require. Only four small gold columns stand to the right of that line.](https://cdn.sanity.io/images/zqt0xptq/production/ef36a07ec46ea134443bb9e2a5a4bfd2626f4e13-2400x1080.webp?rect=0,0,2400,994&w=1600&fit=max)

The distribution has a long tail and a thin bottom. Only about one company in twenty asks for 10 percent or less. Roughly two in five sit in the 11 to 25 percent band, and about three in ten in the 26 to 40 band. One in sixteen asks for more than half the year.

There is a quieter pattern underneath those bands. Three numbers do most of the work: 25 percent, 30 percent and 50 percent together account for about three in every five figures published. Add 20 and 40 and you have covered roughly six in seven.

Employers are not calculating travel. They are picking a round number that sounds right, which is worth remembering when one is quoted at you as though it were a measurement.

Illumio's posting for a Technical Account Manager is the median figure written out in full, and it does something most postings do not, which is separate the two kinds of travel:

> "TRAVEL: Although this is a home-office based position, applicants must be able to travel 30% for customer visits. Additional travel for training and conferences may also be required throughout the year."

Read the second sentence carefully. The 30 percent is customer visits. Conferences and training sit on top of it, unbudgeted. If you are negotiating, that is the sentence to ask about, because the published percentage and the number of nights you will actually be away are not the same number.

## Which customer success roles travel most?

Travel is not spread evenly across the function, and the ordering is consistent enough to plan around.

| ROLE | SHARE OF POSTINGS REQUIRING TRAVEL |
| --- | --- |
| Technical account manager | 37.7% |
| Account management | 31.8% |
| Onboarding and implementation | 27.5% |
| Customer success manager | 22.3% |
| Customer success operations	 | 10.5% |

Technical account managers travel most, with well over a third of postings requiring it, and customer success operations least by a wide margin. Treat that last row as indicative rather than firm: customer success operations is much the smallest group in the sample, so a handful of postings moves it several points.

That ordering makes sense once you look at what each role is for. A technical account manager is often sent where the system is, and [what a technical account manager actually does](https://gaintrace.com/blog/technical-account-manager) is frequently work that needs hands on a configuration. The boundary between the two nearest roles is covered in [customer success versus account management](https://gaintrace.com/blog/customer-success-vs-account-management), and the travel figures track that boundary closely: the role with the commercial number attached to it travels more.

By seniority the pattern is gentler but real, and it does not run the way most people assume.

| LEVEL | SHARE OF POSTINGS REQUIRING TRAVEL |
| --- | --- |
| Director | 32.8% |
| Senior | 29.2% |
| Mid | 25.6% |
| Manager | 23.8% |
| Associate | 20.0% |
| Executive | 14.3% |

Travel rises with seniority up to director and then falls off sharply at executive level, which is the one result that surprised me until I read the postings. Executives do travel. Their postings describe strategy, hiring and board work rather than listing a travel percentage, so the requirement goes unstated rather than absent. It is a measurement artefact, and worth naming as one rather than reporting as a finding about how executives spend their week.

If you want to check the current spread for a particular title or market yourself, the same postings are searchable on our [customer success jobs board](https://gaintrace.com/customer-success-jobs), which refreshes continuously and will therefore show different totals from the one-day snapshot behind this article.

## More than half of these roles will not tell you how much

Here is the finding that should change how you read a job advert.

Of the postings that require travel, more than half state no percentage at all. They use language instead. "As needed" is the most common, followed by "regular", "willingness to travel", "occasional" and "ability to travel".

Those phrases are not equivalent, and they are not harmless. "Occasional travel" and "regular travel" describe materially different lives, and neither commits the employer to anything. An offer that says "some travel as needed" can mean two trips a year or two trips a month, and the person who finds out is you, in month four, when the first quarter's schedule lands.

Cordial's posting shows how the hedging works even when a number is present:

> "Will have opportunities to travel to client sites for various business meetings approximately 10% of the time (or less) annually, but will vary based on the assigned client base."

There is a figure in that sentence, and four separate qualifiers around it. "Opportunities", "approximately", "or less" and "will vary" between them give the employer complete latitude in either direction.

If you are evaluating a role, this is the single most useful question to ask in an interview, and the way to ask it is numerically. Not "is there much travel", which invites a reassuring adjective. Ask how many nights away the person in this role spent last quarter. A company that funds travel properly will know. A company that has not thought about it will say "it varies", and that answer is itself the information.

## What employers say the travel is for

When a posting does explain the purpose, the reasons cluster tightly, and the cluster is not what the advice literature implies.

![Bar chart in two parts. The upper part, headed what the posting names, shows eight stated purposes for customer success travel as a share of the postings that require it: customer or client site 13.4 percent, conferences and industry events 9.6 percent, meeting customers in person 9.1 percent, onboarding or implementation 4.4 percent, training or workshops 4.2 percent, company or internal events 3.1 percent, business reviews 2.2 percent, and executive or strategic meetings 1.9 percent. Conferences and company events are gold, marking travel that is not spent with a customer. The lower part, headed what it almost never names, shows four reasons drawn as empty slots: a renewal at 0.2 percent, an expansion at 0.2 percent, an account at risk with none, and an escalation with none.](https://cdn.sanity.io/images/zqt0xptq/production/af9595997d4ed37d88c1712557767a3315d2596c-2400x1698.webp?w=1600&fit=max)

Customer and client sites lead, named in roughly one in seven of the postings that require travel. But conferences and industry events come second, close behind, and meeting customers in person third. Onboarding, implementation and deployment work follows, then training and workshops, then internal company events such as sales kickoffs.

Read that ordering again. Nearly as much stated customer success travel is pointed at conferences as at customers' offices. A meaningful share of what gets called "customer travel" in a budget conversation is a booth, a sales kickoff or a team offsite.

That is not an argument against conferences. It is an argument for naming them honestly, because a travel budget defended as customer time and spent on events will not survive the first finance review that looks at the itineraries.

## Nobody writes down the trigger

This is the result that made me want to write the article.

Across every posting that requires travel, fewer than one in five hundred names a renewal as the reason to go, and the same is true of expansion. Not one names an account at risk. Not one names an escalation. A business review is named in roughly one travel clause in forty-five.

There are exceptions, and they stand out precisely because they are rare. Specright's posting for a Senior Customer Success Manager is one of the few in the whole set that attaches the travel to a named occasion and a named internal participant:

> "Ability to travel up to 30% of time in role to conduct strategic EBR customer onsites with senior Specright leadership"

That is a budget with a purpose attached. It is also roughly one posting in two hundred.

For the rest, employers are buying the plane ticket and leaving the reason blank.

That absence matters more than any of the percentages above it, because it explains the thing CSMs complain about most: travel that feels arbitrary. If the posting does not say what a trip is for, the operating rhythm will not either, and the trips end up allocated by whoever asked loudest, or by whichever customer happens to be near the conference you were already attending.

The advice literature does not fill this gap. It argues for visiting more, which is a direction rather than a decision rule. The rest of this article is the decision rule.

## What does one customer site visit actually cost?

Nobody in this category publishes the cost, which is strange, because it is knowable from public data.

Two primary sources make it calculable. The United States General Services Administration publishes the per diem rates federal travellers are reimbursed at, and for the 2026 fiscal year the standard rate outside the specially listed cities is 110 dollars a night for lodging and 68 dollars a day for meals and incidentals, dropping to 51 dollars on the first and last day of a trip. The Bureau of Transportation Statistics publishes average domestic itinerary fares by origin airport, and across more than 600 United States airports in the second quarter of 2026 the middle fare was about 436 dollars.

Put those together and a single domestic visit costs roughly this much before anyone's time:

| TRIP | AIRFARE | LODGING | MEALS AND INCIDENTALS | DIRECT COST |
| --- | --- | --- | --- | --- |
| One night | 436 dollars | 110 dollars | 102 dollars | 648 dollars |
| Two nights | 436 dollars | 220 dollars | 170 dollars | 826 dollars |

Those are deliberately conservative numbers. They assume the standard per diem rather than one of the roughly 300 United States locations that carry a higher rate, which includes most cities your enterprise customers are actually in. They exclude ground transport, parking, baggage and the dinner you will put on the card to be hospitable. They exclude international travel entirely. And they exclude the largest cost of all, which is two working days of a salaried person.

Call it 650 dollars and two days for a one-night domestic trip, and treat both halves as real. The second half is the one that gets forgotten in budget conversations and the one that your other accounts pay for.

## What the five-visits-a-month rule really costs

Now the rule can be priced.

Sixty visits a year at one night each is about 38,900 dollars per CSM in direct travel cost. More importantly, it is 120 days door to door against a working year of roughly 230 days after weekends, public holidays and leave. That is 52 percent travel.

If those visits run two nights, which most worthwhile customer visits do, it becomes about 49,600 dollars and 180 days, which is 78 percent travel.

Set that against what employers fund. Fewer than one company in fifteen that publishes a travel figure allows 52 percent. Around one in thirty allows 78 percent. The most repeated piece of advice in this category describes a job that almost no company in the market is hiring for.

Run the arithmetic the other way and it is more useful still. The median published budget of 30 percent is about 69 days on the road. At two days a trip, that buys about 34 visits a year. At three days, about 23.

So the real question was never "should I visit customers more". It is: you have somewhere between twenty and thirty-five trips in the year. Which accounts get them?

## The four triggers that earn a trip

A trip is worth taking when it does something a video call cannot. That is the whole test, and it resolves into four situations. If none of them applies, the trip is a relationship gesture, which is a reasonable use of money as long as it is called that and budgeted separately.

**You need to see the work.** The customer's problem is in their environment: a workflow with a step nobody mentions on calls, a shop floor, a clinical setting, a legacy system behind their firewall. Screen shares show you the software. They do not show you the person who keeps a parallel spreadsheet because your tool does not fit how they actually work. If you suspect there is a gap between the described process and the real one, go and look.

**You need people in one room who will not join one call.** Some accounts have a decision maker who has declined every invitation for a year and will nonetheless walk into a conference room in their own building for forty minutes. Travel converts calendar refusals into attendance. This is the strongest commercial case for a trip and it depends entirely on knowing who is missing, which is what a [stakeholder map](https://gaintrace.com/blog/stakeholder-mapping) is for. Go when the map shows a gap at a level you cannot reach any other way, not when it shows a gap you simply have not tried to fill by email.

**The relationship has to be rebuilt rather than maintained.** After a serious outage, a failed implementation or an escalation that reached senior people, there is a category of repair that does not happen remotely. Showing up is costly, and the cost is the message. If you are at this point, the trip is one component of a plan rather than the plan itself, and [what to do when an escalation has reached the customer's CEO](https://gaintrace.com/explore/playbooks/customer-escalation-reached-the-ceo) covers the rest of it.

**Something large and irreversible is about to be decided.** A multi-year renewal, a platform decision, a consolidation review that will remove one vendor. These have a date, and the trip has to land before the internal discussion rather than after it, which in practice means weeks earlier than feels necessary. Use [the leading indicators of renewal](https://gaintrace.com/explore/metrics/leading-indicators-of-renewal) to find the date, and prepare it the way you would prepare any renewal conversation, with [a renewal call preparation checklist](https://gaintrace.com/explore/playbooks/renewal-call-preparation-checklist) rather than a deck about yourself.

Notice what is not on this list: the account is large, the account is in a city you are visiting anyway, the customer invited you, it has been a while. Those are reasons a trip gets scheduled. They are not reasons it is worth taking.

## When not to visit

The advice literature is almost silent on this and it is half the decision.

**When nothing is blocked.** A trip with no question attached to it comes back with no answer. Pleasant, well-catered visits that end with "that was great, let's do it again next year" are the most common form of wasted customer success travel, and they are rarely counted as waste because everybody enjoyed them.

**When the customer does not want you there.** Hosting a vendor is work. Someone books a room, chases attendees, tidies, and loses most of a day. A customer who keeps deferring is usually telling you something, and overriding that costs more relationship capital than the visit creates.

**When the problem is a product problem.** A trip cannot fix a missing feature or a broken integration. It will buy you goodwill that masks the issue for a quarter, which delays the escalation that would actually have got it fixed. If the product is the blocker, the useful work is [getting that feedback to product properly](https://gaintrace.com/explore/playbooks/customer-feedback-to-product-from-cs-sales-support) and being straight with the customer about timelines.

**When you are going because the account is at risk and you have no plan.** Arriving without a plan converts a quiet problem into a visible one and gives the customer a forum to raise everything at once, in front of their own colleagues. Build the plan first. The visit is how you deliver a plan, not how you find one.

**When the second visit is doing the work of the first.** If a trip did not move the account, a second trip to the same people usually will not either. Repeat visits to an unmoved account read as pressure, and they read that way from the inside too.

## Which accounts qualify

Once you accept that the year holds roughly twenty to thirty-five trips, allocation becomes arithmetic rather than instinct.

Start from value at risk rather than revenue. An account worth 400,000 dollars a year with a signed three-year term and healthy usage is not where the trip belongs. An account worth 120,000 dollars that renews in five months, has lost its champion and has two of five licensed teams using the product is. The same logic drives [how to prioritise a book of accounts](https://gaintrace.com/blog/account-prioritisation-framework), and the travel list should fall out of that ranking rather than being built separately.

Then apply a threshold. A 650 dollar direct cost plus two days of a loaded salary is realistically 1,500 to 2,500 dollars of company money. Most teams will find that defensible somewhere above roughly ten times that figure in annual contract value, which puts the floor in the region of 20,000 dollars a year. Below it, the honest answer is that the account cannot carry a flight and should be served well through [a digital customer success motion](https://gaintrace.com/blog/digital-customer-success) instead. Saying so out loud is better than quietly never visiting and calling it a coverage model.

Finally, check how many accounts you carry. A CSM with 12 enterprise accounts can visit each one twice a year inside a 30 percent budget. A CSM with 90 accounts cannot visit a tenth of them once, and pretending otherwise produces a travel schedule driven entirely by who complains. Where your book sits is covered in [how many accounts one CSM should carry](https://gaintrace.com/explore/playbooks/accounts-per-csm-coverage-model), and it determines whether visits are a programme or an exception.

## What to do on the day

The visit is not a meeting with better coffee. Three things make the difference between a trip that returns the money and one that does not.

**Get out of the conference room.** The most valuable twenty minutes of most customer visits happen at somebody's desk, watching them do the thing they described to you on a call. You will see the workaround. Everyone has a workaround, and almost nobody mentions it on a video call because it has stopped feeling like a problem to them. Ask to sit with two or three actual users and watch rather than present.

**Meet someone you have never met.** You flew there. The marginal cost of adding one unfamiliar name to the schedule is close to zero and the value is high, because the person who will decide your renewal in two years is probably not your current contact. One new relationship per trip is a low bar that compounds across a year.

**Spend less than half the time talking.** The temptation is to use rare face time to demonstrate value, which turns into a roadmap presentation. Flip it. Most of what you cannot get remotely is what they will say unprompted when they are comfortable and on their own ground. If you must present, do it last and keep it short.

### A customer visit agenda that fits the day you actually bought

A one-night trip buys you roughly five working hours on site once you subtract the flight, the hotel check-out and the journey back. Most published visit agendas are written as though you had the whole day. Plan against five hours and the choices get easier, because every block has to displace another one.

| TIME  | BLOCK | WHAT YOU ARE ACTUALLY DOING |
| --- | --- | --- |
| 0:00 to 0:30 | Arrival, no agenda | Coffee and small talk with whoever collects you. Listening for who left, who joined, what the reorganisation was about |
| 0:30 to 2:00 | Sit with users | Two or three people at their own desks doing real work. Watching, not demonstrating |
| 2:00 to 3:00 | The person you have never met | Booked in advance. A level above or a department across from your usual contact |
| 3:00 to 3:45 | Lunch, deliberately mixed | Users and the new contact at the same table. Not a meeting with your champion |
| 3:45 to 4:45	 | The structured session | The business review or roadmap conversation, if one is needed. Last on purpose |
| 4:45 to 5:00	 | Commitments, out loud	 | What you will do, by when, said in front of everyone and written down in the room |

Three of those blocks deserve a note.

**The first 30 minutes feel like waste and are not.** Reorganisations, departures and new hires surface in the corridor, not on a call. If you walk straight into a meeting room you have thrown away the cheapest intelligence of the day.

**When you sit with users, the question that works is "show me what you did before this".** Workarounds live in the gap between what people say they do and what their screen actually shows. Almost nobody volunteers a workaround on a video call, because it has stopped feeling like a problem to them.

**The structured session is last for a reason.** Four hours of listening should change what you say in it. Running it first turns the rest of the day into a follow-up to your own deck.

Notice the ratio. You are presenting for about a fifth of the time and listening for the rest. That inversion is the whole difference between a visit and a long meeting.

**On who else comes with you.** Bringing a second person doubles the cost of the trip, so it needs a reason beyond company. The three that justify it: a solutions or support engineer when the blocker is technical and answering it in the room is the point of going, a product manager when you have agreed in advance that they will listen rather than present, and a senior leader when the customer's own senior people will be there and seniority needs to match. Specright's posting above is explicit that its onsites run with senior leadership attending, which is the rare case of a company funding both halves deliberately. What does not justify a second seat is moral support, and what actively harms the visit is bringing someone who will talk, because two visitors in a room almost always present more and listen less than one.

One structural note. A site visit is a poor container for a standard business review, because the format pushes you back into presenting for most of the day. If the trip and the review coincide, run the review as the one structured block above rather than as the shape of the whole visit. Our guides to [the difference between a QBR and an EBR](https://gaintrace.com/explore/playbooks/qbr-vs-ebr) and [what to do when QBRs stop being useful](https://gaintrace.com/explore/playbooks/qbr-template-when-qbrs-stop-being-useful) cover the review itself.

## What to do afterwards

Most of the value of a customer visit leaks away in the week after it.

Write it up within 48 hours, while you can still remember who said the thing that mattered. The useful report is about a page, and it has five parts.

**What I did not know before.** The single most valuable section and the one most often left out. Anything that surprised you, including things that contradict what the account record says. If nothing surprised you, write that down too, because it is a finding about whether the trip was needed.

**Who I met, and what each one wants.** Name, role, what they care about, and how they treat your product. One line each. This is the part that updates the account's stakeholder coverage, and it is why the visit and the stakeholder map belong in the same place rather than in two separate documents.

**What I committed to.** Verbatim, with owners and dates, including the small ones. The commitments made casually in a corridor are the ones that get dropped and the ones the customer remembers best.

**What this changes about risk.** Up or down, with the reason. This is a judgement and should be labelled as one, separately from the observations above it.

**What I would do differently.** One line. Over a year this is what tells you whether your visit programme is improving or just continuing.

Put it where the account lives, not in your own notes. A report in a personal document is a report that the next CSM to own this account will never see.

Then do the small thing you promised. Visits create a handful of specific commitments, usually minor, and the customer remembers them precisely because you said them in person. Delivering those within two weeks is what converts the trip into trust. Delivering them in two months undoes it.

Finally, update the account's status honestly, including downwards. A visit that revealed a problem is a successful visit. The failure mode is coming back from a pleasant trip and marking the account green because everyone was friendly, which is exactly how a surprise churn gets built. The signals that actually predict renewal sit in product, support and billing data, which is what [a customer health score](https://gaintrace.com/blog/customer-health-score) is for, and a good visit should move that score on evidence rather than on mood.

## How to ask for the travel budget

Most CSMs ask for travel in the abstract and lose. The ask that works is specific and priced.

Name the account, name the date, name the decision it is attached to, state the direct cost and the days out, and state what you expect to change. "I want to visit Acme on the 14th. Their three-year renewal goes to their procurement committee in March, the new VP of Operations has declined four calls, and their head of IT has confirmed she will attend in person. Two days, about 800 dollars direct. I will come back with that VP met and a written position on the consolidation review."

That ask gets approved because it is falsifiable. It also gives you the frame for the next one, because you can report against it.

If you are building a travel budget for a team rather than a trip for yourself, the same discipline scales. Take the number of accounts above your value threshold, multiply by the visits each needs, multiply by cost per visit, and present the number alongside the renewal value it is attached to. A travel line defended by the contracts it protects survives scrutiny. A travel line defended by relationship building does not.

## How this changes for remote-first and international teams

Two adjustments matter.

If your company is remote-first, the per-trip cost is higher than the table above, because the team has no office to meet in and trips often combine a customer with an internal gathering. That combination is efficient and it muddies measurement. Keep the customer days and the company days separate in whatever you report, or the customer travel line will be blamed for the offsite.

Formic's posting shows what the batched version looks like when an employer writes it down, including the constraint it puts on where the person lives:

> "Ability to travel ~30% of the time to customer sites across their region, living in close proximity to a major airport"

If your customers are international, the economics change enough to need a different rule. Long-haul travel turns a two-day trip into a four or five-day one, and the honest version is to batch: one region, one trip, several accounts, planned a quarter ahead. Several postings in the set describe exactly this, asking for travel across a named region rather than a percentage. Batching also raises the stakes on account selection, because a week in a region spends roughly a fortnight's worth of a 30 percent budget.

## Where GainTrace fits

The hardest part of this decision is not the travel policy. It is knowing which account is quietly drifting, because those are the ones worth a seat on a plane and they rarely announce themselves.

GainTrace watches product usage, support history and billing signals across every account and turns them into a score that moves before the renewal conversation does. When the trip list is drawn from that score rather than from who emailed this week, the travel budget stops being a perk and starts being a retention instrument. You can [see how the health score is built](https://gaintrace.com/platform/customer-health) or [start free](https://app.gaintrace.com/auth/login) on 25 accounts.

Want the trip list drawn from risk instead of the inbox?

[Book a demo](https://gaintrace.com/booking)

## Frequently Asked Questions

### How often should a customer success manager visit customers?

There is no researched industry standard, and anyone quoting one is quoting an opinion. What the hiring market funds is a median of about 30 percent travel, which is roughly 34 one-night trips a year or 23 longer ones. Allocate those to accounts where something is blocked, at risk or about to be decided, rather than spreading them evenly.

### How much do customer success managers travel?

About one customer success posting in four requires travel. Among employers who publish a figure, the middle one asks for 30 percent, with the middle half between 25 and 50 percent. Technical account managers travel most and core CSM roles least of the main four role types.

### Is the five-visits-a-month rule realistic?

Not for most roles. Sixty visits a year is about 120 days on the road at one night each, which is 52 percent travel and roughly 39,000 dollars a year in direct cost per person. Fewer than one in fifteen employers that publish a travel figure fund that much.

### What does a customer site visit cost?

At the 2026 United States standard per diem and the second-quarter 2026 median domestic fare, about 648 dollars for a one-night trip and 826 dollars for two nights, covering airfare, lodging and meals only. Add ground transport and two days of salary and the realistic internal cost of a one-night trip is in the 1,500 to 2,500 dollar range.

### Should I visit a customer who is about to churn?

Only with a plan already written. A visit is a way to deliver a recovery plan, not a way to discover one. Arriving empty-handed gives the customer a forum to escalate everything at once in front of their own colleagues.

### What is the minimum account size that justifies a visit?

As a rule of thumb, about ten times the loaded cost of the trip, which puts the floor near 20,000 dollars of annual contract value. Below that, a digital motion serves the account better than an occasional flight.

### Do video calls work just as well?

For status, reporting and most problem solving, yes. They do not substitute for seeing how work is actually done, for getting someone in a room who declines calls, or for the repair that follows a serious failure. Those three are what the trip is for.