M&A support system and M&A support method utilizing partners

Abstract

For example, in M&A transactions involving small businesses and sole proprietors with annual sales of less than 300 million yen, we provide a partner-based M&A support system and method that enables efficient and low-cost M&A support by utilizing partners such as sellers, buyers, M&A support firms, and experts in M&A operations. [Solution] An M&A support system 10 that utilizes expert partners, comprising: a partner selection unit 10A1 that selects an appropriate partner based on seller information about the seller and partner information about the partner; and a case information generation unit 10A2 that creates a case summary and a non-name sheet reflecting the contents of the case summary based on the transfer target business information of the seller registered by the selected partner.

Description

Technical Field

[0004] , , , ,

[0006] , , , , , , , ,

[0005] , , , , , , ,

[0001] The present invention relates to an M&A support system and an M&A support method that utilize partners (also referred to as advisors), such as experts.

Background Art

[0002] In the conventional M&A support industry, due to the need for special and advanced expertise and specialized skills related to M&A operations, the support of experts (partners), such as certified public accountants, has been required.

[0003] In practice, in large-scale M&A operations dealing with large enterprises or mid-sized enterprises, experts were involved.​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​[Problems that the invention aims to solve]

[0007] Therefore, in order to fundamentally solve the above-mentioned conventional structural problems, the present invention aims to provide a partner-based M&A support system and M&A support method that enables efficient and low-cost M&A support utilizing partners such as M&A experts in small-scale M&A transactions involving small businesses and sole proprietors with annual sales of less than 300 million yen. [Means for solving the problem]

[0008] The first invention is an M&A support system that utilizes expert partners, A partner selection unit that selects an appropriate partner based on seller information regarding the seller and partner information regarding the partner, A project information generation unit creates a project summary and a non-name sheet that reflects the contents of the project summary, based on the project information of the seller to be transferred, which is registered by the selected partner. This is an M&A support system that utilizes partners and possesses [certain capabilities].

[0009] The second invention is an M&A support method that utilizes expert partners, A partner selection step in which an appropriate partner is selected based on seller information regarding the seller and partner information regarding the partner, Based on the business information for the business to be transferred of the seller registered by the selected partner, a project information registration step is performed in which a project summary and a non-name sheet reflecting the contents of the project summary are created, This is an M&A support method that utilizes partners who possess the necessary skills and resources.

[0010] Furthermore, the aforementioned project summary document and the aforementioned non-name sheet may be generated and registered as project information format data by the project information generation unit. [Effects of the Invention]

[0011] According to the present invention, in small-scale M&A operations involving small enterprises with an annual turnover of less than 300 million yen and individual business owners, for example, it is possible to efficiently and cost-effectively realize M&A operations that actively utilize partners such as experts in M&A operations.

Brief Description of the Drawings

[0012] [Figure 1] It is a conceptual diagram showing the communication construction between the M&A support system of the first embodiment and each terminal. [Figure 2] It is a block diagram of the M&A support system of the first embodiment. [Figure 3] It is a block diagram of the control unit of the M&A support system of the first embodiment. [Figure 4] It is a block diagram of the storage unit of the M&A support system of the first embodiment. [Figure 5] It is a block diagram of the input unit of the M&A support system of the first embodiment. [Figure 6] It is a block diagram of the output unit of the M&A support system of the first embodiment. [Figure 7] [[ID=二十九]]It is the M&A support flow in the business phase of the first embodiment. [[ID=三十]] [[ID=三十一]] [Figure 8] [[ID=三十二]]It is the M&A support flow in the project formulation phase of the first embodiment. [[ID=三十三]] [[ID=三十四]] [Figure 9] [[ID=三十五]]It is the M&A support flow in the matching phase of the first embodiment. [[ID=三十六]] [[ID=三十七]] [Figure 10] [[ID=三十八]]It is the M&A support flow in the negotiation phase of the first embodiment. [[ID=三十九]] [[ID=四十]] [Figure 11] [[ID=四十一]]It is an explanatory diagram showing Application Example 1 of the M&A support system. [[ID=四十二]] [[ID=四十三]] [Figure 12] [[ID=四十四]]It is an explanatory diagram showing Application Example 2 of the M&A support system. [[ID=四十五]] [[ID=四十六]] [Figure 13] [[ID=四十七]]It is an explanatory diagram showing Application Example 3 of the M&A support system. [[ID=四十八]] [[ID=四十九]] [Figure 14] [[ID=五十]]It is an explanatory diagram showing Application Example 4 of the M&A support system. [[ID=五十一]] [[ID=五十二]] [Figure 15]This is the M&A support flow in the matching phase of the second embodiment.

Mode for Carrying Out the Invention

[0013] [First Embodiment] An M&A support system and an M&A support method using partners according to the first embodiment of the present invention will be described with reference to the drawings. The M&A support system and the M&A support method can also be referred to as an M&A intermediation system and an M&A intermediation method.

[0014] As shown in FIG. 1, the M&A support system 10 is configured to be accessible, for example, by a communication connection using a network such as the Internet among the M&A navigator, the seller, the buyer, and the partners. Specifically, the M&A support system 10 is configured to be communicably connected to the terminal 12 of the M&A navigator, the terminal 14 of the seller, the terminal 16 of the buyer, and the terminal 18 of the partner. Note that the persons involved are not limited to the above four (M&A navigator, seller, buyer, partner), and may include other related persons.

[0015] The M&A support system 10 and the terminal 12 of the M&A navigator may be configured to share the same computer device or the like, but in this embodiment, for convenience of explanation, they are exemplified separately in terms of both concepts. [[ID=2\0]]

[0016] The "M&A navigator" refers to an operator or the like who manages the M&A support system 10. It may be an individual or a corporation.

[0017] The "seller" refers to a person who transfers a company. It may be an individual or a corporation.

[0018] The "buyer" refers to a person who acquires a company. It may be an individual or a corporation.

[0019] A "partner" refers to M&A specialists (practitioners) such as certified public accountants, tax accountants, and small and medium-sized enterprise consultants. This includes individuals or corporations. Examples include those with national qualifications such as lawyers and accountants, private qualifications such as management consultants, certified business innovation support organizations, and individual or corporate consulting firms.

[0020] Communication connections using networks such as the Internet are not limited to, for example, wired or wireless connections, but may also be configured to allow connections using the Internet Cloud.

[0021] The M&A support system 10 is used, for example, as SaaS (Software as a Service). Specifically, the M&A support system 10 is a service that allows users (for example, M&A Navi, sellers, buyers, and partners, all or some of them) to use an application or software running on the service provider's (server) side via a network such as the internet.

[0022] To use the M&A support system 10, an application or software (program) provided for each user's account is downloaded and installed on each user's terminal. The communication method over the internet is not particularly limited.

[0023] As shown in Figure 2, the M&A support system 10 includes, for example, a control unit 10A that controls the entire system, an arithmetic unit 10B that performs calculation processing based on instructions such as programs, a storage unit 10C that stores data or instructions, an input unit 10D that inputs data or instructions, and an output unit 10E that outputs data such as the results of calculation processing.

[0024] The control unit 10A and the arithmetic unit 10B may be configured as a central processing unit such as a CPU, or they may be configured as artificial intelligence (AI). It is preferable to use artificial intelligence (AI) for the control unit 10A and / or the arithmetic unit 10B, as this enables additional learning (machine learning), and thus improves work efficiency and accuracy.

[0025] The control unit 10A has common functions such as a program counter, instruction register, index register, base address register, and decoder. Specifically, the program counter, also called a sequential control counter, has the function of storing the address of the next instruction to be executed after one instruction has been executed. The instruction register receives instructions retrieved from the storage unit 10C and temporarily stores them for execution. The index register, also called an index register, has a value that is the sum of the contents of this register and the address of the instruction word's address portion, which becomes the address to be processed. The base address register is a register that holds the base address. The decoder, also called a decoder, decodes the instruction retrieved in the instruction register and outputs the corresponding control signal.

[0026] The arithmetic unit 10B has general functions such as an arithmetic logic unit, various registers, and an accumulator. Specifically, the arithmetic logic unit performs arithmetic operations and logical operations using adders and complements. The various registers have the function of temporarily storing data necessary for calculations and enabling high-speed access. An accumulator, also called a cumulative unit, is a type of register for holding calculation results.

[0027] Here, since the control unit 10A and the arithmetic unit 10B are integrally configured as a central processing unit such as a CPU or AI, the following components will be described as being included in the control unit 10A. However, this is not the only configuration; configurations included in the arithmetic unit 10B or other parts are also acceptable.

[0028] As shown in Figure 3, the control unit 10A includes, for example, a partner selection unit 10A1, a case information generation unit 10A2, a case information modification unit 10A3, a long list generation unit 10A4, a no-name sheet display unit 10A5, and an interest confirmation determination unit 10A6.

[0029] The partner selection unit 10A1 selects an appropriate or optimal partner based on seller information and partner information. Seller information and partner information are stored in the storage unit 10C. Matching of seller information and partner information is performed, for example, by considering how well the partner's pre-registered expertise (desired field) matches the seller information. It is also possible to nominate not just one person (or company) but multiple individuals (or companies) as potential partners.

[0030] The case information generation unit 10A2 creates a case summary and a non-name sheet reflecting the contents of the case summary, based on the transferable business information of the seller's business registered by the partner selected by the partner selection unit 10A1, and registers them in the data information registration unit 10C4 of the storage unit 10C. Alternatively, the case information generation unit 10A2 may generate the case summary and the non-name sheet as case information format data and register them in the data information registration unit 10C4 of the storage unit 10C.

[0031] A project summary is also simply called a summary or company profile. A project summary includes information about the business being transferred by the seller. Specifically, the project summary includes seller information such as company profile (executive summary), business content, organization, financial status, reasons for transfer, licenses and regulations, asset and equipment status, and business plan.

[0032] A company profile is used to highlight the attractiveness of the company being sold, and includes basic information such as the company name, location, capital, and shareholder structure, as well as business processes, the surrounding industry environment, and desired conditions for the M&A.

[0033] Business details include industry information, the business model of the company being acquired, major customers, suppliers, and other relevant information. For example, this could include a flowchart illustrating transactions, or a description of the company's products and services with accompanying photographs. It could also include information such as market share and competitive advantages.

[0034] Organizational information includes the representative's profile, a list of shareholders and officers, an organizational chart, and employee profiles. For example, it includes information that conveys to the buyer not only quantitative figures but also the founding vision and sales capabilities. Depending on the industry, it may also include information on qualified personnel and licenses obtained. Employee information may include details such as average salary and average age.

[0035] Financial status refers to financial information consisting of the company's financial performance over time, balance sheets for at least three periods, and income statements. In the case of manufacturing companies in particular, it also includes information such as cost of goods manufactured reports. Furthermore, it includes information on the reasons for any sudden changes in assets, liabilities, or revenue. Information on borrowings and corporate bonds is also included.

[0036] The reason for the transfer is the information that acquiring companies are most interested in, such as "why the transfer is being considered at this particular time" and "what vision the company has for the post-transfer period." This includes detailed information that helps acquiring companies make decisions and consider schemes for proceeding with an M&A based on the reason for the transfer.

[0037] Licenses, permits, and legal regulations refer to detailed information about any special licenses, permits, or legal regulations that may apply to the business in question, such as the construction industry.

[0038] The asset and equipment status includes information such as location, area, and ownership type (owner-owned or leased) for the head office. For manufacturing facilities such as factories, it also includes internal layout diagrams. If there are fixed assets such as land or factories, or equipment such as machinery, it also includes detailed information such as location, area, and acquisition cost. In addition, if there are vehicles, leased assets, or non-business assets, information on those is also included.

[0039] A business plan refers to information about future business plans and plans currently being implemented. In particular, if there are currently implemented plans, the acquiring company may take over them, so the plan should include the progress rate towards achieving the plan, its feasibility, and the information that will be gained if the plan is achieved.

[0040] A Non-Name Sheet (NNO) is a document that provides a company overview while protecting the anonymity of the selling company. It is issued before a confidentiality agreement is signed or detailed information is provided to potential acquiring companies, and does not contain any specific information that could identify the selling company. The information contained in this document is generated as data related to the NNO. When printed out, NNOs typically contain only the minimum necessary information on a single A4 page.

[0041] The relationship between the Non-Disclosure Sheet and the Project Summary is that the Non-Disclosure Sheet has a more limited scope of information or a lower level of detail compared to the Project Summary. For example, the Non-Disclosure Sheet does not include information on liabilities, but it is possible to express financial information such as sales as a rank (rating) or range. For example, the Non-Disclosure Sheet may include items such as industry, region, number of employees, sales, operating profit, reason for transfer, transfer scheme (stock transfer, business transfer, etc.), and desired transfer period, but it is not limited to these items.

[0042] A non-name sheet is a summary document about the selling company (seller) used by acquiring companies (buyers) when selecting potential candidates. Therefore, from a confidentiality standpoint, the document contains company information in an anonymous manner so that the selling company (seller) cannot be identified. If an acquiring company (buyer) becomes interested in a selling company (seller) based on the contents of the non-name sheet, they can, for example, enter into a confidentiality agreement with an M&A brokerage firm such as M&A Navi and then view more detailed information in a company profile document, etc. In this way, non-name sheets are used in the initial stages of consideration by acquiring companies (buyers).

[0043] The project information format data includes, for example, (1) company / business information, (2) seller's desired transfer conditions, and (3) valuation information. The project summary and non-name sheet are formats that optimize these (1) to (3) project information according to their purpose. The project information format data reflects the contents of the project summary and non-name sheet.

[0044] Information regarding the business to be transferred by the seller is stored, for example, as data from the partner's terminal 18 that recorded the interview, etc., in the data information registration unit 10C of the storage unit 10C. The case summary document created by the case information generation unit 10A2 and the non-name sheet reflecting the contents of the case summary document are generated by the case information generation unit 10A2 as case information format data and stored in the data information registration unit 10C of the storage unit 10C.

[0045] The case information modification unit 10A3 appropriately modifies at least one of the case summary, non-name sheet, and case information format data based on input from, for example, the M&A Navi and partner terminals 12 and 18. Alternatively, the case information modification unit 10A3 may be configured to appropriately modify at least one of the case summary, non-name sheet, and case information format data based on input from, for example, the seller and buyer terminals 14 and 16.

[0046] The long list generation unit 10A4 creates a list of buyers based on buyer information and generates it as a long list. A long list is a list of potential buyers (or potential acquisition targets) of a target company that is considering an M&A. For example, it would be a list of companies from which significant synergies are expected through an M&A.

[0047] The No-Name Sheet display unit 10A5 is a display control unit that displays the No-Name Sheet or the contents of the No-Name Sheet in a display area that can be displayed on the website of each terminal. In this embodiment, the website refers to a homepage, blog, etc.

[0048] The interest confirmation determination unit 10A6 determines whether the buyer is interested in the contents of the non-name sheet. "Interest" means, for example, "concern." Specifically, the interest confirmation input unit 10D1 of the input unit 10D, which identifies whether the buyer is interested, is displayed on the website of each terminal simultaneously with the contents of the non-name sheet, and the interest confirmation determination unit 10A6 determines whether the buyer is interested based on the input content to the interest confirmation input unit 10D1 of the input unit 10D.

[0049] The storage unit 10C stores the contents of data or instructions. Specifically, as shown in Figure 4, the storage unit 10C includes a seller information registration unit 10C1 for registering seller information about the seller, a buyer information registration unit 10C2 for registering buyer information about the buyer, a partner information registration unit 10C3 for registering partner information about the partner, and a data information registration unit 10C4 for registering all data and information related to M&A, such as data or information generated and calculated by the control unit 10A and the calculation unit 10B.

[0050] The seller information registration section 10C1 stores, for example, information about the business being transferred by the seller.

[0051] The buyer information registration unit 10C2 stores, for example, information about the buyer list based on buyer information concerning the buyer. The buyer list forms the basis for generating the long list.

[0052] The Partner Information Registration Section 10C3 stores information on M&A professionals such as certified public accountants, tax accountants, and small and medium-sized enterprise consultants. For example, it includes detailed information such as the partner's educational background, work history, achievements, strengths, and preferences. This partner information is considered when selecting a suitable partner.

[0053] The data information registration unit 10C4 stores the information generated by the control unit 10A and the calculation unit 10B, such as the contents of the case summary, non-name sheet, and case information format data. It also includes information entered by the buyer (such as the buyer's personal information), the contents of the confidentiality agreement, and the contents of the long list related to the buyer. The data information registration unit 10C4 is also called the case information registration unit.

[0054] As shown in Figure 5, the input unit 10D receives input signals or input information from each communicable terminal. The input unit 10D includes, for example, an interest confirmation input unit 10D1, a personal information input unit 10D2, a consent confirmation input unit 10D3, and a case information input unit 10D4.

[0055] The interest confirmation input unit 10D1 is an input unit for inputting whether or not the buyer is interested in the contents of the non-name sheet. Specifically, it consists of an input display unit (e.g., an input button) that allows the buyer to select "Interested" or "Not Interested," and an input detection unit that detects the input from the input display unit, but is not limited to this configuration. The interest confirmation input unit 10D1 can also be displayed on each terminal as an input unit.

[0056] The personal information input unit 10D2 is displayed when the interest confirmation determination unit 10A6 of the control unit 10A determines that the buyer is interested, and is an input unit for entering the buyer's personal information. Specifically, the buyer's personal information includes at least part of their name, job title, address or residence, telephone number, and email address. When the buyer's personal information is entered into the personal information input unit 10D2, the buyer's personal information is inserted into the party section of the confidentiality agreement, completing the contents of the confidentiality agreement. In other words, a confidentiality agreement is concluded between the buyer and M&A Navi. The contents of the confidentiality agreement are stored as data in the data information registration unit 10C4 of the storage unit 10C. The personal information input unit 10D2 can also be displayed on each terminal as an input unit.

[0057] The consent confirmation input section 10D3 inputs the buyer's expression of consent to the contents of the confidentiality agreement, which has been completed with the buyer's personal information inserted. The consent confirmation input section 10D3 is, for example, an input button. Once the consent confirmation input section 10D3 is filled in, the contents of the case summary document, which contains the seller's information, become available for display. The consent confirmation input section 10D3 can also be displayed on each terminal as an input section.

[0058] The case information input unit 10D4 receives input information from, for example, M&A Navi and partner terminals 12 and 18. This registers M&A-related data and information. Based on the input information entered into the case information input unit 10D4, it is also possible to modify, add, or delete already registered data and information. The case information input unit 10D4 may also receive input information from, for example, the seller's and buyer's terminals 14 and 16. The case information input unit 10D4 can also be displayed on each terminal as an input unit.

[0059] As shown in Figure 6, the output unit 10E outputs an output signal or output information to each communicationable terminal. The output unit 10E includes, for example, a case information transmission unit 10E1 and a case information output unit 10E2.

[0060] The case information transmission unit 10E1 sends an email to the terminal 16 of a buyer registered on the long list, for example, containing identification information (e.g., a link such as a website URL) to identify the display area related to the non-name sheet. In other words, it sends an email to the terminal 16 of a buyer registered on the long list, with identification information (e.g., a link such as a website URL) included in the body of the email to identify the display area related to the non-name sheet. When the buyer clicks the link of the identification information on their terminal 16, the contents of the non-name sheet containing the seller information become available to be displayed on the buyer's terminal 16.

[0061] The case information output unit 10E2 outputs M&A-related case information to the M&A Navi and Partner terminals 12 and 18, respectively, based on requests from the M&A Navi and Partner terminals 12 and 18. The case information output unit 10E2 can also output M&A-related case information to the M&A Navi or Partner terminals 12 and 18, respectively, based on commands from the control unit 10A. The case information output unit 10E2 may also output M&A-related case information to the Seller and Buyer terminals 14 and 16, respectively, based on requests from the Seller and Buyer terminals 14 and 16, respectively.

[0062] Next, we will explain the M&A support flow of the M&A support system and M&A support methods that utilize partners, based on a time chart.

[0063] [overview] The M&A support system and method utilizing partners involves four key players: the seller, the buyer, M&A Navi, and the partner. The M&A support flow consists of four phases: the sales phase, the deal development phase, the matching phase, and the negotiation phase.

[0064] [M&A Support Flow] Next, we will explain the M&A support flow, which consists of four phases. Note that the M&A support system 10 and the M&A Navi terminal 12 may share the same computer device (terminal), but for the sake of explanation in this embodiment, they will be described as independent concepts.

[0065] <Sales Phase> The M&A support flow during the sales phase is as follows. The M&A support flow during the sales phase is shown in Figure 7.

[0066] As shown in Figure 7, seller information is entered from the M&A Navi terminal 12 to the M&A support system 10. As shown in Figure 4, the seller information is registered in the seller information registration unit 10C1 of the storage unit 10C (seller information registration step).

[0067] As shown in Figure 7, the M&A support system 10 outputs information on appropriate partners to the M&A Navi terminal 12. The partner selection unit 10A1 of the M&A support system 10, shown in Figure 3, selects an appropriate partner based on the seller information registered in the seller information registration unit 10C1 shown in Figure 4 and the partner information registered in the partner information registration unit 10C3 (partner selection step). The selected partner information is output from the case information output unit 10E2 shown in Figure 6 to the M&A Navi terminal 12 (selected partner output step).

[0068] Based on the partner information output from the M&A support system 10 to the M&A Navi terminal 12, the M&A Navi terminal 12 outputs the assignment information of the selected partner to the seller's terminal 14 (partner assignment step). Alternatively, the output of the assignment information of the selected partner may be output from the M&A Navi terminal 12 to the seller's terminal 14 via the M&A support system 10.

[0069] The partner accesses the M&A support system 10 from their terminal 18, allowing them to view and confirm seller information regarding the assigned seller on their terminal 18 (partner's seller information confirmation step).

[0070] The partner accesses the seller's terminal 14 from their terminal 18 to schedule a meeting between the partner and the seller (seller meeting scheduling step). Then, the partner accesses the M&A support system 10 from their terminal 18 and registers information regarding the scheduling results in the data information registration unit 10C4 of the storage unit 10C shown in Figure 4 (partner / seller schedule registration step). Alternatively, the partner may access the seller's terminal 14 from their terminal 18 via the M&A support system 10.

[0071] When the meeting date arrives, the partner meets with the seller and accesses the M&A support system 10 from the partner's terminal 18 to register the contents of the meeting record with the seller in the data information registration unit 10C4 of the storage unit 10C shown in Figure 4 (seller meeting record registration step).

[0072] <Project Development Phase> The M&A support flow during the deal development phase is as follows. The M&A support flow during the deal development phase is shown in Figure 8.

[0073] As shown in Figure 8, after meeting with the seller, the partner collects documents related to the business to be transferred from the seller. Then, the partner accesses the M&A support system 10 from the partner's terminal 18 and registers information (files) related to the seller's business to be transferred in the data information registration unit 10C4 of the storage unit 10C shown in Figure 4 (business information registration step).

[0074] The M&A support system 10 shown in Figure 3, specifically the case information generation unit 10A2, creates a draft of a case summary and a non-name sheet reflecting the contents of the case summary based on the uploaded information (file) regarding the seller's business to be transferred, and generates the case summary and non-name sheet as case information format data (case information generation step). The contents of the case summary, non-name sheet, and case information format data are registered in the data information registration unit 10C4 of the storage unit 10C (case information registration step).

[0075] Here, the project summary, non-name sheet, and project information form data include at least one piece of information: information about the company and business that the seller has in possession of the aforementioned business to be transferred, information about the seller's desired transfer conditions for the business to be transferred, or information about the valuation of the business to be transferred by the seller.

[0076] M&A Navi accesses the M&A support system 10 from its terminal 12 to check the draft of the deal summary and non-name sheet (and the contents of the deal information format data) (deal information confirmation step). If the draft of the deal summary and non-name sheet (and the contents of the deal information format data) needs to be corrected, M&A Navi inputs the corrections to the deal information into the M&A support system 10 from its terminal 12 and corrects the draft of the deal summary and non-name sheet (and the contents of the deal information format data) (deal information correction step).

[0077] In the project information modification step, it is possible to modify at least part of the content of the draft project summary and non-name sheet, or the project information format data. Furthermore, it may be configured so that if the content of the draft project summary and non-name sheet is modified, the content of the project information format data is automatically modified.

[0078] After at least a portion of the contents of the project summary, non-name sheet draft, or project information format data has been revised, the M&A support system 10 outputs information indicating the completion of the project information revision to the partner's terminal 18, notifying the partner that the project information revision has been completed (project information revision completion step).

[0079] The partner accesses the M&A support system 10 from their terminal 18 and downloads the revised deal summary and non-name sheet. The contents of the revised deal summary and non-name sheet are registered in the data information registration unit 10C4 of the storage unit 10C shown in Figure 4. Subsequently, the partner meets with the seller.

[0080] The partner accesses the M&A support system 10 from their terminal 18 and registers the contents of the meeting record with the seller in the data information registration unit 10C4 of the storage unit 10C shown in Figure 4 (seller meeting record registration step).

[0081] The deal information modification unit 10A3 of the M&A support system 10 shown in Figure 3 modifies at least part of the contents of the deal summary, non-name sheet, or deal information format data based on the contents of the meeting record between the partner and the seller (deal information modification step).

[0082] After completing the revisions to the project summary, non-name sheet, or project information format data, the process will proceed to the matching phase.

[0083] <Matching Phase> The M&A support flow in the matching phase is as follows. The M&A support flow in the matching phase is shown in Figure 9.

[0084] As shown in Figures 3, 4, and 9, the long list generation unit 10A4 of the M&A support system 10 creates a list of buyers based on the buyer information stored in the buyer information registration unit 10C2, and registers it as a long list (AI long list) in the data information registration unit 10C4 of the storage unit 10C (buyer long list registration step).

[0085] As shown in Figure 6, the deal information transmission unit 10E1 of the M&A support system 10 sends an email containing identification information (e.g., a link such as a website URL) in the body of the email to the buyer's terminal 16 registered on the long list (deal information transmission step).

[0086] The buyer clicks on the identification information displayed in the body of the email received on the buyer's terminal 16 from the M&A support system 10. This allows the website linked to the URL controlled by the non-name sheet display unit 10A5 to be displayed on the buyer's terminal 16, and the buyer can confirm the details of the seller's business being transferred regarding the non-name sheet (buyer's non-name sheet display step).

[0087] As shown in Figures 3 and 5, the buyer inputs whether or not they are interested in the contents of the non-name sheet to the interest confirmation input unit 10D1 (interest confirmation input step). Based on the input results entered in the interest confirmation input step, the interest confirmation determination unit 10A6 determines whether or not the buyer is interested (interest confirmation determination step).

[0088] When the interest confirmation unit 10A6 determines that the buyer is interested, a personal information input field is displayed for the buyer to enter their personal information (e.g., real name, job title, email address, etc.) to be inserted into the contracting parties section of the confidentiality agreement (personal information input display step). The buyer can then input their personal information into the personal information input field and enter it into the personal information input unit 10D2 (personal information input step). A buyer who has entered their personal information can be said to be, for example, a buyer who wishes to disclose their real name.

[0089] When the buyer's personal information (e.g., real name, job title, email address, etc.) is entered into the personal information input section 10D2, the buyer's personal information is automatically inserted into the contracting parties section of the confidentiality agreement (confidentiality agreement completion step). In other words, if the buyer wishes to disclose the real name of the transaction, the control unit 10A of the M&A support system 10 shown in Figure 2 automatically inserts the buyer's personal information into the contracting parties section of the confidentiality agreement, and the contents of the confidentiality agreement are completed. At this point, it may be considered that a confidentiality agreement has been concluded between the buyer and M&A Navi.

[0090] Furthermore, if the buyer is determined to be uninterested during the interest confirmation step, the buyer's personal information (e.g., real name, job title, email address, etc.) for insertion into the contracting parties section of the confidentiality agreement will not be entered into the personal information input section 10D2.

[0091] As shown in Figure 4, information regarding the buyer's interest and the buyer's personal information are registered, for example, in the data information registration unit 10C4 of the storage unit 10C.

[0092] Next, as shown in Figure 5, a consent confirmation input section 10D3 is displayed for the buyer to input their consent to the contents of the confidentiality agreement. The buyer inputs their consent to the consent confirmation into the consent confirmation input section 10D3 (consent confirmation input step). Once the buyer has entered their consent to the consent confirmation, input fields for the buyer's acquisition needs are displayed (acquisition needs input step). The acquisition needs input fields include items such as M&A willingness / experience, industry, area, sales scale, and acquisition background.

[0093] As shown in Figure 6, the deal information transmission unit 10E1 of the M&A support system 10 transmits information regarding scheduling a meeting with a partner to the terminal 16 of a buyer who has entered personal information (referring to a buyer who wishes to disclose their real name) (meeting date scheduling step). The buyer enters their preferred date and time for the meeting. Here, if the transmission means is, for example, email, the buyer sends a reply email to the received email. Alternatively, if the transmission means is a website URL indicated in the body of the email, the buyer may access the website and enter the date and time of the meeting.

[0094] When the meeting date arrives, the partner meets with the buyer. After the meeting, the partner accesses the M&A support system 10 from their terminal 18 and registers the details of the meeting record (buyer meeting record registration step). The information regarding the meeting record is stored in the data information registration unit 10C4 of the storage unit 10C.

[0095] If, as a result of the meeting between the partner and the buyer, the buyer wishes to meet with the seller, the partner, buyer, and seller will coordinate a three-way meeting. Specifically, the three-way meeting is confirmed when the partner registers with the M&A support system 10 from their terminal 18 that the buyer wishes to meet with the seller. Subsequently, the M&A support system 10 sends a message regarding scheduling the three-way meeting to the seller's terminal 14, the buyer's terminal 16, and the partner's terminal 18 (three-way meeting scheduling step). After the date and time of the three-way meeting are decided, the meeting takes place on the scheduled date.

[0096] After the three-party meeting, the partner accesses the M&A support system 10 from their terminal 18 to register the contents of the three-party meeting record (three-party meeting record registration step). The information regarding the three-party meeting record is stored in the data information registration unit 10C4 of the storage unit 10C.

[0097] If the three-way meeting leads to a decision to consider the acquisition, the negotiations will proceed to the next phase.

[0098] <Negotiation Phase> The M&A support flow during the negotiation phase is as follows. The M&A support flow during the negotiation phase is shown in Figure 10.

[0099] As shown in Figure 10, the partners communicate with the seller and buyer to finalize the terms of the M&A agreement (referred to as the M&A contract). Communication can be conducted using each party's terminal to finalize the M&A contract, or it can be finalized through an in-person meeting. The M&A contract can also be finalized through a video conference using each party's terminal.

[0100] As shown in Figures 2 and 4, the partner compiles the contents of the adjusted M&A agreement and accesses the M&A support system 10 from the partner's terminal 18 to register the contents of the adjusted M&A agreement (M&A agreement contents registration step). The data regarding the contents of the M&A agreement is stored in the data information registration unit 10C4 of the storage unit 10C.

[0101] As shown in Figures 3 and 4, the case information generation unit 10A2 of the M&A support system 10 creates a draft of the M&A contract based on the M&A contract details stored in the data information registration unit 10C4 of the storage unit 10C (M&A contract draft creation step). The data related to the draft of the M&A contract is stored in the data information registration unit 10C4 of the storage unit 10C.

[0102] The partner accesses the M&A support system 10 from their terminal 18 to obtain (download) information regarding the draft of the M&A agreement. Subsequently, the partner shares the draft of the M&A agreement with the seller and the buyer and prompts them to make a final confirmation. This final confirmation of the contents of the M&A agreement can be achieved by sending an email from the partner's terminal 18 to the seller's terminal 14 and the buyer's terminal 16. In this case, it is preferable to attach the draft of the M&A agreement file to the email. However, this is not the only option; the draft of the M&A agreement stored in the data information registration unit 10C4 of the storage unit 10C of the M&A support system 10 may be displayed on a website accessible from each terminal, and the URL of the website may be shared among the three parties (partner, seller, and buyer) to make a final confirmation of the contents of the M&A agreement on the website.

[0103] The contents of the M&A agreement are amended as needed. Once the final confirmation of the contents of the M&A agreement is complete, the partner accesses the M&A support system 10 from the partner's terminal 18 and registers the data regarding the amended contents of the M&A agreement in the data information registration unit 10C4 of the storage unit 10C (M&A agreement finalization step).

[0104] The seller and buyer share the revised M&A agreement, and the M&A agreement is concluded. The seller accesses the M&A support system 10 from the seller's terminal 14 to report the conclusion of the M&A agreement (seller's M&A conclusion reporting step). The buyer accesses the M&A support system 10 from the buyer's terminal 16 to report the conclusion of the M&A agreement (buyer's M&A conclusion reporting step).

[0105] Following the above M&A support flow, the M&A is completed and the M&A support is finished.

[0106] [Effects and benefits of M&A support systems and methods] Next, we will explain the effects and benefits of M&A support systems and methods that utilize partners.

[0107] The M&A support system and methods utilizing partners are specialized M&A-focused business systems, enabling thorough digital transformation (DX) across the entire process, including long list management, contract signing, and deal summaries. This significantly increases the number of M&A deals that each partner involved in M&A, such as M&A Navi, can handle.

[0108] In particular, the M&A support system utilizes a proprietary M&A-optimized business support SaaS developed by the patent applicant, which can be provided to external partners involved in M&A, primarily financial institutions. It can also improve the productivity of in-house M&A partners.

[0109] The main functions of the M&A support system include, for example, long list management, deal summary creation, AI long list function, stock price reporting function, and online explanation of important matters function.

[0110] The long list management function allows you to create a long list on the M&A support system and automatically reflect the results of proposals to each buyer.

[0111] The project summary creation function can automatically generate documents such as a comparison of financial data for three periods and a list of business partners, based on past meeting records and received documents.

[0112] The AI ​​longlist function makes it easy to extract potential synergy partners from companies nationwide based on successful domestic deals.

[0113] The stock price reporting function allows users to automatically generate a simplified stock price calculation A4 report from within the M&A support system by inputting financial information.

[0114] The online important matters explanation function can automate everything from the delivery of the important matters explanation document to the preparation and issuance of the brokerage agreement.

[0115] The patent applicant integrates its proprietary CRM and AI platform to personalize the AI ​​for each individual case (hereinafter referred to as "personalized AI"). By adding personalized AI to various tasks, the user experience (UX) for partners involved in M&A can be dramatically improved. In particular, by using personalized AI that has been further trained on case-specific information for each individual case, the efficiency of M&A operations can be greatly improved.

[0116] For example, one of the benefits of matching is that the entire process, from creating a list of candidates to signing a confidentiality agreement with the buyer, can be done online and easily completed with just a few clicks.

[0117] One of the benefits of creating project summaries is that by using a project-specific AI that has been further trained on received documents, project summaries can be easily created simply by entering information into a form on the terminal screen.

[0118] As an effect of negotiation advice and quality control, compliance with guidelines and best practices can be detected and scored based on task completion status, meeting minutes, etc.

[0119] <Example Function 1> As an example of its functionality, we will explain the comprehensive generation of acquisition candidates using an AI longlist. Current situation: When searching and narrowing down results based on job content, users were searching using "industry classification" or "keywords." Problem: It was easy to omit specifying options, and the effort required of partners involved in the M&A to specify the conditions was significant, resulting in a highly individualized process and inconsistent quality depending on the partner involved. Solution: Instead of using industry categories, search for similar companies based on the business description provided in the text. During the search, automatically add potential candidates based on synergy patterns from past cases. An example of its application is shown in Figure 11.

[0120] <Example of function 2> As an example of functionality, we will explain the initial proposal to the buyer and the signing of an NDA using an online non-name sheet (NN sheet). Current situation: NN sheets were created and stored as PDFs. They were then distributed to relevant parties via email attachments. Problem: Managing and sharing files, as well as exchanging emails, was time-consuming. Solution: Create an NN sheet on the CRM and publish it as a website. Send the sharing link to buyers, who will respond with their interest and sign an NDA. An example of its application is shown in Figure 12.

[0121] <Example of function 3> As an example of functionality, we will explain a company profile form that can be completed simply by answering questions, and a chat assistant. Current situation: It was being created in PowerPoint, taking about a week to complete. Challenge: The task involved extracting necessary information from a vast number of PDFs, which was a significant burden. Solution: Similar to year-end tax adjustments, a company profile can be completed simply by answering questions on a website. During this process, a chat assistant, trained to review received documents and interview records, can be used to easily research project details, eliminating the need to search for and learn about projects in PDF format. An example of its application is shown in Figure 13.

[0122] <Function Example 4> As an example of functionality, we will explain OCR specifically for financial statements. Current situation: To prepare financial information for buyers, PDF documents received from sellers were being manually transcribed into Excel spreadsheets. Problem: The figures and accounts included in the financial statements for three periods were being manually transcribed, a process that took approximately three hours. Solution: By using OCR specifically designed for reading financial statements, the data can be converted to Excel in just a few minutes. An example of its application is shown in Figure 14.

[0123] Based on the above, the M&A support system and M&A support method utilizing partners of the present invention can provide an environment in which appropriate expert support reaches small businesses. This can fundamentally solve the structural problem that "supporting small-scale deals is not profitable" and solve Japan's business succession problem.

[0124] In particular, with M&A support systems and methods, technology can be used to reduce the workload of partners involved in M&A, enabling the establishment of an M&A support model capable of closing a large number of deals. It becomes possible to increase the number of deals closed per partner per year from the industry average of 1-2 to over 10, and to offer M&A support services to the selling company at a purely performance-based fee with a minimum fee (e.g., over 2 million yen).

[0125] [Second Embodiment] Next, an M&A support system and M&A support method utilizing a partner according to the second embodiment of the present invention will be described with reference to the drawings. Components that overlap with the M&A support system and M&A support method utilizing a partner according to the first embodiment will be denoted by the same reference numerals and their descriptions will be omitted.

[0126] In the second embodiment, some steps of the matching phase are modified compared to the first embodiment. Note that the M&A support flow in the sales phase, deal development phase, and negotiation phase is the same as in the first embodiment, and therefore will not be explained.

[0127] <Matching Phase> The M&A support flow in the matching phase of the second embodiment is as follows. The M&A support flow in the matching phase of the second embodiment is shown in Figure 15.

[0128] As shown in Figures 3, 4, and 15, the long list generation unit 10A4 of the M&A support system 10 creates a list of buyers based on the buyer information stored in the buyer information registration unit 10C2, and registers it as a long list (AI long list) in the data information registration unit 10C4 of the storage unit 10C (buyer long list registration step).

[0129] As shown in Figure 6, the deal information transmission unit 10E1 of the M&A support system 10 sends an email containing identification information (e.g., a link such as a website URL) in the body of the email to the buyer's terminal 16 registered on the long list (deal information transmission step).

[0130] The buyer clicks on the identification information displayed in the body of the email received on the buyer's terminal 16 from the M&A support system 10. This allows the website linked to the URL controlled by the non-name sheet display unit 10A5 to be displayed on the buyer's terminal 16, and the buyer can confirm the details of the seller's business being transferred regarding the non-name sheet (buyer's non-name sheet display step).

[0131] As shown in Figures 3 and 5, the buyer inputs whether or not they are interested in the contents of the non-name sheet to the interest confirmation input unit 10D1 (interest confirmation input step). Based on the input results entered in the interest confirmation input step, the interest confirmation determination unit 10A6 determines whether or not the buyer is interested (interest confirmation determination step).

[0132] When the interest confirmation unit 10A6 determines that the buyer is interested, a personal information input field is displayed for the buyer to enter their personal information (e.g., real name, job title, email address, etc.) to be inserted into the contracting parties section of the confidentiality agreement (personal information input display step). The buyer can then input their personal information into the personal information input field and enter it into the personal information input unit 10D2 (personal information input step). A buyer who has entered their personal information can be said to be, for example, a buyer who wishes to disclose their real name.

[0133] When the buyer's personal information (e.g., real name, job title, email address, etc.) is entered into the personal information input section 10D2, the buyer's personal information is automatically inserted into the contracting parties section of the confidentiality agreement (confidentiality agreement completion step). In other words, if the buyer wishes to disclose the real name of the transaction, the control unit 10A of the M&A support system 10 shown in Figure 2 automatically inserts the buyer's personal information into the contracting parties section of the confidentiality agreement, and the contents of the confidentiality agreement are completed. At this point, it may be considered that a confidentiality agreement has been concluded between the buyer and M&A Navi.

[0134] Furthermore, if the buyer is determined to be uninterested during the interest confirmation step, the buyer's personal information (e.g., real name, job title, email address, etc.) for insertion into the contracting parties section of the confidentiality agreement will not be entered into the personal information input section 10D2.

[0135] As shown in Figure 4, information regarding the buyer's interest and the buyer's personal information are registered, for example, in the data information registration unit 10C4 of the storage unit 10C.

[0136] Next, as shown in Figure 5, a consent confirmation input section 10D3 is displayed for the buyer to input their consent to the contents of the confidentiality agreement. The buyer inputs their consent to the consent confirmation into the consent confirmation input section 10D3 (consent confirmation input step). Once the buyer has entered their consent to the consent confirmation, input fields for the buyer's acquisition needs are displayed (acquisition needs input step). The acquisition needs input fields include items such as M&A willingness / experience, industry, area, sales scale, and acquisition background.

[0137] M&A Navi sends information regarding the "disclosure of real name" inquiry to the seller's terminal 14 via the M&A support system 10 from M&A Navi's terminal 12 (seller's real name disclosure step). The seller sends information to the M&A support system 10 from the seller's terminal 14 regarding whether or not to disclose the seller's real name to buyers who are registered on the longlist and have entered their personal information (buyers who wish to have their real name disclosed) (seller's real name disclosure response step). M&A Navi confirms the seller's response regarding the disclosure of their real name via the M&A support system 10 from M&A Navi's terminal 12. The seller's real name disclosure response information is stored as data in the data information registration 10C4. These steps are called the NC workflow.

[0138] M&A Navi sends an email containing identification information (for example, a link such as a website URL) that includes the deal summary to the buyer's terminal 16, which has been authorized (approved) by the seller to disclose its real name, from M&A Navi's terminal 12 via the M&A support system 10 (email sending step to authorized buyer). M&A Navi may send the email to the seller's authorized buyer's terminal 16 from M&A Navi's terminal 12 via the M&A support system 10, or it may send the email to the seller's authorized buyer's terminal 16 from M&A Navi's terminal 12 without going through the M&A support system 10. The buyer authorized by the seller opens the email received on the buyer's terminal 16 and accesses (clicks to display) the identification information that includes the deal summary, thereby confirming the contents of the deal summary stored in the M&A support system 10 (buyer's deal summary confirmation step). If the buyer wishes to proceed with the acquisition consideration, they press the meeting date scheduling button on the buyer's terminal 16. When the buyer's terminal 16 presses the button to schedule an interview, the M&A support system 10 is entered to schedule the interview. These steps are called online instant messaging (IM).

[0139] When the meeting date arrives, the partner meets with the buyer. After the meeting, the partner accesses the M&A support system 10 from their terminal 18 and registers the details of the meeting record (buyer meeting record registration step). The information regarding the meeting record is stored in the data information registration unit 10C4 of the storage unit 10C.

[0140] If, as a result of the meeting between the partner and the buyer, the buyer wishes to meet with the seller, the partner, buyer, and seller will coordinate a three-way meeting. Specifically, the three-way meeting is confirmed when the partner registers with the M&A support system 10 from their terminal 18 that the buyer wishes to meet with the seller. Subsequently, the M&A support system 10 sends a message regarding scheduling the three-way meeting to the seller's terminal 14, the buyer's terminal 16, and the partner's terminal 18 (three-way meeting scheduling step). After the date and time of the three-way meeting are decided, the meeting takes place on the scheduled date.

[0141] After the three-party meeting, the partner accesses the M&A support system 10 from their terminal 18 to register the contents of the three-party meeting record (three-party meeting record registration step). The information regarding the three-party meeting record is stored in the data information registration unit 10C4 of the storage unit 10C.

[0142] If the three-way meeting leads to a decision to consider the acquisition, the negotiations will proceed to the next phase.

[0143] In the NC workflow, when a buyer interested in a non-name sheet requests further disclosure, the partner will contact the seller with the buyer's information to confirm whether they are willing to disclose their real name (name clearing). Only buyers who approve the request will the partner then disclose the seller's information.

[0144] Previously, these exchanges were conducted via email and telephone, but when requests for detailed disclosure were received from multiple buyers at different times, the communication between the seller and buyers became extremely complex and cumbersome. In addition, the partner had to research each buyer's information online, organize the buyers' information, and then confirm with the seller whether the seller would disclose their names.

[0145] According to NC Workflow, the collection of buyer information and confirmation with sellers can be automated, reducing the burden on partners. In addition, sellers can view all buyer information at any time from their device screen and respond immediately to unanswered approval requests.

[0146] According to the online IM (Instant Message) system, the deal summary is sent to the buyer after the seller's name clear approval is obtained. Traditionally, partners would password-protect the deal summary as a PDF and attach it to an email to send it to the buyer. However, with the online IM function, a webpage IM can be sent securely and easily from the M&A support system via a URL.

[0147] It should be noted that the above embodiments, including the various names or naming conventions, are merely examples that embody the technical concept of the present invention. Naturally, the present invention is not limited to these embodiments, but includes all aspects that utilize the technical concept of the present invention. [Explanation of Symbols]

[0148] 10 M&A support systems 12 M&A Navi terminal 14. Seller's terminal 16. Buyer's terminal 18. Partner's device 10A Control Unit (M&A Support System) 10B Calculation Unit (M&A Support System) 10C Memory Unit (M&A Support System) 10D Input Unit (M&A Support System) 10E Output Unit (M&A Support System) 10A1 Partner Selection Unit (Control Unit) 10A2 Case Information Generation Unit (Control Unit) 10A3 Case Information Modification Department (Control Unit) 10A4 Longlist Generation Unit (Control Unit) 10A5 No-Name Sheet Display Unit (Control Unit) 10A6 Interest Confirmation and Determination Unit (Control Unit) 10C1 Seller Information Registration Section (Memory Section) 10C2 Buyer Information Registration Section (Storage Section) 10C3 Partner Information Registration Section (Storage Section) 10C4 Data Information Registration Unit (Storage Unit) 10D1 Interest Confirmation Input Section (Input Section) 10D2 Personal Information Input Section (Input Section) 10D3 Consent Confirmation Input Section (Input Section) 10D4 Project Information Input Section (Input Section) 10E1 Case Information Transmission Unit (Output Unit) 10E2 Project Information Output Unit (Output Unit)

Claims

1. This is an M&A support system that utilizes expert partners. A partner selection unit that selects an appropriate partner based on seller information regarding the seller and partner information regarding the partner, A project information generation unit creates a project summary and a non-name sheet that reflects the contents of the project summary, based on the project information of the seller to be transferred, which is registered by the selected partner. A partner-based M&A support system that possesses [specific features / abilities].

2. The M&A support system utilizing a partner as described in claim 1, comprising a case information modification unit for modifying the contents of the case summary or the non-name sheet.

3. An M&A support system utilizing a partner as described in claim 1 or 2, wherein the aforementioned case summary or non-disclosure sheet includes at least one piece of information: information concerning the company and business of the seller that owns the business to be transferred, information concerning the seller's desired transfer conditions for the business to be transferred, or information concerning the valuation of the business to be transferred by the seller.

4. An M&A support system utilizing partners according to claim 1 or 2, comprising a long list generation unit that generates a list of buyers based on buyer information relating to the buyers and generates it as a long list.

5. The M&A support system utilizing partners according to claim 1 or 2, further comprising a non-name sheet display unit that displays the contents of the non-name sheet in a display area on a website.

6. The M&A support system utilizing partners according to claim 4, further comprising a case information transmission unit that sends an email containing identification information for identifying the display area of ​​the non-name sheet to the buyer registered in the long list.

7. The M&A support system utilizing partners according to claim 4, comprising a case information transmission unit that sends an email containing identification information for specifying the display area of ​​the non-name sheet to the buyer who is registered on the long list and approved by the seller.

8. An interest confirmation input unit for inputting whether the buyer is interested in the contents of the non-name sheet, Based on the input results of the interest confirmation input unit, an interest confirmation determination unit determines whether or not the buyer is interested, An M&A support system utilizing the partner described in claim 6, having the features described in claim 6.

9. The M&A support system utilizing a partner as described in claim 8, further comprising a personal information input unit for inputting the buyer's personal information, which is displayed when the interest confirmation unit determines that the buyer is interested, and for insertion into the contracting parties section of the confidentiality agreement.

10. The M&A support system utilizing a partner as described in claim 9, wherein when the buyer's personal information is entered into the personal information input section, the personal information is inserted into the contracting parties section of the confidentiality agreement.

11. The M&A support system utilizing a partner as described in claim 10, further comprising a consent confirmation input unit for inputting the buyer's expression of consent regarding the contents of the confidentiality agreement.

12. This is an M&A support method that utilizes expert partners. A partner selection step in which an appropriate partner is selected based on seller information regarding the seller and partner information regarding the partner, A project information registration step involves creating and registering a project summary and a non-name sheet reflecting the contents of the project summary, based on the project information of the seller to be transferred registered by the selected partner, A method of M&A support that utilizes partners.

13. A method for supporting M&A using a partner as described in claim 12, comprising a step of modifying the contents of the aforementioned case summary or the aforementioned non-name sheet.

14. A method of M&A support utilizing a partner as described in claim 12 or 13, wherein the aforementioned case summary or non-disclosure sheet includes at least one piece of information: information concerning the company and business that the seller has in possession of the business to be transferred, information concerning the seller's desired terms for the transfer of the business to be transferred, or information concerning the valuation of the business to be transferred by the seller.

15. A method for supporting M&A transactions using a partner as described in claim 12 or 13, comprising a longlist registration step in which a list of buyers is created based on buyer information relating to the buyers and registered as a longlist.

16. A method for supporting M&A using a partner according to claim 12 or 13, further comprising a no-name sheet display step in which the contents of the no-name sheet are displayed in a display area on a website.

17. A method for supporting M&A transactions using a partner as described in claim 15, comprising a step of sending a case information transmission email to the buyer registered on the long list, the email containing identification information for identifying the display area of ​​the non-name sheet.

18. A method for supporting an M&A transaction using a partner, according to claim 15, further comprising a step of sending transaction information to the buyer who is registered on the long list and approved by the seller, the buyer who has been approved by the seller, and the email containing identification information for identifying the display area of ​​the non-name sheet.

19. An interest confirmation input step is to input whether the buyer is interested in the contents of the non-name sheet, An interest confirmation determination step, which determines whether or not the buyer is interested based on the input results entered in the interest confirmation input step, A method for supporting M&A using a partner as described in claim 17, comprising:

20. A method for supporting an M&A transaction using a partner as described in claim 19, further comprising a personal information input step for inputting the buyer's personal information, which is displayed when the interest is determined to be present in the interest confirmation step and for insertion into the contracting parties section of the confidentiality agreement.

21. A method of M&A support utilizing a partner as described in claim 20, wherein when the buyer's personal information is entered in the personal information input step, the personal information is inserted into the contracting parties section of the confidentiality agreement.

22. A method for supporting an M&A transaction using a partner as described in claim 21, further comprising a consent confirmation input step in which the buyer inputs an expression of consent regarding the contents of the confidentiality agreement.

Images