Reported operating use · Investment banking and M&A advisory

AI M&A deal sourcing diligence: OffDeal example

OffDeal's engineering account says it consolidated more than twelve agentic workflows into Archie, built on Anthropic's Claude Agent SDK, for buyer sourcing, deal coordination, diligence and banker materials. It tests against frozen production-data slices and describes missed tasks and plausible but incorrect financial answers.

Buyer sourcing, deal coordination, diligence and banker materials

OffDeal

Production internal banking workflows; daily production-data benchmarking reported by its co-founder/CTO.

A published third-party example, not a Nuvepro customer case or evidence of a partnership.

The workflow at a glance

OffDeal reported work

Illustrative summary of the published account

Reported work components. Their arrangement does not imply a fixed execution order or simultaneous work.

  • Internal agent

    Archie deal workflows

    Buyer research, deal coordination, diligence and banker materials.

  • Evaluation substrate

    Frozen relational deal slices

    Isolated PostgreSQL schemas, MCP and callback routing support repeated tests.

  • Reported failures

    Missed tasks and wrong financial answers

    Plausible responses can omit follow-ups or misinterpret deal evidence.

Production internal banking workflows; daily production-data benchmarking reported by its co-founder/CTO. No independent outcome audit or demonstrated equivalence of generic scenarios to production-derived deal slices. Different published evaluation vintages should not be combined into a single score series. See the source account and limitations below.

What the source reports

OffDeal consolidated more than twelve agentic workflows into Archie. Its engineering account documents frozen production-data slices, isolated PostgreSQL schemas, in-process MCP and webhook routing for repeatable testing. It describes missed tasks and plausible but incorrect financial answers. The account explicitly says manually specifying sufficient deal context was impractical. This is implemented business work and evaluation, not a proposed demonstration.

Reported technology: Anthropic Claude Agent SDK and Claude Platform; other models also used. Scope and outcomes are source-reported.

What the enterprise environment would need

The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.

Proposed practice environment

Prepare a traceable deal review package

Illustrative project design to scope with your enterprise.

  1. 1 · Set up the environment

    Linked deal records

    Fictional mandates, buyer history and financial evidence preserve cross-record relationships.

  2. 2 · Preparation and agent contributions

    Prepare banker materials

    Research buyers, document valuation assumptions and draft requested deal tasks.

  3. 3 · Independent checks

    Reconcile valuations and tasks

    Independent reference calculations and banker-defined expected follow-ups expose omissions.

  4. 4 · People decide acceptance

    Banker accepts bounded evidence

    Review ambiguity, confidentiality and changed mandates before accepting the practice version.

Only within the accepted practice scope
Practice output

A reviewable evidence package

A valuation evidence pack, buyer findings and complete draft task register.

If a check fails → withhold acceptance.

A changed mandate or missing related record undermines valuation or follow-up. Withhold acceptance, repair, independently recheck and return to owner review.

Failure or owner rejection returns to review

  1. Hold
  2. → 2 · Revise work
  3. → 3 · Rerun independent checks
  4. → 4 · Owner review

Operating boundary. Isolated deal workspace; no investor outreach, deal commitment or live task changes.

Proposed, not an executed Nuvepro project or a description of the named company’s implementation. Owners agree the data, rules, responsibilities and acceptance criteria for their enterprise.
Systems and tools
Published: PostgreSQL, BigQuery, GCS, Docker, MCP and external callbacks. Proposed: compose approved existing services.
Data and state
Published: OffDeal describes relationally complete production slices. Proposed: use approved extraction and de-identification while preserving relationships between deal records. If using synthetic cases, check that they retain the relationships needed for the tasks being evaluated.
People and handoffs
Proposed: bankers review ambiguous deal interpretation and incomplete task creation; assess agent and banker contributions separately.
Rules and authority
Proposed: encode confidentiality and approval boundaries without fixing the reasoning sequence.
Normal and exception cases
Published failures include omitted follow-up tasks and wrong valuation. Proposed: add cross-deal identity confusion and ambiguous instructions.
Reset and replay
Published: frozen SQL restored into per-test schemas, then teardown. Proposed: version external-provider responses separately from database state.

A proposed simulation

An illustrative practice design derived from this work, not an executed assessment.

Take a new seller mandate through buyer research, valuation questions, deal tasks and banker handoff. Change the mandate midway and introduce incomplete financial evidence.

Review gate: Reconcile valuation inputs, supported conclusions and every requested follow-up against banker-qualified outcomes; check confidentiality and missing-evidence escalation.

Challenge the result: Withhold a related deal record or change a mandate. If the assessment still rewards a confident but unsupported valuation or omitted follow-up, its readiness result is invalid.

What needs checking

  • Published: comparisons, precision/recall and model judgments with concrete failure inspection.
  • Proposed: banker-qualified expected outcomes and separate checks for every requested downstream task.
  • Published: production-derived relational context rather than hand-authored context.
  • Proposed: compare staging tool effects and human handoffs with live operating traces.

Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.

Questions about this example

What does OffDeal use AI for in M&A advisory?
OffDeal uses Archie, built with the Claude Agent SDK and Claude Platform, across buyer sourcing, deal coordination, diligence and banker materials. It consolidated more than twelve agentic workflows into one agent, and other models are also used.
How does OffDeal check the agent's financial answers?
OffDeal's account describes comparisons, precision and recall, and model judgments with concrete failure inspection. Published failures include omitted follow-up tasks and wrong valuation. A proposed check, not from the source, would have bankers review ambiguous deal interpretation and incomplete task creation.
How strong is the evidence for this OffDeal example?
The evidence class is reported use: production internal banking workflows, with daily production-data benchmarking reported by its co-founder and CTO. There is no independent outcome audit, and different published evaluation vintages should not be combined into a single score series.
What would an enterprise need to build something similar?
This is Nuvepro's proposed design, not OffDeal's system. It would use approved extraction and de-identification that preserves relationships between deal records, banker-qualified expected outcomes, versioned provider responses and a mid-task mandate change, so a confident but unsupported valuation fails the assessment.

Shape this around your enterprise

Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.

Sources and limitations

Curation review: . This is the date this source example was reviewed, separate from source publication dates.

  • No independent outcome audit or demonstrated equivalence of generic scenarios to production-derived deal slices. Different published evaluation vintages should not be combined into a single score series.
  1. OffDeal powers every stage of M&A advisory with one Claude-based agent
  2. How Do You Grade an AI Investment Banker?Source publication: 2026-02-17

More banking and insurance examples

All 10 banking and insurance examples

Explore more enterprise work