I want to establish a perks program for my members by offering them discounts from travel partners like airlines, hotels, etc.

The idea of an MVP is 'minimum, viable' ... If you feel you need a "good amount" of funding, I would challenge if you are minimum enough. Obviously, without knowing the details of your product, your ideal customer, or what need you will solve, it is hard to help expose what is necessary in an MVP and what is a Phase II or Phase III feature. I am happy to help you work through this, or answer specific questions, to get you rolling. Just book a call with some times that will work for you. Regardless, I would love to know more about it and how it goes after launch. To your success, -Shaun

Yes. Who I would recommend would depend on what you'd like to see happen. Are you building only for iOS, or only for Android, or both? Will you have a bunch of content/stuff in your app or just a little? Are you thinking game or non-game app? Do you already have a big fanbase or would you be trying to build one while building the app? It's easy to save a bunch of money on mobile development if you know how, and even easier to overspend. Making an app can be a ton of fun or a major headache. I'd recommend the fun. So if you want an outside perspective, give me a ring.

2 different categories come to mind. H&R Block or other tax preparation services. The second is restaurants. This may seem like a product more than a service but I think it truly falls into the category of service, especially if you look at the national chains. Think Applebee's, TGI Fridays etc. The reason people go to these places is because of the experience they receive. The franchisors have created a system that generates nearly identical results nationwide. The first thing you need to do is figure out what makes your service superior to others out there, then you need to figure out how and why this is the case. From there you need to document it and make sure that you have a mechanism in place to ensure compliance. Granted that is a huge amount of work, but the basic premise is quite simple. You want all of the people you hire to do things more or less the way you would do them.

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 :).

It varies and it's very very specific to what you want to develop. The concrete design of your circuit matters. Also prototype building costs are usually a factor 10-100 higher than series. If you already have your prototype then you can shop around various manufacturing companies. To do that, you need Gerber files (your PCB design) and a bill of materials. You also need to think about casing: designing it and creating the mold is expensive. If you don't have your prototype yet, I recommend having it engineered in eastern Europe. Custom engineering is cheap there and high quality. IP protection is a problem. One thing to do is to distribute the work to different manufacturers. For the design phase you are safer if you design your prototype in Europe or the US where international patent laws apply. I could give you more specific advise in a phone call, getting to know a bit better what you are trying to build.