Help request: How to find programmers for a startup
theplanis.com
theplanis.com
The worst thing to say is "Just build it, and let me worry about selling it", or "Everyone will be excited about this, trust me". To an engineer this just sounds like you haven't done any actual work yet, besides thinking of the idea, and you are unlikely to do anything, ever. If you expect a coder to build something for you, have a plan of work that you will contribute (even though it will change).
Also: "Anyone who hasn't spent a whole night awake writing blog posts, calling Japanese leads and obsessing over traffic numbers will probably view the product as the most important thing in the enterprise."
Should it be "will probably not view the product..."? And what about partnerships a being bad thing to mention? This would be helpful to me too, to know more about what to watch for :)
WRT partnerships...
They often take forever to sign up, even longer to integrate, and frequently don't produce any results because one partner backs out.
For every successful partnership (erm...) I can quote you three partnership development projects from my own experience that bombed without seeing the light of day.
Maybe I'm just scarred by some bad experiences :-)
I don't think so; the idea that the author is attempting to convey is that people who haven't spent a lot of time working on the parts of a business that aren't building the product won't realise how important those other things are. Admittedly it could have been explained a lot more clearly—I had to go back and read that sentence over too.
More often than not, if you look at successful technology companies even the "business guys" (the CTO and even the CFO) often have an EE/CS/Math/Physics degrees and have, at one point, have held technical roles. Engineering/math/natural sciences act as "brain gymnastics" which come in handy in any role which requires fast, analytical thinking.
That being said, in enterprise software having a strong sales team is often more important than having a strong product. Ideally, you'd want to have a founder who had worked in roles such as field sales/application engineer/sales engineer/consultant and has a Computer Science background: this way they will understand both the technology involved and the acute pain the target customers experience.
For consumer Internet, however, "sales guys" are only needed when you have something to sell (e.g. a critical amount of impressions in an advertising-supported site). The canonical examples (Craigslist, eBay, Google AdWords/Overture) are brilliant in that they're self serve: you don't need a large sales force to sell them.
1) The idea/market has legs
2) You can pull your own weight
As I've said earlier, the best person to start an enterprise software company would be an applications engineer/field sales engineer/professional services consultant from either a large or fast growing enterprise software company.
Not only will they know how to sell, they will also understand the technology, be able to program well enough to create a prototype, be interview developers, know how to support the customer, deal with the end-users and know most importantly what the end-users want (best enterprise software is the enterprise software employees are begging to install).
Two related points.
If you can't "sell" an engineer, why are you sure that you can sell to your proposed customers?
While developing your pitch, be sure that you'll be happy with folks who want what you're offering. If it's not unique, you'll lose the good ones to folks who offer "more".
What is the inverse log scale? 1/log(x) or exp(x)?
I thought I might try and write up some of my experiences - I plan to post this to a whole bunch of the London start up lists where the worst offenders hang out. If you have any suggestions for improvements I would appreciate them.
Thanks!
Just call them computer programmers or software developers but treat them with respect, don't treat them like code monkeys.