Per-Seat vs. Per-Deal Pricing: What Makes Sense for a Boutique Bank

The two models, stated plainly

Per-deal pricing charges the bank each time it opens a mandate on the platform, sometimes with additional charges for data room storage, buyer list size, or document volume. The bank pays nothing when idle. Cost scales directly with activity. That structure resembles usage-based pricing, where charges are tied to how much of a service a customer uses during a billing period. [2] A data room fee may be passed through to the client or absorbed as a deal expense, depending on the engagement and the bank's agreement.

Per-seat pricing charges a flat monthly amount for each person who has a login. The bank pays whether it has one mandate open or eight. Cost scales with the team, not with the work. In a standard per-seat model, the number of paid seats maps to the number of users, typically as a recurring charge. [1] That model fits a platform the bank uses continuously rather than only per transaction.

A hybrid exists: a base subscription plus a per-deal charge. It combines a fixed cost with a variable one, so the partner should ask what the per-deal component is before accepting a low headline subscription.

When per-deal pricing is the right answer

Per-deal pricing is right when mandates are rare and lumpy. A two-partner firm that runs one or two sell-side engagements a year, with long gaps between them, has no reason to pay a monthly subscription for eight idle months. The per-deal charge is a deal expense, it can often be passed to the client if the engagement permits it, and the bank's exposure is limited to the engagements it actually wins.

It is also right when the bank is uncertain whether it will use the tool at all. A per-deal arrangement on one mandate is a low-commitment way to find out, provided the bank understands that the economics will look different if it later runs five.

And it is right for tools the bank uses on some mandates but not others. A specialized data room for a large competitive auction may be worth per-deal pricing on the two auctions a year that need it, while the bank's routine processes run elsewhere.

What per-deal pricing is not right for is the core workflow of a bank whose plan is to do more. Every incremental mandate adds cost, and the bank is trying to make incremental mandates cheaper on the tool side.

When per-seat pricing is the right answer

Per-seat pricing is right when the bank runs mandates continuously and wants the marginal mandate to cost nothing on the tool side. A ten-person bank with four to eight live engagements at any time is using the platform every day. The subscription is a fixed cost of operating, like the office or the research terminal, and it belongs in the overhead budget rather than in deal expenses.

The strategic fit is the main argument. A bank that adopts a platform to run five mandates with the team that used to run three has decided to grow revenue per banker. Per-seat pricing means the tool cost per banker is flat while revenue per banker rises. Per-deal pricing means the tool cost rises with the number of mandates, which may be tolerable but leaves less of the incremental revenue after tool costs.

There is a behavioral argument too. When each mandate carries a per-deal charge, the bank may hesitate to put a small engagement on the platform, and the small engagement may get run the old way, in spreadsheets and email. Per-seat removes that particular price hesitation. Every mandate can go on the platform because the next one carries no additional deal fee, and the bank can pursue the consistency that makes the platform worth having.

Per-seat pricing also makes budgeting simple. The partner knows the recurring tool cost in January. There are fewer usage-driven surprises in a busy quarter, subject to the contract's limits and renewal terms.

The question that decides it: can one seat run several processes

The detail that determines whether per-seat is actually per-seat is whether one login can run multiple concurrent mandates. If each process requires its own seat, the pricing is per-deal with a different label, and the bank should evaluate it as such.

Ask the vendor directly: can one associate's seat run four live mandates at once. Ask whether there are limits on the number of processes, clients, or buyer lists per seat. Ask whether seats are named, tied to a person, or floating, shared, because a small bank with part-time contractors may prefer the latter.

Then do the arithmetic for the bank's own headcount. A ten-person bank might need six seats: three partners who review and approve, two associates who run processes, and one analyst who manages data. Multiply by the monthly price and compare to the annual total of the current stack, including the labor the stack consumes in handoffs. The comparison depends on the bank's actual mandate volume and contract terms, so treat this as an illustrative scenario, not a measured result.

Hidden charges to ask about under either model

Whichever model, the headline price may not be the whole price. A partner should ask about five things before signing.

Data room storage: is there a charge per gigabyte or per page, and does it apply to every client's data room. Buyer database access: is the database included, is there a cap on exports or list size, and is there a charge for refreshing. Document generation: is there a limit on teasers or CIMs per month or per mandate. Owner portal: is the client-facing portal included, and does it carry the bank's branding without an extra fee. Renewal: what is the price increase cap at renewal, and does the vendor commit to it in writing.

The best answer to all five is that they are included in the seat price. The second-best answer is a clear schedule. The worst answer is an unclear usage policy, because the bank may find out about a variable charge in a busy quarter.

Presenting the choice to the partnership

The pricing decision is easier to make when framed as a question about strategy rather than a question about price. The sponsoring partner can put it to the partnership in one sentence: do we intend to run more mandates with this team, or the same number. If more, per-seat matches the plan. If the same, and the number is small, per-deal may be fine.

Then show the arithmetic for three scenarios: the bank's current mandate count, one and a half times that, and double. Under per-deal, the tool cost increases with the mandates. Under per-seat, the seat component stays flat. The gap at double is the cost of choosing the wrong model, and its size depends on the quoted prices, included limits, and actual usage.

A practical step for this week: pull the last twelve months of tool invoices and sort them into fixed and per-deal. The per-deal total, divided by the number of mandates, is what the bank currently pays per engagement on the tool side. That is the number a per-seat proposal is designed to remove, subject to its seat count and any excluded charges.

How Acquivo Pro fits

Acquivo Pro is priced per seat on a flat monthly subscription with no per-deal fees, and one seat runs multiple concurrent processes, so an additional mandate carries no additional deal fee on the platform. The seat covers the full workflow: valuations across 21 industry verticals, teaser and CIM generation from the questionnaire and data room, buyer matching using documented acquisition criteria, and NDA, IOI, and LOI flow for every client in a single pipeline. The owner's branded document portal is part of the platform. To see it on a live mandate, request a demo through the Contact page.