Ask Slashdot: Compensating Technical People For Contributing to Sales? 331
cloud-yay writes "I work for an IT consulting firm and recently I've been tasked with heading up our engineering consulting team — which without the fancy corporate speak means that we're trying to empower our engineering team to think a little like sales people instead of being purely service orientated. To clarify, our technical people are viewed by our customers as trusted advisors and when they see a opportunity for a complementary sale/network refresh/project they often involve our sales team, however when the customer sees the sales people, they always clam up because they're 'sales people' and customers think they are just interested in alleviating them of their money! I'm interested in what the Slashdot community thinks of how we should remunerate engineering teams for this 'sales' work (which would cost us commission to sales people anyway) but in a way that doesn't foster any animosity between sales and tech staff because in the end sales people live and die on commission. Has anyone worked in this environment anywhere and what works/doesn't work in your experience?"
This spells disaster. (Score:4, Interesting)
Ok, let's say that by some piece of luck your engineers become sales people. Good sales people, even.
Now they look around and realize something -- they don't need you. In fact, they don't need anyone else, because they can do the R&D *and* the sales.
If they don't have the power to fire all of you, they certainly have the power to take your customer list and leave to start their own company.
it's a good way (Score:0, Interesting)
...to get rid of your engineers.
When the engineers start feeling like sales people they feel dirty inside - they're not used to lying to the customer like sales are - they just want to deliver a good service.
When they realize you're pushing them towards sales they'll leave.
It is called a Sales Enginner (Score:4, Interesting)
...or sometimes a Solution Architect.
Most big tech companies (think SAP, Oracle, IBM, Red Hat) have a specific role for this. It is someone who could be an engineer but is specifically assigned to the sales process. Once the sales person has found the lead, the SE works with the customer to identify their needs and how best to meet them with the company's products. The sales person writes the deal and handles all the "sales" stuff.
Oh, and the SE gets a set percentage of the commission.
Perhaps? (Score:4, Interesting)
Comment removed (Score:4, Interesting)
Re:Inside vs. outside sales (Score:5, Interesting)
It's not about the % - the idea is ass backwards!
Instead of turning your highly skilled techs into sales people spend the money training your sales people to understand the tech. They don't need to understand the minutia but they should understand it well enough to be able to converse with a tech. Rather than having them hand off a client from one person to the next have your sale's guy be the primary and only contact point. They should never need to consult with the technicians as to how/whether something can be done rather only be able to understand and communicate exactly what the client needs.
Re:Let's look at that, okay? (Score:4, Interesting)
It has to do with honesty and the perception that the person you're talking to has your best interest at heart. People are generally pretty good at smelling a rat, and if your engineer is in the same boat as your customer - then there's a trust that's there that's generally pretty easy to work with. The problem breaks down if the engineer or sales person doesn't have a broader view of the coming problems, or architecture changes that might be necessary as this typically comes from pure experience.
Working for a large consulting arm of a large (now mostly defunct) technical company .. we really turned a corner when we convinced our mgmt that it was bad practice to always have to recommend our companies products - particularly when there were better products out there .. this also enabled us to work more closely with the backline engineers to either make things better, or eliminate dead weight. Honesty can go a long way in developing trust, and can help you either really believe in your product or take you to the place where you can help others understand what needs to be done for customers to believe in your product.
Re:Exactly. (Score:5, Interesting)
Our company uses an internal billing mechanism. Each sales person is allotted (x) hours of engineering time a month. Engineers are expected to perform (y) hours of consults with sales as part of their normal job (x and y are different because we have more sales people than engineers). Anything above (y) is considered bonus pay for the engineer and he earns extra pay at a relatively high hourly rate. The bonus pay comes directly from the sales person's commission. All engineering consults must be scheduled in advance through the project manager, to keep sales from killing our internal development timelines.
It works for us. Engineers get a chance to see the sales process, see what customers are doing with the product or what problem they want the product to solve, and a chance to earn extra pay. Engineers that have good social skills get requested by sales more often than others. The project manager is available to control the impact on our development. Sales people see the cost of having engineers on the call and thus are encouraged to keep it to a minimum or learn the technical details themselves.