Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> If they say “yes,” you’re happy because the terms or money are so good, it more than compensates for the distraction, perhaps funding the thing you really want to do.

Perhaps. Make sure you're high bar is high enough. Opportunity cost is an underappreciated metric. The exceptional (read: as in a rare exception well above average, mean, etc.) can be addicting, and eventually self-defeating (read: before you know it your temporary digital ditch digger stint gets less stint-y and more permanent-esque). It's like a bad-ish romantic relationship that goes on too long. Regrets, and the some.

If you're going to go this route, be certain to plan your exit. For example, "The first X weeks are $Y per hour. After that we revisit, if necessary." Baking this into the agreement will force you at the end of X weeks to recalibrate the revenue vs the opportunity costs.

In fact, for any type of contract work with too many unknowns and/or too much possible career friction always include a time limit along with the rate.



I think that’s the virtue of setting a high price on what you don’t want to do as your “not saying no”/funding strategy.

It’s a reflection of your perceived opportunity cost.

But you are right to suggest time-bounding your engagement up front to avoid getting stuck in a local maxima.

Or, at a certain scale, have a segregated set of people doing these requests where possible to limit and help govern the distraction.


There are things I don't really love doing like ghostwriting company blogs but if the project is short and well-defined (and is something I can actually do a good job of fairly quickly), I'll take a few $K from you. I'd be much more hesitant to commit to something more open-ended even if the income stream were good if it were something I was doing strictly for the money.


The other thing I wanted to mention, aside from opportunity cost, is risk. I'm not suggesting never leave your sweet spot. That would be stupid on my part :)

However, as you leave your sweet spot, be aware (read: beware) of what you don't know. Be aware of the fact that bad decisions are very similar to trust...one slip and you've lost 10x more than you anticipated. If you're going to leave your sweet spot be sure you're prepared for the worse. It can and does happen.

Put in real terms, over the years I've worked as a contractor for a number of marketing / web dev agencies. The more successful ones didn't get there from yes, they got there because of no. No to projects beyond them. No to clients with expectations out of proportion to budget. No for the win, so to speak.

I've also seen those same agencies start to drink their own Kool Aid. They get in a financial pinch and take on work / clients they're not tuned for. For example, they don't have the in house expertise in the technology / solution required. Eventually the project costs more than it brings in *and* the team is miserable, has lost faith, leaves the conpany, etc.

If you're leaving your sweet spot and you're not concerned, you're probably doing it all wrong.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: