Ask HN: How to show business co-founders that I'm actually working hard
My commute is roughly 2 hours and I have a young child at home and am much more productive coding when we aren't all together. I seriously think they think I work 10 hours a week when in fact I work 100. I'm happy to attend however many meetings they want to have. Ironically, I've been the one to suggest 2/3 of the weekly meetings we do have. How can I convince them short of sitting right next to them in the office from 9-5 every day that I'm actually delivering a lot of value to the company?
Salient details: We don't have much funding, less than 100K, and I'm a very experienced engineer, so its highly unlikely I can be replaced in a reasonable amount of time. We have had listings for $40K salary/2-3% equity for both developers and designers on many sites for months with no takers. Before I arrived, another developer cost them ~$50K and took 4 months to build a website which was unusable according to their standards and generated no sales. I built our website in 2 months and this has lead to $40K in sales and the expectation to hit 6 figures imminently.
16 comments
[ 2.7 ms ] story [ 48.8 ms ] threadI can point out involvement on Slack, where I am super engaged to everyone who posts and in contrast, they respond haphazardly if at all, but this gets petty.
I don't know you, but I would suggest being more aggressive with asking them what their contribution is. Objectively, they would have $0 of sales without your work. Conversely, you may have had $0 of sales without their personal network. I think this would be a good topic for conversation to set the bar for establishing the value of each founder's contributions.
No amount Slack comment content/timestamps, github commits content/timestamps, website features that get added seem to be able to clue them in to level of effort.
You are not being treated and trusted as a co-founder, you're being treated and trusted as a hired CTO. You can choose to accept this, or not.
If you're going to accept it, you have to be the one to close the gap. In situation like this, you have to make the time to show plans that demonstrate what you're doing, and the time required for each. It doesn't need to be a fancy planning tool - just a Google sheet listing the item, the estimated work effort, the deadline, and any dependencies. The blocks of time should be less than 40 hours each - even below 8 if you can get them there. Then be fully transparent about your progress. When new work gets added, ask what drops. If you have ad-hoc support tasks, add them to the log. This may add 30 minutes to each day, but it will save you more than than in aggravation.
If you choose not to accept it, the market is still good for solid engineers. You can find a job that pays more and allows you to see your kid. (Are you crazy working 100 hours when you have a baby? The divorce will take away all your equity! And besides, you'll have to work more on-site if this thing actually grows.)
Because of our baby, i'm often up at crazy hours, the guys joke regularly about my 4am Slack comments on the business and that I must not sleep at all. This makes it even more baffling that my commitment is being questioned.
Q: "Why isn't it faster" A: "Quality code takes time" Q: "I think it shouldn't take that long, these fixes are easy" A: "Then code it yourself"
I would have a face to face with your partners and ask them if they are actually dissatisfied with your progress or is it just a general frustration with business progress that is reflected in a sort of "are there yet?" behavior.
Then again, they may just want you around until they can find someone who they think can do what they want.
A month later, if you've provided whatever they said would satisfy them and they're STILL whining - see previous action.
You shouldn't put up with "I'm mad and I'm not going to tell you why" in business relationships any more than you should in personal relationships.
Also, keep in mind that you may walk out of that initial meeting without a job. The sort of nasty assclowns that your co-founders sound like don't typically appreciate being directly challenged.