The best candidates already decided how they want to work. The only question is whether you're competing for them, or filtering them out before they ever apply.
Post an open role today, one that used to require a desk, a badge, and a parking spot, and watch what happens. The applicants who show up first, before you've even finished describing the job, are checking exactly one thing: is it remote.
If the answer is no, a meaningful share of them close the tab without reading another word. Not because they're lazy. Because they already ran the math on what an in-office job actually costs them, and they've stopped relitigating it for every posting they consider.
Most founders are still writing job descriptions for a labor market that stopped existing around 2021. They aren't losing candidates to competitors with better roles. They're losing them before the role is ever read, to an assumption baked into the first line of the posting.
Key Takeaways
- Remote postings have consistently pulled in a larger share of applications than their share of postings would predict, and the gap has grown since it was first measured.
- The true cost of commuting, gas, vehicle ownership, and time, often rivals or exceeds the raise a founder would need to offer to make an in-office role competitive.
- Widening your applicant pool by going remote doesn't lower your standards. It raises the odds the best available person for the role actually sees the posting.
- The real objection underneath most in-office mandates is trust, not location, and trust gets solved by hiring for the right traits, not by watching someone sit at a desk.
- Requirements that aren't actually essential to the role, local, in-office "culture fit," bilingual when the job doesn't need it, quietly shrink your pool for no real benefit.
- Remote doesn't require an all-or-nothing switch. The same math applies on a smaller scale to hybrid roles.
- The office isn't a neutral default. It's usually the more expensive way to compete for the same person.
The Market Already Decided
This isn't a story about a temporary disruption that eventually snapped back. For about two years, millions of employers ran an involuntary experiment: send everyone home, keep the business running, and see what breaks. For most jobs that weren't tied to a physical location, a truck, a job site, equipment, not much broke. What changed was expectation. Once someone has worked a year without a commute, "no longer remote" reads as a pay cut, whether or not the offer letter says so.
It's a pattern that shows up anywhere a full return-to-office mandate gets tested: the person most likely to walk first usually isn't the average performer. It's the strongest one, the person with the most options, who spent a year proving the job didn't require a seat in a building and has no interest in un-proving it.
What an In-Office Requirement Actually Costs the Person You're Hiring
Run the numbers the way a candidate actually runs them, not the way a P&L runs them, and the picture changes. As of late 2026, the average American commute is around 27 minutes each way, which works out to roughly 218 hours a year spent in a car for a standard five-day workweek. That's more than five full 40-hour workweeks spent driving to and from a job, unpaid, before the actual work starts.
Then there's the cost of the vehicle that makes the commute possible in the first place. The average price of a gallon of regular gas was running just over four dollars nationally as of late summer 2026, and higher than that in plenty of markets. Add financing, insurance, and maintenance, and owning the car that gets someone to your office costs upward of $11,500 a year, before a single mile gets driven for work. The average new car payment alone is running close to $780 a month.
None of that shows up on your books. All of it shows up on theirs. A candidate weighing your in-office offer against a remote one isn't comparing two salary numbers side by side. They're comparing your salary minus the commute against a remote salary that keeps the whole thing intact: the gas money, the 218 hours, the wear on the car, the flexibility to handle a sick kid or a repair appointment without burning a vacation day.
Most founders never run that comparison from the candidate's side. They run it from the business's side instead, where the commute is invisible and the salary line is the only number that exists. That's how the same $80,000 offer looks generous on a spreadsheet and unremarkable in an inbox.
The Mistake Most Founders Make
The mistake tends to show up in one of two directions, and both come from skipping the actual math.
Some founders treat remote as a discount. If the job doesn't require an office, the thinking goes, it shouldn't require a real salary either, and the posting goes out priced for someone who'll settle rather than someone who's good. That pool self-selects down to people with fewer other options, not more talented ones.
Others treat remote as a sacrifice they have to overpay for, as if not commuting is a perk the employee needs to be compensated for giving up. That thinking has it backwards. The employee isn't giving anything up by working remote. They're avoiding a cost you would otherwise be asking them to absorb.
The Reframe: The Office Is the Expensive Option
The office is the expensive option. Every dollar spent trying to make in-office competitive, extra salary, a gas stipend, parking, covers a cost the job itself created. Every dollar saved by letting someone work from where they already live is a dollar they'd have spent anyway on that commute, and now it stays with them instead of getting handed to a gas station and an auto insurer.
That's not a discount you're asking a candidate to accept. It's a trade that works in both directions, and it only feels risky because most founders have never actually written the math down. Once it's on paper, offering a strong salary for a remote role and skipping the in-office requirement isn't generous. It's just accurate.
Why the Pool Gets Better, Not Just Bigger
The cost argument is only half of it. The other half is who actually shows up to apply.
Back in 2022, LinkedIn measured this directly: remote postings made up under 20 percent of jobs on the platform, but pulled in more than half of all applications. That's not a small skew. It means the average remote posting was drawing roughly two and a half times its expected share of interest. That specific measurement is a few years old now, but the underlying dynamic hasn't reversed. If anything, more of today's strongest candidates have had more time to decide remote is non-negotiable for them.
Here's why that matters more than raw volume. The people willing to uproot their life, or accept a long commute, for an in-office role are a much smaller and more constrained group than the people who are simply good at the job. Restrict a posting to local, in-office candidates, and the pool isn't just smaller. It's skewed toward people with fewer other options, not toward people with better qualifications. Open it up, and you're not just getting more resumes. You're getting a fundamentally different, more competitive set of people to choose from.
Building the System
None of this means throwing out standards or hiring the first resume that comes through. It means building the role around three things.
Price it against a remote-adjusted market rate for the actual work, not against what it would cost to make someone tolerate an office. Define the job by what has to get produced, calls made, files processed, deals closed, whatever the seat actually exists to do, instead of by hours logged at a desk. And go through the requirements list and cut anything that isn't actually essential to doing the job. If "local," "bilingual" when the role doesn't require it, or "the right culture fit from being in the room" isn't a real requirement of the work itself, it's a filter quietly shrinking your pool for no benefit to the business.
The harder part isn't deciding to go remote. It's trusting someone you hired without being able to watch them do it. That's the real objection underneath most of the anxiety here: not "will this person work," but "how would I even know." A resume and a strong interview don't actually answer that question in an office either. They just feel like they do, because you can see the person at a desk between nine and five, whether or not they're doing anything that matters.
This is where the TA-12 earns its place in the conversation. It exists because "I can see them working" was never actually a measurement of performance. It scores eight behavioral traits and four cognitive traits, in 45 minutes, against a validated ideal built for the specific role, not a generic personality type. Hire for the traits that predict the outcome, and the location the person works from stops being the thing you're managing.
Remote Without Losing Control
The anxiety under most in-office mandates isn't really about the work getting done. It's about not being able to see it happen, and that's a management instinct, not a leadership one. A manager wants a person who fits a seat and stays visible. A leader wants a person who's good at the job and gives them the room to do it without supervision standing in for trust.
The fix isn't a tracking tool or a check-in schedule that turns remote work into a form of probation. It's building the role around what actually gets delivered and holding people to that, the same way you'd hold anyone accountable regardless of where they're sitting. A hard worker underperforms in an office as easily as at home if the role was never defined by outcomes in the first place. The reverse is also true: define the outcomes clearly, and the location stops being a variable worth worrying about.
What We Learned Going Remote Ourselves
This isn't theoretical for us. When COVID hit, our team was still running out of a single office, thirty people in one room, run like a call center. There was no transition plan. It was a scramble: pack up computers, get them to people's homes, figure out the rest as it came.
One of the people on that team had close to an hour commute each way. Once she didn't have to make that drive anymore, she never wanted to come back to the office, and she didn't have to, because nothing about the work actually required her to be in that room. The room had been a habit, not a requirement, and most jobs built around "everyone comes to the office" are the same way. Nobody designed it that way on purpose. It's just how the role was staffed the first time, and nobody ever went back and asked whether it still needed to be.
What to Do Next
If you're deciding whether your next open role should be remote, ask three questions before you post it. Does this role genuinely require physical presence, a job site, equipment, hands-on work, or is the office requirement just a habit left over from how the seat used to be filled? What would a remote-adjusted market rate for this role actually be, and have you ever sat down and calculated it rather than guessed? And if you can't physically see someone working, do you already know what you'd measure instead? If the answer to that last question is no, that's the actual gap in your hiring process. It was never the location.
You don't need to overhaul how you hire to test this. Price your next open role at a remote-adjusted rate, write the description around outcomes instead of hours, and see what shows up in your pipeline. The difference in both the volume and the caliber of who applies tends to make the case faster than any argument we could make here.
If you want a second set of eyes on what a specific role should actually cost and who it should actually go to, that's the conversation we have with founders every day.
Go Deeper
Frequently Asked Questions
Does remote work actually save money on compensation?
It can, but not because you're paying someone less for the same thing. You're removing a cost, the commute, that they'd otherwise need to be compensated for, and letting them keep that value instead of asking you to replace it with salary.
How do I know if a role can actually be remote?
Ask whether the role requires physical presence to do the work itself, like being on a job site or handling equipment, or whether being in an office is just how the role has always been staffed. Most operations, admin, ISA, transaction coordination, and acquisitions roles fall into the second category, even inside real estate, construction, and other traditionally in-person industries.
What if my business is field-based, like real estate or construction?
Roles that require someone physically on-site, showings, site supervision, hands-on trades, obviously stay in person. But the admin and operations layer behind those field roles almost never does, and that's usually where the biggest untapped remote opportunity sits for these businesses.
What if I can't tell whether someone's actually working from home?
That's a hiring problem, not a location problem. Define the role by its output and hire for the traits that predict someone will deliver it, and the "are they working" question answers itself.
Will going remote lower the quality of who applies?
The data says the opposite. Remote postings consistently pull in a larger and more competitive applicant pool because more of today's strongest candidates filter for remote roles before anything else.
Do I have to go fully remote to get these benefits?
No. The same math applies to hybrid roles. The savings and the applicant pool advantage scale with how much commute burden you remove, not with an all-or-nothing switch.
How much can I actually expect to save by hiring remote instead of in-office?
It varies by role and market, so there's no universal percentage worth quoting. The number worth calculating is the gap between your local in-office market rate and a remote-adjusted rate for the same role, since you're no longer compensating for a cost that doesn't exist for that hire.
What's the biggest mistake founders make with remote compensation?
Treating it as either a discount they're owed or a concession they have to overpay for. Neither is accurate. It's a trade, and it only works once you've actually run the numbers on both sides.
