Thanks for confirming my suspicions, I didn't really like adding anything to that original statement. I need to remember that just because the description is b

Thanks for confirming my suspicions, I didn't really like adding anything to that original statement. I need to remember that just because the description is brief and in many cases, not flashy, doesn't mean it can't be exciting. If you are discovering the next big thing, I guess a decent analogy would be a sailor spotting a small, nondescript distortion on the horizon. Could that be land?! The public speaking isn't a problem, VR is a new form of training for the Fire Service which will allow users to become overwhelmed by simulated chaos, identify their weaknesses and correct them. In regards to what my customers want, well, I started this years ago because I wanted a product that didn't exist. It's more than that however, there are multiple stakeholders for a single product: Mind you, these stakeholders could widely vary: Fire Officer - USER - (he is in the trenches, on the streets) Battalion/District - USER/Possible Customer (Taking a more supervisory role, although still runs larger scenes) Fire Chief - CUSTOMER - Typically will approve a budget to be submitted County/City Manager/Councilmember/Mayor/ETC - CUSTOMER'S BOSS - Approves Budget submitted by Fire Dept Taxpayers - CUSTOMER'S BOSS's BOSSES - Can complain of wasteful spending While any weighting I could give to these would be subjective, I obviously gear my product and marketing towards the user and the customer. When speaking with a Fire Chief, I invite him to consider putting their City manager INSIDE the VR simulator so they can see how challenging his job is and why he is requesting the budget he's requesting. (involuntary empathy) Thank you for taking the time to respond to my comment!