Business support apparatus, method for producing graph of business profit, and program

Abstract

To solve the conventional problem that a business profit structure cannot be properly visualized.SOLUTION: A business support apparatus 1 configured to properly visualize a business profit structure includes: a graph configuring unit 132 that uses business information containing one or more pieces of funnel information, one or more pieces of tier information associated with the one or more pieces of funnel information, and one or more pieces of revenue information associated with the one or more pieces of tier information, and further containing probability information of a next action being performed, to configure a graph with a graph structure in which the one or more pieces of funnel information, the one or more pieces of tier information, and the one or more pieces of revenue information are taken as nodes, association between the funnel information and the tier information is taken as an edge connecting the node of the funnel information and the node of the tier information and association between the tier information and the revenue information is taken as an edge connecting the node of the tier information and the node of the revenue information, the nodes being respectively associated with names, and the edges being associated with the probability information; and a graph output unit 141 which outputs the graph configured by the graph configuring unit 132.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a business support device or the like that visualizes the profit structure of a business. [Background technology]

[0002] BACKGROUND ART Conventionally, there has been a management support device that aims to break away from rules of thumb and efficiently propose effective measures for improving management in a business entity (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-160633 Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional technologies have not been able to properly visualize the revenue structure of a business. [Means for solving the problem]

[0005] The business support device of the first invention is business information related to a business corresponding to one budget, the business information being information related to a funnel which is a starting stage among one or more stages related to the business, one or more funnel information having a funnel name, information corresponding to each of the one or more funnel information and identifying a tier which is a stage at the end of the funnel and a stage before sales, one or more tier information having a tier name, information corresponding to each of the one or more tier information and identifying revenue which is a product or product category at the end of the tier, one or more revenue information having a revenue name, first probability information related to the corresponding funnel information and tier information and the probability that the funnel specified by the funnel information will be performed and the tier specified by the tier information will be performed, and tier information related to the corresponding tier information and revenue information the business support device is provided with: a business management unit that stores business information having second probability information related to the probability that a tier specified by the funnel information will be performed and that a revenue specified by the revenue information will be performed; a graph configuration unit that configures a graph in which one or more pieces of funnel information, one or more pieces of tier information, and one or more pieces of revenue information are nodes, the correspondence between the funnel information and the tier information is represented by edges connecting the funnel information nodes and the tier information nodes, and the correspondence between the tier information and the revenue information is represented by edges connecting the tier information nodes and the revenue information nodes, and the funnel information nodes, the tier information nodes, and the revenue information nodes are respectively associated with funnel names, tier names, and revenue names, and the edges are associated with the first probability information or the second probability information; and a graph output unit that outputs the graph configured by the graph configuration unit.

[0006] This configuration allows the revenue structure of a business to be properly visualized in a graph.

[0007] Furthermore, in the business support device of the second invention, compared to the first invention, the funnel information also has the quantity of actions to be taken corresponding to the funnel information, the tier information also has the quantity of actions to be taken corresponding to the tier information, and the revenue information also has the quantity of actions to be taken corresponding to the revenue information, and the graph construction unit constructs a graph in which the nodes of the funnel information, the nodes of the tier information, and the nodes of the revenue information correspond to funnel names and quantities, tier names and quantities, and revenue names and quantities, respectively.

[0008] This configuration allows the revenue structure of a business to be properly visualized using a graph.

[0009] Furthermore, the business support device of the third invention is a business support device in which a lead time is associated with each of one or more edges in comparison with the second invention.

[0010] This configuration allows the revenue structure of a business to be properly visualized using a graph.

[0011] Furthermore, the business support device of the fourth invention is a business support device that, compared to the third invention, includes a sales information acquisition unit that acquires sales information for two or more months using quantities and lead times corresponding to one or more revenues, and a sales information output unit that outputs the sales information for each month acquired by the sales information acquisition unit.

[0012] With this configuration, sales information that takes lead time into consideration can be acquired.

[0013] Furthermore, the business support device of the fifth invention is a business support device in which, compared to any one of the first to fourth inventions, the graph construction unit constructs a graph in which the outer shape of a node of any type of funnel information, tier information, or revenue information has a different outer shape depending on the type of node.

[0014] This configuration allows the revenue structure of a business to be properly visualized using a graph.

[0015] Furthermore, the business support device of the sixth invention is a business support device in which, compared to the second invention, one or more pieces of revenue information have a unit price, and the graph construction unit constructs a graph in which sales calculated by multiplying the unit price and quantity correspond to nodes of one or more pieces of revenue information.

[0016] This configuration allows the revenue structure of a business to be properly visualized using a graph.

[0017] In addition, the business support device of the seventh invention is a business support device that, in addition to any one of the first to sixth inventions, further includes an editing instruction receiving unit that receives editing instructions for the graph output by the graph output unit, a graph modification unit that modifies the graph output by the graph output unit in accordance with the editing instructions, and a business information modification unit that modifies the business information of the business management unit in accordance with the changes made by the graph modification unit.

[0018] With this configuration, it is possible to edit a graph showing the profit structure of a business. [Effects of the Invention]

[0019] According to the business support device of the present invention, the profit structure of a business can be appropriately visualized. [Brief explanation of the drawings]

[0020] [Figure 1] Conceptual diagram of business support system A in embodiment 1 [Figure 2] Block diagram of the business support system A [Figure 3] A flowchart illustrating an example of the operation of the business support device 1. [Figure 4] A flowchart illustrating an example of the accumulation process [Figure 5] A flowchart illustrating an example of the graph configuration process. [Figure 6] A flowchart illustrating an example of the change process [Figure 7] Flowchart for explaining an example of the node deletion process [Figure 8]A flowchart illustrating an example of the edge deletion process [Figure 9] A flowchart illustrating an example of the sales information acquisition process [Figure 10] A flowchart illustrating an example of the operation of the terminal device 2 [Figure 11] An example of the project information [Figure 12] An example of the project information [Figure 13] Figure showing an example of the graph output [Figure 14] Figure showing an example of the sales information management table output [Figure 15] An example of the project information [Figure 16] An example of the project information [Figure 17] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

[0021] Hereinafter, embodiments of a business support device and the like will be described with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore repeated description may be omitted.

[0022] (Embodiment 1) In this embodiment, a business support device is described that uses information on the relationships and transition probabilities between funnels, tiers, and revenues corresponding to a single budget to create and output a graph that visually shows the revenue structure of a business. A single budget can be considered to be synonymous with a single organization. An organization is typically an entity that conducts business, such as a company, an organization, a company department, a company's workplace, or a sole proprietorship. A budget is a budget for conducting business and is a unit of business.

[0023] In this embodiment, a business support device that also manages the lead time between the funnel and the tier, and between the tier and the revenue, and outputs sales information for each month taking the lead time into consideration will be described.

[0024] In this embodiment, a business support device will be described which manages the unit price of revenue and outputs sales figures in association with each revenue.

[0025] In this embodiment, a business support device will be described in which the graph being output is editable, and the managed business information is updated by editing the graph.

[0026] 1 is a conceptual diagram of a business support system A according to this embodiment. The business support system A includes a business support device 1 and one or more terminal devices 2.

[0027] The business support device 1 and one or more terminal devices 2 are usually capable of communicating with each other via a network such as the Internet.

[0028] The business support device 1 is a server that manages business information for each of one or more budgets and can provide the user with a graph that graphically shows the profit status of the business. The business support device 1 may also be a terminal. When the business support device 1 is a server, it is, for example, an ASP server, a cloud server, etc. When the business support device 1 is a terminal, it is, for example, a so-called personal computer, a tablet terminal, a smartphone, etc. However, the type of business support device 1 is not important.

[0029] The terminal device 2 is a terminal used by a user to input business information and output graphs. The terminal device 2 may be, for example, a personal computer, a tablet terminal, a smartphone, or the like, and the type does not matter. Note that if the business support device 1 is a terminal, the terminal device 2 is not required.

[0030] 2 is a block diagram of a business support system A according to this embodiment. The business support device 1 includes a storage unit 11, a reception unit 12, a processing unit 13, and an output unit 14. The storage unit 11 includes a business management unit 111 and a sales information management unit 112. The reception unit 12 includes a business information reception unit 121 and an editing instruction reception unit 122. The processing unit 13 includes an accumulation unit 131, a graph construction unit 132, a sales information acquisition unit 133, a graph modification unit 133, and a business information modification unit 134. The output unit 14 includes a graph output unit 141 and a sales information output unit 142.

[0031] The terminal device 2 includes a terminal storage unit 21, a terminal reception unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal reception unit 25, and a terminal output unit 26.

[0032] Various types of information are stored in the storage unit 11 that constitutes the business support device 1. The various types of information include, for example, business information (described later), sales information (described later), and a budget identifier. The budget identifier is information that identifies a budget. The budget identifier may also be information that identifies an organization. The budget identifier is, for example, an ID, a budget name, or a company name.

[0033] The business management unit 111 stores one or more business information. A budget identifier is associated with each of the one or more business information. For example, an organization identifier is associated with each of the one or more business information. The organization identifier is information that identifies an organization. For example, the organization identifier is an organization ID or organization name.

[0034] The business information includes one or more funnel information. The business information includes one or more tier information. The business information includes one or more revenue information. The business information includes, for example, one or more edge information. The business information includes one or more probability information. The probability information is, for example, first probability information or second probability information described below. The business information includes, for example, one or more lead times.

[0035] Funnel information is information related to funnels. A funnel is the starting stage among one or more stages related to a business. Each of the two or more stages has an order. A stage is, for example, an action related to a business or information related to a business. A funnel includes, for example, an entry action into a business. Examples of funnels are "app download," "webpage access," "membership registration," "agency introduction," and "exhibition." Funnel information includes the funnel name, quantity, lead time, growth rate, change rate, and points of contact with other funnels. The subject of the action here is, for example, a consumer, business, or agency.

[0036] Additionally, multiple funnels and tiers can be combined and treated as a single funnel. For example, "SNA ad impressions" could be defined as Funnel A, with "clicks," "downloads," and "membership registrations" defined as the tiers below it, "offline events" could be defined as Funnel B, with "applications," "participation (downloads)," and "membership registrations" defined as the tiers below it, and the final tier of "membership registrations" could be combined to define "total number of members" as Funnel C, with "monthly number of users" defined as the tier below it.

[0037] Tier information is information about tiers. A tier is a stage at the end of a funnel, a stage before sales. Here, "end" refers to a later stage in time. Sales refers to a consumer purchasing a product or service. Starting from the funnel, there may be linear or tree-like tiers, which are more detailed stages. For example, a funnel may be defined as "LP inflow," and a tier may be defined as "click" or "application." Examples of tiers include "membership registration" and "payment information registration." Tier information corresponds to, for example, one or more pieces of funnel information. Tier information associated with funnel information is information about the tier that follows the funnel identified by the funnel information. One or more pieces of tier information may correspond to one or more pieces of tier information. In other words, a funnel and a tier have a 1-to-N (N is a natural number greater than or equal to 1) relationship, and tiers may have an N-to-N relationship. Tier information includes a tier name. Tier information includes, for example, a quantity. Note that the subject of the action here may be, for example, a consumer, a business, or an agency.

[0038] Revenue information is information related to revenue. Revenue is the product or product category beyond the tier. Revenue is, for example, something that generates sales, an action that determines profits. Product can also be a consumer action. An action that determines profits can be said to be an action that determines the sale of a product or service. Product categories are, for example, "high-priced products" and "low-priced products." Revenue is, for example, "paid membership registration" or "product purchase." Revenue information corresponds to one or more pieces of tier information. Revenue information that corresponds to tier information is information on revenue that occurs after the tier specified by the tier information. Revenue information has a revenue name. Revenue information has, for example, a quantity. Revenue information has, for example, a unit price. The unit price is the unit price for the product or service that corresponds to the revenue information.

[0039] The funnel information, tier information, and revenue information correspond to nodes in a graph, which will be described later. The funnel, tier, and revenue can be considered examples of nodes. The funnel information, tier information, and revenue information can be considered examples of node information.

[0040] Edge information is information about edges. For example, an edge associates a previously performed funnel with a tier performed after the funnel. For example, an edge associates a previously performed tier with another tier performed after the tier. For example, an edge associates a previously performed tier with a revenue performed after the tier. Edge information has information that identifies two nodes to be associated. For example, edge information has a funnel identifier and a tier identifier. For example, edge information has a tier identifier and a tier identifier. For example, edge information has a tier identifier and a revenue identifier.

[0041] The edge information may be said to have, for example, a first identifier and a second identifier. The first identifier and the second identifier are information for identifying a node. For example, the first identifier identifies a node for an action performed earlier than the node identified by the second identifier.

[0042] A funnel identifier is information that identifies a funnel. For example, a funnel identifier is a funnel ID or a funnel name. A tier identifier is information that identifies a tier. For example, a tier ID or a tier name. A revenue identifier is information that identifies revenue. For example, a revenue ID or a revenue name.

[0043] Probability information is information indicating the probability that a subsequent action will be performed among the number of previous actions (for example, the number of users).

[0044] The first probability information is information relating to the corresponding funnel information and tier information, and is information specifying the probability that a funnel specified by the funnel information will be performed, followed by a tier specified by the tier information. Examples of the first probability information are "50%" and "0.7." The first probability information is included in the edge information, for example.

[0045] The second probability information is information relating to corresponding tier information and revenue information, and is information specifying the probability that a tier specified by the tier information will be performed, followed by a revenue specified by the revenue information. The second probability information is information relating to corresponding tier information and tier information, and may be information specifying the probability that a tier specified by one piece of tier information will be performed, followed by a tier specified by the other piece of tier information. Examples of the second probability information are "60%" and "0.3". The second probability information is included in edge information, for example.

[0046] The lead time is the period from when the previous action is performed until the next action is performed. For example, the lead time is the period from when the funnel is performed until the tier is performed, or the period from when the tier is performed until the revenue is performed. For example, the lead time is "1 month," "3 months," or "0."

[0047] The sales information management unit 112 stores one or more pieces of sales information. The sales information is associated with a budget. The sales information may also be associated with revenue. The sales information is, for example, information indicating the sales amount of a product or service. The sales information is, for example, information indicating the number of products or services sold. The sales information management unit 112 typically stores two or more pieces of sales information for each month for one budget.

[0048] The reception unit 12 receives various types of information and instructions. Here, reception refers to, for example, reception, but the concept may also include reception of information input from an input device such as a keyboard, mouse, or touch panel, or reception of information read from a recording medium such as an optical disk, magnetic disk, or semiconductor memory. The various types of information and instructions include, for example, business information, elements that constitute the business information, graph output instructions, sales information output instructions, and editing instructions, which will be described later.

[0049] The graph output instruction is an instruction to output a graph. The graph output instruction includes, for example, a budget identifier. The budget identifier may be the same as the organization identifier.

[0050] The sales information output instruction is an instruction to output sales information. The sales information output instruction includes, for example, a budget identifier. The budget identifier may be the same as the organization identifier.

[0051] The business information receiving unit 121 receives all or part of the business information. The part of the business information is an element that constitutes the business information. The element is, for example, all or part of the funnel information, all or part of the tier information, all or part of the revenue information, or all or part of the edge information. Here, receiving means, for example, receiving.

[0052] The editing instruction receiving unit 122 receives an instruction to edit the graph output by the graph output unit 141. The reception here refers to, for example, reception.

[0053] An editing instruction is an instruction to edit the graph output by the graph output unit 141. An editing instruction is, for example, a node addition instruction, a node deletion instruction, a node modification instruction, an edge addition instruction, an edge deletion instruction, or an edge modification instruction. A node addition instruction is an instruction to add a node. A node is a funnel, a tier, or a revenue. A node deletion instruction is an instruction to delete a node. A node modification instruction is an instruction to change some or all of the node information. An edge addition instruction is an instruction to add edge information. An edge deletion instruction is an instruction to delete edge information. An edge modification instruction is an instruction to change edge information.

[0054] The processing unit 13 performs various types of processing. The various types of processing are, for example, processing performed by the storage unit 131, the graph configuration unit 132, the sales information acquisition unit 133, the graph modification unit 133, or the business information modification unit 134.

[0055] The storage unit 131 stores some or all of the business information received by the business information receiving unit 121 in the business management unit 111. The structure of the business information stored by the storage unit 131 is not important. The storage unit 131 stores, for example, a funnel management table, a tier management table, a revenue management table, and an edge management table, which will be described later. The storage unit 131 stores the business information in, for example, the JSON format, which will be described later.

[0056] The graph construction unit 132 constructs a graph. A graph is a diagram of a network structure having nodes and edges. Here, the edges are usually directed. For example, in response to receiving a graph output instruction, the graph construction unit 132 constructs a graph showing a revenue structure that can be read from information contained in the business information of the budget corresponding to the graph output instruction.

[0057] The graph construction unit 132 constructs a graph in which, for example, funnel information nodes, tier information nodes, and revenue information nodes correspond to funnel names and quantities, tier names and quantities, and revenue names and quantities, respectively.

[0058] The graph construction unit 132 preferably constructs a graph in which the outer shape of any one of the types of nodes, among funnel information, tier information, and revenue information, varies depending on the type of node. Different outer shapes mean different node attribute values. The node attribute values ​​include, for example, the shape of the node, the background color of the node, the font of the character string within the node, and the font color of the character string within the node.

[0059] The graph construction unit 132 constructs a graph in which, for example, for each of one or more pieces of revenue information, the sales amount obtained by multiplying the unit price by the quantity is associated with the node of the revenue information.

[0060] The sales information acquisition unit 133 acquires sales information for two or more months using the quantity and lead time corresponding to one or more revenues. There is no restriction on the trigger for the sales information acquisition unit 133 to acquire the sales information. Examples of triggers include the business information reception unit 121 receiving business information, the reception unit 12 receiving an instruction to obtain sales information, or a predetermined time (for example, 12:00 on the first day of each month).

[0061] The graph modification unit 133 modifies the graph output by the graph output unit 141 in accordance with the editing instruction received by the editing instruction receiving unit 122. The graph modification unit 133 modifies the output of the graph that is being output.

[0062] The business information change unit 134 changes the business information of the business management unit 111 in accordance with the changes made by the graph change unit 133 .

[0063] The output unit 14 outputs various types of information. The various types of information are, for example, graphs and sales information. Here, output means, for example, transmission to the terminal device 2, but may also be a concept that includes display on a display, projection using a projector, printing on a printer, sound output, storage on a recording medium, and delivery of processing results to other processing devices or other programs.

[0064] The graph output unit 141 outputs the graph constructed by the graph construction unit 132. The graph output unit 141 transmits the graph constructed by the graph construction unit 132 to the terminal device 2, for example.

[0065] The sales information output unit 142 outputs the sales information for each month acquired by the sales information acquisition unit 133. The sales information output unit 142 transmits the sales information for each month acquired by the sales information acquisition unit 133 to the terminal device 2, for example.

[0066] Various types of information are stored in the terminal storage unit 21 that constitutes the terminal device 2. The various types of information are, for example, a company identifier and a budget identifier.

[0067] The terminal reception unit 22 receives input of instructions, information, etc. from the user. Examples of instructions, information, etc. include business information, elements that make up the business information, graph output instructions, sales information output instructions, and editing instructions. Note that the means for inputting instructions, information, etc. may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0068] The means for inputting instructions and information may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0069] The device processing unit 23 performs various types of processing, such as processing to change instructions, information, etc. received by the device receiving unit 22 into instructions, information, etc. with a structure to be transmitted, and processing to change information received by the device receiving unit 25 into a structure to be output.

[0070] The terminal transmitting unit 24 transmits various types of information, instructions, etc. to the business support device 1. The various types of information, instructions, etc. are, for example, business information, elements that constitute business information, output instructions, and editing instructions.

[0071] The terminal receiving unit 25 receives various types of information from the business support device 1. The various types of information include, for example, graphs and sales information.

[0072] The terminal output unit 26 outputs various types of information. The various types of information include, for example, graphs and sales information. Here, output refers to, for example, display on a display, but may also include projection using a projector, printing with a printer, sound output, storage on a recording medium, transmission to another processing device, or delivery of processing results to another processing device or another program.

[0073] The storage unit 11, business management unit 111, sales information management unit 112, and terminal storage unit 21 are preferably non-volatile recording media, but may also be realized as volatile recording media.

[0074] There is no restriction on the process by which information is stored in the storage unit 11 etc. For example, information may be stored in the storage unit 11 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the storage unit 11 etc., or information input via an input device may be stored in the storage unit 11 etc.

[0075] The reception unit 12, the business information reception unit 121, and the editing instruction reception unit 122 are usually realized by wireless or wired communication means. However, the reception unit 12 and the like may also be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0076] The processing unit 13, storage unit 131, graph construction unit 132, sales information acquisition unit 133, graph modification unit 133, business information modification unit 134, and terminal processing unit 23 can usually be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0077] The output unit 14, graph output unit 141, and sales information output unit 142 are typically implemented by wireless or wired communication means. However, the output unit 14 and the like may also be implemented by driver software for an output device such as a display or speaker, or by a combination of driver software for an output device and the output device.

[0078] The terminal reception unit 22 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0079] The terminal transmitting unit 24 is usually realized by a wireless or wired communication means, but may also be realized by a broadcasting means.

[0080] The terminal receiving unit 25 is usually realized by a wireless or wired communication means, but may also be realized by a means for receiving broadcasts.

[0081] The terminal output unit 26 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 26 may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0082] Next, an example of the operation of the business support device 1 will be described with reference to the flowchart of FIG.

[0083] (Step S301) The business information receiving unit 121 determines whether or not business information has been received. If business information has been received, the process proceeds to step S302, and if business information has not been received, the process proceeds to step S303. The business information receiving unit 121 determines whether or not business information has been received from the terminal device 2, for example.

[0084] (Step S302) The storage unit 131 stores the business information received in step S301 in the business management unit 111. Return to step S301. An example of such storage processing will be described with reference to the flowchart of FIG.

[0085] (Step S303) The reception unit 12 determines whether or not a graph output instruction has been received. If a graph output instruction has been received, the process proceeds to step S304; if not, the process proceeds to step S306. The reception unit 12 determines whether or not a graph output instruction has been received from the terminal device 2, for example.

[0086] (Step S304) The graph configuration unit 132 configures a graph. An example of such graph configuration processing will be described with reference to the flowchart in FIG.

[0087] (Step S305) The graph output unit 141 outputs the graph constructed in step S304. Return to step S301. The graph output unit 141 transmits the graph to the terminal device 2, for example.

[0088] (Step S306) The editing instruction receiving unit 122 determines whether or not an editing instruction has been received. If an editing instruction has been received, the process proceeds to step S307; if not, the process proceeds to step S308. The editing instruction receiving unit 122 determines whether or not an editing instruction has been received from the terminal device 2, for example.

[0089] (Step S307) The business information change unit 134 changes the business information. Return to step S301. An example of such change processing will be described with reference to the flowchart in FIG.

[0090] (Step S308) The reception unit 12 determines whether or not a sales information output instruction has been received. If a sales information output instruction has been received, the process proceeds to step S309; ​​if not, the process returns to step S301. The reception unit 12 determines whether or not a sales information output instruction has been received from the terminal device 2, for example.

[0091] (Step S309) The sales information acquisition unit 133 acquires sales information. An example of the sales information acquisition process will be described with reference to the flowchart in FIG.

[0092] (Step S310) The sales information output unit 142 acquires the sales information acquired in step S309. Return to step S301. The sales information output unit 142 transmits the sales information to the terminal device 2, for example.

[0093] In the flowchart of FIG. 3, the process ends when the power is turned off or an interrupt occurs to end the process.

[0094] Next, an example of the accumulation process in step S302 will be described with reference to the flowchart in FIG.

[0095] (Step S401) The accumulation unit 131 assigns 1 to a counter i.

[0096] (Step S402) The accumulation unit 131 determines whether the i-th funnel name is included in the received business information. If the i-th funnel name is included, the process proceeds to step S403, and if the i-th funnel name is not included, the process returns to the upper process.

[0097] (Step S403) The accumulation unit 131 acquires a unique funnel identifier. The accumulation unit 131 generates funnel information having the funnel identifier and the i-th funnel name. The funnel information is, for example, the quantity in the received business information, and includes the quantity corresponding to the i-th funnel name.

[0098] (Step S404) The accumulation unit 131 accumulates the funnel information constructed in step S403 in the business management unit 111.

[0099] (Step S405) The accumulation unit 131 assigns 1 to the counter j.

[0100] (Step S406) The accumulation unit 131 determines whether the received business information includes the jth tier name corresponding to the i-th funnel name. If the jth tier name corresponding to the i-th funnel name is included, the process proceeds to step S407; if not, the process proceeds to step S413.

[0101] (Step S407) The accumulation unit 131 configures tier information having the tier identifier and the j-th tier name. Note that the tier information is, for example, the quantity in the accepted business information, and includes the quantity corresponding to the j-th tier name.

[0102] (Step S408) The accumulation unit 131 determines whether or not the tier information constructed in step S407 exists in the business management unit 111. If the tier information exists in the business management unit 111, the process proceeds to step S410, and if it does not exist, the process proceeds to step S409. Note that the comparison here does not use a tier identifier.

[0103] (Step S409) The accumulation unit 131 acquires a unique tier identifier. The accumulation unit 131 composes tier information having the tier identifier and the information acquired in step S407, and accumulates the tier information in the business management unit 111.

[0104] (Step S410) The accumulation unit 131 acquires edge information regarding an edge that links the i-th funnel information and the j-th tier information. The edge information has, for example, a funnel identifier included in the i-th funnel information and a tier identifier included in the j-th tier information. The edge information has, for example, probability information. The probability information is, for example, "quantity included in the j-th tier information / quantity included in the i-th funnel information."

[0105] (Step S411) The accumulation unit 131 accumulates the edge information acquired in step S410 in the business management unit 111.

[0106] (Step S412) The accumulation unit 131 increments the counter j by 1. The process returns to step S406.

[0107] (Step S413) The accumulation unit 131 assigns 1 to the counter k.

[0108] (Step S414) The accumulation unit 131 determines whether or not the kth lower node exists in the received business information. If the kth lower node exists, the process proceeds to step S415; if not, the process proceeds to step S427. The lower node is tier information or revenue information.

[0109] (Step S415) The accumulation unit 131 determines whether the k-th lower node is the lowest node. If it is the lowest node, the process proceeds to step S416, and if it is not the lowest node, the process proceeds to step S421.

[0110] (Step S416) The accumulation unit 131 generates revenue information having a revenue name, which is a name (character string) included in the information of the kth lower node. The revenue information includes, for example, a quantity and a unit price.

[0111] (Step S417) The accumulation unit 131 determines whether revenue information identical to the revenue information constructed in step S416 exists in the business management unit 111. If identical revenue information exists, the process proceeds to step S419; if not, the process proceeds to step S419. Note that the comparison here does not use a revenue identifier.

[0112] (Step S418) The accumulation unit 131 acquires a unique revenue identifier. Revenue information including the revenue identifier and the revenue name acquired in step S416 is created and accumulated in the business management unit 111.

[0113] (Step S419) The accumulation unit 131 acquires the identifier of the upper node of the kth lower node. The accumulation unit 131 acquires edge information having the identifier of the upper node and the identifier of the kth lower node. The edge information has, for example, probability information. The probability information is, for example, "quantity included in the node information of the kth lower node / quantity included in the node information of the upper node."

[0114] (Step S420) The accumulation unit 131 accumulates the edge information acquired in step S419 in the business management unit 111.

[0115] (Step S421) The accumulation unit 131 configures tier information having a tier name, which is a name (character string) included in the information of the kth lower node. Note that the tier information has, for example, a quantity.

[0116] (Step S422) The accumulation unit 131 determines whether or not the same tier information as the tier information constructed in step S421 exists in the business management unit 111. If the same tier information exists, proceed to step S424, and if it does not exist, proceed to step S423. Note that the comparison here does not use a tier identifier.

[0117] (Step S423) The accumulation unit 131 acquires a unique tier identifier. Tier information having the tier identifier and the tier name acquired in step S422 is constructed and accumulated in the business management unit 111.

[0118] (Step S424) The accumulation unit 131 acquires the identifier of the upper node of the kth lower node. The accumulation unit 131 acquires edge information having the identifier of the upper node and the identifier of the kth lower node. The edge information has, for example, probability information. The probability information is, for example, "quantity included in the node information of the kth lower node / quantity included in the node information of the upper node."

[0119] (Step S425) The accumulation unit 131 accumulates the edge information acquired in step S424 in the business management unit 111.

[0120] (Step S426) The accumulation unit 131 increments the counter k by 1. The process returns to step S414.

[0121] (Step S427) The accumulation unit 131 increments the counter i by 1. The process returns to step S402.

[0122] In the flowchart of FIG. 4, only tiers can be connected to revenue, but funnels, tiers, or revenues may also be connectable to revenue.

[0123] Next, an example of the graph construction process in step S304 will be described with reference to the flowchart in FIG.

[0124] (Step S501) The graph configuration unit 132 acquires a budget identifier included in the graph output instruction.

[0125] (Step S502) The graph construction unit 132 acquires the business information paired with the budget identifier from the business management unit 111.

[0126] (Step S503) The graph configuration unit 132 assigns 1 to the counter i.

[0127] (Step S504) The graph construction unit 132 determines whether the i-th funnel information exists in the business information acquired in step S502. If the i-th funnel information exists, the process proceeds to step S505; if not, the process returns to the upper process.

[0128] (Step S505) The graph construction unit 132 constructs a funnel node corresponding to the ith funnel information. The funnel node has an outer shape corresponding to the funnel information.

[0129] (Step S506) Graph configuration unit 132 places the i-th funnel node.

[0130] (Step S507) The graph configuration unit 132 assigns 1 to the counter j.

[0131] (Step S508) The graph construction unit 132 determines whether the jth edge information exists among the edge information in the business information acquired in step S502, which includes the funnel identifier of the ith funnel information. If the jth edge information exists, the process proceeds to step S509; if not, the process proceeds to step S515.

[0132] (Step S509) The graph configuration unit 132 acquires the probability information included in the j-th edge information.

[0133] (Step S510) The graph construction unit 132 constructs edges having probability information.

[0134] (Step S511) The graph construction unit 132 acquires the node identifier of the other node included in the j-th edge information. The graph construction unit 132 acquires node information corresponding to the node identifier from the business information acquired in step S502. The graph construction unit 132 uses the node information to construct a lower node.

[0135] (Step S512) The graph construction unit 132 arranges the nodes constructed in step S511.

[0136] (Step S513) Graph configuration unit 132 places the edge configured in step S510 at the position connecting the two nodes.

[0137] (Step S514) The graph configuration unit 132 increments the counter j by 1. The process returns to step S508.

[0138] (Step S515) The graph configuration unit 132 assigns 1 to a counter k.

[0139] (Step S516) Graph construction unit 132 determines whether or not a kth lower-level node that has been placed exists. If the kth lower-level node exists, the process proceeds to step S517; if not, the process proceeds to step S526.

[0140] (Step S517) The graph configuration unit 132 assigns 1 to the counter l.

[0141] (Step S518) Graph configuration unit 132 determines whether or not the l-th edge information exists. If the l-th edge information exists, the process proceeds to step S519, and if not, the process proceeds to step S525.

[0142] (Step S519) The graph configuration unit 132 acquires the probability information included in the l-th edge information.

[0143] (Step S520) The graph construction unit 132 constructs edges having probability information.

[0144] (Step S521) Graph configuration unit 132 acquires the other node identifier included in the l-th edge information. Graph configuration unit 132 acquires node information corresponding to the node identifier. Graph configuration unit 132 configures a node using the node information.

[0145] (Step S522) The graph construction unit 132 arranges the nodes constructed in step S521.

[0146] (Step S523) The graph configuration unit 132 arranges the edges configured in step S520.

[0147] (Step S524) The graph configuration unit 132 increments the counter 1 by 1. The process returns to step S518.

[0148] (Step S525) The graph configuration unit 132 increments the counter k by 1. The process returns to step S516.

[0149] (Step S526) The graph configuration unit 132 increments the counter i by 1. The process returns to step S504.

[0150] Next, an example of the change processing in step S307 will be described with reference to the flowchart in FIG.

[0151] (Step S601) Graph modification unit 133 determines whether the edit instruction is a node addition instruction. If it is a node addition instruction, the process proceeds to step S602, and if it is not a node addition instruction, the process proceeds to step S604.

[0152] (Step S602) The graph modification unit 133 acquires the funnel name, tier name, or revenue name included in the node addition instruction, and configures node information having the funnel name, tier name, or revenue name.

[0153] (Step S603) The graph modification unit 133 stores the node information configured in step S602 in the business management unit 111. The process returns to the upper level processing.

[0154] (Step S604) The graph modification unit 133 determines whether the edit instruction is an edge addition instruction. If it is an edge addition instruction, the process proceeds to step S605, and if it is not an edge addition instruction, the process proceeds to step S607.

[0155] (Step S605) The graph modification unit 133 configures edge information having the two node identifiers included in the edge addition instruction.

[0156] (Step S606) The graph modification unit 133 accumulates the edge information configured in step S605 in the business management unit 111. The process returns to the upper level processing.

[0157] (Step S607) Graph modification unit 133 determines whether the edit instruction is a node modification instruction. If it is a node modification instruction, the process proceeds to step S608, and if it is not a node modification instruction, the process proceeds to step S610.

[0158] (Step S608) The graph modification unit 133 acquires node information to be modified in response to the node modification instruction.

[0159] (Step S609) The graph modification unit 133 accumulates the node information acquired in step S608, updates the node information to be modified, and returns to the upper-level processing.

[0160] (Step S610) The graph modification unit 133 determines whether the edit instruction is an edge modification instruction. If it is an edge modification instruction, the process proceeds to step S611, and if it is not an edge modification instruction, the process proceeds to step S613.

[0161] (Step S611) The graph modification unit 133 acquires edge information to be modified in response to an edge modification instruction.

[0162] (Step S612) The graph modification unit 133 accumulates the edge information acquired in step S611, updates the edge information to be modified, and returns to the upper-level processing.

[0163] (Step S613) Graph modification unit 133 determines whether the editing instruction is a node deletion instruction. If it is a node deletion instruction, the process proceeds to step S614, and if it is not a node deletion instruction, the process proceeds to step S615. Note that here, if the editing instruction is not a node deletion instruction, the editing instruction is an edge deletion instruction.

[0164] (Step S614) In accordance with the node deletion instruction, the graph modification unit 133 performs a node deletion process to delete the node specified by the node deletion instruction, the edges below the node, and the nodes below that node that are not connected to anything else. The process then returns to the upper level process. An example of the node deletion process will be described with reference to the flowchart in FIG. 7.

[0165] (Step S615) In accordance with the edge deletion instruction, the graph modification unit 133 performs a node deletion process to delete the edge specified by the edge deletion instruction and the node that is lower than the edge and is not connected to any other nodes. The process returns to the upper level process. An example of the edge deletion process will be described with reference to the flowchart in FIG. 8.

[0166] Next, an example of the node deletion process in step S614 will be described with reference to the flowchart in FIG.

[0167] (Step S701) The graph modification unit 133 deletes from the business management unit 111 the node information identified by the node identifier included in the node deletion instruction.

[0168] (Step S702) The graph modification unit 133 acquires from the business management unit 111 one or more pieces of lower-level edge information connected to the node information deleted in step S701.

[0169] (Step S703) The graph modification unit 133 assigns 1 to the counter i.

[0170] (Step S704) The graph modification unit 133 determines whether or not the i-th edge information exists among the edge information acquired in step S702. If the i-th edge information exists, the process proceeds to step S705; if not, the process returns to the upper level process.

[0171] (Step S705) The graph modification unit 133 deletes the i-th edge information from the business management unit 111.

[0172] (Step S706) The graph modification unit 133 determines whether or not there is another node connected to the edge identified by the i-th edge information. If there is another node, the process proceeds to step S707; if there is no other node, the process proceeds to step S709.

[0173] (Step S707) Graph modification unit 133 determines whether the other node is not connected to any node other than the node deleted in step S701. If the other node is not connected to any node other than the node deleted in step S701, the process proceeds to step S708, and if the other node is connected, the process proceeds to step S709.

[0174] (Step S708) The graph modification unit 133 performs a node deletion process for the other node.

[0175] (Step S709) The graph modification unit 133 increments the counter i by 1. The process returns to step S704.

[0176] Next, an example of the edge deletion process in step S615 will be described with reference to the flowchart in FIG.

[0177] (Step S801) The graph modification unit 133 deletes the edge information that is the target of the edge deletion instruction from the business management unit 111.

[0178] (Step S802) The graph modification unit 133 determines whether or not there is a lower node connected to the edge. If there is a lower node, the process proceeds to step S803, and if there is no lower node, the process returns to the upper process.

[0179] (Step S803) The graph modification unit 133 determines whether the lower node connected to the edge is connected to another node. If it is connected to another node, the process returns to the upper level process, and if it is not connected to another node, the process proceeds to step S804.

[0180] (Step S804) The graph modification unit 133 performs processing to delete the lower node connected to the edge. This node deletion processing has been described using the flowchart in FIG.

[0181] Next, an example of the sales information acquisition process in step S309 will be described with reference to the flowchart in FIG.

[0182] (Step S901) The sales information acquisition unit 133 assigns 1 to a counter i.

[0183] (Step S902) The sales information acquisition unit 133 determines whether or not the i-th revenue information exists in the business management unit 111. If the i-th revenue information exists, the process proceeds to step S903; if not, the process proceeds to step S917.

[0184] (Step S903) The sales information acquisition unit 133 acquires the quantity included in the i-th revenue information.

[0185] (Step S904) The sales information acquisition unit 133 acquires the unit price included in the i-th revenue information.

[0186] (Step S905) The sales information acquisition unit 133 calculates the amount (quantity x unit price) corresponding to the i-th revenue information.

[0187] (Step S906) The sales information acquisition unit 133 assigns 1 to the counter j.

[0188] (Step S907) The sales information acquisition unit 133 determines whether or not the jth higher-level edge information connecting the i-th revenue information exists in the business management unit 111. If the higher-level edge information exists, the process proceeds to step S908; if not, the process proceeds to step S911.

[0189] (Step S908) The sales information acquisition unit 133 acquires the lead time included in the higher-level edge information.

[0190] (Step S909) The sales information acquisition unit 133 adds the lead time acquired in step S908.

[0191] (Step S910) The sales information acquisition unit 133 increments the counter j by 1. The process returns to step S907.

[0192] (Step S911) The sales information acquisition unit 133 acquires the sales for the total lead time period as "0." Note that the total lead time period is the period finally calculated in step S909.

[0193] (Step S912) The sales information acquiring unit 133 assigns "the period of the lead time + 1 month" to the counter k.

[0194] (Step S913) The sales information acquisition unit 133 determines whether or not to acquire the sales for the kth month. If the sales for the kth month are to be acquired, the process proceeds to step S914; if not, the process proceeds to step S916. The maximum value of k is predetermined. The maximum value of k is, for example, 12 months or 24 months.

[0195] (Step S914) The sales information acquisition unit 133 accumulates the amount calculated in step S905 in a buffer (not shown) as the k-th month's sales. Note that the sales information acquisition unit 133 may acquire the accumulated amount as the k-th month's sales.

[0196] (Step S915) The sales information acquisition unit 133 increments the counter k by 1. The process returns to step S913.

[0197] (Step S916) The sales information acquisition unit 133 increments the counter i by 1. The process returns to step S902.

[0198] (Step S917) The sales information acquisition unit 133 assigns 1 to the counter k.

[0199] (Step S918) The sales information acquisition unit 133 determines whether or not there is a kth month for calculating the total sales. The maximum value of k is predetermined. The maximum value of k is, for example, 12 months or 24 months.

[0200] (Step S919) The sales information acquisition unit 133 acquires the total amount of money for the kth month for two or more revenues, associates it with k, and stores it in a buffer (not shown).

[0201] (Step S920) The sales information acquisition unit 133 increments the counter k by 1. The process returns to step S918.

[0202] Next, an example of the operation of the terminal device 2 will be described with reference to the flowchart of FIG.

[0203] (Step S1001) The terminal reception unit 22 determines whether or not business information has been received. If business information has been received, the process proceeds to step S1002, and if not, the process proceeds to step S1003.

[0204] (Step S1002) The terminal processing unit 23 acquires a budget identifier from the terminal storage unit 21. The terminal processing unit 23 associates the business information received in step S1001 with the budget identifier. The terminal transmission unit 24 transmits the business information associated with the budget identifier to the business support device 1. Return to step S1001.

[0205] (Step S1003) The terminal reception unit 22 determines whether or not a graph output instruction has been received. If a graph output instruction has been received, the process proceeds to step S1004, and if not, the process proceeds to step S1007.

[0206] (Step S1004) The device processing unit 23 acquires a budget identifier from the terminal storage unit 21. The device processing unit 23 composes a graph output instruction having the budget identifier. The terminal transmission unit 24 transmits the graph output instruction to the business support device 1.

[0207] (Step S1005) The terminal receiving unit 25 determines whether or not a graph has been received from the business support device 1. If a graph has been received, the process proceeds to step S1006, and if not, the process returns to step S1005.

[0208] (Step S1006) The terminal processing unit 23 creates a graph to be output based on the received graph. The terminal output unit 26 outputs the graph. The process returns to step S1001.

[0209] (Step S1007) The terminal reception unit 22 determines whether or not an edit instruction has been received. If an edit instruction has been received, the process proceeds to step S1008, and if not, the process proceeds to step S1010.

[0210] (Step S1008) The terminal processing unit 23 changes the display of the graph being output in accordance with the editing instruction.

[0211] (Step S1009) The terminal processing unit 23 acquires the budget identifier corresponding to the output graph. The terminal processing unit 23 associates the editing instruction with the budget identifier. The terminal transmitting unit 24 transmits the editing instruction associated with the budget identifier to the business support device 1. Return to step S1001.

[0212] (Step S1010) Terminal reception unit 22 determines whether or not a sales information output instruction has been received. If a sales information output instruction has been received, the process proceeds to step S1011, and if not, the process returns to step S1001.

[0213] (Step S1011) The device processing unit 23 acquires a budget identifier from the terminal storage unit 21. The device processing unit 23 composes a sales information output instruction having the budget identifier. The terminal transmission unit 24 transmits the sales information output instruction to the business support device 1.

[0214] (Step S1012) The terminal receiving unit 25 determines whether or not sales information has been received from the business support device 1. If sales information has been received, the process proceeds to step S1013, and if not, the process returns to step S1012.

[0215] (Step S1013) The terminal processing unit 23 composes sales information to be output based on the received sales information. The terminal output unit 26 outputs the sales information. The process returns to step S1001.

[0216] In the flowchart of FIG. 10, the process ends when the power is turned off or an interrupt occurs to end the process.

[0217] A specific example of the operation of the business support system A in this embodiment will be described below.

[0218] Assume now that a user has input a company identifier "Company C," a budget identifier "C1," two pieces of funnel information, five pieces of tier information, and two pieces of revenue information into a terminal device 2 that is outputting a screen for inputting business information. It is also assumed that this screen is a screen that enables the user to grasp the connection relationships between the funnel information, tier information, and revenue information. Here, the funnel information input by the user has a "funnel name" and a "quantity." The tier information input by the user has a tier name and a quantity. The revenue information input by the user has a revenue name, a quantity, and a unit price. It is assumed that the user inputs information so that the connection relationships between the funnel information, tier information, and revenue information can be grasped: the higher-level node information (funnel information, tier information, or revenue information), the lower-level node information connected to the higher-level node information, the probability of transition to the lower-level node information connected to the higher-level node information, and the lead time.

[0219] Next, the terminal device 2 accepts the business information. The terminal device 2 also accepts the business information associated with the company identifier “Company C” and the budget identifier “C1”, and transmits the business information associated with the company identifier “Company C” and the budget identifier “C1” to the business support device 1.

[0220] Next, the business information receiving unit 121 of the business support device 1 receives the business information associated with the company identifier "Company C" and the budget identifier "C1".

[0221] Next, the storage unit 131 associates the received business information with the company identifier "Company C" and the budget identifier "C1" and stores it in the business management unit 111. As a result, the business information in Figures 11 and 12 is stored in the business management unit 111.

[0222] Figure 11(a) is a funnel management table that manages funnel information. The funnel management table manages two or more records that have a "funnel identifier," "funnel name," and "funnel attribute value." The "funnel attribute value" has a "quantity."

[0223] Figure 11(b) is a tier management table that manages tier information. The tier management table manages two or more records that have a "tier identifier," "tier name," and "tier attribute value." The "tier attribute value" has a "quantity." Note that the record for tier identifier "T05" in Figure 11(b) may also exist in the funnel management table in Figure 11(a). In other words, "free membership registration" for T05 may also be a funnel.

[0224] Figure 11(c) is a revenue management table that manages revenue information. The revenue management table manages two or more records that have a "revenue identifier," "revenue name," and "revenue attribute value." The "revenue attribute value" has a "quantity," "unit price," and "amount."

[0225] FIG. 12 is an edge management table for managing edges. Here, the edges are, for example, edges connecting funnel information and tier information, edges connecting tier information and tier information, or edges connecting tier information and revenue information. The edge management table manages two or more records each having an "edge identifier" and an "edge attribute value." The "edge attribute value" includes a "first identifier," a "second identifier," a "probability (%)," and a "lead time." The "first identifier" is the node identifier of the higher-level node connected by the edge. The "second identifier" is the node identifier of the lower-level node connected by the edge. The node identifier is a funnel identifier, a tier identifier, or a revenue identifier. The "probability (%)" is the probability of transitioning from the first node identified by the first identifier to the second node identified by the second identifier. The "lead time" is the period (here, the number of months) required for transition from the first node identified by the first identifier to the second node identified by the second identifier.

[0226] The funnel attribute value "quantity" in Fig. 11(a) and the "probability (%)" in Fig. 12 may be input by a user, and the tier attribute value "quantity" in Fig. 11(b) may be automatically calculated and accumulated. Also, the funnel attribute value "quantity" in Fig. 11(a) and the tier attribute value "quantity" in Fig. 11(b) may be input by a user, and the "probability (%)" in Fig. 12 may be automatically calculated and accumulated.

[0227] Thereafter, it is assumed that the user inputs a graph output instruction “<company identifier>Company C <budget identifier>C1” to the terminal device 2. Next, the terminal device 2 accepts the graph output instruction and transmits it to the business support device 1.

[0228] Next, the reception unit 12 of the business support device 1 receives the graph output instruction "<company identifier> Company C <budget identifier> C1".

[0229] Next, the graph construction unit 132 acquires the business information paired with "<company identifier> Company C <budget identifier> C1" (FIGS. 11(a), (b), (c), and 12).

[0230] Next, the graph construction unit 132 constructs a graph, which is a graphical representation in which the funnel information, tier information, and revenue information are each treated as a node, by the process described using the flowchart of FIG. 5, and the nodes are connected according to the connection relationships indicated by the edge information of FIG. 12. At this time, the graph construction unit 132 constructs nodes having different outer shapes (here, background colors) depending on the node type so that the funnel information nodes, tier information nodes, and revenue information nodes can be visually easily distinguished from each other. Furthermore, the graph construction unit 132 arranges the funnel name and quantity in the funnel information node, the tier name and quantity in the tier information node, and the revenue name and quantity in the revenue information node. Note that the quantity is enclosed in parentheses. Furthermore, the graph construction unit 132 assigns a probability to each edge. Through the above process, the graph construction unit 132 constructs a graph showing the revenue structure of the business.

[0231] Next, the graph output unit 141 transmits the constructed graph to the terminal device 2.

[0232] Next, the terminal device 2 receives and outputs the graph. An example of such a graph output is shown in FIG. 13. In FIG. 13, nodes have different background colors depending on their type. Also, by having quantities in the nodes and probabilities in the edges, users can easily understand the revenue structure of the business, making it easier to take measures to improve revenue. Also, in FIG. 13, node 1301 is a tier, but as mentioned above, it can also be a funnel.

[0233] Next, it is assumed that the user inputs a sales information output instruction "<company identifier>Company C <budget identifier>C1" to the terminal device 2. Next, the terminal device 2 accepts the sales information output instruction and transmits it to the business support device 1.

[0234] Next, the reception unit 12 of the business support device 1 receives the sales information output instruction "<company identifier>Company C <budget identifier>C1".

[0235] Next, the sales information acquisition unit 133 acquires sales information using the business information (FIGS. 11 and 12) paired with "<company identifier> Company C <budget identifier> C1" through the sales information acquisition process described using the flowchart in Fig. 9. Here, the sales information acquisition unit 133 calculates the revenue for each month from April to September 2024 for the two revenues "Paid Membership Registration (Premium Plan)" and "Paid Membership Registration (Highest Plan)", as well as the "total" of the two revenues, and creates a sales information management table.

[0236] Next, the sales information output unit 142 transmits the sales information management table to the terminal device 2.

[0237] Next, the terminal device 2 receives and outputs the sales information management table. An output example of such a sales information management table is shown in Figure 14. In Figure 14, since the lead time of "1 month" in the edge information is taken into consideration, sales for "April 2024" are "0", and there is a one-month delay in generating profits.

[0238] This means that by April 2024, when revenue will be "0," it will be necessary to take measures such as borrowing from a bank.

[0239] As described above, according to this embodiment, the profit structure of a business can be visualized using a graph.

[0240] Furthermore, according to this embodiment, sales information that takes lead time into consideration can be acquired.

[0241] Furthermore, according to this embodiment, the promoter of the business can easily formulate a business strategy by being able to view the graph of the business's revenue structure as shown in Fig. 13 together with the sales information as shown in Fig. 14. Making it easier to formulate a business strategy means, for example, that it becomes easier to take measures to increase revenue.

[0242] In this embodiment, the accumulation unit 131 accumulates business information having the structure shown in, for example, Figs. 11 and 12. However, the accumulation unit 131 may accumulate business information having the JSON structure shown in, for example, Figs. 15 and 16. 1501 in Fig. 15 shows an example of a definition of a node that is a funnel, tier, or revenue. 1502 shows an example of a definition of an edge. Fig. 16 shows an example of a definition of an attribute value of each node.

[0243] Note that "funnel...", "tier...", "revenue...", and "connection..." in 1501 are all concepts of "models" and definitions of "parameter input boxes". "funnel...", "tier...", and "revenue..." correspond to the nodes in Figure 13. "connection..." corresponds to the edges in Figure 13.

[0244] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to the other embodiments in this specification. The software that realizes the business support device 1 in this embodiment is the following program. In other words, this program is business information related to a business corresponding to one budget, information related to a funnel indicating an entry action of a consumer for the business, one or more funnel information having a funnel name, information corresponding to each of the one or more funnel information, which is a consumer action at the end of the funnel and which identifies a tier indicating an action before sales, one or more tier information having a tier name, information corresponding to each of the one or more tier information, which is a consumer action at the end of the tier and which identifies revenue indicating an action that determines revenue, one or more revenue information having a revenue name, and, for the corresponding funnel information and tier information, first probability information related to the probability that the funnel specified by the funnel information will be performed and the tier specified by the tier information will be performed, and, for the corresponding tier information and revenue information, first probability information related to the probability that the tier specified by the tier information will be performed and the revenue will be determined The program causes a computer that can access a business management unit in which business information having second probability information regarding the probability that the revenue specified by the information will be made to function as a graph construction unit that constructs a graph in which each of the one or more funnel information, each of the one or more tier information, and each of the one or more revenue information are nodes, the correspondence between the funnel information and the tier information is an edge connecting the node of the funnel information and the node of the tier information, and the correspondence between the tier information and the revenue information is an edge connecting the node of the tier information and the node of the revenue information, and the nodes of the funnel information, the nodes of the tier information, and the nodes of the revenue information are respectively associated with funnel names, tier names, and revenue names, and the edges are associated with first probability information or second probability information, and a graph output unit that outputs the graph constructed by the graph construction unit.

[0245] FIG. 17 is a block diagram of a computer system 300 that executes the programs described in this specification to realize the business support device 1 and the like according to the various embodiments described above.

[0246] 17, computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304. In addition to a CD-ROM drive 3012, computer 301 also includes an MPU 3013, a bus 3014 connected to CD-ROM drive 3012 and the like, a ROM 3015 for storing programs such as a boot-up program, a RAM 3016 connected to MPU 3013 for temporarily storing instructions for application programs and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0247] A program that causes the computer system 300 to execute the functions of the business support device 1 of the above-described embodiment, etc., may be stored on a CD-ROM 3101, inserted into the CD-ROM drive 3012, and then transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored on the hard disk 3017. The program is loaded into the RAM 3016 when executed. The program may also be loaded directly from the CD-ROM 3101 or the network.

[0248] The program does not necessarily include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the business support device 1 of the above-described embodiment. The program only needs to include instructions that call appropriate functions (modules) in a controlled manner to achieve the desired results. How the computer system 300 operates is well known, and a detailed description thereof will be omitted.

[0249] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

[0250] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or distributed processing.

[0251] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0252] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0253] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0254] As described above, the business support device 1 according to the present invention has the effect of being able to visualize the profit structure of a business, and is useful as a server or the like that supports a business. [Explanation of symbols]

[0255] A Business Support System 1 Business support equipment 2. Terminal Device 11 Storage area 12 Reception 13 Processing section 14 Output section 21 Terminal storage section 22 Terminal Reception 23 Terminal processing section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Unit 111 Business Management Department 112 Sales Information Management Department 121 Business Information Reception Department 122 Editing Instructions Reception Department 131 Storage Unit 132 Graph Construction Section 133 Graph Change Section 133 Sales Information Acquisition Department 134 Business Information Change Department 141 Graph output section 142 Sales information output section

Claims

1. a business management unit in which business information is stored, the business information being business information related to a business corresponding to one budget, the business information being information related to a funnel which is a starting stage among one or more stages related to the business, the business information being one or more funnel information having a funnel name, information corresponding to each of the one or more funnel information and identifying a tier which is a stage at the end of the funnel and a stage prior to sales, the business information being one or more tier information having a tier name, and information corresponding to each of the one or more tier information and identifying revenue which is a product or product category at the end of the tier, the business information having one or more revenue information having a revenue name, the business information having first probability information regarding the probability that the funnel specified by the funnel information and the tier specified by the tier information will be performed, with respect to the corresponding funnel information and tier information, and second probability information regarding the probability that the tier specified by the tier information will be performed, with respect to the corresponding tier information and revenue information, a graph configuration unit that configures a graph in which each of the one or more funnel information, each of the one or more tier information, and each of the one or more revenue information is a node, a correspondence between the funnel information and the tier information is an edge connecting the node of the funnel information and the node of the tier information, and a correspondence between the tier information and the revenue information is an edge connecting the node of the tier information and the node of the revenue information, wherein a funnel name, a tier name, and a revenue name correspond to the node of the funnel information, the node of the tier information, and the node of the revenue information, respectively, and first probability information or second probability information corresponds to the edge; a graph output unit that outputs the graph constructed by the graph construction unit.

2. The funnel information also includes a quantity of an action corresponding to the funnel information to be performed; The tier information also includes a quantity of an action corresponding to the tier information to be performed; The revenue information also includes a quantity for which an action corresponding to the revenue information is to be performed; The graph construction unit The business support device according to claim 1 , wherein the graph is configured such that the nodes of the funnel information, the nodes of the tier information, and the nodes of the revenue information each correspond to a funnel name and a quantity, a tier name and a quantity, and a revenue name and a quantity.

3. 3. The business support device according to claim 2, wherein a lead time is associated with each of the one or more edges.

4. a sales information acquisition unit that acquires sales information for two or more months using the quantity corresponding to each of one or two or more revenues and the lead time; 4. The business support device according to claim 3, further comprising a sales information output unit that outputs the sales information for each month acquired by the sales information acquisition unit.

5. The graph construction unit 5. The business support device according to claim 1, wherein a graph is formed in which the contours of nodes of any one of funnel information, tier information, and revenue information have different contours depending on the type of node.

6. one or more of the revenue information items include a unit price; The graph construction unit 3. The business support device according to claim 2, wherein the graph is constructed by associating sales, calculated by multiplying the unit price and the quantity, with the one or more nodes of the revenue information.

7. an edit instruction receiving unit that receives an edit instruction for the graph output by the graph output unit; a graph modification unit that modifies the graph output by the graph output unit in response to the editing instruction; 2. The business support device according to claim 1, further comprising a business information change unit that changes the business information of the business management unit in response to the change made by the graph change unit.

8. a graph construction unit and a graph output unit, the graph construction unit comprising: a business management unit storing business information, the business information being business information related to a business corresponding to one budget, the business information being information related to a funnel which is a starting stage among one or more stages related to the business, the one or more funnel information having funnel names, information corresponding to each of the one or more funnel information and identifying a tier which is a stage at the end of the funnel and a stage before sales, the one or more tier information having tier names, and information corresponding to each of the one or more tier information and identifying revenue which is a product or product category at the end of the tier, the one or more revenue information having revenue names, the business information having, for the corresponding funnel information and tier information, first probability information relating to the probability that the funnel specified by the funnel information will be performed and the tier specified by the tier information will be performed, and second probability information relating to the corresponding tier information and revenue information, a graph construction step in which the graph construction unit constructs a graph in which each of the one or more funnel information, each of the one or more tier information, and each of the one or more revenue information is a node, a correspondence between the funnel information and the tier information is an edge connecting the node of the funnel information and the node of the tier information, and a correspondence between the tier information and the revenue information is an edge connecting the node of the tier information and the node of the revenue information, and a funnel name, a tier name, and a revenue name correspond to the node of the funnel information, the node of the tier information, and the node of the revenue information, respectively, and first probability information or second probability information corresponds to the edge; a graph output step in which the graph output unit outputs the graph constructed by the graph construction unit.

9. a computer accessible to a business management unit in which business information is stored, the business information being business information related to a business corresponding to one budget, the business information being information related to a funnel which is a starting stage among one or more stages related to the business, the one or more funnel information having funnel names, information corresponding to each of the one or more funnel information and identifying a tier which is a stage at the end of the funnel and a stage before sales, the one or more tier information having tier names, and information corresponding to each of the one or more tier information and identifying revenue which is a product or product category at the end of the tier, the computer having access to a business management unit in which business information is stored, the computer having first probability information regarding the probability that the funnel specified by the funnel information and the tier specified by the tier information will be performed, and second probability information regarding the probability that the tier specified by the tier information will be performed, and the revenue specified by the revenue information will be performed, a graph configuration unit that configures a graph in which each of the one or more funnel information, each of the one or more tier information, and each of the one or more revenue information is a node, a correspondence between the funnel information and the tier information is an edge connecting the node of the funnel information and the node of the tier information, and a correspondence between the tier information and the revenue information is an edge connecting the node of the tier information and the node of the revenue information, wherein a funnel name, a tier name, and a revenue name correspond to the node of the funnel information, the node of the tier information, and the node of the revenue information, respectively, and first probability information or second probability information corresponds to the edge; A program for causing the graph construction unit to function as a graph output unit that outputs the graph constructed by the graph construction unit.

Images