Business Plan - Outline and Product descriptions

I want your feedback on the roadmap for LifeGraph software features and capabilities. The Life in LifeGraph refers to a natural and legal persons, which are expected to live to 100 years. The Graph in LifeGraph refers to the trajectory, orientation, configuration, and operation of the natural person, a product or an instance of nature as classified by some taxonomy or ontology. Ownership is the concept that filters or bounds the scope of LifeGraphs. If and when you think about LifeGraphs you should remember you are thinking about what a person owns and not merely possesses or is in proximity to something or someone. The mobile mirror world (MMW) I seek to make available to everyone with access to a computer is a world of items traded between legal and/or natural persons during the lifetime of the person. Moreover, the periods of life when a natural person is incapable of trading (strictly speaking) those items provided to him/her are treated as if he/she traded for them. Specifically, I'm referring to natural persons in infancy, childhood, etc. and senile seniors.

The following outline will serve as a guide for the next 20 posts. I found this Table of Contents at www.bplans.com for software companies. There are hundreds of samples to choose from so I am not going to put much energy into format now.

Executive Summary

Objectives

Keys to success

Mission

Company Summary

Products

Market Analysis Summary

Strategy and Implementation Summary

Management Summary

Financial Plan

Appendix

I hope to make LifeGraph software affordable to everyone who can afford any computer system, new or used--say $10 (2010 dollars). Ironically, I see a paper-based product developing concurrently with LifeGraph software that will sell for $100 (2010 dollars) a volume just to appeal to the traditionalists who will like an acid-free paper version bounded under hardcover to last a century. A volume is a decade's worth of object-oriented transactions pretty-formatted, indexed and printed for binding.

LifeGraphs are native XML databases with valid and well-formed XML documents that are encoded with the 3D geometry, 3D acoustics and 6-DoF haptics for tangible items (i.e., goods). These documents are either richly or poorly annotated with financial, legal, regulatory and operational safety parameters found on receipts, warranties, packaging labels, instructional manuals, notices, and other printed materials for the good. Services are XML documents that animate the behavior delivered. Since the recipient of the service may not own any of the goods to be in a configuration to receive the service, the standards for providing the 3D characteristics of those items are questionable. For example, if you buy a $300 ticket to attend the superbowl and you don't even get a paper ticket but just have to show two government issued ID cards, what does the ticket seller provide you for your LifeGraph?