A boutique bank should not make a $5M mandate a miniature version of a $100M mandate, nor should it treat the larger deal as automatically complex. Start with the transaction's likely buyer universe, financial quality, ownership issues, diligence burden, financing needs, regulatory exposure, and expected negotiation intensity. Keep evidence standards, confidentiality controls, source checking, conflict review, and final banker accountability constant. Scale the number of workstreams, specialist support, marketing iterations, buyer-contact controls, data-room preparation, and senior review points to the risks and decisions in the specific mandate. AI can help organize and draft low-risk work, but a named banker should verify source records, judgment-heavy conclusions, disclosures, outreach, and approvals before anything is used externally.
Start with complexity, not the headline value
The $5M and $100M labels are starting points, but they are not a scope of work. A smaller company can have messy revenue recognition, concentrated customers, unclear ownership, cross-border operations, environmental exposure, or a succession dispute. A larger company can have clean reporting, a prepared management team, and a narrow buyer universe. The staffing and preparation plan should therefore follow the decisions the bank must support, not a universal percentage of enterprise value.
At kickoff, write a short complexity assessment. Record the transaction objective, expected consideration structure, enterprise-value definition, ownership and authority questions, financial reporting quality, customer and supplier concentration, intellectual property, employment matters, tax and legal dependencies, financing assumptions, likely buyer types, confidentiality sensitivity, and expected timetable. The assessment is an internal scoping record, not a valuation conclusion.
Use the assessment to classify each workstream as light, standard, or intensive. That creates a defensible reason for adding or removing work. It also leaves room to re-scope when diligence reveals a new issue. A size-based template can still provide a starting checklist, but it should never override the facts of the mandate.
Keep the evidence standard constant
A $5M mandate may justify fewer iterations, but it does not justify weaker support for a material claim. Historical financial figures should tie to source records. Adjustments should be defined and documented. Buyer-facing statements should have an accountable reviewer. Valuation assumptions should be separated from reported facts, and unresolved gaps should be visible rather than hidden in polished prose.
The same principle applies to valuation support. The International Valuation Standards Council describes business valuation as work that requires clarity about what is being valued, for whom, for what purpose, on what basis, and within what limitations. It also places responsibility for the provenance and reliability of inputs with the valuer, and says a model does not take responsibility away from the valuer [1]. A smaller mandate can use a narrower analysis, but the scope and limitations still need to be explicit.
Define an evidence register before drafting marketing materials. For each important statement, identify the source record, period, owner, status, and reviewer. Mark items as verified, management-provided, estimated, or unresolved. This prevents a larger budget from being mistaken for better evidence and prevents a smaller budget from becoming an excuse for unsupported claims.
Scale the core workstreams deliberately
For a straightforward smaller mandate, the core workstreams may be a focused financial normalization, a concise valuation range with clear assumptions, a short confidential profile, a targeted buyer hypothesis, a controlled outreach plan, and a simple diligence tracker. The bank may use fewer review cycles and concentrate senior attention at the scoping decision, final materials, and important buyer communications.
A larger mandate may need separate workstreams for quality of earnings, working capital and net debt, customer and contract analysis, management presentation preparation, tax and legal coordination, financing analysis, broader buyer segmentation, data-room architecture, and bid comparison. More work does not automatically mean better work. Each added stream should have a decision it informs, a source-of-truth record, an owner, a deliverable, and a review gate.
The scope should identify what is excluded. For example, a bank may prepare a high-level market perspective without promising a fairness opinion, legal diligence, a tax conclusion, or a financing commitment. Those boundaries should be stated in the engagement materials and revisited when the facts change.
Match staffing to judgment and coordination risk
Staffing should reflect the number of interdependent judgments, not just the expected fee or enterprise value. A smaller deal with one owner and a clean set of records may need one primary deal lead, an analyst, and scheduled senior review. A more involved mandate may need a deal lead, financial-modeling support, a diligence coordinator, industry or buyer research support, and access to legal, tax, accounting, or other specialists where appropriate.
The key question is who owns each judgment. Assign a human reviewer for normalized earnings, valuation assumptions, buyer eligibility, confidential information, management claims, and every external communication. Do not let an analyst, software output, or automated draft become the de facto approver because the mandate is small. For regulated broker-dealers, the exact requirements depend on status and jurisdiction. FINRA Rule 3110, for example, requires member firms to maintain a supervisory system and written procedures, including documented principal review of investment banking or securities transactions, with procedures appropriate to the firm's business, size, structure, and customers [2]. That is a firm-specific regulatory requirement, not a universal template for every adviser.
Build escalation triggers into the staffing plan. Examples include a material accounting adjustment, a new related-party issue, a threatened confidentiality breach, a buyer request outside the approved process, a conflict, a disputed valuation input, or a proposed disclosure that cannot be supported. The trigger should name the person who pauses the work and the person who decides whether it resumes.
Prepare the seller and the records before marketing
Preparation is often where a smaller mandate can benefit most from disciplined scope. Start with a document inventory and a three-way reconciliation among the general ledger or financial statements, management reporting, and the draft marketing narrative. Investigate differences before they become buyer questions. Confirm ownership, authority to sell, material contracts, debt, leases, customer concentration, employee dependencies, intellectual property, litigation or disputes, and any other issue that could change the buyer's view.
For a lighter mandate, a prioritized request list may be more useful than a large data room. For a larger mandate, the bank may need a staged data-room index, request ownership by workstream, version control, management interview agendas, and a process for logging open items. In both cases, do not collect sensitive information merely because a template contains a field. Collect what is relevant to the decision and define who can access it.
The implementation outcome should be a scope that tells the team what good preparation means. It should specify the records required for the first buyer conversation, the records deferred until a qualified indication of interest, and the conditions that stop outreach until a material gap is resolved.
Use AI for bounded production work, not approval
AI can assist with bounded tasks such as classifying a document list, spotting inconsistent labels, extracting dates for a human check, comparing two versions of a draft, or proposing a first-pass question list. The task owner should define the permitted inputs, the expected output, the source-of-truth record, and the reviewer before the pilot begins. The prompt should not be a substitute for an engagement scope.
For a smaller mandate, pilot one low-risk task on a redacted or approved sample. Stop the pilot if the tool invents a source, loses a material qualifier, exposes confidential information, produces inconsistent classifications, or cannot preserve the required record of human correction. For a larger mandate, use separate pilots for separate tasks and test edge cases that resemble the actual work. Keep a sample of inputs and outputs so the reviewer can reproduce what happened.
NIST describes its AI Risk Management Framework as a voluntary framework for incorporating trustworthiness considerations into the design, development, use, and evaluation of AI systems, organized around Govern, Map, Measure, and Manage [3]. That framework can inform a pilot checklist, but it does not guarantee security, confidentiality, accuracy, privilege, compliance, or transaction outcomes. A banker must review financial extractions, valuation language, buyer eligibility, confidential information, outreach, negotiation positions, and approvals. AI should not send outreach, negotiate, approve disclosure, or make a final scope decision autonomously.
Design buyer coverage and process controls
Buyer coverage should be a reasoned hypothesis, not an unbounded list. Define the buyer characteristics that matter, the information needed to test fit, the confidentiality stage at which information can be shared, and the human approval required before contact. A small mandate may use a focused set of likely buyers and a shorter process. A larger mandate may need buyer segmentation, conflicts screening, financing-capacity questions, strategic rationale, and a more formal bid timetable.
The same process controls apply at both sizes. Maintain an approved outreach list, record who approved each contact, use the authorized information package, log responses, and document changes to the process. Do not assume a larger pool improves results. The relevant question is whether each contact is plausible, permissible, and supported by the mandate's confidentiality and conflict rules.
If the bank is subject to broker-dealer or other professional obligations, apply the rules and written procedures that govern that firm and transaction. The SEC staff explains that conduct obligations and policies can depend on facts, circumstances, business model, and relationships, and should be tailored rather than applied mechanically [4]. That supports a tailored control design, but it is not a blanket legal conclusion for all boutique banks or transactions.
Set review gates and stopping conditions
A useful scope names review gates before work begins. A practical sequence is: approve the complexity assessment; reconcile core financial records; approve the valuation basis and assumptions; approve the confidential profile; approve the buyer hypothesis and outreach list; review buyer feedback; and approve any revised positioning or disclosure. The larger the coordination burden, the more explicit the gates should be. A smaller deal can use fewer gates, but it should not omit the gates that protect evidence, confidentiality, and authority.
Each gate should have a pass condition and a stop condition. A pass condition might be that every material financial claim has a source and reviewer. A stop condition might be that ownership authority is unresolved, a material contract is missing, a buyer requests unapproved disclosure, or a model output cannot be reconciled to the source records. Record the decision, owner, date, and follow-up. This creates a usable audit trail without promising that the process eliminates uncertainty.
Re-scope when facts change. A mandate that begins as a focused preparation engagement may become intensive after a quality-of-earnings issue, a buyer's financing condition, or a cross-border diligence request. Conversely, a workstream can be retired when it no longer informs a decision. The goal is not maximum activity. It is proportionate, reviewable work.
Turn the scope into an engagement decision
Before presenting the engagement, summarize the proposed workstreams in a matrix with five fields: objective, deliverable, owner, review gate, and exclusion. Add a complexity rationale for each intensive item. This makes the discussion concrete and lets the owner understand what is included without confusing a process description with a guaranteed result.
A sensible decision rule is to keep standards fixed and capacity variable. Keep source checking, confidentiality, conflict review, human approval, and escalation requirements fixed. Vary the number of iterations, depth of analysis, specialist involvement, buyer segmentation, data-room structure, and senior review frequency according to the mandate's facts. Revisit the rule at each stage rather than assuming the original scope remains correct.
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. It is user-operated software, so the bank remains responsible for setting permissions, checking source records, applying its professional procedures, and making human decisions.
Key Points
- Treat $5M and $100M as starting labels, not automatic scopes. Complexity, evidence quality, buyer process, and coordination risk should drive the workplan.
- Keep source checking, confidentiality, conflict review, documented approvals, and human accountability constant even when a smaller mandate uses fewer iterations.
- Give every workstream an objective, owner, source-of-truth record, deliverable, review gate, and explicit exclusion.
- Use AI only for bounded, testable production tasks with approved inputs, a named banker reviewer, pilot stopping criteria, and no autonomous outreach, negotiation, or approval.
- Re-scope when diligence, financing, ownership, regulatory, or confidentiality facts change. Proportionate work is not the same as minimal work.
Sources and references
Source retrieval dates record research access, not article publication. Read our editorial and date policy.
Choose your next step
Acquivo is user-operated software. Owners and their professionals remain responsible for decisions, communications, and professional review.
Educational information, not individual legal, tax, or investment advice. Consult qualified professionals for your circumstances. Acquivo provides software, not representation or negotiation on your behalf.