3 ms·
> You need hunter-gatherers to find them, corral them, and set up a collaborative sales process with them. I guess it depends on what the product is. I've init
by apaprocki 13y ago
> You need hunter-gatherers to find them, corral them, and set up a collaborative sales process with them.
I guess it depends on what the product is. I've initiated contact in a bunch of cases (mostly situations where the product is a public SaaS or already well-liked) and in others, evaluating a product stems from of a conversation at a meetup or conf.
IMO, the best thing anyone can do is make the product discoverable. If it has competitors, write blog posts and clear feature comparisons (they don't all have to be positive, either). If performance matters to whatever it is, write objective benchmarks and discuss performance aspects/tradeoffs. If it is something with an API, try to ensure there are a variety of platforms supported. This stuff is all good-to-have anyway, but many companies might not realize that people from large companies are browsing their sites and leaving unsatisfied.
I think developer-evangelist roles actually play a big part in this. Having someone set up real-world use cases and blog about them or post code somewhere can really help a customer out who just wants to try something but doesn't want to spend a lot of time doing it.
If the product is private, maybe have an easy way to generate an expiring VM image with some kind of demo setup so that you can quickly send it to leads. There's not a single person on earth that wants to do rounds of conference calls and in-person visits to just play with something.
> It's much easier to sell services to bigcos than products.
I've found the exact opposite, but maybe it depends on what you're referring to exactly. Carving out budget dollars for "3 people @ X/hr" is much harder and more scrutinized than product. "Product" is a loose term, though. "1-yr license" or "1-yr maintenance contract" are products, not consulting, even though the company selling them might not view them that way.
When it comes to SaaS products, we typically want to buy an appliance (read: VM image) that just works, deals with some form of standard authentication/authorization tech (LDAP/AD, OAuth, SAML, OpenID), and x-yr support contracts. Per-seat licenses usually involve more effort. Purchasing professionals are looking to mitigate risk. They don't want to enter into a purchase that has an attractive up-front price, but open-ended potential rate hikes down the road.
- tptacek 13y agoIt may be the case that developer offerings are easier to sell into bigcos than other services. For my part, I have (a) had no luck selling products into enterprises using passive sales techniques (blogging "developer evangelist"-type strategies being an example of passive sales), and (b) talked to a bunch of other people who report similar results. Regarding consulting: yes, 3 full-time consultants as staff aug is hard to sell. But most consulting projects aren't like that. Our typical project is 2 people, 2 weeks; we scale down to 1 person/week easily. A 1 p/w project isn't hard to sell at all.