I assume by technical labor you mean programming effort. It is hard to communicate the effort required to produce software to a non-programmer. But it can be do

I assume by technical labor you mean programming effort. It is hard to communicate the effort required to produce software to a non-programmer. But it can be done. You have to understand the nature of the problem. "How long will it take for you to do X?" "It will take me about a month." "Really? It doesn't look like it's that much work." This is not an information gap, it is a perspective gap. You are looking at it from the angle of completing the task, and he is looking at it from the angle of cutting costs. You say, "X is harder than you think because of Y and Z," and he says, "Then just leave out Y and Z for now and do only X." You say, "It takes Google two months to do X," and he says, "That's why we're going to beat them to it." You say, "Many smart people have tried to do X and failed," and he says, "Then do it right this time." There's no end to these conversations. Just give the best guess you can on estimates, and don't budge. Don't feel like you have to justify it by revealing personal details about your life, like cost of living. It's not like you're building snowboarding trips into your estimate. This is your professional opinion. Just tell him, if you want rushed software that's gonna fail in 6 months, I can deliver it whenever you want, but I'm trying to build something you can use. Sometimes it's even a trust issue. If the level of trust is not established, then he will doubt you no matter what you say. So you might have to roll up your sleeves and itemize the crap out of every task until he understands that you aren't just pulling his leg.