Where can I find top notch Lamp Stack engineers with the business know how and VC connections?

Very little. At the angel/seed stage, they're investing in the founders, so there's no expectation of patents, etc... They might check that you're incorporated in good standing, and ensure you have a solid startup/corporate lawyer, and have good employment and IP ownership agreements with your staff and contractors, and that's about it.

Convertible notes are by no means "earned." They are often easier to raise for early-stage companies who don't want to or can't raise an equity round. Equity rounds almost always require a simultaneous close of either the whole round or a defined "first close" representing a significant share of the raised amount. Where there are many participants in the round comprised mostly of small seed funds and/or angel investors, shepherding everyone to a closing date can be very difficult. If a company raises money on a note and the company fails, the investors are creditors, getting money back prior to any shareholder and any creditor that doesn't have security or statutory preference. In almost every case, convertible note holders in these situations would be lucky to get pennies back on the dollar. It would be highly unusual of / unheard of for a convertible note to come with personal guarantees. Happy to talk to you about the particulars of your situation and explain more to you based on what you're wanting to know.

There are three questions here: - the strike price of the options - the market value of the company - how much those options are actually worth to the recipient 1. The strike price is the price people pay to exchange their options for shares. You can set any strike price you like: it's just a negotiable contract term. However, if the strike price is less than the market value of the shares, the options are taxable (which people tend to avoid), so you typically set the strike price at or above the market value. 2. The market value of the company is how much the company is worth. The celebrity of the founder is clearly a big part of it. If the company were sold, the acquirer would want the founder to lock in as part of the acquisition. So figure out the value a couple of ways: (1) off standard profitability metrics: X times yearly profit and/or revenue vs. comparable companies (2) off the acquisition price: with and without the founder and add the percentage chance the founder would go with it (3) off recent transactions in the stock (what people pay for the stock is a great indicator of value) These will give three different answers: pick some sort of average number, so you can justify your strike price. 3. What the options are worth to the recipient: remember they are only worth something if the recipient can exercise them for stock, and then sell the stock (or receive dividends) for more than the option's strike price. So figure out the probability of the company being sold above the strike price in the next X years, and what an weighted average expected sale price is for the company in the next few years (noting the founder's importance), and that's what the options are worth. I hope that helps.

I am assuming your question is more pertaining to empowering and motivating (rather than hiring). I can outline some of the practices I have seen really result in high motivation and sense of ownership among engineering teams: * Empathize - Your engineering team will work well and be more motivated if they see you as one of them rather than a person who doesn't understand their function. Show your geeky side to them, and show that you understand their thought process and drivers. * Pick their brain on big and small decisions (roadmap, usability, whatever it is) - Product teams value being heard. The more you position yourself as someone who is WANTS to listen, is keen to have their inputs, you will be surprised at how involved they can get, and also how you can actually tap into a lot of smart ideas/thoughts from them that you can develop on. * Take care to explain - show how you arrive at decisions. Share your research, competitive analysis, and even your thought process on arriving at a feature set or list of things for a release. Its stuff you would have worked on anyway - so no harm sharing with more eyes! * Share customer feedback - nothing motivates your engineers than a positive interaction with a customer. Get them to see customer feedback. Have them sit in and observe some of the usability studies. (B2B - have them see you do some demos or do a successful sales pitch) * Send out interesting articles, insights, business and tech articles with your comments/highlights to them on a regular basis (maybe twice a week?) - maybe even some analysis you did on competition or customer feedback * Engineers like working with people they feel are competent and complement the work they are doing to build a great product. So make sure they see how everyone else around them is also doing a good job and adding value and contributing to the success of the product. * Be transparent about the product/business - Make them feel they are responsible and involved in the business, not just technology. I've seen engineering teams happy about their annual goals having components relating to making revenues, keeping customers happy, or reducing costs. If they are enthused about the business as a whole, they will be more motivated with their engineering efforts * Have a mix of little experiments, R&D, attending to engineering debt, in addition to bug fixes and new features that each engineer gets to spend some time on (based on their interest) * Finally get to know each of your engineers personally, and be aware of what their priorities are. Each of us has different motivations in life, so there is no silver bullet to motivate people. When they know you care for them, they are more motivated :).

I like to take a rule from the Steve jobs playbook and use simple circles... one larger than the other but no more than 2. your most immediate target (realistic reachable) and one of the "enemy" competitor company. or overall untapped market cap. **for this to be effective you must provide as accurate projections as possible** no bar graphs and as little or no text as possible... remember that a deck is a companion to the speaker... avoid bullet points and use the deck to entertain rather than educate... is not a class is a pitch. :)