Live data from Hacker News

The salesman and the developer

swombat.com

41–50 of 59 posts

Re: The salesman and the developer

#41

Completely off topic (or is it?) I find myself being quickly turned off by all these blogposts which 'casually' mention Steve Jobs on every single occasion the author comes across. Taken individually, each of these articles (like this one) would have a prefectly defendable reason to mention it. I'm annoyed with the trend. I have mentioned this issue before in other comments threads on HN. Am I the only one annoyed by…

Harsh considering one mention and this was in relation to an old Apple product, within context of the article. People write about Jobs too much (agreed) but this is more about mainstream familiarity than laziness.

Re: The salesman and the developer

#42
post #39
post #37

This is just a terribly bad analogy.

Care to expand on why?

It just breaks down on so many levels. So the client is a bear, and the developer is setting up camp, and the salesperson draws a bear into the cabin which destroys all of the developer's hard work.

So the real-world analogy would be that the developer is setting up an architecture (which performs similar to a camp - as a staging point for reaching goals), and the business guy brings in a client that then...what? Destroys the architecture? Invalidates it in some way?

It doesn't follow. A better analogy would be that the developer is digging a pit to catch a bear in, and the business guy finds a bear that's too big to fit into the hole. In that case, you have an instance where no one is at fault and there's simply an unshared assumption about the limits of how big the bear can and can't be.

But that doesn't make for as exciting of a blog post.

Re: The salesman and the developer

#43

There's nothing worse than a company where the sales department has too much power. Especially if they are able to hand off the project once the sale is made. It makes it impossible for the rest of the company to innovate on products.

I assume you're referring to BigCo, or even just a non-startup. If you're referring to a startup, I have to disagree with you -- revenue in the door when you're starting out, even if you have to alter your product, is invaluable. In fact, you'll likely have to alter the product from the original vision to get revenue in the door period :)

Re: The salesman and the developer

#44
post #24

Earlier quoted context omitted.

One hallmark of the truly great sales person is that they can sell the product they have rather than the one they wish you had.

Where are those employed? I have never seen it; from small companies to MS (and especially Oracle), from services to product companies. They don't right-out lie because they've actually been drinking the kool-aid so they do not really know that actually the stuff they sell is hard (impossible) to produce. I'm talking software here; no clue :) about other branches of business.

Sales guys are great fabulists for the most part, so in the absence of "blue sky" stuff for reveries w/potential customers, they will just start riffing on their own independently.

This is where a huge amount of the rub between sales-marketing and dev comes in. But this "imagine all the possibilities" type of stuff is pure crack in the sales-customer relationship.

So I try to fill the void for the sales guys so they won't be making stuff up on their own. That is, I take a lot of care/explaining to them what are some of the near term possibilities of our app that we haven't built out yet, but make sense, that sort of thing, how much it would cost, risk factors, etc.

Fill up their fantastical story buffer in advance w/stuff that is acceptable to me. This seems to work well with little friction because sales guys tend to be a lot less intransigent than devs/designers about features - basically, they care less about the substance of the story rather than simply how well it sells.

In short, I try to make my fantasies their fantasies as well.

Re: The salesman and the developer

#45
This statement is pure gold: "I now believe that having someone whose job it is to go and find clients willing to give you money from day one is so important, that I would not start any company without such a person."

Re: The salesman and the developer

#47
post #42
post #39

Earlier quoted context omitted.

Care to expand on why?

It just breaks down on so many levels. So the client is a bear, and the developer is setting up camp, and the salesperson draws a bear into the cabin which destroys all of the developer's hard work. So the real-world analogy would be that the developer is setting up an architecture (which performs similar to a camp - as a staging point for reaching goals), and the business guy brings in a client that then...what? Des…

That's hardly the point I was trying to make... What do you think of the rest of the article, which has nothing to do with architecture or whatever, but to do with the importance of sales in a business?

Re: The salesman and the developer

#48
post #47
post #42

Earlier quoted context omitted.

It just breaks down on so many levels. So the client is a bear, and the developer is setting up camp, and the salesperson draws a bear into the cabin which destroys all of the developer's hard work. So the real-world analogy would be that the developer is setting up an architecture (which performs similar to a camp - as a staging point for reaching goals), and the business guy brings in a client that then...what? Des…

That's hardly the point I was trying to make... What do you think of the rest of the article, which has nothing to do with architecture or whatever, but to do with the importance of sales in a business?

You don't touch on the crux of the problem - good sales is about building client relationships and account management, not one night stands (which is usually what the analogy you're describing devolves into).

Dropping an swaddled and basketed infant sale on the programmer's doorstep is not what sales is about.

Re: The salesman and the developer

#49
post #31
post #20

Earlier quoted context omitted.

How exactly do you tweak a gun? And what sort of gun that will kill bears ain't gonna kill a wolf? And I am not sure that wolves stampede.

> How exactly do you tweak a gun? And what sort of gun that will kill bears ain't gonna kill a wolf? Simple example: there are a number of guns that can be converted from semi-automatic to full-automatic with very simple changes, removing a spring, filing something down, etc. If you've got a pack of wolves coming at you the rate of fire could certainly change the balance in your favor.

If you are equipped to hunt bear, I don't think you are using a semi-automatic.

It seems like we are getting into further trouble here. As this pack of wolves is stampeding (never heard of wolves stampeding, though) at you, removing the spring, filing something down might not be consistent with the very short period of time you have as this herd (?) of wolves is closing the gap on your, er, person.

Re: The salesman and the developer

#50
Two things.

You can build a product but until you manage to sell your product to someone, it's not a company.

'Salesmen' are not the only way to get people to buy your product.

I think it's important to start making a distinction between sales and marketing. At one place I worked, the marketing team resented being lumped in with sales and were actually in direct competition with them: organic signups nibbled away at a salesperson's commission.

People are becoming more comfortable with the idea of purchasing a product without ever having spoken to a human being in the entire sales cycle, and that's a marketing job. For some companies, it obviates the need for 'sales'.

Having made that distinction, I would not go to war, so to speak, without a great marketer by my side. A salesperson, on the other hand...

The problem with traditional sales is the pay structure. For mediocre salesmen, working on a commission means "any warm body will do as long as they don't churn before I get paid". This translates into having problematic customers who will thrash and cause you grief before inevitably cancelling your service or returning your product.

Post reply on HN