Ask HN: $1,500,000 in sales, who to hire next?
My startup has reached $1.5 million in sales. Right now, we have 3 people, and I'm the technical guy and handles every including server administration.
I want to expand my business and relieve myself from the technical role. I'm having a hiring dilemma:
Option 1: Hire a system admin to maintain the current system. He might not be a superstar but he will take care of the current system. Later on, hire someone with more experience/knowledge.
Option 2: Hire an architect type of person where he will be able to handle the current system and able to expand future systems. This person will be someone like a chief technical officer.
Option 2 will take longer to search so I will be stuck in the technical position for awhile. Option 1 will immediately relieve me from the technical duties so I can build the business.
Which one should I take? Do Option 1 now and expand search later or wait for Option 2?
14 comments
[ 2.6 ms ] story [ 19.9 ms ] threadHowever, I am pretty much assuming CTO equity is in the offer.
This gives you some room to think about the business and where you should be prioritizing your efforts (sales, product, marketing, biz-dev).
Contact me at freelanceadmin@forward.cat (email valid until 25th april)
Your ability to grow is tied to two things:
1) The health of any business is measured by the rate at which it is getting new customers.
2) To provide fulfillment to said new customers, you have to make sure you are thinking about your architecture.
If you get the sales first, you may hit the need to scale your architecture, or not.
Whatever you do try to be aware that management by abdication is not managing or scaling -- no matter what you do during a growth phase you will be putting in just as much energy and attention as ever.
Also I would consider hiring a less senior person for your first technical hire, at least initially. If you hire the wrong person into the CTO role, they are gonna push you to refactor, re-architect, or in some cases completely re-write your code. Be very careful about who you hire into this role and make sure they have a realistic understanding of how startup quality code gets built.
For example I consider myself more of a 2 of the two types listed here. I am a builder and would never accept a sysadmin job. It would be boring to me.
Perhaps the fact that there are tools out there which automate repetitive sys admin tasks is a sign that these types of people have been placed in these jobs before and they did what they do best. Perhaps that's even reason enough to place them in these jobs to begin with. I may have just talked myself out of thinking this is a bad idea...