The conversation that started all of this
It was 2019. I was wrapping up a placement — a senior network engineer, twelve years of experience, strong candidate. I had found him a contract role paying $92 an hour, W2 through a staffing firm. He called me the next morning to say he was turning it down. A competing firm had offered him a 1099 contract at $78 an hour, and he was taking that instead because, in his words, "the math was obviously better."
I did the math in my head while he was talking. It wasn't obviously better. After self-employment tax alone — which he would now be paying in full, both the employee and employer halves — he was already behind. Add federal income tax with no QBI planning in place, add the health insurance he'd have to buy out of pocket, add the three weeks of unpaid time between contracts that a W2 role would have paid him through. He wasn't coming out ahead. He was coming out roughly $14,000 a year worse.
"He thought the hourly rate was the income. It isn't. It never is."
— Jonathan, on the conversation that changed his thinking
I tried to explain it to him on the phone. He was polite, but I could hear that he'd already decided. The 1099 number just looked bigger on paper, and that was enough. He took the job. I still think about that call.
What made it stick wasn't the money he left on the table — contractors make these judgment calls every week. What made it stick was that I realized I had been watching this happen for years, and I had no good tool to hand someone so they could see the full picture in thirty seconds.
What eleven years of headhunting actually taught me
When people think of recruiting, they imagine someone skimming LinkedIn and forwarding résumés. What it actually involves — at least in the technical and financial markets where I worked — is understanding compensation structures well enough to negotiate them. That means understanding the real difference between a W2 salary, a W2 contract, a 1099 contract, and a corp-to-corp arrangement. It means knowing what a contractor's effective hourly rate needs to be to match what they were making as a salaried employee. It means being the person in the room who can run the numbers and show them to both sides.
I placed engineers, IT consultants, financial analysts, project managers, and a lot of nurses and allied health professionals in the last few years before I left recruiting. Across every one of those fields, the same thing happened again and again. Candidates would negotiate hard on the hourly rate and pay almost no attention to the tax structure. They'd focus on the gross number — the number on the offer letter or the contract — and treat it as though it were the number they'd actually see.
First exposure to the 1099 vs W2 gap. Candidates regularly misjudged their effective take-home when comparing offers. Started building my own spreadsheets to walk them through it.
Healthcare contractors, especially travel nurses and locum physicians, were particularly vulnerable. High gross rates, high self-employment tax exposure, and zero benefits. The math was brutal if you didn't plan for it.
Started seriously thinking about building something. Spent months collecting edge cases: different states, different filing statuses, S-Corp scenarios. Consulted with a CPA I trusted to make sure my tax logic was defensible.
The early version was a Google Sheet I shared with candidates during calls. Over two years, hundreds of contractors used it. Their feedback — especially around the S-Corp analysis and the benefits offset — shaped what this eventually became.
What you're using now. Updated each January for the new IRS brackets and wage base. State rates reviewed and corrected quarterly. The methodology hasn't changed — it's still the same logic I ran on that phone call in 2019.
The contractors I kept thinking about
Over the years I kept a mental file of the types of contractors who got burned most often. Not because they weren't smart — most of them were exceptionally good at their work. But because nobody had ever clearly explained the tax structure to them, and there was no tool that did it either.
The newly independent. The software developer or consultant who had just left a W2 job and gone out on their own for the first time. They'd been used to getting a paycheck with taxes already taken out. The first quarterly estimated tax payment — often four or five figures — came as a genuine shock. Several of them came back to me asking if I'd placed them wrong, if there had been some mistake. There hadn't. The tax structure had just never been explained to them.
The travel nurses and locum physicians. Healthcare contractors earning very high gross rates — sometimes $80–$140/hr — but working in states they didn't live in, carrying their own health insurance, paying for their own professional liability coverage. The gap between gross and net was enormous, and the 1099 flexibility they valued came with a cost many hadn't fully costed out.
The ones comparing the wrong numbers. Contractors trying to decide between a contract role and a salaried position, who were comparing the hourly rate to the salary without accounting for the tax difference, the benefits, the unpaid days between contracts. The comparison was apples to a very different kind of apple, and nobody had handed them a tool that showed it clearly.
"The gross rate is not your income. It is your starting point. What you keep is the question."
— The framing I used on every contractor call for years
Why I built the calculator the way I did
There were already tax calculators online when I started building this. Most of them had the same problem: they were designed for W2 employees or for general income tax estimation. They didn't account for the self-employment tax correctly, didn't apply the half-SE deduction before calculating federal taxable income, and almost none of them included a QBI deduction estimate for 1099 filers. The numbers they produced were wrong in ways that consistently made 1099 income look more attractive than it was.
I also wanted to build something that was honest about its own limitations. This calculator uses flat effective state rate approximations — not actual state brackets — because real state tax calculations require knowing your full state tax return, which varies by credits, local taxes, and filing status in ways that are genuinely complex. It would be dishonest to present a number with false precision. So the methodology is disclosed clearly, and I've always been explicit that a CPA who knows your full financial picture will always give you a better answer than this tool.
What this tool does is give you a fast, accurate order-of-magnitude comparison that's good enough to make the right decision about whether an offer deserves serious consideration, and to understand why two seemingly similar rates can produce very different take-home numbers.
A note on what this is — and isn't
RealContractorPay is a free educational tool. It is not a tax preparation service. It is not a licensed financial advisor. It does not file anything or store any of your information. Every number it produces is an estimate built on simplified assumptions, and I tell you exactly what those assumptions are in the methodology section beneath the calculator.
If you're making a significant financial decision — taking a contract, electing S-Corp status, comparing a job offer to a contract — please talk to a CPA. Use this tool to understand the landscape and ask better questions. Use a licensed professional to confirm the specifics.
I say this not as a legal disclaimer (though it is that too), but because it's genuinely true: the contractors I watched make the best decisions were the ones who came into those conversations already understanding the framework. This calculator gives you the framework. The CPA fills in your specific details.
How to reach me
I read every email. If you've found an error in the calculator — a state rate that looks off, a bracket that seems wrong, a scenario that doesn't calculate the way you'd expect — I want to know about it. Tax rates change, IRS rules get updated, and I'm one person maintaining this. I make mistakes and I correct them when they're pointed out.
If you have a question about how the methodology works, or you want to understand why the calculator produces a specific number, send me a note. I'll write back with a real answer, not an auto-reply.
You can reach me at jonathan@realcontractorpay.com. I'm usually responsive within a business day or two.