f setting up the whole environment will be making sure that all the parts work together. Integrating all the various software components will require extensive testing in both functionality and performance. The system will have to be flexible enough to handle all the software we plan on plugging into it as well as be robust enough to handle the load of a large number of concurrent users hitting the system and straining available resources.The biggest risk we face is having the hardware and software in place but disappointing our users through non-availability, slow response, or offering functionality that they either do not want or do not need. It should be possible to sing up clients because of the promise of user friendliness and innovative product offerings. Keeping them as clients will require that we keep them happy providing a level of service that we have promised.5.3 Proprietary IssuesPropriety issues include the content that we will be providing to our clients, data about our clients that we store on our servers, and our business “best practices” that will allow us to server our clients.Client issues can be handled through appropriate segregation of customer data. We will do this by setting up separate databases, Virtual Private Networks, and logins for each client. This should ease any fears of data contamination as well as allow us to better manage our proprietary data by marking it specific to each customer.6. The Financial Plan6.1 Actual Income Statements and Balance Sheets6.1.1 Expenses2001200220032004Staffing494,992 791,339 2,302,619 6,227,837 Technology729,523 904,251 1,198,932 1,620,195 Projects1,920,000 71,533 60,000 136,023 Other70,000 70,000 70,000 70,000 TOTAL $3,214,514 $1,837,124 $3,631,552 $8,054,056 6.1.2 Revenue2001200220032004Revenue$689,456.06 $2,625,286.25 $11,202,679.85 $25,011,536.56 Expenses$3,349,089.19 $2,044,441.62 $4,241,547.64 $9,634,079.27 Net Profits/(loss)($2,659,633.13)$580,844.63 ...
