REMOTE WORK & DIGITAL NOMAD
Should You Tell Clients You Are Traveling? Honest Pros and Cons
You are on a video call with a prospective client. It is going well. They like your portfolio, the budget talk went smoothly, and then they ask, almost as…
✓The honest case for telling✓The honest case for not leading✓The middle path most experienced
Quick Answer
There is no single right answer, and honest freelancers disagree. Telling clients you travel builds trust with the right clients and filters out the wrong ones, but it can also trigger biases about reliability and rates that have nothing to do with your work. Most experienced traveling freelancers land on a middle path: lead with your working hours and reliability, and let location come up naturally.
- The case for telling: honesty sets accurate expectations about time zones, and clients who are fine with it tend to become your most loyal, longest-lasting clients.
- The case for not leading with it: some clients hear “abroad” and quietly downgrade their rate offer or their trust, so leading with hours and reliability instead keeps the focus on your work.
- Never lie when asked directly: a direct question deserves a direct answer, because getting caught in a small lie destroys more trust than any location ever could.
- Make the question boring: when your connection runs through HomeIPVPN, your logins and calls always show a stable home address, so location rarely even comes up.
You are on a video call with a prospective client. It is going well. They like your portfolio, the budget talk went smoothly, and then they ask, almost as small talk: “So where are you calling from today?” Behind you, through the window, there is very obviously a beach.
Time slows down. Do you say “Bali” and watch their expression change? Do you say “I work remotely” and hope they do not press? Do you lie, say “Austin,” and spend the whole contract hoping they never notice? Every traveling freelancer has lived some version of this moment, and the forums are full of heated arguments about the right answer.
Here is the honest version: both sides have real points, and the freelancers who navigate this best are not the ones with a rigid rule. They are the ones who understand the trade-offs and choose deliberately, client by client. Let us walk through both sides properly.
The honest case for telling clients you travel
Start with the obvious virtue: it is true. You do travel, and building a business on the truth is simply easier than maintaining a story. No mental bookkeeping about what you told whom. No panic when a client suggests an in-person coffee. No background anxiety that one stray detail will unravel everything. Freelancers who disclose describe this as a weight lifting, and that lightness shows up in how they communicate.
There is a business case too, and it is stronger than most people expect. Telling clients up front acts as a filter. The clients who flinch at “I am based in Vietnam but work US hours” are disproportionately the clients who would have been difficult about everything: the scope creepers, the 11pm messagers, the ones who treat freelancers like employees. The clients who shrug and say “cool, as long as the work lands” tend to be the relaxed, professional, high-paying ones. Disclosure does not just cost you bad fits. It actively selects for good ones.
It also sets accurate expectations from day one. Time zones, holiday schedules, the occasional travel day, all of it is easier to navigate when it was never a secret. A client who knows you move around will not be confused by a delayed reply during a travel day. A client who thought you lived in Austin will feel misled by the exact same delay, even though nothing about your work changed.
And there is a subtler benefit: some clients genuinely love it. Startup founders, marketing agencies, anyone who has traveled themselves, they often find it interesting, even a plus. It makes you memorable. In a stack of fifty identical proposals, “the developer who works from Lisbon” is the one they remember at dinner.
The honest case for not leading with it
Now the other side, because it is real too. Some clients hear that you are abroad and something shifts. Not always consciously, not always unfairly in their own minds, but measurably. Freelancers report the same patterns again and again: the budget conversation gets tighter, as if your cost of living should discount your rate. The trust conversation gets longer, as if distance were evidence of flakiness. Questions multiply that a local freelancer would never face.
This is the rate bias, and it deserves plain language. A client who would happily pay a designer in San Francisco $80 an hour sometimes balks at paying the same to a designer in Bali, even for identical work. The logic, if you press it, is that your expenses are lower so your price should be too. That logic is nonsense, you are selling skill and results, not reimbursing your rent, but it operates anyway, quietly, in budget decisions you never get to see.
There is also the compliance trigger. Some clients, especially at larger companies, have rules about where contractors can be located. Mentioning travel can kick off a legal review that a quiet, professional working relationship would never have triggered. Nothing about your work changed. But a policy got involved, and policies do not care about your portfolio.
And then there is simple human psychology. “Abroad” is vague, and vague things feel risky. A client picturing you on a beach with a laptop is not picturing your actual life: the apartment with fiber internet, the standing desk, the calendar full of overlap hours. They are picturing a stock photo. Until you replace that image with evidence, it works against you.
The middle path most experienced freelancers actually take
Here is what long-term traveling freelancers mostly do in practice: they do not lie, they do not volunteer a travelogue, and they lead with the information the client actually needs. Your profile and proposals lead with working hours, response times, and reliability proof. Location, when it comes up, is answered honestly and briefly, then the conversation moves back to the work.
This is not evasion. Think about what a local freelancer does. They do not open proposals with “I live in Austin and here is my commute.” They open with what matters to the client. You are doing the same thing: leading with working hours and reliability because that is what the client is actually buying. Your travel is a personal detail, like your apartment or your hobbies, and personal details come up naturally or not at all.
The exact wording matters less than the posture. “I am based in Vietnam and work US Central hours, 8am to 1pm, with fast replies in that window” is honest, complete, and immediately practical. Compare that with a nervous paragraph explaining your whole lifestyle, which reads as defensive, or a flat “remote,” which reads as evasive. Short, factual, forward-looking. Then stop talking about it.
When you must tell: the non-negotiable situations
The middle path has boundaries, and you should know them. If a client asks directly where you are, answer directly. “Where are you based?” gets a straight answer, always. A small truth told plainly builds trust. A discovered evasion destroys it out of all proportion, because now the client is not wondering about your location, they are wondering what else you are not saying.
Tell proactively when location affects the work. If your travel means you will be offline for two days, say so in advance, just as a local freelancer would announce a vacation. If a client’s contract or security policy restricts contractor locations, that is their rule to know about, and hiding your location to dodge it can end the relationship and your reputation in one move.
And tell when the relationship is becoming long-term. A client you have worked with for six months deserves to know the basics of your life, the same way you would naturally learn theirs. At that point it is not a disclosure, it is just conversation, and it usually deepens the relationship rather than threatening it.
What to do when they react badly
Sometimes you tell, and the client’s face changes. The energy drops. The follow-up email never comes. It stings, and it is worth having a plan for it beyond just feeling bad.
First, do not chase. A client who has decided your location is a dealbreaker will not be argued out of it, and trying looks desperate. A short, gracious reply keeps the door open: you never know when their situation changes or when they mention you to someone else. Freelancers report that some of their best clients arrived months after an initial “no,” through exactly these graceful exits.
Second, learn the pattern. If every client in a particular niche reacts badly, that niche may simply be a poor fit for a traveling freelancer, and your energy is better spent where it is welcomed. If it is occasional, it is just the cost of the filter doing its job. Either way, the data is useful.
Third, and most important: do not let one reaction rewrite your policy. The temptation after a bad reaction is to start hiding, to scrub every hint of travel from your presence. That trades an occasional lost client for a permanent background anxiety, and anxious freelancers communicate worse. Keep the policy that fits your values. Let the filter work.
Make the whole debate quieter with one stable setup
Here is something the disclosure debate often misses: much of the drama comes not from travel itself but from its visible traces. The client who discovers your location from a tracker or a dropped call reacts worse than the client you told yourself, because discovery feels like concealment. A surprising number of “should I tell?” dilemmas are really “they found out before I decided” dilemmas.
This is where your technical setup does quiet work for you. When every login, every tracked hour, every email, and every call goes through one stable home connection, there is no trail of changing locations forcing the conversation before you are ready. You tell clients about your travel on your own terms, in your own words, because you chose to, not because a tool told them first. That is what a home ip vpn gives you in practice: control over your own story. Many freelancers get exactly that with HomeIPVPN, which holds one home IP address steady no matter how many countries appear in their travel plans.
Freelancers who work this way describe the disclosure question getting smaller and smaller until it barely registers. Their connection is consistent, their hours are stated, their work is excellent, and location becomes what it should have been all along: a personal detail, mentioned or not, that changes nothing about the professional relationship.
Bringing it together
So should you tell clients you are traveling? Tell the truth when asked, lead with hours and reliability instead of geography, disclose proactively when it affects the work, and let the filter do its quiet job of sorting good clients from bad ones. That is the whole policy, and it fits in one paragraph because it was never actually complicated. The complicated part was the fear, and fear shrinks every time you act on principle and watch it work out.
Underneath the whole debate sits one practical root cause: the visible traces of travel that force conversations before you are ready and feed the exact biases this post described. That is the problem HomeIPVPN was built to solve, giving you one stable home IP address so your professional presence stays consistent while your personal story stays yours to tell. If you would rather have someone set it up and verify it works, the Pre-Travel Audit & Advisory session is 1 hour, costs $79, and that fee comes straight off the $279 Secure Home IP VPN System session if you go ahead.
Wherever you are reading this from, I hope your next client conversation is about your work and nothing else. You have earned that. Tell your story on your own terms, and let the work speak the loudest.

