most people who want to negotiate remote at a non-remote company ask the wrong question.
they say: “i’d like to work from home a few days a week.” or, slightly worse: “i’m thinking about moving somewhere else and wanted to check if that would be okay.”
both of these frame the request as something you want for personal reasons. and the moment it becomes about what you want, the conversation shifts. your manager starts thinking about fairness to other employees, about what the policy says, about what it means if they say yes to you and then have to say yes to everyone.
you don’t want that conversation.
why most people get this wrong
the instinct is to be honest about the motivation: you want more flexibility, you want to travel, you want to not be stuck in an office. that’s true, and it’s fine, but it’s the wrong thing to lead with.
the ask that actually works positions remote work as a productivity arrangement, not a lifestyle preference.
companies don’t mind where you work if the work gets done well. what they’re worried about is precedent, management overhead, and accountability. if you can address those things directly, the personal reason doesn’t matter.
the 3-stage approach
stage 1: the experiment
don’t ask for permanent remote. ask for a trial.
“i’d like to try a fully remote arrangement for 6 weeks. i’ll track my output the same way we track it now, and we can review at the end of week 6 whether it’s working.”
the word “experiment” does a lot of work here. it signals that this isn’t irreversible. it gives your manager an out if it doesn’t work. and it’s much harder to say no to a 6-week experiment than to a permanent policy change.
during the 6 weeks: over-communicate. send a short weekly summary of what you shipped. be more responsive than usual. show up on time to every meeting. the goal is to make the experiment so uneventful that the review conversation is awkward to even have.
stage 2: prove it worked
at the 6-week mark, come with data. literally a document.
“here’s what i shipped in the 6 weeks. here’s my response time on messages (faster than before). here’s feedback from the last cross-functional project. i’d like to make this permanent.”
this works because you’ve already answered the question they’d otherwise have to wonder about: would this person’s performance suffer if they were remote? you’ve just shown them it didn’t.
stage 3: make it permanent
once they say yes to permanent, get it in writing. not a memo, not an email that could be walked back. get it in your contract or an addendum to it. “location: remote” or “remote arrangement as of [date]” on a signed document.
this matters more than people realize. companies change HR policies. managers leave. without something in writing, a new manager 18 months from now has every right to say “actually, we need everyone in the office.”
the ask script
here’s roughly what you say in the meeting:
“i’ve been thinking about how to increase my output and cut down on context-switching. one thing i’ve noticed is that i do my deepest work when i’m not in an open office environment — and i wanted to propose a trial. for the next 6 weeks, i’d like to work fully remote. i’ll keep exactly the same meeting cadence, same response times, same output expectations — i’ll just be doing it from [wherever]. i’ll put together a simple weekly summary so we can both see whether it’s working. at the end of 6 weeks, we review and decide.”
that’s it. don’t explain where you want to go, don’t mention travel, don’t mention lifestyle. just the productivity case and the trial offer.
what to do if they say no
first: find out what the actual objection is. “no” to remote sometimes means:
- “we don’t trust you to manage your time” (a different conversation, and one worth having)
- “the policy doesn’t allow it” (meaning your manager can’t say yes without pushing it up — ask if they’d be willing to)
- “it sets a precedent we’re not ready to deal with” (possibly true, possibly an excuse)
- “we genuinely need you in the room for collaboration reasons” (this might actually be real)
the answer to each is different. if it’s trust, you probably need to build more evidence in-office first. if it’s policy, help them navigate the policy conversation. if it’s precedent, ask what would need to be true for them to say yes.
when to leave vs. when to push
if the company is fully in-person and proud of it, the culture is the constraint, not the policy. no amount of negotiation will change that, and it might damage the relationship to try too hard.
the honest question to ask yourself: is this a company that’s in-person by default but would be fine with flexibility if you proved your case? or is this a company that genuinely believes physical presence is part of the job?
if it’s the first, the 3-stage approach will work. if it’s the second, the faster path is finding a different company. a company that’s remote-first doesn’t require any of this.
the market for remote-first roles in tech, consulting, design, finance, and operations is real. it takes longer to find the right one than filtering on LinkedIn suggests, but it exists. if your current company is a dead end on this, don’t spend 12 months negotiating. spend that time looking.
the thing people miss
the goal of going remote at your current company isn’t just flexibility. it’s proof. a year of performing well in a remote arrangement is the single most valuable thing you can add to your resume if you want to compete for remote-first roles elsewhere.
so even if your current company isn’t your long-term plan, get the remote arrangement first if you can. it buys you time, income stability, and evidence. all of which make the next step easier.
if you want to talk through how to position this for your specific job — book the free intro call.