The Client Portal: What the Owner Sees and What the Attorney Sees

Why the owner needs a narrow view

An owner running a company while selling it has limited attention. In the readiness and marketing phases, the owner's job is specific: answer the questionnaire, upload the documents on the request list, review the CIM draft, approve the buyer list, and approve each disclosure before it goes out. Everything else, from buyer research to NDA negotiation to IOI tracking, is the firm's work.

When the owner is shown too much, two things can go wrong. The owner may start reacting to buyer activity in real time, calling the partner because a particular private equity firm opened the teaser, or because a competitor requested the NDA. The owner may also start to feel that the process is being done to the business rather than directed by the owner. Neither response helps the process.

A narrow view keeps the owner on task. The portal shows a list of document requests with status, a place to upload each item once, a queue of items awaiting approval, including the teaser, the CIM, the buyer list, and each data room release, and a summary of where the process stands by phase. The owner logs in, sees what is needed, does it, and logs out. The partner gets a notification. Nobody has to maintain a separate spreadsheet. A firm should still configure access and review procedures that fit its confidentiality obligations. ABA Model Rule 1.6 calls for reasonable efforts to prevent inadvertent or unauthorized disclosure of, or access to, client information. [1]

What a document request looks like from the owner's side

The document request list is the first thing the owner interacts with, and it sets the tone. A good list is organized by category, such as corporate, financial, customers, employees, contracts, real estate, intellectual property, insurance, litigation, and tax. Each item says what is wanted, why, and whether it is needed before launch or can wait for the second round.

From the owner's side, each request shows a status: requested, uploaded, reviewed by the firm, or released to the data room. The owner uploads once. The firm reviews. If the document is incomplete or raises a question, the associate's note appears against that item and the owner responds in the same place. When the firm is ready to release the document to buyers, the owner sees the request for approval, and nothing goes into the data room until the owner approves it.

This matters for confidentiality and for the record. An approval workflow can document what the owner authorized, but it is not a substitute for the attorney's review of the disclosure or the firm's access controls. A dated version and activity history can also help the team reconstruct what happened. NIST describes security log management as a way to maintain records of system activity and support audit and accountability practices. [2]

What the attorney sees across every client

The attorney's view is the pipeline. For a firm running three client processes at once, that means three rows or three boards, depending on preference, each showing the client's phase, the buyers in the process, and the status of each buyer against NDA, IOI, data room access, management meeting, and LOI.

Within a single client, the partner can see which buyers received the teaser and when, which requested the NDA, which have signed, which have been given data room access and at what stage, which have submitted IOIs, and what each IOI said. The associate's outreach log sits in the same place. The paralegal's NDA tracker sits in the same place. The data room activity log is a click away.

Across clients, the partner sees the firm's capacity. If one client is in the offers phase with an IOI deadline next week, a second is in readiness with forty document requests outstanding, and a third is in exclusivity with a diligence calendar running, the partner can assign the associate's week accordingly. These quantified scenarios are illustrative, not measured Acquivo results. Without a shared pipeline, this information may live in three email threads and the partner's memory.

The line between the two views

The attorney decides what crosses from the pipeline into the owner's portal. Some things always cross: document requests, draft materials for review, the buyer list for approval, each disclosure for approval, and a phase summary. Some things cross at the attorney's discretion: the IOI comparison, once the attorney has reviewed it and is ready to discuss it with the owner. Some things do not cross: outreach notes, buyer-side NDA negotiations, the associate's internal comments, and buyers who were researched but not yet proposed to the owner.

This line is a professional judgment, not a claim that software itself makes a legal or confidentiality decision. The attorney who runs the process is the owner's counsel and controls the flow of information to the client as in any other engagement. The portal makes that judgment easier to execute because it has two sides, and the attorney chooses what goes on the owner's side. The firm should confirm with its own counsel how applicable professional-responsibility, privacy, and other rules affect its particular workflow.

Why the portal should carry the firm's name

An owner who logs in to a portal that says the firm's name, not a software vendor's, understands who is running the process. The firm is the owner's advisor. The software is the firm's tool. This is the intended relationship, and it should be visible in the client experience.

It also matters for the firm's practice development. An owner who completes a sale through a portal with the firm's name on every screen may tell other owners that the firm ran the sale. An owner who completes a sale through a vendor's portal may instead remember the vendor. The firm did the work either way; the branding influences which name is most visible.

Setting up the portal for a client this week

For a client who has agreed to begin a readiness review, the attorney can set up the portal in an afternoon if the firm's process and the client's materials are ready. The partner approves the document request list, tailored to the client's industry. The paralegal sends the portal invitation to the owner and the controller. The associate schedules a thirty-minute walkthrough with the owner to show where requests appear, how to upload, and where approvals will be requested. From that point, the owner's work is visible to the firm as it happens, and the firm's requests are visible to the owner in one place.

The attorney should also tell the owner what will not appear in the portal and why: buyer research and outreach stay on the firm's side until the owner is asked to approve a list. Owners who hear this up front can better understand the division of work. They have a company to run.

How Acquivo Pro fits

Acquivo Pro provides the two views described here on one login. The owner sees a branded document portal under the firm's name where document requests appear, uploads happen once, and disclosures are approved. The firm sees the full pipeline: NDA, IOI, and LOI flow for every buyer and every client, with valuations, teasers, CIMs, and buyer lists built from the client's questionnaire and data room. One seat runs multiple concurrent client processes on a flat monthly subscription with no per-deal fees, and client data is isolated. Software prepares, organizes, matches, and tracks; the attorney and the client decide and act. To walk through a process on a client you have in mind, request a demo through the Contact page.