3 ms·
>Here’s an idea, if raising money is such a bother than build products that don’t require you to do it. There has been a lot of talk on HN that you don't need
by hammock 14y ago
>Here’s an idea, if raising money is such a bother than build products that don’t require you to do it.
There has been a lot of talk on HN that you don't need a non-technical cofounder. Bryce makes a good case for why a business-savvy partner can be a huge help.
- mindcrime 14y agoThere has been a lot of talk on HN that you don't need a non-technical cofounder. Bryce makes a good case for why a business-savvy partner can be a huge help. That, or one of the techs has to commit to becoming (enough of) a marketing / bizdev / sales / strategy person to do things like articulating a clear value proposition, creating financial models, etc. I'm not actually sure which is the better idea. At Fogbeam Labs, we don't have a dedicated "business person," and - to date - I've chosen to throw myself into the marketing / business world. But that was kinda easy for me, since I always liked marketing anyway. And even with that being the case, I still find myself wondering if spending a lot of time focusing on marketing is a good use of my time, since that will probably never be my specialty. For now, my position is basically "if we find the right person to bring on as a sales/marketing/bizdev co-founder, we'll do it. But the fit has to be just right, otherwise I'll continue working on reinventing myself as that kind of person." Funny thing, even as I'm typing this, I'm listening to a Mixergy interview on "Communicating Product Value". And when I get home from the dayjob tonight, I'll be back to immersed in Chet Holmes videos, learning about building a "core story" and constructing a "stadium pitch" etc. No rest for the wicked...
- Retric 14y agoMore large tech company's started out without a business person than without a technical person. I suspect a large part of this is the importance of a BS detector when delegating things. Or as PG said, The more of an IT flavor the job descriptions had, the less dangerous the company was. The safest kind were the ones that wanted Oracle experience. You never had to worry about those. You were also safe if they said they wanted C++ or Java developers. http://paulgraham.com/avg.html http://paulgraham.com/avg.html It's not that you can't build a good website with C++ or an Oracle back end, it's if your company desides to use them your probably also making a lot of other stupid decisions. PS: (During the Bubble, Oracle used to run ads saying that Yahoo ran on Oracle software. I found this hard to believe, so I asked around. It turned out the Yahoo accounting department used Oracle.) http://paulgraham.com/vwfaq.html http://paulgraham.com/vwfaq.html