Online Document Hosting, E-signature, and Insurance Transact

A cloud based document hosting service which allows users to conduct insurance transactions with clients. Web interface has a unique built-in e-signature solution. The system uses a standard folder structure but also has tagging features. Other features include document versioning, syncronization with local folders and files, and drag and drop support. Web Interface Description: Simple 2 column layout – left column holds file structure and list of contacts, right column shows document. Files searchable based on name and content and “tags” Files can be commented on and PDFs can be marked up but not edited. Documents need to be rendered as quickly as possible and in a method that can be viewed on an ipad. Need to be able to render all PDF’s, MS Office file formats and .MSG files (Outlook email files). Organization: Folder structure Folders and subfolders can be created, moved, renamed, shared and made visible or not with admin privileges. “Tags” Each user can create unlimited “Tags” which can be applied to any folder or file. Data can then be sorted or searched via tags. Two types of tags: user generated and tags associated with a contact record. Contact Records: Clients can be setup as outside (outside of organization) users. Their contact record will be used for interacting with them using the system as described in next section. Collaborating with Contacts: The site is designed to enable a user to complete an entire insurance transaction with client online. E-Signatures: There is an e-signature system that works in the following manner: Any inividual page in a PDF can can be marked for signature. The e-signature box needs to be "exact placement" meaning that it can be graphically placed by the user anywhere on the document. The user has a choice of allowing the signer to see all the pages of the PDF or just the ones that are marked for signature. There needs to be a system that allows user to mark pages from multiple PDF's for signature. The system should assume that the signer is the person in the contact record that is tagged to the folders or a contact can be manually selected. Marking a page for signature automatically initiates an e-signature "session". A button appears that the user will press when he is finished marking pages for signature at which point he can move on to setting up the signer's billing session. Billing system: User can setup an online invoice as part of this transaction. After e-signing his pages, a client will be taken to a payment page where he will enter checking account information. This needs to be a secure session but since credit cards won't be accepted at first, we won't need a payment gateway. We'll build credit card processing into a future version. After completing the e-signature and billing setup, the user will be able to select from a set of saved messages or type a new one. The message will go out with a link to the client to complete his transaction. There should also be an option for automatic reminders to go out on a scheduled basis containing the link. Desktop Client The desktop client should include the same functionality as the web interface with the addition of the following functionality: - Application conceals itself but is always available as a small tab over all windows at edge of screen. - Drag and drop a file into a folder uploads that file to that folder online. - Opening a file from the desktop client gives option of opening it online, or downloading it (depending on permissions). If the file exists locally, the local file will be opened. - File sync: The desktop client will install a contextual menu item which allows user to mark any folder for sync. When a folder is added to sync, the software initially creates the folder online and then uploads content to it. When another user makes a change a new version is created. If a user has a local copy of a file that was changed, the new version will be downloaded and replace current version. If a file is deleted, the online copy should be moved to a recycle bin to make it available for restore for 30 days after which it should be deleted from server.