A freelancer gets a tempting offer: a client wants to bring them on as a part-time contractor, on-site two days a week, at a rate that looks noticeably better than their usual freelance number. It's tempting to say yes on the number alone. It's also the exact situation where the sticker rate and the real hourly wage diverge the most.
The number on the offer only counts the hours you're paid for
A quoted rate describes what happens during the hours you're actually clocked in and billing. It says nothing about the hour spent commuting each way, twice a week, that isn't paid and isn't optional if the role requires being physically present. It says nothing about the cost of maintaining a separate wardrobe or gear for on-site work, parking, or the gap between your usual flexible freelance schedule and a fixed on-site block that limits when other client work can happen.
None of that shows up on the offer. All of it shows up in your actual time and money once the arrangement starts.
Commute time is unpaid labor that gets normalized
An hour of commuting each way, ten hours a week across a five-day on-site arrangement, is real time that produces zero income and can't be spent on other billable work. Treating it as a rounding error is easy to do because it's so culturally normalized, everyone commutes, so it barely registers as a cost. But ten unpaid hours a week is ten hours that would otherwise be available for other clients, and leaving it out of the math is exactly the kind of gap that makes a quoted rate look better than it turns out to be.
Commuting research consistently finds that the time cost compounds beyond just the hours themselves, through stress and reduced availability for other work, which matters even more for someone whose income depends directly on billable hours rather than a fixed salary.
Taxes and structure change the comparison too
A W-2 style part-time arrangement and a 1099 contract rate aren't directly comparable numbers even before commute time enters the picture, because the tax treatment, benefit access, and expense deductibility differ. A freelancer used to deducting home office costs and software subscriptions against 1099 income needs to run the actual after-tax comparison, not just eyeball the two rate numbers side by side. The IRS's self-employed tax hub lays out how those distinctions actually work, and it's worth checking before assuming an on-site rate bump nets out ahead after tax treatment shifts.
Gear, wardrobe, and food costs that only exist because of the arrangement
On-site work introduces small recurring costs that a fully remote freelance schedule simply doesn't have. Lunch bought out instead of made at home, a wardrobe suited to a specific office environment, parking or transit passes, even the incidental cost of coffee runs with coworkers, all of it adds up to real money that wouldn't exist under a remote arrangement at the same rate.
None of these costs are large individually. Together, across a full month of two on-site days a week, they can easily run into a few hundred dollars that never gets subtracted from the quoted rate before comparing it to what a purely remote engagement would have paid.
The remote alternative changes the comparison entirely
It's worth explicitly running the same math against a remote counteroffer, if one exists, or against staying with existing remote freelance clients at the current rate. A remote arrangement at a lower quoted rate can easily come out ahead in real hourly terms once the on-site version's commute time, gear costs, and schedule inflexibility are subtracted out. The comparison only works if both options get the same honest treatment, rather than taking the on-site number at face value because it's the newer, shinier offer.
Running the real numbers before saying yes
This is exactly the kind of comparison a real hourly wage calculator is built for: enter the quoted rate, the actual commute time, any new work expenses the arrangement introduces, and the real hourly number often lands meaningfully lower than the one on the offer. Sometimes it still comes out ahead. Sometimes the "better" rate turns out to be worse once the unpaid hours are counted honestly, and that's exactly the kind of decision worth making with real numbers instead of a gut reaction to a bigger figure on paper.
The Bureau of Labor Statistics tracks wage and commuting data at a national level, and while it won't answer an individual's specific math, it's a useful reality check on how much unpaid commute time factors into typical compensation comparisons across the broader labor market.
The same gap shows up in freelance pricing generally
This isn't a one-off scenario limited to on-site contract offers. It's the same underlying pattern behind why a calculated freelance hourly rate rarely matches what actually gets earned: any time unpaid hours, whether commute, admin, or unbilled scope, get left out of the rate math, the number on paper stops describing reality. Investopedia has broader coverage of effective versus nominal compensation that applies just as directly to this kind of offer comparison.
Before accepting a rate bump that comes with new unpaid time attached, run the actual math. The offer that looks better on the letter isn't always the one that pays better per real hour worked, and the only way to know for sure is to do the arithmetic instead of comparing two headline numbers directly. EvvyTools has this calculator, and several others like it, free to use for exactly this kind of decision.
A quick checklist before you say yes
Before responding to any offer that changes your usual working arrangement, on-site instead of remote, longer hours instead of flexible ones, it helps to run through a short, consistent checklist rather than relying on how good the headline number feels in the moment.
First, total the actual unpaid time the arrangement adds: commute, prep, any mandatory presence that isn't billable. Second, total any new recurring costs the arrangement introduces that wouldn't exist otherwise. Third, check whether the tax treatment changes anything material about take-home pay, since a 1099 to W-2 shift, or the reverse, moves more than people expect. Only after all three of those are accounted for does the comparison against your current rate actually mean anything.
Why this matters more the longer the arrangement lasts
A one-time project with a slightly worse real hourly wage than usual is rarely worth agonizing over. A recurring, months-long arrangement with the same gap compounds into a real difference in annual income, and it's much harder to renegotiate an ongoing arrangement upward than it is to price a new one correctly from the start. Running the numbers before saying yes costs a few minutes. Running them after several months of an underpriced arrangement costs a much harder conversation, or a decision to simply eat the gap for as long as the engagement lasts.
What to do if the math comes back worse than expected
If the real hourly wage on an on-site or otherwise less flexible offer comes out lower than your current arrangement, that doesn't automatically mean the offer should be declined outright. Sometimes the appeal is something the calculator can't capture: steadier income, a client relationship worth investing in, or simply variety after a long stretch of similar remote projects. What matters is that the decision gets made with the real number in front of you, rather than the headline rate alone, so any tradeoff is a conscious one rather than an accidental discount you didn't realize you were accepting.
A reasonable middle path, if the gap is real but the opportunity still seems worth it, is to negotiate around the specific cost driving the gap. A rate bump tied directly to commute days, or a hybrid arrangement that trims the on-site time to one day a week instead of two, can close most of the difference without walking away from an otherwise good opportunity.
Top comments (0)