What is the right ratio of sales and customer handling staff VS other staff?

I would be curious to know why you feel it is important to use personality testing. I have hired over 20 sales reps and I have never used any testing. I have conversations with my hires because that is going to tell me more about their personality any day than a test. Plus you might eliminate someone because of a test score that could be a great fit for your organization. I have a pretty strong process for hiring sales people and could share with you my steps and even the questions if you would like.

Instead of looking at who does what .. why not look at the things that need to get done for a small techology team. Product: 6 people - 3 full stack engineers - 2 front end developers - 1 designer / product person Marketing & Community, 1 person - Full time hire, or CEO Support & Operations, 1 person - Part time hire, or CEO + Whole team I believe it's important for everyone on the team to help with support. Also, if you have a great product, then support shouldn't be that taxing. Q&A is usually needed when you have a bad development process (no unit testing or continuous integration deployments). Outsource everything else. - Bookeeping - HR stuff - Legal - Government program paperwork Hope that helps. P.S. I would put as many people on product as that's where you'll get the most bang for your buck.

Some of this is stage dependent and all of it is highly dependent on the team above the product manager. The simplest answer of course is to find PM's from companies who have had exemplary success where the Product Manager candidate either led prior success or was exposed to it in a meaningful way. A simple starting point is to ask them to give you examples of conflicting opinions on a feature and how they evaluated the conflicting opinions and made a decision and tracked the success or failure of that decision. AirBnb actually gives PM's homework as part of the interview process where they have to actually present a unique idea (from scratch) to the interviewing team. Happy to talk to you about best process based on your stage and existing team.

Please resist the urge to pull the band-aid. I'm not a fan of keeping a poor performer, but unless this person is a behavioral or "for cause" termination, he deserves some professionalism here. 30-day Performance Plan, make the goals aggressive and stick to it - he can consider that his head start to either buck up or start searching. Remember, your other employees watch how you treat their former colleagues. A quick termination before a holiday is prickish, an aggressive performance plan is taking care of business.

I'll divide your question into 2 questions, because I am not sure which one you're really asking :-) 1. Should I hire him despite the costs involved? You seem to already agree to this, based on what you wrote ("I am willing to set aside...assuming I see some ROI..."). 2. How to I justify his high salary to other employees? A few options: a. You don't tell them. b. The CEO's compensation can be structured in a way that his 'salary' isn't that high (and this is what the other employees will see - so no problems), and he gets a large bonus based on results (which could be measured within 6 months and then 12 months). This is also better for you seeing that you don't know how good is will be. Additionally, if he is so confident he can do the job, he shouldn't object to that structure. c. Make it clear to your employees, that if he manages to generate more income for the company, they too will benefit from it (end of the year bonus/increased salaries/holiday gifts?). d. the tough option: tell them that if you don't make some hard choices, there won't be a company for them to work at down the line (due to the yearly decrease in profits) It's your company (which you seem to have managed successfully), so I am sure that you know what would work best with your employees. I'm happy to help you construct the employment contract with the potential adviser. Good luck p.s.: let me know how things turned out. I'm curious :-)