What we learned after launching SalaryLabs

A few hours into launching SalaryLabs on Product Hunt, I’ve been thinking about something slightly different:

How do people actually want to use salary data?

There are plenty of salary websites out there, but I kept running into the same problem — salary numbers are useful,

but they often leave you with more questions.

“Is $85k a good salary?”

“How much is that per hour?”

“What would I actually take home?”

“How does it compare with another role or location?”

“And what happens after taxes?”

That was one of the reasons I built SalaryLabs.

Instead of treating salary data as just a number, I wanted to make it easier to do something with that number.

So right now, SalaryLabs includes free tools for things like:

• Salary comparisons
• Annual-to-hourly conversions
• Take-home pay estimates
• Overtime calculations
• US tax calculations
• Career and salary guides

And there’s no account required just to use the tools.

The product is still early, and launching on Product Hunt is partly about getting it in front of people who will notice things I might miss.

So I’m curious:

When you look at a salary number, what’s the first thing you want to know next?

Is it take-home pay?
Cost of living?
How it compares to other jobs?
Whether the offer is actually competitive?
Something else?

I’d love to use the answers to shape what I build next for SalaryLabs.