How Should a Boutique Bank Price and Bound a Preparation-Only Engagement?

Start with the boundary, not the number

A preparation-only engagement answers a narrower question than a sell-side mandate: what must be assembled, tested, and approved before anyone decides whether to run a process? The scope should say that plainly. It can cover organizing financial information, identifying diligence questions, preparing an internal valuation analysis, drafting an information memorandum, or creating a process-readiness checklist. It should not imply that the bank is engaged to contact buyers, solicit indications, negotiate terms, manage a live auction, or close a transaction unless those activities are expressly added.

Write the boundary as an operating rule. “No external distribution or buyer communication occurs under this engagement” is more useful than “preparation services only.” Define the decision that ends the work: delivery and approval of a specified package, a scheduled review meeting, or written notice that the preparation phase is complete. A clear end point limits accidental drift into an open-ended mandate.

Turn the scope into an effort worksheet

Use one row for each workstream and assign an accountable human owner. Useful rows include data intake, financial normalization, quality checks, valuation analysis, narrative drafting, presentation formatting, review meetings, and final handoff. For each row, record inputs, output, review owner, included review cycles, and an effort assumption in internal work units or hours. The purpose is not to publish a universal rate. It is to make the internally approved fee traceable to the agreed work.

Separate production effort from review effort. A draft produced with an AI tool still needs a person to compare figures to source-of-truth records, check that statements are not overstated, remove unsupported inferences, and confirm that the client has permission to use supplied materials. Record who performs that review and who can approve release. If the reviewer cannot verify a claim, route it to an open item or omit it rather than treating fluent text as evidence.

Show dependencies. A management presentation may depend on a reconciled trial balance. A valuation discussion may depend on agreed historical periods and definitions. If a dependency is missing, the schedule and fee basis should pause or change through written change control.

Define deliverables so acceptance is testable

Name each deliverable by format, content, and acceptance test. “Draft marketing materials” is vague. “One internal review draft of a company overview and financial summary, based on client-provided records, with a source index and unresolved questions” is testable. State whether the output is for internal planning, counsel review, or possible later distribution. A preparation file should not be called buyer-ready if no buyer diligence, outreach approval, or external review is included.

Include a source-of-truth record for each material section. Version it, preserve the date received, and note assumptions separately from reported figures. The reviewer should check arithmetic, period labels, units, definitions, and consistency across narrative and exhibits. Set review rounds and response windows. A correction fixes an error against an agreed source. A new request adds a section, changes the audience, introduces a new period, or requires new analysis. This distinction makes the boundary visible before additional work begins.

Choose a fee architecture without making a recommendation

A firm may use a fixed project fee, staged fees tied to defined deliverables, time-based billing, or another approved structure. This article does not prescribe which is best. The worksheet should show why the selected structure fits uncertainty in the inputs and the client’s need for budget visibility. State whether the fee is payable in advance, on milestones, or after delivery, and what happens to unperformed prepaid work if the engagement ends early. SEC Form ADV Part 2, where applicable to the firm and service, calls for descriptions of compensation, fee schedules, negotiability, billing, other costs, and treatment of prepaid fees. [1]

Do not hide variable effort inside a fixed label. List assumptions such as source files, reporting periods, business units, interviews, draft versions, and review meetings. State the unit that triggers a change. Avoid invented market benchmarks or a “standard” percentage. If the firm could receive transaction-related compensation later, make the relationship between the preparation fee and later compensation explicit. Do not imply that a preparation fee automatically earns a success fee or that a later mandate is guaranteed. Where securities offerings or regulated activity are involved, firm-specific rules may apply. FINRA Rule 5110 addresses underwriting compensation in public offerings and includes financial consulting and advisory fees within its framework, but applicability depends on the transaction and member status. [3]

Make exclusions operational

An exclusion should identify the action that is not authorized, not merely say “no transaction services.” Typical preparation-stage exclusions may include buyer identification, external outreach, distribution of materials, data-room management, negotiation, bids or indications, diligence coordination, fairness opinions, tax advice, legal advice, and closing support. The actual list must match the firm’s service model and regulatory review. State whether the bank may use subcontractors or software tools, who approves them, and what confidentiality instructions apply.

Treat client responsibilities as part of the boundary. The client should identify authorized records, confirm the right to use third-party content, designate a reviewer, answer open questions, and approve any permitted external use. If an input is late, show whether the deliverable is delayed, narrowed, or re-scoped rather than promising a date that depends on uncommitted information.

Handle AI as a controlled production step

If AI assists with extraction, drafting, classification, or formatting, name the task and its limits in the internal workflow. Keep source records separate from generated text. The accountable reviewer should compare every financial figure and material claim to the source, check for omitted qualifiers, and confirm that confidential information is handled under approved policy. Do not upload a document merely because a tool can accept it. Decide what may be processed, where it may be processed, how long it is retained, and whether a non-AI route is required.

Use a small pilot before expanding. Stop if the tool invents facts, drops units or periods, exposes restricted material, produces inconsistent classifications, or requires more correction than the approved effort assumption allows. The human owner then decides whether to revise the prompt, change the source format, switch tools, or complete the task manually. No AI output should authorize outreach, disclosure, negotiation, or approval by itself.

Separate a later mandate transition

A later sale mandate should be a separately approved decision, even when preparation work is successful. Define the transition trigger as a new written scope, approval authority, effective date, and fee schedule. Identify which deliverables may be reused, which must be refreshed, and which assumptions expire. State whether prior fees are credited or remain separate only if the firm has chosen that treatment and counsel has reviewed the language.

Be precise about any tail, termination, exclusivity, or protected-party concept. These terms can affect the commercial result and may be jurisdiction-dependent. Do not copy a broad tail clause into a preparation-only letter just because it appears in a full mandate. Define what event, time period, parties, and approval would make a later obligation relevant, then have qualified counsel review it.

Conflict disclosure should evolve with the mandate. The ABA Business Law article on financial-adviser engagement letters describes the letter as a tool for vetting conflicts and discusses representations and disclosure of later conflicts. [4] The SEC staff bulletin emphasizes that compensation conflicts should be disclosed specifically, in plain English, including incentive, source and scale of compensation, benefits, and client costs. [2] A transition review should revisit conflicts rather than treating the preparation letter as permanent clearance.

Use a release checklist before signing

Before execution, the engagement owner should answer six questions: What is the exact preparation outcome? What is not included? Which source records control? Who reviews and approves each deliverable? What event changes the scope or stops the work? What happens if a later mandate is considered? The answers should appear in the engagement letter or incorporated scope schedule, with the worksheet retained as the internal operating record.

Run a consistency check across the proposal, worksheet, fee schedule, and engagement letter. The same deliverables should have the same names. Review limits should match. Billing, expenses, conflicts, confidentiality, data handling, and termination language should not contradict one another. The SEC cautions against generic “may have a conflict” language when a conflict actually exists. [2] Specific, plain-language drafting is a quality control, not only a legal formality.

Acquivo is a software platform that delivers the entire sell-side M&A process, valuation, marketing materials, buyer matching, and deal management, on one platform for business owners, M&A attorneys, and boutique investment banks. A boutique bank can use a software workflow as a user-operated aid to organize the worksheet and review trail, while the bank retains responsibility for scope, approvals, client communications, and professional obligations.