SELF-QUOTING SYSTEM FOR LIFE CONTINGENT AND GUARANTEED FUTURE PAYMENTS

Abstract

A self-quoting system for life contingent payments and guaranteed future payments for charting health viability, for assisting a structured settlement provider in formulating lump sum payment offers for a recipient, in the form of real-time instant quotes, the system including a multi-tiered network, wherein a first tier of the multi-tiered network comprises a computing device having a user interface, wherein the user interface is operable to display a series of consecutive tabular forms displaying sets of field parameters pertaining to a recipient's identification, structured settlement payment information, history and lifestyle. The system further includes a second tier in communication with the first tier, the second tier including an application server configured for manipulating data responsive to the field parameters, for executing and generating an instant quote; and a third tier in communication with the second tier, configured for storing data responsive to the field parameters and the instant quote.

Claims

1. A self-quoting system for life contingent payments and guaranteed future payments, for assisting a structured settlement provider in formulating lump sum payment offers for a recipient, the system comprising: a multi-tiered network, wherein a first tier of the multi-tiered network comprises a computing device having a user interface, wherein the user interface is operable to display a first tabular form comprising a first set of field parameters, for receiving and displaying a first set of data responsive to the first set of field parameters; a second tier of the multi-tiered network in communication with the first tier, wherein the second tier comprises an application server for receiving the first set of data responsive to the first set of field parameters from the first tier and wherein the application server is configured for manipulating the first set of data responsive to the first set of field parameters and for executing and generating a first set of calculations thereon; a third tier of the multi-tiered network in communication with the second tier, wherein the third tier includes a database server configured for storing data within the multi-tiered network, whereby data stored in the database server includes the first set of data responsive to the first set of field parameters and the first set of calculations executed and generated by the second tier.

2. The system of claim 1, wherein in response to a command by the user, the user interface is operable to display a second tabular form comprising a second set of field parameters, for receiving and displaying a second set of data responsive to the second set of field parameters, and wherein the second tabular form is displayed consecutively and subsequently to the first tabular form; the system of claim 2, wherein the second tier is configured to receive the second set of data responsive to the second set of field parameters from the first tier and wherein the application server is configured for manipulating the second set of data responsive to the second set of field parameters and for executing and generating a second set of calculations thereon; and wherein data stored in the database server includes the second set of data responsive to the second set of field parameters and the second set of calculations executed and generated by the second tier.

3. The system of claim 2, wherein in response to a command by the user, the user interface is operable to display a third tabular form comprising a third set of field parameters, for receiving and displaying a third set of data responsive to the third set of field parameters, and wherein the third tabular form is displayed consecutively and subsequently to the second tabular form; the second tier is configured to receive the third set of data responsive to the third set of field parameters from the first tier and wherein the application server is configured for manipulating the third set of data responsive to the third set of field parameters and for executing and generating a third set of calculations thereon; and wherein data stored in the database server includes the third set of data responsive to the third set of field parameters and the third set of calculations executed and generated by the second tier.

4. The system of claim 1, wherein the application server of the second tier of the multi-tiered network generates a lump sum payment quote that is instantaneously relayed to the first tier of the multi-tiered network for transmission to the user, and wherein the lump sum payment quote is simultaneously transmitted instantaneously to the database server of the third tier of the multi-tiered network for storage.

5. The system of claim 2, wherein the application server of the second tier of the multi-tiered network generates a lump sum payment quote that is instantaneously relayed to the first tier of the multi-tiered network for transmission to the user, and wherein the lump sum payment quote is simultaneously transmitted instantaneously to the database server of the third tier of the multi-tiered network for storage.

6. The system of claim 5, wherein the lump sum quote reflects a guaranteed payment offer.

7. The system of claim 3, wherein the application server of the second tier of the multi-tiered network generates a lump sum payment quote that is instantaneously relayed to the first tier of the multi-tiered network for transmission to the user, and wherein the lump sum payment quote is simultaneously transmitted instantaneously to the database server of the third tier of the multi-tiered network for storage.

8. The system of claim 7, wherein the lump sum quote reflects a life contingent payment offer.

9. The system of claim 6, wherein the application server executes and generates lump sum payment quote comprises a first numerical figure, wherein the first numerical figure is a minimum upfront lump sum payable to the recipient and a second numerical figure, and wherein the second numerical figures is a maximum upfront lump sum payable to the recipient.

10. The system of claim 8, wherein the application server executes and generates lump sum payment quote comprises a first numerical figure, wherein the first numerical figure is a minimum upfront lump sum payable to the recipient and a second numerical figure, and wherein the second numerical figures is a maximum upfront lump sum payable to the recipient.

11. The system of claim 6, wherein the lump sum payment quote is initially revealed and displayed to the user for a first period of time.

12. The system of claim 8, wherein the lump sum payment quote is initially revealed and displayed to the user for a first period of time.

13. The system of claim 10, wherein the user is prompted to enter a unique code generated by the system and transmitted to the user, for verification in order to retrieve the lump sum payment quote for a second period of time subsequent to the first period of time.

14. The system of claim 10, wherein the first period of time is within a range of 1 to 10 seconds.

15. The system of claim 1, wherein the first set of field parameters includes a first plurality of fields, wherein the first plurality of fields solicits a response to variously identify, the recipient's first name, the recipient's last name, an insurance company, wherein the insurance company identifies a structured settlement company providing monetary payments to the recipient, the recipient's age, gender or e-mail.

16. The system of claim 2, wherein the second set of field parameters includes a second plurality of fields, wherein the second plurality of fields solicits a response to variously identify, a payment type, wherein the payment type is a life contingent payment or a guaranteed payment, a payment start date, wherein the payment start date is the date that a structured settlement company starts or started providing monetary payments to the recipient, a payment end date, wherein the payment start end date is the date that a structured settlement company will stop providing monetary payments to the recipient, a payment amount, a payment frequency, wherein the payment frequency identifies a period payment, including weekly, monthly, quarterly, semi-annual or annual period payments, a payment amount, wherein the payment amount identifies the payment amount disbursed to the recipient within the period payment; and an annual increase percentage rate, wherein the annual increase percentage rate ranges from 1 to 10.

17. The system of claim 3, wherein the third set of field parameters includes a third plurality of fields, wherein the third plurality of fields solicits a response to variously identify the recipient's personal attributes, wherein the personal attributes relate to the recipient's height, weight, health profile and status, including smoking status, blood pressure, and driving record, including suspensions of driver license, driving under the influence, driving while intoxicated.

18. The system of claim 1, wherein the database server includes a source available cross platform, document oriented, database program.

19. The system of claim 2, wherein the data stored in the database server includes the lump sum quote.

20. The system of claim 3, wherein the data stored in the database server includes the lump sum quote.

21. The system of claim 1, wherein a cloud server is in communication with the first tier and the second tier, whereby the first set of data is transmitted to the second tier via the cloud server.

22. The system of claim 5, wherein a cloud server is in communication with the second tier and the first tier, whereby the lump sum payment quote generated by the application server of the second tier is instantaneously relayed to the first tier via the cloud server.

23. The system of claim 3, wherein data responsive to the third set of field parameters is auto-filled with data configured to provide the recipient with an optimum payment offer

Description

BRIEF DESCRIPTION OF THE INVENTION

[0030] FIG. 1 is a flow chart of the system and method of the present invention illustrating the process of using an interface to generate a quote.

[0031] FIG. 2 is a conceptual block diagram illustrating an embodiment of a first step in the process relating to the first tabular form displayed in the first tier of the networking system of the present invention.

[0032] FIG. 3 is an illustration of an embodiment of a display of the first tabular form as it would appear on a computing device when using the system and method of the present invention.

[0033] FIG. 4 is a conceptual block diagram illustrating an embodiment of a second step in the process relating to the second tabular form displayed in the first tier of the networking system of the present invention.

[0034] FIG. 5 is an illustration of an embodiment of a display of the second tabular form as it would appear on a computing device when using the system and method of the present invention.

[0035] FIG. 6 is a conceptual block diagram illustrating an embodiment a third step in the process relating to the third tabular form displayed in the first tier of the networking system of the present invention.

[0036] FIG. 7 is an illustration of an embodiment a display of the third tabular form as it would appear on a computing device when using the system and method of the present invention.

[0037] FIG. 8 is a conceptual block diagram illustrating the interconnection of the first, second and third tiers of the networking system of the present invention

[0038] FIG. 9 illustrates the cloud base hosting aspect of the present invention in connection with a user interface and the second tier, or backend server in relation to the third tier, or application server of the present invention.

[0039] FIG. 10 is a conceptual block diagram illustrating an embodiment of the process of the system and method of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0040] The terms customer or client may be used throughout to refer to a recipient of a structured settlement plan. The term user is used throughout to refer to the user of the invention. It is appreciated that a user may include by way of example and not limitation, a client, a recipient, a sales associate or agent.

[0041] Referring now to FIGS. 1-10, there are shown illustrations of a process for a life risk analysis system and method 1 for generating life contingent payments for a potential client and/or recipient. The system 1 includes a multi-tiered network 100 including a first tier 110, a second tier 120 and a third tier 130. The first tier 110 includes an Internet browser on a computing device 140 such as for example, a desktop or smart phone. The second tier 120 includes an application server 150 for processing data and generating quotes 170 and the third tier 130 includes a database server 160 for storing data and quotes.

[0042] In particular, FIG. 1 is a flow chart of the system 1 of the present invention illustrating an overview of the process 1. As shown a user 2 employs a user interface 3 to generate a quote/discounted range 72. The user 2 completes a first step 10 relating to a recipient's account information, a second step 20 relating to a recipient's payment information, and a third step 30 relating to a recipient's basic information, wherein the user 2 provides the recipient's account information in the first step 10, the recipient's payment information in the second step 20, and the recipient's basic lifestyle information in the third step 30.

[0043] In a fourth step 40 the user 2 submits data compiled from the first step 10, the second step 20 and the third step 30, such that the account information of the first step 10, payment information of the second step 20, and basic lifestyle information of the third step 30 is submitted for processing. In a fifth step 50 data from the first step 10, second step 20 and third step 30, and data submitted in the fourth step 40 is directed to the application server 150 of the second tier 120 (shown in FIGS. 8 and 9) for calculating and generating a discounted rate range. Data generated from the first step 10, second step 20 and third step 30, and the discounted range quote 72 generated by means of the application server 150 of the second tier 120 is stored in the database server 160 of the third tier 130 (shown in FIGS. 8 and 9).

[0044] The user 2 may proceed to a first alternative fourth step 41 of submitting data directly from the second step 20, thereby effectively bypassing the third step 30. Data submitted in the first alternative fourth step 41 is directed to the application server 150 of the second tier 120 (shown in FIGS. 8 and 9) of the multi-tiered network 100 (shown in FIGS. 8 and 9) for calculating/generating a discounted rate range 72. Data generated from the first step 10 and the discounted data range 72 generated by means of pursuing the first alternative fourth step is stored in the database server 160 of the third tier 130 (shown in FIGS. 8 and 9) of the multi-tiered network 100 (shown in FIGS. 8 and 9).

[0045] In yet another embodiment, the user 2 may proceed to a second alternative fourth step 42 of submitting data from the first step 10, the second step 20 and the third step 30. Data submitted in the second alternative fourth step 42 is directed to the application server 150 of the second tier 120 of the multi-tiered network 100 (shown in FIGS. 8 and 9) for calculating/generating a discounted rate range 72. Data generated from the first step 10 and the discounted data range 72 generated by means of pursuing the second alternative fourth step 42 is stored in the database server 160 of the third tier 130 of the multi-tiered network 100 (shown in FIGS. 8 and 9).

[0046] In FIG. 2 there is shown a conceptual block diagram illustrating an embodiment of the first step 10 in the process 1 relating to a first tabular form 12 of the first step 10 displayed in the first tier 110 of the multi-tiered network 100 (shown in FIG. 11) of the present invention, wherein the first tabular form 12 includes a first plurality of fields 12.1-12.6. Thus, there is shown the first plurality of fields 12.1-12.6 within the first step 10. In particular the user 2 (shown in FIGS. 1, 10) is prompted to enter the recipient's first name in a first field 12.1, the recipient's second name in a second field 12.2, an insurance company name in a third field 12.3, wherein the insurance company name may be selected from of list of potential providers, and wherein the insurance company name further provides an-option for the user 2 (shown in FIGS. 1, 10) to select “other” as an option for the insurance company name.

[0047] The first tabular form 12 of the first step 10, additionally include fields for the recipient's age 12.4, the recipient's gender 12.5. In a preferred embodiment, optional fields for the gender 12.5 include by way of example, male female or prefer not to tell. Field 12.6 includes an optional field for an email address 12.6. In an embodiment, fields 12.1, 12.2, 12.3, 12.4, 12.5 and 12.6 may not be skipped by the user and data responsive to fields 12.1, 12.2, 12.3, 12.4, 12.5 and 12.6 in the first tabular form 12 must be provided by the user.

[0048] FIG. 3 is an illustration of an embodiment of a display of the first tabular form 12 of the first step 10, as it would appear on a computing device 140 when using the system and method 1 of the present invention. As shown, the user 2 (shown in FIGS. 1, 10) completes the first plurality of fields 12.1-12.6 of the first step 10 (as shown in FIG. 2) of first tabular form 12. The user 2 (shown in FIG. 1) enters the first name in field 12.1, the last name in field 12.2, the insurance company name in field 12.3, the age in field 12.4, the gender in field 12.5 and the e-mail address in field 12.6. The recipient's data responsive to the first plurality of fields 12.1-12.6 is displayed to the user 2 (shown in FIGS. 1, 10)) on a screen 142 of the computing device 140.

[0049] FIG. 4 is a conceptual block diagram illustrating an embodiment of the second step 20 in the process relating to a second tabular form 22 of the second step 20 of the system and method 1 of the present invention displayed in the first tier 110 (shown in FIG. 11) of the multi-tiered networking system 100 (shown in FIG. 11) of the present invention. A second plurality of fields 22.1-22.6 includes a field for a payment type 22.1, a field for a payment start date 22.2, a field for a payment end date 22.3, a field for payment amount 22.4, a field for payment frequency 22.5 and a field for an annual percent increase 22.6. An annual percent increase 22.6 offsets inflation. In an embodiment, fields 22.1, 22.2, 22.3, 22.4, 22.5 and 22.6 may not be skipped by the user and data responsive to fields 22.1, 22.2, 22.3, 22.4, 22.5 and 22.6 in the second tabular form 22 must be provided by the user.

[0050] In one embodiment, the annual percent increase 22.6 is a figure determined to offset the cost of inflation. For example, a structured settlement may commence at $1000 a month with an annual three percent increase. The payment type 22.1 is optionally a life contingent payment or a guaranteed payment. The field for the payment start date 22.2 represents the date when recurring payments made to a recipient begin. It is understood that the user 2 (shown in FIGS. 1, 10) may also be the recipient. The field for the payment end date 22.3 is the date when recurring payments made to a recipient end. The field for the payment amount 22.4 is the amount of each recurring payment received by the recipient. In one embodiment, the field for payment frequency 22.5 may be categorized to include a field for weekly payments, monthly payments, quarterly payments, semi-annual payments or annual payments.

[0051] FIG. 5 is an illustration of an embodiment of the second tabular form 22 as it would appear on the display 142 of the computing device 140 (shown in FIG. 6) when using the system and method 1 of the present invention. The user 2 (shown in FIG. 1) completes the second plurality of fields 22.1-22.6 of the second step 20 of the second tabular form 22 (as shown in FIG. 4), the user 2 (shown in FIG. 1) enters the payment type in the first field 22.1 of the second tabular form 2, the payment start date in a second field 22.2 of the second tabular form 22, the payment end date in the third field 22.3 of the second tabular form 22, the payment amount in the fourth field 22.4 of the second tabular form 22, the payment frequency in the fifth field 22.5 of the second tabular form 22 and the annual increase in the sixth field 22.6 of the second tabular form 22 as a percentage rate. Data responsive to the second plurality of fields 22.1-22.6 is displayed on the screen 142 of the computing device 140.

[0052] FIG. 6 is a conceptual block diagram illustrating an embodiment of a third plurality of fields 32.1-32.6 relating to a third tabular form 32 of the third step 30 of the system and method 1 displayed in the first tier 110 (shown in FIG. 11) of the multi-tiered networking system 100 (shown in FIG. 11) of the present invention. The third plurality of fields 32.1-32.6 includes a field directed to an inquiry into the recipient's height 32.1, wherein in a preferred embodiment, the field for the height 12.8 is within a range having a minimum height and a maximum height. In a preferred embodiment, the minimum height is 3 feet and the maximum height is 7 feet and 7 inches. The third plurality of fields 32.1-32.6 further includes a field directed to an inquiry into the recipient's weight 32.2, wherein in a preferred embodiment, the field for weight 32.2 is required to be within a range having a minimum weight and a maximum weight.

[0053] In a preferred embodiment, the minimum weight is 75 pounds and the maximum weight is 400 pounds. The third plurality of fields 32.1-32.6 further includes a field directed to an inquiry into whether the recipient smokes 32.3, wherein an acceptable response includes a field for yes or no. The third plurality of fields 32.1-32.6 further includes a field directed to an inquiry into a health profile of the recipient 32.4. The third plurality of fields 32.1-32.6 further includes a field directed to an inquiry into a driver's record, including driver license suspension in the last five years 32.5, wherein acceptable responses include fields for yes, no or prefer not to answer. The third plurality of fields 32.1-32.6 further includes a field directed to an inquiry into the recipient's blood pressure 32.6, wherein acceptable responses include fields for normal, medicated, high, not sure or prefer not to answer. In an embodiment, fields 32.1, 32.2, 32.3, 32.4, 32.5 and 32.6 may not be skipped by the user and data responsive to fields 32.1, 32.2, 32.3, 32.4, 32.5 and 32.6 in the third tabular form 32 must be provided by the user.

[0054] FIG. 7 is an illustration of an embodiment of a display of the third tabular form 32 as it would appear on the computing device 140 when using the system and method 1 of the present invention. As shown, the user 2 (shown in FIGS. 1, 10) completes the third plurality of fields 32.1-32.6 of the third step 30 of the third tabular form 32 (shown in FIG. 6). The user 2 enters a response to inquiries regarding the recipient in fields directed to the recipient's height 32.1, weight 32.2, smoking habits 32.3, the recipient's health profile 32.4, driving record, including record of driver license suspension in the last five years 32.5 and the recipient's blood pressure 32.6. Data responsive to the third plurality of fields 32.1-32.6 is displayed to the user 2 (shown in FIG. 1) on the computing device 140.

[0055] FIG. 10 is a conceptual block diagram illustrating an embodiment of the process of the system and method 1 of the present invention. In order for a user 2 to calculate an offer 170, data pertaining to a recipient is inputted into the system 1. The first step 10, is to input data in the first plurality of fields 12.1-12.6 of the first tabular form 12. The second step 20 allows the user 2 to input data in the second plurality of fields 22.1-22.6 of the second tabular form 22. The third step 30 allows the user 2 to input data in the third plurality of fields 32.1-32.6 of the third tabular form 32. Optionally, the user 2 may elect to skip the third step 30. The user 2 is invited to accept terms and conditions 80. If terms and conditions are not accepted, the system 1 will process an error 82. Once the user 2 submits 40 data the system 1 may prompt the user 2 to enter the phone number 78. The user 2 may elect to go back to a prior step, in which event a pop will appear to advise the user 2 that “[t]he information entered will be erased and the process will be restarted.” If terms and conditions 80 are accepted by the user 2 data entered from the first form 10, second form 20 and third form 30, is submitted 84 for processing to the application server 150 of the second tier 120 of the multi-tiered networking system 100 to calculate the offer or discounted rate range 72. The next step in the process is to store the recipient's data in the database server 160 of the third tier 130 of the multi-tiered networking system 100. An operation decision 86 is made to offer a discounted range 72 The user 2 is invited to enter a phone number 78 and enter a verification code 88 in order to view the offer or discounted rate range 72.

[0056] FIG. 11 is a conceptual block diagram illustrating the interconnection of the first tier 110, a second tier 120 and a third tier 130 of the multi-tiered networking system 100. There is shown communication between the first tier 110 and the second tier 120, whereby the first tier 110 relays data to the second tier 120 which includes the backend or application server 150 and wherein the first tier 110 receives data from the second tier 120. The first tier 110 is a client tier and may include a web browser on the computing device 140. The computing device 140 may be a desktop, laptop, smartphone or the like. The second tier 120 is preferably a business logic tier and includes the application server 150 for receiving and processing data transmitted from the first tier 110. The second tier 120 transmits data to the third tier 130. The third tier 130 is preferably a database tier including the database server 160 for storing data received from the first tier 110 and the second tier 120. The third tier 130 may also transmit stored data to the second tier 120, where it can be further transmitted to the first tier 110.

[0057] FIG. 12 illustrates the cloud base hosting aspect of the system 1 whereby the first tier 110 includes and/or is a client server and includes the user interface 3, such as a browser on the computing device 140 (shown in FIGS. 3,5,7,9) in communication with the second tier 120 via a cloud-based server 200. The second tier 120 includes and/or is a backend or application server 150 and transmits data to and receives data from the third tier 130, wherein the third tier 130 includes and/or is a database server 160.

[0058] Thus, while there has been shown and described, fundamental novel features of the disclosure as applied to various specific embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of the apparatus illustrated, and in their operation, may be made by those skilled in the art without departing from the spirit of the disclosure. For example, it is expressly intended that all combinations of those elements which perform substantially the same function, in substantially the same way, to achieve the same results, are within the scope of the invention. Moreover, it should be recognized that structures and/or elements shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore to be limited only as indicated by the scope of the claims appended hereto.