WO2016081446A1

WO2016081446A1 - Provisioning an interactive and integrated lender-real estate service via a network

Info

Publication number: WO2016081446A1
Application number: PCT/US2015/061067
Authority: WO
Inventors: Nathanael G. WALLEN
Original assignee: Bellaruby, Llc
Priority date: 2014-11-17
Filing date: 2015-11-17
Publication date: 2016-05-26

Abstract

A A first server, associated with a real estate agent, may receive an invitation to associate with a second server associated with a lender; output an acceptance of the invitation; receive an instruction to create a website; obtain property listings of the agent; create a first webpage based on the listings; output, to a third server associated with a vendor of services for real estate owners, another invitation to associate with the first server; receive an acceptance of the other invitation; associate the third server with the first server or the second server; create a second webpage that identifies the agent, the lender, or the vendor; output the website based on the first and second webpages; receive, from a user device via the second webpage, a service request; and output, to the second server or the third server, a referral that identifies the user device or a user thereof.

Description

PROVISIONING AN INTERACTIVE AND INTEGRATED LENDER-REAL ESTATE

SERVICE VIA A NETWORK

BACKGROUND

[0001] User devices and other computational and/or communication devices (e.g., tablet computers, laptop computers, desktop computers, etc.) are capable of performing an increasing variety of functions and tasks that continue to improve the user's experience. For example, user devices can run a variety of applications, can connect to a variety of wired and wireless networks to receive services, can access a variety of services and/or perform various functions associated with ecommerce, point of sale transactions, social networking, downloading and uploading content, sending and receiving messages, etc.

[0002] Among the challenges faced by real estate agents is the ability to obtain referrals. Referrals enable the real estate agents to provide services to buy and sell real estate. Because the vast majority of all real estate transactions involve some form of financing (e.g., usually through a mortgage) real estate agents and mortgage lenders often work together to close the financial and real estate transactions for their respective clients.

[0003] Most referrals between real estate agents and mortgage lenders are provided by word of mouth, by telephone, or via electronic messages such as email. Such methods tend to be performed manually, rely on memory for follow-up, and/or can be cumbersome for the Agent and Lender.

SUMMARY

[0004] According to one implementation, described herein, a first server associated with a real estate agent providing real estate services, the first server may comprise one or more processors executing one or more instructions to: receive, from a second server associated with a mortgage lender, a first invitation to associate with the second server; output, to the second server, an acceptance of the first invitation; and receive, from the second server, an instruction to create a website. The instruction may include information associated with the mortgage lender. The first server may also obtain, based on receiving the instruction, information associated with one or more property listings of the agent; create a first web page based on the information associated with the one or more property listings or the information associated with the mortgage lender; output, to a third server associated with a vendor of services used in the real estate industry, a second invitation to associate the third server with the first server; and receive, from the third server, an acceptance of the second invitation. The acceptance of the second invitation may include information associated with the vendor. The first server may further: associate the third server with the first server or the second server based on the acceptance of the second invitation; create a second web page based on at least one of: information associated the agent, the information associated with the mortgage lender, or the information associated with the vendor; output the website based on the first web page and the second webpage; receive, from a user device and via the second webpage, a request for service; and output, to the second server or the third server, a referral based on receiving the request for service, the referral including information associated with the user device or a user of the user device.

[0005] According to another implementation, described herein, a system to provision integrated and interactive lender and real estate services to a user device may include: a first server, associated with a lender, executing one or more first instructions to communicate with or provision a lender service to the user device, the lender service enabling a user, of the user device, to obtain a mortgage on a property being purchased by the user; and a second server, associated with a vendor, executing one or more second instructions to communicate with or provision a vendor service to the user device. The vender service may enable the user or a seller, of the property, to close on the property or to maintain the property after the closing. The system may also include a third server, associated with a real estate agent, executing one or more third instructions to communicate with or provision an agent service to the user device. The agent service may enable the user or the seller to purchase or sell the property, respectively. The third server may be further to: receive, a first referral from the first server or the second server, where the referral may include information associated with the user device or the user; communicate, with the user device, to enable the agent service to be provided to the user device or the user in connection with the purchase of the property; receive, from the user device, an offer to purchase the property; obtain, based on receiving the offer, first information that identifies pre-closing activities, relating to the property, to be performed to enable a closing on the property; output the first information to the user device or a different user device associated with the seller; output, to the first server or the second server, a second referral that identifies one or more of the pre- closing activities to be performed. The second referral may enable: the first server to communicate with the user device to provide the lender service associated with at least one of the pre-closing activities, or the second server to communicate with the user device to provide the vendor service associated with at least a different one of the pre-closing activities.

[0006] According to yet another implementation, described herein, a method performed by a first server, associated with a real estate agent, executing one or more instructions, the method may include: receiving, by the first server and from a second server associated with a lender, a first invitation to associate with the second server; outputting, by the first server and to the second server, an acceptance of that the first invitation; receiving, by the first server and from the second server, information associated with the lender that describes lender services offered by the lender; obtaining, by the first server and based on receiving the information associated with the lender, information associated with one or more property listings of the agent; and creating, by the first server, a first web page based on the information associated with the one or more property listings, information associated with the agent, or the information associated with the lender. The method may also include: outputting, by the first server and to a third server associated with a vendor of services used in the real estate industry, a second invitation to associate the third server with the first server; receiving, by the first server and from the third server, an acceptance of the second invitation, the acceptance of the second invitation including information associated with the vendor; associating, by the first server, the third server with the first server or the second server based on the acceptance of the second invitation; and creating, by the first server, a second web page based on at least one of: the information associated the agent, the information associated with the lender, or the information associated with the vendor. The method may further include: outputting, by the first server, the website based on the first web page and the second webpage; receiving, by the first server and from a user device via the first webpage, a request for service; and outputting, by the first server and to the second server or the third server, a referral based on receiving the request for service. The referral may include information associated with the user device or a user of the user device.

DESCRIPT BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Fig. 1 is a diagram of an example environment in which the systems, methods, apparatus, technologies, and/or techniques, described herein, may be implemented;

[0008] Fig. 2 is a diagram of example components of one or more of the devices of Fig. 1 ;

[0009] Fig. 3 is a diagram of an example framework that may be associated with an application being hosted and/or executed by an application server of Fig. 1;

[0010] Fig. 4 is a diagram of an example interactive and integrated lender-agent service scheme provisioned by an application server according to an implementation described herein;

[0011] Fig. 5 is a flow chart of an example process that may be used to register a lender server and/or to associate an agent server therewith according to an implementation described herein;

[0012] Fig. 6 is a diagram of an example user interface that may be used to register a lender server of Fig. 1;

[0013] Fig. 7 is a diagram of an example user interface that may be used to associate an agent server with a lender server of Fig. 1 ; [0014] Fig. 8 is a flow chart of an example process that may be used to register an agent server and/or to associate a vendor server therewith according to an implementation described herein;

[0015] Fig. 9 is a diagram of an example framework and/or service scheme between a user device and one or more of a lender server, agent server and/or vendor server that is provisioned by an application server according to an implementation described herein;

[0016] Figs. 10A and 10B are flow charts of example processes that may enable an application server to provision referrals and/or create analytics according to an implementation described herein;

[0017] Fig. 11 is a diagram of an example user interface that may include analytics associated with services being provisioned according to an implementation described herein;

[0018] Fig. 12 is a flowchart of an example process for tracking performance of pre-closing activities and post-closing activities associated with a property listing according to an implementation described herein; and

[0019] Fig. 13 is a diagram of an example user interface via which information associated with performance of pre-closing and/or post-closing activities that may be presented.

DETAILED DESCRIPTION

[0020] Figures 1-13 are attached thereto and incorporated herein by this reference. The following detailed description refers to the accompanying Figures 1-13. The same reference numbers in different figures may identify the same or similar elements.

[0021] The systems, methods, technology and/or techniques (hereinafter, the "systems and/or methods") may include a system that uses and/or is associated with information technology (e.g., user devices, servers, processors, logic, wired and wireless communication links and/or networks, etc.), logic (e.g., hardware, software, or a combination thereof), network architecture, communication and technology protocols and standards, and/or data and information being processed by and/or flowing through the system.

[0022] The systems and/or methods may include an application server that executes an application (hereinafter, a "lender-agent application") that enables services, associated with integrated and interactive real estate and mortgage lender services, to be automated and/or provisioned to and/or among a lender server associated with an mortgage lender (hereinafter, a "Lender"), an agent server associated with a real estate agent (hereinafter, an "Agent"), a vendor server associated with a vendor and/or service provider (e.g., an architect, a home inspector, a title search firm, a home repair firm, a heating, ventilation and air conditioning (HVAC) service firm, a construction firm, a maintenance and repair firm, a real estate attorney or law firm, etc.) (hereinafter, a "Vendor"), and/or a user device associated with a buyer, seller, and/or mortgagee (hereinafter, a "user").

[0023] The systems and/or methods may enable the application server to register a Lender and/or lender server. The application server may enable the Lender to identify and/or select one or more Agents with which to do business. The application server to output an invitation to one or more agent servers, associated with the selected Agent(s), to register with the application server. The application server may use information associated with the Lender and/or lender server (e.g., Lender name, lender license information, address, email address, telephone number, network address of lender server, information associated with Lender services, etc. obtained from the Lender and/or lender server) to create a lender profile and/or a lender website (hereinafter, a "lender site"). The lender site may, for example, identify the Lender, lender services provided by the lender, etc.

[0024] The systems and/or methods may enable the application server to register an Agent and/or agent server based on receiving an acceptance from the agent server as a result of outputting an invitation (on behalf of the Lender) to the agent server (as described above). The application server may use information associated with the Agent and/or agent server (e.g., Agent name, real estate license information, address, email address, telephone number, network address of the agent server, information associated with agent services, etc. obtained from the Agent and/or agent server) to create an agent profile and/or agent website (hereinafter, a "agent site"). The application server may associate the agent profile with the lender profile and/or may update the lender site based on the information associated with the agent (e.g., by identifying on the lender site one or more selected agents, links to agent servers, property listings of the Agent, Vendors used by the Agent etc.). The application server may enable the Agent to identify and/or select one or more Vendors with which to do business. The application server may output an invitation to one or more vendor servers, associated with the selected Vendor(s), to register with the application server. The agent site may, for example, identify the Lender, lender server (e.g., based on a link to the lender site), Agent (e.g., Agent name, real estate license information, address, email address, telephone number, information associated with agent services, etc.).

[0025] The systems and/or methods may enable the Agent to develop property listings that identify one or more properties associated with the Agent (hereinafter, "property listing site"). The systems and/or methods may, in a manner described above and herein, enable the Agent to develop Vendor listings that identify one or more Vendors associated with the Agent (hereinafter, "agent network site"). The application server may associate the property listing site and/or the agent network site with the agent site and/or with the lender site. [0026] The systems and/or methods may enable the application server to register a Vendor and/or vendor server based on receiving an acceptance from the vendor server as a result of outputting an invitation (on behalf of the Agent) to the vendor server (as described above). The application server may use information associated with the Vendor and/or vendor server (e.g., Vendor name, vendor license information, address, email address, network address associated with the vendor server, telephone number, information associated with vendor services, etc. obtained from the Vendor and/or vendor server) to create a vendor profile and/or to update a vendor website (e.g., by identifying the Agent and/or Lender or causing links to the lender and/or agent site to be displayed via the vendor website). The application server may associate the vendor profile with the agent profile and/or lender profile. The application server may update the agent site and/or lender site based on the information associated with the agent (e.g., by identifying on the lender site and/or agent site one or more selected vendors, links to vendor servers, etc.).

[0027] The systems and/or methods may enable a user device to access the lender site and select an Agent with which to communicate, which may cause the application server to provide a notification to the agent server with which the selected agent is associated. The notification may include information associated with the referring Lender and/or lender server, and/or information associated with the user device and/or user associated therewith (e.g., user name, address, telephone number, information associated with a property being bought or sold, desired method of communication (email, telephone, text message etc.), desired time when available, etc.) (hereinafter, a "lender referral"). Additionally, or alternatively, the application server may provide a notification to the user device that includes information identifying the Lender, the Agent, and/or Vendors associated with the Agent from which the user may communicate (e.g., by selecting a link, sending an email, placing a telephone call, etc.) to obtain other services (hereinafter an "agent network referral" or a "network referral"). Additionally, or alternatively, the application server may direct the user device to access the agent site. The systems and/or methods may enable a user device to access the lender site and/or to select a Vendor with which to communicate, which may cause the application server to provide a lender referral to the vendor server with which the selected Vendor is associated.

[0028] The systems and/or methods may enable a user device to access the agent site (e.g., via the agent site, property listing site, and/or agent network site) and select a lender with which to communicate, which may cause the application server to provide a notification to the lender server with which the selected Lender is associated. The notification may include information associated with the referring Agent and/or agent server, and/or information associated with the user device and/or user associated therewith (hereinafter, an "agent referral"). Additionally, or alternatively, the application server may direct the user device to access the selected lender site. Additionally, or alternatively, the application server may provide an agent network referral to the user device that includes information identifying the selected Lender, the Agent, and/or one or more Vendors associated with the Agent from which the user may communicate (e.g., by selecting a link, sending an email, placing a telephone call, etc.) to obtain services. The systems and/or methods may enable a user device to access the agent site (e.g., via the agent site, property listing site, and/or agent network site) and select a vendor with which to communicate, which may cause the application server to provide an agent referral to the vendor server with which the selected vendor is associated.

[0029] The systems and/or methods may enable a user device to access the vendor site and/or to select an Agent with which to communicate, which may cause the application server to provide a notification to the agent server with which the selected agent is associated. The notification may include information associated with the referring Vendor and/or vendor server, and/or information associated with the user device and/or user associated therewith (e.g., user name, address, telephone number, information associated with a property being bought or sold, desired method of communication (email, telephone, text message etc.), desired time when available, etc.) (hereinafter, a "vendor referral"). Additionally, or alternatively, the application server may provide a network referral to the user device that includes information identifying the Lender, Agent, and/or other Vendors associated with the Agent from which the user may communicate (e.g., by selecting a link, sending an email, placing a telephone call, etc.) to obtain services. Additionally, or alternatively, the application server may direct the user device to access the agent site. The systems and/or methods may enable a user device to access the vendor site and/or to select a Lender with which to communicate, which may cause the application server to provide a vendor referral to the lender server with which the selected Lender is associated.

[0030] The systems and/or methods may enable the application server may obtain, from the lender server, agent server, vendor server, and/or user device, information associated with the above-described accesses to websites by user devices (hereinafter, referred to as "views"), any notifications (e.g., lender referrals, agent referrals, and vendor referrals) associated therewith that are provided by the application server, any agent network referrals to user devices, etc. The application server may monitor when a user device accesses or otherwise communicates with any lender server, agent server and/or vendor server in response to an agent network referral. The systems and/or methods may enable the application server to monitor leads that are generated by a referral (e.g., lender referrals, agent referrals, and/or vendor referrals), and/or an agent network referrals. For example, the application server may determine when an agent server communicates with a user device based on a lender referral and/or vendor referral (e.g., a "lead"), and may determine that a view has been "converted" to a lead. Additionally, or alternatively, the application server may also, or alternatively, determine that a view has been converted to a lead when a user device communicates with lender server, agent server, and/or vendor server as a result of an agent network referral being outputted to the user device.

[0031] The systems and/or methods may enable the application server to develop analytics that identifies the quantity of views, particular sites being viewed, referrals, agent network referrals, leads, or rate at which views are converted to leads. The analytics may also, or alternatively, identify ratings and/or scores associated with Vendors, Agents, and/or Lenders based on the views, referrals, agent network referrals, leads, rate of conversions, etc.

[0032] The systems and/or methods may enable the application server to provide services to track ecommerce transactions (e.g., between users and Vendors, Agents, or Lenders), Agent- Vendor network collaboration, scoring of a property listing (e.g., associated with an Agent's property listing site) relative to other comparable property listings ("comps"), manage and/or track real estate closing activities. Such services may include providing a user interface that provides information associated with ecommerce transactions, property scoring, closing progress, property listing percent complete (e.g., percentage of documents or other information associated with a complete property listing), creation of a virtual real estate "property book" that includes various documents related to the property (e.g., insurance information, elevation certificate, utility rate and/or consumption information, property tax information, flood zone information, etc.), a user-owner dashboard, etc.

[0033] The application server may alone, and/or in communication with one or more servers associated with a Lender, Agent and/or Supplier, provide a variety of services including, for example, Lender services (e.g., any service associated with and/or provided by a Lender and/or Lender server), Agent services (e.g., any service associated with and/or provided by a real estate agent and/or Agent server), Vendor services (e.g., any service associated with and/or provided by a Vendor and/or vendor server, including advertising), and/or an user-owner dashboard. The dashboard may, for example, be formed by a user interface that enables a Lender, Agent, and/or Vendor to interact with and/or stay in contact with a user after a sale and/or enable the user to monitor and/or manage actions and/or services related to the maintenance, upkeep, value of purchased property and/or a future sale of the property.

[0034] Fig. 1 is a diagram of an example environment 100 in which the systems and/or methods, described herein, may be implemented. As shown in Fig. 1, environment 100 may include a group of user devices 110-1, 1 10-J (collectively referred to herein as "user devices 110," and individually as "user device 1 10") (where J > 1), a group agent servers 120-1, 120- K (collectively referred to herein as "agent servers 120" and individually as "agent server 120") (where K > 1), a group of lender servers 130-1, 130-L (collectively referred to herein as "lender servers 130" and individually as "lender server 130") (where L > 1), a group of vendor servers 140-1, 140-M (collectively referred to herein as "vendor servers 140" and individually as "vendor server 140") (where M > 1), an application server 150, a database 155, a public server 160, and a network 170. The number of devices and/or networks, illustrated in Fig. 1, is provided for explanatory purposes only. In practice, there may be additional networks and/or devices, fewer networks and/or devices, different networks and/or devices, or differently arranged networks and/or devices than illustrated in Fig. 1.

[0035] Also, in some implementations, one or more of the devices of environment 100 may perform one or more functions described as being performed by another one or more of the devices of environment 100. Devices of environment 100 may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

[0036] User device 110 may include any computation or communication device, such as a wireless mobile communication device, that is capable of communicating with network 140. For example, user device 1 10 may include a radiotelephone, a personal communications system (PCS) terminal (e.g., such as a smart phone that may combine a cellular radiotelephone with data processing and data communications capabilities), a personal digital assistant (PDA) (e.g., that can include a radiotelephone, a pager, Internet/intranet access, etc.), a laptop computer, a tablet computer, a personal computer, a camera, a personal gaming system, or another type of computation or communication device. In one example implementation, user device 110 may include a global positioning satellite (GPS) component that communicates with a GPS constellation to provide and/or obtain location information associated with user device 110. Additionally, or alternatively, user device 110 may include logic, such as one or more processing or storage devices, that can be used to perform and/or support processing activities on behalf of a user.

[0037] User device 110 may perform communication operations by sending data to or receiving data, via network 170, from another device, such as agent server 120, lender server 130, vendor server 140, and/or application server 150. Data may refer to any type of machine- readable information having substantially any format that may be adapted for use in one or more networks and/or with one or more devices. Data may include digital information or analog information. Data may further be packetized and/or non-packetized. User device 1 10 may include logic for performing computations on user device 1 10 and may include the components illustrated in Fig. 2 in an example implementation.

[0038] User device 110 may execute a copy of a lender-server application and/or may communicate with agent server 120 to access an agent site (e.g., including property listing site and/or agent network site), hosted by agent server 120, to obtain services from an Agent; lender server 130 to access a lender site, hosted by lender server 130, to obtain services from a Lender; and/or vendor server 140 to access a vendor site, hosted by vendor server 140, to obtain services from a Vendor associated with Agent. User device 120 may receive an agent network referral and may communicate with agent server 120, lender server 130, and/or vendor server 140 based on such agent network referral.

[0039] Agent server 120 may include one or more server devices, or other types of computation or communication devices, that gather, process, search, store, and/or provide information in a manner described herein. Agent server 120 may, for example, be associated with an Agent and/or a profile associated with a Lender and/or lender server 130. Agent server 120 may execute a copy of a lender-server application and/or may host an agent site, a property listing site (described in greater detail below), and/or an agent network site (described in greater detail below). Agent server 120 may be associated with one or more vendor server 140 and/or other agent servers 120 that have accepted an invitation to be part of an agent network associated with agent server 120. Agent server 120 may communicate with user device 110 to provide agent services to a user of user device 1 10. Agent server 120 may transmit an agent referral to another agent server 120, lender server 130 and/or vendor server 140. The agent referral may include information associated with a user (e.g., user name, address, telephone number, information associated with a property being bought or sold, and/or information identifying a desired service, method of communication (email, telephone, text message etc.), time to be contacted, etc.) and/or user device 1 10 (e.g., mobile directory number (MDN), Internet Protocol (IP) address, and/or some other network address or device identifier). Agent server 120 may also, or alternatively, receive lender referrals from lender server 130, vendor referrals from vendor server 140, and/or an agent referral from another agent server 120. Agent server 120 may also, or alternatively, provide information to user device 110 that enables a user to track closing progress associated with a real estate transaction, track when maintenance should be performed on a purchased home, access pertinent information about a property that the user is evaluating for purchase (e.g., a "property book" that include documents or information associated with utility bills and/or rates, property taxes, flood zone information, elevation certificate, home owner's insurance, flood insurance, etc.).

[0040] Agent server 120 may also, or alternatively, output to user device 1 10 (and/or other agent server 120, lender server 130, and/or vendor server 140), an agent network referral that identifies information associated with an agent network of an Agent with which agent server 120 is associated. The information, associated with the agent network, may, for example, identify a Lender and/or lender server 130 associated with agent server 120 (e.g., based on link and/or URL associated with to the lender site), another Agent and/or other agent server 120 associated with agent server 120 (e.g., based on link and/or URL associated with to the agent site), and/or one or more Vendors and/or vendor servers 140 associated with agent server 120 (e.g., based on link and/or URL associated with to the vendor site).

[0041] Lender server 130 may include one or more server devices, or other types of computation or communication devices, that gather, process, search, store, and/or provide information in a manner described herein. Lender server 130 may, for example, be associated with a Lender that provides lender services (e.g., mortgage services, refinance services, etc.). Lender server 130 may also, or alternatively, be associated with one or more Agents and/or agent servers 120 associated with such Agents. Lender server 130 may execute a copy of a lender- server application and/or may host a lender site via which a user, of user device 1 10, may access and/or order lender services via the lender site. Lender server 130 may transmit a lender referral to agent server 120 and/or vendor server 140 that includes information associated with a user and/or user device 1 10 and/or the Lender and/or lender server 130. Lender server 130 may also, or alternatively, receive agent referrals from agent server 120 and/or vendor referrals from vendor server 140. Lender server 130 may also, or alternatively, output to user device 110 (and/or agent server 120, lender server 130, and/or vendor server 140), an agent network referral that identifies information associated with an agent network, of an Agent and/or agent server 120, with which lender server 130 is associated.

[0042] Vendor server 140 may include one or more server devices, or other types of computation or communication devices, that gather, process, search, store, and/or provide information in a manner described herein. Vendor server 140 may, for example, be associated with a Vendor that provides services (e.g., architecture, inspection, construction, maintenance and repair, flood insurance, homeowners insurance, HVAC, legal, etc.). Vendor server 140 may also, or alternatively, be associated with one or more Agents and/or agent servers 120 associated with such Agents. Agent server 140 may host a vendor site via which a user, of user device 110, may access and/or order vendor services via the vendor site. Vendor server 140 may transmit a vendor referral to agent server 120 and/or lender server 130 that includes information associated with a user and/or user device 1 10 associated with the user. Vendor server 140 may also, or alternatively, receive agent referrals from agent server 120 and/or lender referrals from lender server 130. Vendor server 140 may also, or alternatively, output to user device 1 10, (and/or agent server 120, lender server 130, and/or other vendor server 140) an agent network referral that identifies information associated with an agent network, of an Agent and/or agent server 120, with which vendor server 140 is associated.

[0043] Application server 150 may include one or more server devices, or other types of computation or communication devices, that gather, process, search, store, and/or provide information in a manner described herein. Application server 150 may store one or more copies of a lender-server application that enables application server 150 to communicate via network 170, with agent server 120, lender server 130, vendor server 140, public server 160 and/or user device 1 10, and/or to provision lender-agent services as described herein. Application server 150 may register agent server 120, lender server 130 and/or vendor server 140, and/or may provide a copy of a lender-agent application that can be downloaded, installed on, and/or executed by agent server 120, lender server 130, and/or vendor server 140 to enable agent server 120, lender server 130, and/or vendor server 140 to perform operations as described herein. Application server 150 may create and/or maintain profiles in connection with agent server 120 and/or an Agent associated therewith, lender server 130 and/or a Lender associated therewith, and/or vendor server 140 and/or a Vendor associated therewith. Application server 150 may store the profiles on database 155.

[0044] Application server 150 may receive agent referrals (e.g., from agent server 120), lender referrals (e.g., from lender server 130), and/or vendor referrals (e.g., from vendor server 140), may process the referrals (e.g., by creating analytics information associated therewith, etc.) and/or may transmit the referrals to their intended recipient server 120, 130 and/or 140. Application server 150 may receive agent network referrals (e.g., from agent server 120, lender server 130, and/or vendor server 140), may process the agent network referrals (e.g., by creating analytics information associated therewith, etc.), and/or may transmit the agent network referral to user device 1 10 (and/or agent server 120, lender server 130, and/or vendor server 140).

[0045] Application server 150 may monitor and/or track information associated with views (e.g., when a user device 1 10 accesses an agent site, lender site, and/or vendor site), leads (e.g., when agent server 120, lender server 130, and/or vendor server 140) communicate with user device 1 10 in response to a view, referral, or agent network referral. Application server 150 may monitor and/or track the quantity, rate, or trends thereof associated with views, leads, leads converted from views, quantity of sales and/or closings based on views and/or leads, etc. Application server 150 may process and/or aggregate analytics, and/or may provide such analytics to agent server 120, lender server 130, and/or vendor server 140.

[0046] Database 155 may include one or more devices that store information received from application server 150. For example, database 155 may store copies of the lender-agent application that are supported by and/or compatible with different types of servers 120 through 140. Database 155 may store one or more profiles associated with an Agent and/or agent server 120, Lender and/or lender server 130, and/or Vendor and/or vendor server 140. Database 155 may also, or alternatively, store analytics information associated with quantity, rates and/or trends in connection with views, leads, referrals, agent network referrals, a quantity and/or rate of referrals, closings, etc. of an agent network.

[0047] Public server 160 may include one or more server devices, or other types of computation or communication devices, that gather, process, search, store, and/or provide information in a manner described herein. Public server 160 may communicate via network 170, with application server 150, agent server 120, lender server 130, and/or vendor server 140. For example, public server 160 may provide a property listing service (e.g., via a website, etc.), such as the multiple listing service (MLS), via which application server 150, agent server 120, lender server 130, and/or vendor server 140 may access to obtain information. Public server 160 may also, or alternatively, provide a service based on a graphical information system (GIS), from which property tax and/or title information associated with a property may be obtained, from which Lender, Agent and/or Vendor licensing information can be obtain, etc.

[0048] Network 170 may include one or more wired and/or wireless networks. For example, network 170 may include a cellular network, a public land mobile network (PLMN), a second generation (2G) network, a third generation (3G) network, a fourth generation (4G) network (e.g., a long term evolution (LTE) network), a fifth generation (5G) network, and/or another network. Additionally, or alternatively, network 170 may include a wide area network (WAN), a metropolitan network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), an ad hoc network, an intranet, the Internet, a fiber optic-based network, and/or a combination of these or other types of networks.

[0049] Fig. 2 is a diagram of example components of a device 200 that may correspond to user device 1 10, agent server 120, lender server 130, vendor server 140, application server 150, and/or public server 160. Additionally, or alternatively, each of user device 110, agent server 120, lender server 130, vendor server 140, application server 150, and/or public server 160 may include one or more devices 200. Device 200 may include a bus 210, a processor 220, a memory 230, an input component 240, an output component 250, and a communication interface 260. Although Fig. 2 shows example components of device 200, in other implementations, device 200 may include fewer components, additional components, different components, or differently arranged components than depicted in Fig. 2. Additionally, or alternatively, in other implementations, one or more components of device 200 may perform one or more tasks described as being performed by one or more other components of device 200.

[0050] Bus 210 may include a path that permits communication among the components of device 200. Processor 220 may include a processor, microprocessor, or processing logic that may interpret and execute instructions. Memory 230 may include any type of dynamic storage device that may store information and instructions for execution by processor 220, and/or any type of non- volatile storage device that may store information for use by processor 220.

[0051] Input component 240 may include a mechanism that permits an operator to input information to device 200, such as a keyboard, a keypad, a button, a switch, a mouse, trackpad, touch screen, etc. Output component 250 may include a mechanism that outputs information to the operator, such as a display, a speaker, one or more light emitting diodes (LEDs), etc. Communication interface 260 may include any transceiver-like mechanism that enables device 200 to communicate with other devices and/or systems via wireless communications (e.g., radio frequency, infrared, and/or visual optics, etc.), wired communications (e.g., conductive wire, twisted pair cable, coaxial cable, transmission line, fiber optic cable, and/or waveguide, etc.) or a combination of wireless and wired communications. For example, communication interface 260 may include mechanisms for communicating with another device or system via a network, such as network 170.

[0052] As will be described in detail below, device 200 may perform operations relating to provisioning an interactive, integrated lender-agent service as described herein. Device 200 may perform these operations in response to processor 220 executing software instructions contained in a computer-readable medium, such as memory 230. A computer-readable medium may be defined as a non-transitory memory device. A memory device may include space within a single physical memory device or spread across multiple physical memory devices. The software instructions may be read into memory 230 from another computer-readable medium or from another device. The software instructions contained in memory 230 may cause processor 220 to perform processes described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0053] Fig. 3 is a diagram of an example framework 300 that may be associated with a lender-agent application being hosted and/or executed by application server 150. Additionally, or alternatively, the lender-agent application, associated with framework 300, may be hosted and/or executed on agent server 120, lender server 130, and/or vendor server 140. Framework 300 may include logic in the form of software, hardware (e.g., electronic, optical, etc.) or a combination of software and hardware that, when executed, enables application server 150, agent server 120, lender server 130, and/or vendor server 140 to perform the operations described herein. As shown in Fig. 3, framework 300 may include a lender module 310, an agent module 320, a vendor module 340, and a control module 360.

[0054] Lender module 310 may enable application server 150 and/or lender server 130 to manage and/or control a manner in which lender operations, associated with a Lender and/or lender server 130, are performed. Lender module 310 may include a lender profile module 312, a lender service module 314, and a lender analytics module 316.

[0055] Lender profile module 312 may enable application server 150 and/or lender server 130 to create, manage and/or store a profile associated with a Lender and/or lender server 130 with which the Lender is associated and/or to update the profile based on one or more agent servers 120 that are associated with lender server 130. Lender service module 314 may enable application server 150 and/or lender server 130 to associate one or more agent servers 120 with lender server 130; create a lender site (e.g., that includes information associated with the Lender, lender services offered by the Lender, and/or one or more Agents associated with the Lender); to create and/or output lender referrals and/or network referrals; to receive and/or process agent referrals, vendor referrals and/or network referrals; and/or to create and/or output notifications associated with views to the lender site, track leads based on referrals and/or views; and/or perform other lender services. Lender analytics module 316 may enable application server 150 and/or lender server 130 to create and/or aggregate analytics based on views, leads, referrals, closings, etc.

[0056] Agent module 320 may enable application server 150 and/or agent server 120 to manage and/or control a manner in which agent operations, associated with an Agent and/or agent server 120, are performed. Agent module 320 may include an agent profile module 322, a property listing module 324, an agent network module 326, an agent service module 328, an agent analytics module 330 and a closing module 332. Agent profile module 322 may enable application server 150 and/or agent server 120 to create, manage and/or store a profile associated with an Agent and/or agent server 120 with which the Agent is associated.

[0057] Property listing module 324 may enable application server 150 and/or agent server 120 to create a property listing website that identifies one or more properties being offered by the Agent. Each property listing may include information associated with the Agent (e.g., Agent name, an image, address, email address, telephone number, etc.), the property description (e.g., address, size, (e.g., acreage, square footage, quantity of bedrooms, quantity of bathrooms, time of construction, etc.), highlights associated with the property (e.g., convenience to transportation, location relative to landforms (such as lakes, rivers, mountains, etc.), quality of view, location relative to cities, quality of schools, upgrades, etc.), images or video content associated with the property, documents associated with the property (e.g., copies of utility bills, elevation certificate, tax bills, insurance, covenants, title, etc.) etc.

[0058] Agent network module 326 may enable application server 150 and/or agent server 120 to create an agent network and/or an agent network website by outputting invitations one or more vendor servers 140 associated with one or more Vendors and/or one or more other agent servers 120 associated with other Agents with which the Agent desire to do business. Agent network module 326 may, for example, allow application server 150 and/or agent server 120 to track invitations that are accepted, ignored and/or rejected; associate those vendor servers 140 and/or other agent servers 120 that accepted the invitation; and/or to create an agent network for the Agent based on the accepted invitations. Agent profile module 322 may update the Agent profile based on the agent network.

[0059] Agent service module 328 may enable application server 150 and/or agent server 120 to create an agent site based on the property listing website (created using property listing module 324) and/or the agent network website (e.g., created using agent network module 326) as illustrated in Fig. 4. Fig. 4 is a diagram of an example interactive and integrated lender-agent service scheme 400 (hereinafter, "service scheme 400") provisioned by application server 150 and/or agent server 120 according to an implementation described herein. As shown in Fig. 4, service scheme 400 may enable user device 1 10, another agent server 120, lender server 130 and/or vendor server 140 to access a lender-agent service via the agent site in a manner described herein. The lender-agent service may, for example, include a property listing service (e.g., that can be accessed via the property listing website) and/or an agent network service (e.g., that can be accessed via the agent network website).

[0060] Agent service module 328 may also, or alternatively, enable application server 150 and/or agent server 120 to create and/or output agent referrals and/or agent network referrals; to receive and/or process agent referrals (from other agent user devices 120), lender referrals, vendor referrals and/or agent network referrals; and/or to create and/or output notifications associated with views to the agent site (including property listing site and/or agent network site), track leads based on referrals and/or views; and/or perform other agent services.

[0061] Agent analytics module 330 may enable application server 150 and/or agent server 120 to create and/or aggregate analytics based on views, leads, referrals, closings, etc. associated with agent server 120.

[0062] Closing module 332 may enable application server 150 and/or agent server 120 to track a manner in which a property, identified in the property listing site, receives a purchase offer from a user of user device 110, a real estate contract is executed, due diligence regarding the property is performed by the buyer and/or seller, earnest money is paid by buyer, inspections and/or repairs are performed by a Vendor (e.g., home inspections and/or repairs, termite inspection and/or treatment, mold inspection and/or treatment, etc.), documents pertaining to the property are made available for inspection by the seller (e.g., utility bills, title, tax bills, elevation certificate, insurance policies, etc.), pre-approval of a mortgage or executing a mortgage from the Lender by the buyer, etc. Closing module 332 may enable progress to closing to be tracked, quantified (e.g., percent complete, etc.) for each element of closing and/or due diligence, etc.

[0063] Vendor module 340 may enable application server 150 and/or vendor server 140 to manage and/or control a manner in which vendor operations, associated with a Vendor and/or vendor server 140, are performed. Vendor module 340 may include a vendor profile module 342, a vendor service module 344, and a vendor analytics module 346.

[0064] Vendor profile module 342 may enable application server 150 and/or vendor server 140 to create, manage and/or store a profile associated with a Vendor and/or vendor server 140 with which the Vendor is associated and/or to update the profile based on one or more agent servers 120 with which the Vendor and/or vendor server 140 are associated. Vendor service module 344 may enable application server 150 and/or vendor server 140 to create a vendor site (e.g., that includes information associated with the Vendor, vendor services offered by the Vendor, and/or one or more Agents with which the Vendor is associated); to create and/or output vendor referrals and/or agent network referrals; to receive and/or process agent referrals, lender referrals and/or agent network referrals; and/or to create and/or output notifications associated with views to the vendor site, track leads based on referrals and/or views; and/or perform other vendor services. Vendor analytics module 346 may enable application server 150 and/or vendor server 140 to create and/or aggregate analytics based on views, leads, referrals, closings, etc.

[0065] Control module 360 may control a manner in which application server 150 uses modules 310 - 346. Control module 360 may enable profiles associated with the Lender, Agent and/or Vendor to be managed and/or updated based on referrals sent or received, new leads created, association of another agent server 120 and/or another vendor server 140, the provisioning of lender services, agent services, and/or vendor services, and/or based on a listing, purchase offer, real estate contract, securing a mortgage, closing of a real estate transaction, etc. Control module 360 may track views (e.g., to lender site, agent site, vendor site, etc.), leads associated with views or referrals or agent network referrals, etc. and may generate analytics in a manner similar to that described above.

[0066] Control module 360 may also, or alternatively, enable application server 150 to track the life cycle of a real estate transaction from executing an agreement between an Agent and buyer or seller (e.g., user associated with user device 110), obtaining comps, listing a property, receiving an offer, executing a real estate contract, performing due diligence, securing a mortgage, closing, etc. Control module 360 may, for example, enable application server 150 to compare first property parameters associated with the property to second parameters associated with comparative properties (obtained from public server 160) to determine any differences in pricing, price per square foot, insurance rates, tax rates, utility bills, regime fees, flood insurance, etc. Control module 360 may identify any first parameter that differs from a corresponding second parameter by an amount that is greater than a threshold (e.g., 10%, 20%, 30%, 40%, etc.) and may output a notification to enable the Agent to suggest, to the user, an adjustment to the identified parameter for the listing. Control module 360 may enable the progress toward closing to be monitored, identify tasks completed, in process, or yet to be completed. Control module 360 may cause application server 150 to output notifications when such tasks are complete, in process, to be completed, overdue.

[0067] Although Fig. 3 shows an example number of modules associated with framework 300, in other implementations, framework 300 may include fewer modules, additional modules, different modules, or differently arranged modules than depicted in Fig. 3. In still other implementations, one or more modules of framework 300 may perform one or more tasks, functions and/or operations described as being performed by one or more other modules of framework 300.

[0068] Fig. 5 is a flow chart of an example process 500 that may be used to register lender server 130 and/or to associate agent server 120 therewith according to an implementation described herein. Process 500 may be performed by application server 150. Additionally, or alternatively, some or all of process 500 may be performed by a device or a collection of devices separate from, or in combination with, application server 150, such as lender server 130 and/or agent server 120. Fig. 6 is a diagram of an example user interface 600 that may be used to register lender server 130. Fig. 7 is a diagram of an example user interface that may be used to associated agent server 120 with lender server 130. Some or all of process 500 of Fig. 5 is described below with references to user interface 600 of Fig. 6 and user interface 700 of Fig. 7.

[0069] As shown in Fig. 5, process 500 may include registering a lender server, obtaining lender information, and/or obtaining selection of one or more Agents (BLOCKS 505 through 515). For example, lender server 130, associated with a Lender, may communicate with application server 150 to register and/or to obtain a copy of a lender-agent application. Application server 150 may, based on the communication, register lender server 130 and/or creating an account associated with the Lender. Application server 150 may also, or alternatively, transmit a copy of the lender-agent application to lender server 130. Lender server 130 may receive the application and may execute the application to cause a user interface, such as user interface 600 of Fig. 6 to be displayed on a display device associated with lender server 130.

[0070] As shown in Fig. 6, user interface 600 may include a collection of fields and/or buttons including lender information field 605, lender materials field 610, upload button 612, agent selection field 615, save button 620, and/or an edit button 625. Lender information field 605 may enable the Lender to enter lender information that identifies in a non-limiting example, a Lender name, lender address, description of lender services, an email address, a website address on which the lender site is to be associated, etc. Lender materials field 610 may enable the Lender to transmit, to application server 150, one or more documents, images, videos or other information or data from a storage location associated with lender server 130 (e.g., by selecting one or more browse buttons, selecting one or more files associated with such lender materials, and selecting upload button 612). Agent selection field 615 may enable the Lender to select one or more agents (e.g., by selecting or placing a mark (e.g., "X", a check mark, etc.) in the a box associated with an Agent (e.g., shown as Agent 1, Agent 2, ... Agent N) to be associated with lender server 130 and/or by entering a name of a particular Agent in the search agent field to cause application server 150 to perform a search for the particular Agent. Save button 620, when selected by the Lender may cause lender information, lender materials and/or information identifying the selected or searched Agent to be transmitted, as lender information, to application server 150. Application server 150 may receive the lender information from lender server 130 and/or may obtain, from the received lender information, information identify one or more Agents selected by the Lender.

[0071] Returning to Fig. 5, application server 150 may create a lender profile associated with the Lender and/or lender server 130 based on the received lender information and/or selected Agent, and may store the lender profile in database 155 (BLOCK 520). Application server 150 may also, or alternatively, create a lender site based on some or all of the information associated with the profile, which identifies the Lender and/or one or more selected Agents. Application server 150 may output information associated with the lender site to cause the lender site to be hosted by application server 150 and/or lender server 130, discovered via Network 170 (e.g., via the Internet, etc.), and/or accessed by user device 1 10, agent server 120, vendor server 140, etc. (BLOCK 525). Additionally, or alternatively, lender server 130 may create the lender profile and/or lender site and may transmit, to application server 150, the lender profile and/or information associated with the lender site.

[0072] Application server 150 may obtain, from database 155, information associated with agent server 120 with which a selected Agent is associated, such as, for example, a network address (e.g., an IP address, a media access control (MAC) address, etc.). Application server 150 may create and invitation based on the information associated with selected Agent and/or information associated with the Lender (e.g., Lender name, address, email address, URL associated with the lender site, etc.) and may transmit, to agent server 120, the invitation based on the network address obtained from database 155 (BLOCKS 530 and 535). Additionally, or alternatively, lender server 130 may create and/or transit the invitation to agent server 120. [0073] Agent server 120 may receive the invitation and the Agent may accept, ignore or reject the invitation. In the event the Agent rejects or ignores the invitation, Application server 150 and/or lender server 130 may not associate agent server 120 with lender server 130. In the event that the Agent accepts the invitation (e.g., by selecting an accept button or some other button or field associated with the invitation), agent server 120 may transmit the acceptance and application server 150 and/or lender server 130 may receive the acceptance of the invitation and may associate the Agent and/or agent server 120 with lender server 130 (BLOCK 540). Associating the Agent and/or agent server 120 with lender server 130 may cause application server 150 and/or lender server 130 to store, in the lender profile, information associated with the Agent and/or agent server 120 (e.g., the network address, etc.). Application server 150 and/or lender server 130 may communicate with agent server 120 to obtain information associated with the Agent (sometimes referred to as "agent information") (BLOCK 545). For example, application server 150 may, based on receiving the acceptance from agent server 120, provide a lender-agent application to agent server 120. Agent server 120 may receive the application and may execute the application to cause a user interface, such as user interface 700 of Fig. 7 to be displayed on a display device associated with agent server 120.

[0074] As shown in Fig. 7, user interface 700 may include a collection of fields and/or buttons including agent information field 705, property information field 710, save and enter new property information button 712 (hereinafter, "save button 712"), vendor selection field 715, save button 720, and/or an edit button 725. Agent information field 705 may enable the Agent to enter agent information that identifies, in a non-limiting example, an Agent name, address, description of agent services, an email address, a website address on which the agent site is to be associated, etc. Property information field 710 may enable the Agent to enter and/or transmit to application server 150, information associated with a property to be listed within the agent site (e.g., the property listing site), such as, in a non-limiting example, information identifying a property address, a property description (e.g., size (acreage, square footage, etc.), number of bedrooms, number of bathrooms, time of construction, etc.), highlights associated with the property (e.g., convenience to nearby transportation, location relative to landforms (such as lakes, rivers, mountains, etc.), and/or quality of view, location relative to cities, quality of schools, upgrades, etc.). Property information field 710 may also, or alternatively, enable the Agent to browse agent server 120 to identify and upload any images or video content associated with the property, and/or documents associated with the property (e.g., copies of utility bills, elevation certificate, tax bills, insurance, covenants, title, etc.) etc. from a storage location associated with agent server 120 (e.g., by selecting one or more browse buttons, selecting one or more files associated with such images, videos and/or documents, and selecting upload save 712). Vendor selection field 715 may enable the Lender to select one or more Vendors (e.g., by selecting or placing a mark (e.g., "X", a check mark, etc.) in the a box associated with an Vendor (e.g., shown as Vendor 1, Vendor 2, ... Vendor P, where P > 1) to be associated with agent server 120 and/or by entering a name of a particular Vendor in the search vendor field to cause application server 150 to perform a search for the particular Vendor entered into the search field. Save button 720, when selected by the Agent may cause agent information, property information and/or information identifying the selected or searched Vendor to be transmitted, as agent information, to application server 150. Application server 150 may receive the agent information from agent server 120 and/or may obtain, from the received agent information, information identify one or more Vendors selected by the Agent.

[0075] The number of fields and/or buttons shown in Fig. 6 and 7, with respect to user interface 600 and 700 respectively, is provided for explanatory purposes only. Additionally, or alternatively, user interface 600 of Fig. 6 and/or user interface 700 of Fig. 7 may include additional fields and/or buttons, fewer fields and/or buttons, different fields and/or buttons, or differently arranged fields and/or buttons than are shown in Figs. 6 and/or 7, respectively.

[0076] Returning again to Fig. 5, application server 150 may create an agent profile associated with the Agent and/or agent server 120 based on the received agent information and/or information identifying the selected Vendor, and/or based on lender information obtained from the lender profile (BLOCK 550). Application server 150 may store the agent profile in database 155. Additionally, or alternatively, agent server 120 may create the agent profile and may transmit, to application server 150 and/or lender server 130, the agent profile. Application server 150 may also, or alternatively, associate the agent profile with the lender profile by storing information identifying the Agent and/or agent server 120 within the lender profile and/or storing information identifying the Lender and/or lender server 130 within the agent profile (BLOCK 555). Additionally, or alternatively, application server 150 may associate the agent profile with the lender profile by storing information that identifies a storage location of the agent profile (e.g., within database 155) within the lender profile and/or by storing information that identifies a storage location of the lender profile (e.g., within database 155) in the agent profile.

[0077] Based on associating agent server 120 with the lender server 130 and/or associating the agent profile with the lender profile, application server 150 and/or lender server 130 may update the lender site by including information associated with the Agent (e.g., an Agent name, image, address, email address, telephone number, etc.) and/or agent server 120 (e.g., a link or URL associated with an agent site, etc.) within one or more webpages of the lender site.

[0078] Fig. 8 is a flow chart of an example process 800 that may be used to create an agent site and/or associate a vendor server with an agent server according to an implementation described herein. Process 800 may be performed by application server 150. Additionally, or alternatively, some or all of process 800 may be performed by a device or a collection of devices separate from, or in combination with, application server 150, such as agent server 120 and/or vendor server 140. Fig. 9 is a diagram of an example agent network 900 that is provisioned by application server 150 according to an implementation described herein. Some or all of process 800 of Fig. 8 is described below with references to agent network 900 of Fig. 9.

[0079] Application server 150 may create an agent profile and/or associate the agent profile with the lender profile in a manner similar to that described above with respect to process 500 (BLOCKS 530 - 555) of Fig. 5 and may output, to agent server 120, an instruction to create an agent site. As shown in Fig. 8, process 800 may include receiving the instruction to create the agent site (BLOCK 820). Based on receiving the instruction, application server 150 and/or agent server 120 may use the lender-agent application to create a property listing site based on property information obtained from the agent information (BLOCK 825). The property information may correspond to the agent information that was entered by the Agent (e.g., into user interface 700 of Fig. 7) and transmitted to application server 150 in a manner similar to that described above (e.g., with respect to block 545 of Fig. 5). Each listing, within the property listing site, may be based on respective property information for each property to be listed within the property listing site.

[0080] In a non-limiting example, the property listing site may correspond to property listing 910 of Fig. 9. Property listing site 910 may include property information for each property listed on property listing site 910. In one example, each property may be associated with its own individual property site (e.g., shown as property 1 site, property 2 site, property X site). Property listing site 910 and/or individual property site associated therewith may include information associated with the Agent and/or Lender to enable views and/or leads to be generated, and/or agent referrals and/or agent network referrals to be created and/or transmitted to lender server 130 and/or user device 110.

[0081] Returning to Fig. 8, application server 150 and/or agent server 120 may obtain, from database 155 and/or a memory associated with agent server 120 respectively, information associated with vendor server 140 with which a selected Vendor is associated, such as, for example, a network address (e.g., an IP address, a MAC address, etc.). Application server 150 and/or agent server 120 may create a vendor invitation based on the information associated with selected Vendor (e.g., a Vendor name, address, telephone number, etc.) and/or information associated with the Agent (e.g., Agent name, address, email address, URL associated with the agent site, etc.) and may transmit, to vendor server 140, the vendor invitation based on the network address associated with vendor server 140 (BLOCKS 830 and 835). [0082] Vendor server 140 may receive the vendor invitation and the Vendor may accept, ignore or reject the vendor invitation. In the event the Vendor rejects or ignores the invitation, Application server 150 and/or agent server 120 may not associate vendor server 140 with agent server 120 and/or create a profile associated with the Vendor. In the event that the Vendor accepts the vendor invitation (e.g., by selecting an accept button or some other button or field associated with the invitation), vendor server 140 may transmit an acceptance to application server 150 and/or agent server 120. Application server 150 and/or agent server 120 may receive the acceptance of the vendor invitation and may associate the Vendor and/or vendor server 140 with agent server 120 (BLOCK 840). Associating the Vendor and/or vendor server 140 with agent server 120 may cause application server 150 and/or agent server 120 to store, in the lender profile and/or agent profile, information associated with the Vendor and/or vendor server 140 (e.g., the network address, etc.). Application server 150 and/or agent server 120 may communicate with vendor server 140 to obtain information associated with the Vendor (sometimes referred to as "vendor information") (BLOCK 845). For example, application server 150 and/or agent server 120 may, based on receiving the acceptance from vendor server 140, communicate with vendor server 140 to obtain vendor information associated with the Vendor (e.g., Vendor name, address, telephone number, description of vendor services, a URL associated with a website associated with the Vendor, etc.).

[0083] Application server 150 and/or agent server 120 may create a vendor profile associated with the Vendor and/or vendor server 140 based on the received vendor information, and/or based on agent information obtained from the agent profile and/or lender information obtained from the lender profile (BLOCK 850). Application server 150 may store the vendor profile in database 155. Application server 150 and/or agent server 120 may also, or alternatively, associate the vendor profile with the agent profile and/or lender profile by storing information identifying the Vendor and/or vendor server 140 within the agent profile and/or lender profile and/or by storing information identifying the agent and/or agent server 120, and/or lender and/or lender server 130 within the vendor profile (BLOCK 855). Additionally, or alternatively, application server 150 may associate the vendor profile with the agent profile and/or lender profile by storing information that identifies a storage location of the vendor profile (e.g., within database 155) within the agent profile and/or lender profile, and/or by storing information that identifies a storage locations of the agent profile and/or lender profile (e.g., within database 155) in the vendor profile. Based on associating the vendor profile with the agent profile and/or lender profile, application server 150 and/or agent server 120 may create and/or update an agent network, associated with agent server 120, to include information associated with the Vendor and/or vendor server 140, and/or may update an agent network site associated with agent server 120 (BLOCK 860).

[0084] Application server 150 and/or agent server 120 may, in a manner similar to that described above (e.g., with respect to blocks 830 - 855), associate another agent server 120 with which another Agent is associated (e.g., a different Agent that is subordinate to the Agent, etc.) with agent server 120 and/or lender server 130. Additionally, or alternatively, application server 150 and/or agent server 120 may create another agent profile for the other Agent and/or other agent server 120, and may associate the other agent profile with the agent profile and/or the lender profile. Based on associating the other agent profile with agent profile and/or lender profile, application server 150 and/or agent server 120 may use the lender-agent application to create and/or update the agent network and/or may create or update an agent network site associated with agent server 120.

[0085] In a non-limiting example, the agent network site may correspond to agent network site 930, of Fig. 9, that includes information associated with one or more other agents associated with the Agent (e.g., shown as Agent 1, Agent 2, ..., Agent Y). The information, associated with the one or more other agents, may include information identifying the other Agent (e.g., other Agent name, address, email address, telephone number, etc.) and/or other agent devices 120 (e.g., a link based on a network address, URL, etc.) and/or a website associated with or hosted by other agent servers 120 or some other server device. Additionally, or alternatively, agent network site 930, of Fig. 9, may include information associated with one or more Vendors associated with the Agent (e.g., shown as Vendor 1, Vendor 2, Vendor Z). The information, associated with the one or more Vendors, may include information identifying the Vendor (e.g., Vendor name, address, email address, telephone number, etc.) and/or vendor devices 140 (e.g., a link based on a network address, URL, etc.) and/or a website associated with or hosted by vendor servers 140 or some other server device. As shown in Fig. 9, agent site 900 may include information and/or links to the lender site associated with and/or hosted by lender server 130, property listing site 910 associated with and/or hosted by agent server 120, and/or the agent network site associated with and/or hosted by the agent network server 120.

[0086] As described above (e.g., with respect to block 825 of Fig. 8), property listing site 910 may include property information for each property listed on the property listing site as well as information associated with the Agent and/or Lender to enable views and/or leads to be generated, and/or agent referrals and/or agent network referrals to be created and/or transmitted to lender server 130 and/or user device 110.

[0087] Agent network site 930 may identify each Vendor and/or other Agent associated with the agent network of an Agent, associated with agent server 120, to enable a user to view the agent network, make contact with the Lender, the Agent, one or more Vendors, and/or one or more other Agents. Such views may generate referrals that may be converted to leads that can be used by the Lender, Agent, Vendor and/or other vendors.

[0088] The number of sites and/or indicators shown in Fig. 9, with respect to framework 900, is provided for explanatory purposes only. Additionally, or alternatively, framework 900 may include additional sites and/or indicators, fewer sites and/or indicators, different sites and/or indicators, or differently arranged sites and/or indicators than are shown in Fig. 9. For example, the lender site may include a property listing site, an agent network site, and/or agent or vendor indicators in addition to, or instead of, the agent site. Additionally, or alternatively, a vendor site may be associated with the lender site and/or agent site and may include a property listing site, an agent network site, and/or agent or lender indicators in addition to, or instead of, the agent site.

[0089] Figs. 10A and 10B are flow charts 1000 and 1030, respectively, of example processes that may enable an application server to provision referrals and/or create analytics according to an implementation described herein. Processes 1000 of Fig. 10A and 1030 of Fig. 10B may be performed by application server 150. Additionally, or alternatively, some or all of processes 1000 and/or 1030 may be performed by a device or a collection of devices separate from, or in combination with, application server 150, such as agent server 120, lender server 130 and/or vendor server 140.

[0090] In a non-limiting example with respect to process 1000 of Fig. 10A, an Agent, associated with agent server 120, may desire to add a new Vendor to the Agent's agent network and may output a notification, to application server 150, that the new Vendor, associated with vendor server 140, is being associated with agent network. Application server 150 may receive the notification and may (alone and/or in combination with agent server 120), in a manner similar to that described above in process 800 of Fig. 8, use the lender-agent application to transmit an invitation to vendor server 140. Based on receiving an acceptance of the invitation from vendor server 140, application server 150 and/or agent server 120 may create a vendor profile and/or associate the vendor profile with the agent profile and/or lender profile (with which the agent profile is associated). Additionally, or alternatively, application server 150 may associate vendor server 140 with agent server 120 and/or lender server 130 (with which agent server 120 is associated).

[0091] Additionally, or alternatively, the Agent may desire to add a new Agent to the Agent's agent network and may output a notification, to application server 150, that the new Agent, associated with a different agent server 120, is being associated with the agent network. Application server 150 may receive the notification and may (alone and/or in combination with agent server 120), in a manner similar to that described above in process 800 of Fig. 8, use the lender-agent application to transmit an invitation to different agent server 120. Based on receiving an acceptance of the invitation, application server 150 and/or agent server 120 may create a new agent profile and/or associate the new agent profile with the agent profile and/or lender profile (with which the agent profile is associated). Additionally, or alternatively, application server 150 may associate different agent server 120 with agent server 120 and/or lender server 130 (with which agent server 120 is associated).

[0092] Based on receiving the notification in connection with associating the new Vendor and/or new Agent with the agent network, application server 150 and/or agent server 120 may use the lender-agent application to create and agent network referral and output the agent network referral to vendor server 140 and/or different agent server 120 (BLOCKS 1010 and 1015). The agent network referral may include information associated with the Lender and/or lender server 130, the Agent and/or agent server 120, and/or information associated with one or more other Vendors and/or vendor servers 140 and/or other Agents and/or other agent servers 120. The agent network referral may inform the new Vendor and/or new Agent of the other Vendors, Agents and/or Lenders with which the new Vendor and/or new Agent may desire to do business. The agent network referral may also, or alternatively, enable vendor server 140 and/or other agent server 120 to create or update a vendor site and/or other agent site, respectively, based on information obtained from the agent network referral.

[0093] Based on outputting the agent network referral, application server 150 may update analytics associated with the agent network and/or may output the information associated with the updated analytics (BLOCKS 1020 and 1025). For example, application server 150 may obtain analytics associated with the agent network (e.g., from an agent profile and/or lender profile stored in database 155) and may store, in the profile, information that indicates that the new Vendor and/or new Agent are associated with the agent network. Additionally, or alternatively, the application server 150 may store, in the profile, information associated with the creation and/or output of the agent network referral. Application server 150 may output information associated with the updated analytics to lender server 130 and/or agent server 120 that may enable the information, associated with the updated analytics to be displayed via the lender site (e.g., hosted by lender serve 130) and/or agent site (e.g., agent network site hosted by agent server 120.

[0094] Turning now to Fig. 10B, user device 1 10 may access a lender site, agent site or vendor site to receive a service. For example, when user device 1 10 access a lender site, lender server 130 may receive a request, from user device 110, to access a lender service and/or an agent service (e.g., when the user selects an identifier associated with an Agent associated with the Lender), and/or a vendor service (e.g., when the user selects a second identifier associated with a Vendor associated with the Lender) (BLOCK 1035). Lender server 130 may determine a type of service being requested and based on such a determination may provide the service and/or create a referral and/or an agent network referral (BLOCK 1040). In a non-limiting example, when lender server 130 determines that the request pertains to a lender service, lender server 130 may provide the service or output a notification for a Lender to contact the user, of user device 1 10. Additionally, or alternatively, lender server 130 may obtain (e.g., from application server 150 and/or a memory associated with lender server 130) information associated with the agent network with which lender server 130 is associated. The information, associated with the agent network, may include information associated with each Lender and/or lender server 130, each Agent and/or agent server 120, and/or each Vendor and/or vendor server 130 associated with the agent network. Lender server 130 may create an agent network referral based on the information associated with the agent network and may output the network agent referral to user device 110 (BLOCK 1045 and 1050).

[0095] In the event that lender server 130 determines that the requested service is an agent service, lender server 130 may create a referral that includes information associated with lender server 130 and/or the Lender, as well as information associated with the type of service being requested, information associated with user device 1 10 (e.g., a MDN, an IP address, etc.) and/or information associated with the user (e.g., a user name, address, telephone number, email address, a description of the requested service, etc.). Lender server 130 may output the referral agent server 120 to enable an Agent, associated with agent server 120, to contact the user (e.g., by telephone, communicating with user device 110, etc.). In another non- limiting example, when lender server 130 determines that the request pertains to a vendor service, lender server 130 may output the referral to vendor server 140 to enable a Vendor, associated with vendor server 140, to contact the user (e.g., by telephone, communicating with user device 110, etc.). While the example, above describes the user device 110 accessing a lender site, similar referrals may be generated and/or outputted to the agent network by agent server 120, when user device 110 accesses or requests a service via an agent site and/or when user device 110 accesses and/or requests a service via a vendor site.

[0096] Based on outputting the referral and/or agent network referral, application server 150 may receive, from lender server 130, an indication that the referral and/or agent network referral has been outputted. Based on receiving such an indication, application server 150 may update analytics associated with the agent network based on information associated with the type of service requested and/or information associated with the referral and/or agent network referral (BLOCK 1055). In a non-limiting example, application server 150 may obtain analytics associated with the agent network (e.g., from an agent profile, lender profile, and/or vendor profile stored in database 155) and may store, in one or more of the profiles and/or database 155, analytics information associated with user device 110, the user, the type of service requested, a time associated with the request, the referral outputted and/or the agent network referral that was outputted. Application server 150 may output information associated with the updated analytics to lender server 130 and/or agent server 120 that may enable the information, associated with the updated analytics, to be displayed via the lender site (e.g., hosted by lender serve 130) and/or agent site (e.g., agent network site hosted by agent server 120) (BLOCK 1060).

[0097] Fig. 11 is a diagram of an example user interface 1100 that may include analytics associated with services provisioned according to an implementation described herein. User interface 1100 may be displayed on a display device associated with agent server 120 and/or application server 150. As shown in Fig. 1 1, user interface 1100 may include a collection of fields and/or buttons including an agent field 1 105, a property listing field 11 10, and an agent network field 1120.

[0098] Agent field 1105 may include information associated with an Agent (e.g., an Agent name, address, etc.). Property listing field 1 110 may include information associated with one or more property listings entered by the Agent identified in agent field 1 105. Each property listing may include an identifier associated with a property (e.g., shown as property 1, property 2, etc.), information that identifies a property location (e.g., shown as address 1, address2, etc.), a date on which the property was listed and/or entered as a property listing (e.g., 1/27/2015, 1 1/15/2015, etc.), a type of property (e.g., single family, condominium, etc.), the property owner (e.g., shown as J. Smith, J. Doe, etc.), a listing price, etc.

[0099] Property listing field 11 10 may also include analytics information that identifies, for example, a quantity of property listings, a quantity of types of listings, a quantity of views to the property listing (e.g., via the property listing site, agent site, etc.), a quantity of leads (e.g., based on a user, of user device 110, that has expressed interest in the listed property), a ration of the quantity of leads relative to the quantity of view (e.g., shown as conversion %), etc. Other analytics that property listing field 1 110 may include are quantity of referrals received from other Vendors (e.g., received from vendor servers 140), Agents (e.g., received from other agent servers 120), and/or lender (e.g., received from servers 130); quantity of agent network referrals associated with the listing properties, trends regarding the one or more analytics parameters, etc.

[00100] Refer button 1 11 1 may, when selected (e.g., by an Agent, etc.), cause information, associated with the property listing, with which refer button 1 1 11 corresponds, to be transmitted to another agent server 120, lender server 130, vendor server 140 and/or user device 110.

[00101] Agent network field 1120 may include a lender network field 1 122, an other agent network field 1 124 and/or a vendor network field 1 126. Lender network field 1 122 may include information associated with a Lender within the Agent's agent network such as a Lender name, address, a time at which the Lender was associated with the agent network, a type of lender (e.g., mortgage loans, refinance, etc.), a name of a loan officer (e.g., R. Cash), a license associated with the Lender and/or loan officer, etc. Lender network field 1 122 may include a refer button 1123, that when selected, may cause agent server 120 to transmit a referral, associated with the Lender, to another agent server 120, lender server 130, vendor server 140 and/or user device 1 10.

[00102] Other agent network field 1124 may include information associated with another Agent within the Agent's agent network such as an other Agent name, address, a time at which the other Agent was associated with the agent network, a type of other Agent (e.g., premium properties, investment properties, residential properties, etc.), a name of a particular other agent (e.g., J. James, J. Russell, etc.), a license associated with the other Agent (e.g., not shown in Fig. 11), a geographical region covered by the other agent, etc. Other agent network field 1 124 may include a refer button 1125, that when selected, may cause agent server 120 to transmit a referral, associated with the other Agent, to another agent server 120, lender server 130, vendor server 140 and/or user device 1 10.

[00103] Vendor network field 1 126 may include information associated with a Vendor within the Agent's agent network such as a Vendor name, address, a time at which the Vendor was associated with the agent network, a type of Vendor (e.g., home repair, maintenance, HVAC, home inspection, termite services, legal services, construction, etc.), a name of a particular Vendor (e.g., R. Bass, A. Long, etc.), a license associated with the Vendor (e.g., not shown in Fig. 1 1), a geographical region covered by the Vendor, etc. Vendor network field 1 126 may include a refer button 1127, that when selected, may cause agent server 120 to transmit a referral, associated with the Vendor, to another agent server 120, lender server 130, vendor server 140 and/or user device 110.

[00104] The number of fields and/or buttons shown in Fig. 1 1, with respect to user interface 1100, is provided for explanatory purposes only. Additionally, or alternatively, user interface 1100 may include additional fields and/or buttons, fewer fields and/or buttons, different fields and/or buttons, or differently arranged fields and/or buttons than are shown in Fig. 1 1.

[00105] Fig. 12 is a flowchart of an example process 1200 for tracking performance of pre- closing activities and post-closing activities, associated with a property listing according to an implementation described herein. Process 1200 may be performed by an application server 150. Additionally, or alternatively, process 1200 may be performed by a device or combination of devices separate from or in addition to application server 150 including, for example, agent server 120. Fig. 13 is a diagram of an example user interface 1300 via which information associated with performance of pre-closing and/or post-closing activities associated with a property listing that may be presented. Some or all of process 1200 of Fig. 12 is described below with references to user interface 1300 of Fig. 13. Assume, in the description below, that a user, associated with a user device 110, has made an offer to purchase property associated with a property listing within the Agent's property listing site.

[00106] As shown in Fig. 12, process 1200 may include receiving an indication that an offer to purchase real estate, associated with a property listing, has been made by a user of user device 110. The offer may be documented in a writing (e.g., a purchase offer, etc.) and uploaded by user device 110 and/or by the Agent to agent server 120. Uploading the offer may provide an indication, to agent server 120, that an offer has been received (BLOCK 1205). Agent server 120 may transmit, to application server 150, another indication that an offer, associated with the property listing, has been received. Based on receiving the indication, application server 150 and/or agent server 120 may obtain, from database 155 and/or a memory associated with agent server 120, first information associated with one or more activities that are expected to be performed by the user (e.g., buyer), seller, Agent, Lender, Vendor, etc. prior to closing on the property (BLOCK 1210). Application server 150 and/or agent server 120 may output the first information, such as by presenting the first information, for display on display device associated with agent server 120, via a user interface such as user interface 1300 of Fig. 13 (BLOCK 1215). Outputting the first information may enable user device 110 to access the user interface to allow the user, buyer and/or seller to view and track progress toward closing.

[00107] As illustrated in Fig. 13, user interface 1300 may include a collection of fields and/or buttons including an agent field 1305, a property listing field 1310, a pre-closing activity field 1315 (hereinafter, "pre-closing field 1315"), a post-closing activity field 1320 (hereinafter, "post- closing field 1320") and a property document library field 1325. Agent field 1305 may include information associated with the Agent with which agent server 120 is associated (e.g., the Agent name, address, etc.). Property listing field 1310 may include information associated with the property for which an offer has been received (e.g., a property identifier (e.g., Property 1), an address associated with the property, a purchase price offered for the property (e.g., $1,346,000), etc.

[00108] Pre-closing field 1315 may identify one or more activities to be performed prior to closing (e.g., sign contract, perform inspection, provide utility bills, apply for mortgage, etc.), a date on which performing such activities are due, a status of such activities (e.g., closed, open, in work, etc.), and a field that identifies which party is responsible for performing such activities (e.g., buyer, seller, Lender, Agent, Vendor, etc.). Pre-closing field 1315 may also, or alternatively, include one or more find buttons 1316 associated with some or all of the listed pre- closing activities that, when selected, may cause agent server 120 and/or applications server 150 to transmit a list of Lenders and/or Vendors, associated with the agent network, from which the user may select to assist in completing the activity with which find button 1316 is associated. When an activity is complete, the Agent may select a status field (e.g., using a mouse, touching a screen, pressing a key on a keyboard, etc.) associated with an activity to update the status (e.g., from open to close) when an activity is complete.

[00109] Returning to Fig. 12, process 1200 may include obtaining second information associated with the performance of one or more pre-closing activities and processing the second information based on the first information to identify progress toward closing (BLOCKS 1220 and 1225). For example, application server 150 and/or agent server 120 may obtain, from database 155 and/or a memory associated with agent server 120 respectively, the second information and may determine a quantity of activities that have been completed relative to those that have not been completed based on the first information. Based on the comparison, application server 150 and/or agent server 120 may determine and/or compute progress toward closing based on, for example, a percentage, ratio, fraction, etc. of all closing activities that have been completed. Additionally, or alternatively, agent server 120 and/or application server 150 may obtain second information that identifies typical periods of time (e.g., an average, mean, a range of times, etc.) to complete pre-closing activities that have not been completed and may determine an estimated time to complete the incomplete activities. Application server 150 and/or agent server 120 may output the processed second information and/or first information (BLOCK 1230) for display via a user interface, such as via pre-closing field 1315 of Fig. 13, indicating the percentage, ratio, fraction, etc. of closing activities that have been completed (e.g., shown as 28 % complete in Fig. 13).

[00110] When all pre-closing activities have been performed and closing has occurred, the Agent may change the status of the closing activity (e.g., by change the status from open, as shown in pre-close field 1315 of Fig. 13, to close) which may be an indication that a closing has occurred (BLOCK 1235). Additionally, or alternatively, the Agent may cause agent server 120 to transmit an indication, to application server 150, the closing has occurred. Based on the indication, application server 150 and/or agent server 120 may obtain third information, associated with one or more post-closing maintenance activities associated with the property, from database 155 and/or a memory associated with agent server 120, respectively (BLOCK 1240).

[00111] Application server 150 and/or agent server 120 may output the third information (BLOCK 1245), such as by presenting the third information for display, on display device associated with agent server 120, via a user interface (e.g., via post-closing field 1320 of user interface 1300 of Fig. 13). Outputting the third information may enable user device 1 10 to access the user interface to allow the user, buyer and/or seller to view and track maintenance activities of the property after closing.

[00112] As illustrated in Fig. 13, post-closing field 1320 may include information that identifies one or more year-round service and/or activities that are recommended, by the Agent, for the property. In a non-limiting example, the year round activities and/or services may include a termite treatment, check smoke detectors, clean gutters, HVAC maintenance, lawn treatment, etc. Post-closing field 1320 may also, or alternatively, identify recommended due dates before which such activities should be performed.

[00113] Returning to Fig. 12, process 1200 may include obtaining fourth information associated with the performance of one or more post-closing activities and processing the fourth information based on the third information to determine progress toward completing the post- closing activity (BLOCKS 1250 and 1255). For example, application server 150 and/or agent server 120 may obtain, from database 155 and/or a memory associated with agent server 120 respectively, the fourth information and may determine a quantity of post-closing activities that have been completed relative to those that have not been completed based on the third information. Based on the comparison, application server 150 and/or agent server 120 may determine and/or compute progress toward completing the post-closing activities based on, for example, a percentage, ratio, fraction, etc. of all post-closing activities that have been completed. Application server 150 and/or agent server 120 may output the processed fourth information associated with progress toward completion of post-closing activities (BLOCK 1260) for display via a user interface, such as via post-closing field 1320 of Fig. 13, indicating the percentage, ratio, fraction, etc. of post-closing services that have been performed and/or completed (e.g., shown as 0 % complete in Fig. 13).

[00114] Post-closing field 1320 may also, or alternatively, include one or more find buttons 1321 associated with some or all of the listed post-closing activities and/or services that, when selected, may cause agent server 120 and/or applications server 150 to transmit a list of Vendors, associated with the agent network, from which the user may select to assist in completing a service and/or activity with which find button 1321 is associated. When a service and/or an activity is complete, the Agent may select a status field (e.g., using a mouse, touching a screen, pressing a key on a keyboard, etc.) associated with the service and/or activity to update the status (e.g., from open to close) when the service and/or activity is complete. Application server 150 and/or agent server 120 may cause the status of each activity to return to an incomplete status (e.g., open) based on a time period (e.g., monthly, quarterly, annually, seasonally, a time interval, etc.). [00115] User interface 1300 of Fig. 13 may include a property document field 1325 that, when selected, may display a list of documents associated with the property (e.g., a deed, a title document, flood elevation certificate, architectural drawings, surveys, insurance policies, a mortgage document, an appraisal, a lease, covenants, etc.). The user may select a document, which may cause agent server 120 and/or application server 150 to obtain the document and/or transmit the document to user device 1 10.

[00116] The foregoing description provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the embodiments. For example, the systems and/or methods are described in a manner in which lender server 130 associates one or more agent servers 120, and agent server 120 associates one or more other agent servers 120 and/or one or more vendor servers 140 for explanatory purposes and need not be so limited. In another implementation, agent server 120 may associated one or more lenders servers 130, one or more other agent servers 120 and/or one or more vendor servers 140. Additionally, or alternatively, vendor server 140 may associate one or more lender servers 130 and/or one or more agent servers 120.

[00117] While series of blocks have been described with regard to Figs. 5, 8, 10A, 10B, and 12, the order and/or timing of the blocks is not intended to be limiting and may be modified in other implementations. Further, non-dependent blocks may be performed in parallel, concurrently, substantially concurrently, and/or in a different order. Additionally, or alternatively, in other implementations, the processes described with regard to Figs. 5, 8, 10A, 10B, and 12 may include additional elements, less elements, modified elements, and/or different elements than shown in Figs. 5, 8, 10A, 10B, and 12.

[00118] It will be apparent that systems and methods, as described above, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the implementations. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code— it being understood that software and control hardware can be designed to implement the systems and methods based on the description herein.

[00119] Further, certain portions, described above, may be implemented as a component or logic that performs one or more functions. A component or logic, as used herein, may include hardware, such as a processor, an ASIC, or a FPGA, or a combination of hardware and software (e.g., a processor executing software).

[00120] It should be emphasized that the terms comprises and comprising, when used in this specification, are taken to specify the presence of stated features, integers, steps or components but do not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

[00121] Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of the embodiments. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one other claim, the disclosure of the embodiments includes each dependent claim in combination with every other claim in the claim set.

[00122] No element, act, or instruction used in the present application should be construed as critical or essential to the implementations unless explicitly described as such. Also, as used herein, the article "a" is intended to include one or more items. Where only one item is intended, the term "one" or similar language is used. Further, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise.

Claims

WHAT IS CLAIMED IS:

1. A first server associated with a real estate agent providing real state services, the first server comprising:

one or more processors executing one or more instructions to:

receive, from a second server associated with a mortgage lender, a first invitation to associate with the second server;

output, to the second server, an acceptance of the first invitation; receive, from the second server, an instruction to create a website, the instruction including information associated with the mortgage lender;

obtain, based on receiving the instruction, information associated with one or more property listings of the agent;

create a first web page based on the information associated with the one or more property listings or the information associated with the mortgage lender;

output, to a third server associated with a vendor of services used in the real estate industry, a second invitation to associate the third server with the first server;

receive, from the third server, an acceptance of the second invitation, the acceptance of the second invitation including information associated with the vendor; associate the third server with the first server or the second server based on the acceptance of the second invitation;

create a second web page based on at least one of:

information associated the agent,

the information associated with the mortgage lender, or

the information associated with the vendor;

output the website based on the first web page and the second webpage;

receive, from a user device and via the second webpage, a request for service; and output, to the second server or the third server, a referral based on receiving the request for service, the referral including information associated with the user device or a user of the user device.

2. The first server of claim 1, where the one or more processors are further to:

output, to a fourth server associated with another real estate agent, a third invitation to associate the fourth server with the first server;

receive, from the fourth server, an acceptance of the third invitation, the acceptance of the third invitation including information associated with the other agent; associate the fourth server with the first server, the second server, or the third server based on the acceptance of the third invitation;

update the second web page based on the information associated the other agent; output the website based on the first web page and the updated second webpage; receive, from another user device and via the updated second web page, a particular request for service; and

output, to the second server, the third server or the fourth server, a different referral based on receiving the particular request for service.

3. The first server of claim 1, where, when associating the third server with the first server or the second server, the one or more processors are further to:

output, to the second server, a notification that the third server is associated with the first server or the second user device.

4. The first server of claim 1, where the one or more processors are further to:

receiving, from another user device and via the first web page, a request for information associated with a property listing, of the one or more property listings;

output, to the other user device, the information associated with the property listing;

create particular referral based on the information associated with the lender, the information associated with the agent, and the information associated with the vendor; and

output, to the other user device, the particular referral.

5. The first server of claim 1, where

the information associated with the agent includes information associated with the first server,

the information associated with the mortgage lender includes information associated with the second server, and

the information associated with the vendor includes information associated with the third server.

6. The first server of claim 1, where the one or more processors are further to:

receive an indication that an offer to purchase property, associated with a property listing of the one or more property listings, has been received,

obtain first information that identifies pre-closing activities, relating to the property listing, to be performed to enable closing on a sale of the property; output the first information for display via a user interface that can be accessed by a purchaser or seller of the property;

obtain second information that identifies which of the pre-closing activities have been performed;

process the second information, based on the first information, to determine a percentage of the pre-closing activities that have been performed; and

output the second information or the processed second information for display via the user interface to enable the purchaser or the seller of the property to identify:

which of the pre-closing activities have been performed, or

the percentage of the pre-closing activities that have been performed.

7. The first server of claim 6, where the one or more processors are further to:

receive a notification that the closing has occurred;

obtain, based on receiving the notification, third information associated with post- closing activities relating to the maintenance of the property after the closing on the sale of the property;

output the third information for display via a different user interface that can be accessed by the purchaser of the property;

obtain fourth information that identifies which of the post-closing activities have been performed;

process the fourth information, based on the third information, to determine a percentage of the posting-closing activities that have been performed; and

output the fourth information or the processed fourth information for display via the different user interface to enable the purchaser of the property to identify

which of the post-closing activities have been performed, or

the percentage of the post-closing activities that have been performed.

8. A system to provision integrated and interactive lender and real estate services to a user device, the system comprising:

a first server, associated with a lender, executing one or more first instructions to communicate with or provision a lender service to the user device, the lender service enabling a user, of the user device, to obtain a mortgage on a property being purchased by the user;

a second server, associated with a vendor, executing one or more second instructions to communicate with or provision a vendor service to the user device, the vender service enabling the user or a seller, of the property, to close on the property or to maintain the property after the closing; a third server, associated with a real estate agent, executing one or more third instructions to communicate with or provision an agent service to the user device, the agent service enabling the user or the seller to purchase or sell the property, respectively, where the third server is further to:

receive, a first referral from the first server or the second server, the referral including information associated with the user device or the user;

communicate, with the user device, to enable the agent service to be provided to the user device or the user in connection with the purchase of the property,

receive, from the user device, an offer to purchase the property,

obtain, based on receiving the offer, first information that identifies pre-closing activities, relating to the property, to be performed to enable a closing on the property; output the first information to the user device or a different user device associated with the seller;

output, to the first server or the second server, a second referral that identifies one or more of the pre-closing activities to be performed, the second referral enabling:

the first server to communicate with the user device to provide the lender service associated with at least one of the pre-closing activities, or the second server to communicate with the user device to provide the vendor service associated with at least a different one of the pre-closing activities.

9. The system of claim 8, where the third server, executing one or more third instructions, is further to:

obtain second information that identifies which of the pre-closing activities have been performed, and

output the second information to the user device or the different user device associated with the seller.

10. The system of claim 9, where, when outputting the second information, the third server, executing one or more third instructions, is further to:

output the second information for display via a user interface or a website to enable the user device or a different user device, associated with the seller, to identify:

a portion of the pre-closing activities remaining to be performed to support the closing on the property,

a respective due date for some or all of the pre-closing activities, a status of each of the pre-closing activities that identifies whether the each of the pre-closing activities have been performed, or a percentage of completion of the pre-closing activities based on the portion of the pre-closing activities remaining to be performed.

11. The system of claim 9, where the third server, executing one or more third instructions, is further to:

process the second information, based on the first information, to determine a percentage of completion of all of the pre-closing activities based on the pre-closing activities that have been performed.

12. The system of claim 8, where the third server, executing one or more third instructions, is further to:

receive a notification that the closing on the property has occurred; obtain, based on receiving the notification, second information associated with post-closing activities relating to the maintenance of the property,

output the second information to the user device, and

output, to the second server, a second referral that identifies one or more of the post-closing activities to be performed, the second referral enabling the second server to communicate with the user device to provide the vendor service associated with at least one of the post-closing activities.

13. The system of claim 12, where the third server, executing one or more third instructions, is further to:

obtain third information that identifies which of the post-closing activities have been performed, and

output the third information to the user device.

14. The system of claim 8, where the first server, executing one or more first instructions, is further to:

output, to the third server and prior to sending the first referral, an invitation to associate the third server with the first server;

receive, from the first server, an acceptance of the invitation, the acceptance of the invitation including information associated with the real estate agent or information associated with the third server; and

associate the third server with the first server based on the acceptance of the invitation, associating the third server with the first server enable one or more referrals to be transmitted between the first server and the third server.

15. The system of claim 14, where the first server, executing one or more first instructions, is further to: create a website, associated with the lender, based on at least one of:

information associated the lender,

the information associated with the real estate agent, the information associated with the third server,

information associated with the second server previously associated with the first server, or

information associated with the vendor when the second server is previously associated with the first server,

receive, from the user device, a request for the agent service, and output the first referral to the third user device.

16. A method, performed by a first server, associated with a real estate agent, executing one or more instructions, the method comprising:

receiving, by the first server and from a second server associated with a lender, a first invitation to associate with the second server;

outputting, by the first server and to the second server, an acceptance of that the first invitation;

receiving, by the first server and from the second server, information associated with the lender that describes lender services offered by the lender;

obtaining, by the first server and based on receiving the information associated with the lender, information associated with one or more property listings of the agent;

creating, by the first server, a first web page based on the information associated with the one or more property listings, information associated with the agent, or the information associated with the lender;

outputting, by the first server and to a third server associated with a vendor of services used in the real estate industry, a second invitation to associate the third server with the first server;

receiving, by the first server and from the third server, an acceptance of the second invitation, the acceptance of the second invitation including information associated with the vendor;

associating, by the first server, the third server with the first server or the second server based on the acceptance of the second invitation;

creating, by the first server, a second web page based on at least one of:

the information associated the agent,

the information associated with the lender, or

the information associated with the vendor; outputting, by the first server, the website based on the first web page and the second webpage;

receiving, by the first server and from a user device via the first webpage, a request for service; and

outputting, by the first server and to the second server or the third server, a referral based on receiving the request for service, the referral including information associated with the user device or a user of the user device.

17. The method of claim 16, further comprising:

outputting, by the first server and to a fourth server associated with another real estate agent, a third invitation to associate the fourth server with the first server;

receiving, by the first server and from the fourth server, an acceptance of the third invitation, the acceptance of the third invitation including information associated with the other agent;

associating, by the first server, the fourth server with the first server, the second server, or the third server based on the acceptance of the third invitation;

updating, by the first server, the second web page based on the information associated the other agent;

outputting, by the first server, the website based on the first web page and the updated second webpage;

receiving, by the first server and from another user device via the updated second web page, a particular request for service; and

outputting, by the first server and to the second server, the third server or the fourth server, a different referral based on receiving the particular request for service.

18. The method of claim 16, where associating the third server with the first server or the second server further comprises:

outputting, by the first server and to the second server, a notification that the third server is associated with the first server or the second user device,

the notification including information associated with third server or the information associated with the vendor.

19. The method of claim 16, further comprising:

receiving, by the first server and from another user device via the first web page, a request for information associated with a property listing, of the one or more property listings; outputting, by the first server and to the other user device, the information associated with the property listing;

creating, by the first server, particular referral based on the information associated with the lender, the information associated with the agent, or the information associated with the vendor; and

outputting, by the first server and to the other user device, the particular referral.

The method of claim 16, further comprising:

receiving, by the first server, an offer to purchase property, associated with a property listing of the one or more property listings;

obtaining, by the first server, first information that identifies pre-closing activities, relating to the property listing, to be performed to enable closing of the purchase of the property;

outputting, by the first server, the first information for display via a user interface that can be accessed by a purchaser or seller of the property;

obtaining, by the first server, second information that identifies which of the pre- closing activities have been performed;

processing, by the first server, the second information, based on the first information, to determine a percentage of the pre-closing activities that have been performed; and

outputting, by the first server, the second information or the processed second information for display via the user interface to enable the purchaser or the seller of the property to identify

a portion of the pre-closing activities that have been performed, or the percentage of the pre-closing activities that have been performed.

The method of claim 16, further comprising:

receiving, by the first server, a notification that the closing has occurred;

obtaining, by the first server and based on receiving the notification, third information associated with post-closing activities relating to maintenance of the property after the closing;

outputting, by the first server, the third information for display via a different user interface that can be accessed by the purchaser of the property;

obtaining, by the first server, fourth information that identifies which of the post- closing activities have been performed; processing, by the first server, the fourth information, based on the third information, to determine a percentage of the posting-closing activities that have been performed; and

outputting, by the first server, the fourth information or the processed fourth information for display via the different user interface to enable the purchaser, of the property, to identify:

which of the post-closing activities have been performed, or the percentage of the post-closing activities that have been performed.