644 karma · joined October 14, 2010
Keepify: http://keepify.com Cold calling book: http://www.coldcallingbook.net Blog: http://whitetailsoftware.com
I joked that the PhD program was like a girlfriend no one liked, but they waited to say so until I quit.
I've been thinking about this lately. It's really important to chose to spend time on things that are positive for you whether the primary aim or best case scenario pans out or not. Great post.
Figure out a way to offer some value to them. http://bit.ly/oeZDzC [whitetailsoftware.com]
When you are speaking with them, ask open questions like "What are your three biggest problems in X business?"
One of the three is usually hiring quality people. Anyone got a solution?
More ideas on refining the calling approach: http://bit.ly/vPCtuI [blog.asmartbear.com]
The second question is easier to get an estimate for, but you probably defined your market incorrectly (especially if you're not solving your own problem).
The last one is sticky. It reminds me of BSG. The human capacity for self-deception is without bound...
That said, it's still useful to struggle with these questions periodically. Startups are all about the fight. You'll never have certain answers. Measure, learn, and adjust.
Or maybe you'll move on and it isn't that big of a deal.
You have been warned.
There is no claim that cooking is equivalent to writing code. The claim is that writing code is rarely done on a whiteboard (Perhaps design, architecture, or some logic back-and-forth but rarely code.) and that interviewees shouldn't be expected to perform well at something they don't do.
I'm happy to be a good neighbor, but policy should happen as close to the local level as possible. I don't think that is a shocking insight.
I don't care what your reason is for charging less. I don't care if money isn't important to you. Try it. Talk less about why you charge this or that. Challenge your own assumptions and try raising your rates.
Some fields lend themselves to domain experts who can write software making large leaps in productivity, but many do not. There are a lot of desirable skills I'd prefer the education system teach before Python. In the end, I think you want a society where anyone with the need or interest can go learn it on their own. This presents a huge educational challenge that we should try to fix as best we can, but this problem will never be completely solved. We should use our resources to improve things as best we can.
I never managed to sell the Scout product online. It is incredibly bad marketing copy that I modified from some examples I found around the web. Any sales of that product required calls or in person handling. I did best at a trade show. There is no online audience I could reach for it. I underpriced the product and marketed it poorly. I found some success in higher-touch sales, but you are correct that the price point needs to support that effort level and you should target your market accordingly. That particular product also has an entrenched and highly likable competitor.
Phone numbers (business listings) from a service like Hoover's are free at your public library.
You're also correct that working on a technical product has nothing to do with writing marketing copy, but I'll bet that not everyone in this audience knows that. Hopefully my story lent them some perspective.
I'm working on another product at the moment. I wrote the article about my experience developing those products hoping that people would think about what might work for them and be open to ideas that aren't commonplace. I'm glad to have your perspective as it may help everyone consider their options from every angle.