PlaygroundM&A

Meridian Partners

Fictional companyM&A

A mid-market acquirer running screening, diligence, valuation, and integration planning on a repeatable deal process.

Modeled on

  • ASC 805 / IFRS 3: Business combinations — purchase price allocation, goodwill, identifiable intangibles.
  • Quality of Earnings: Adjusted EBITDA, add-backs, run-rate adjustments, working-capital peg.
  • Standard diligence workstreams: Financial, legal, commercial, technical, people, tax, environmental.

The genome map

Roles in their reporting line, the process step by step with the role on each step, the rules on the steps they govern, and the resources the work acts on. Select a role to see what it reaches.

Roles Select a role to see its reach.

Deal Execution Operated by Managing Partner

Screening through close — the operating model that produces a defensible valuation.

  1. 1 Screen target Deal LeadTarget.Screen
  2. 2 Open diligence Diligence LeadDiligenceRequest.List
  3. 3 Resolve requests Diligence LeadDiligenceRequest.Resolve
  4. 4 Validate synergies Financial AnalystSynergyCase.Validate
    • Synergies validated by both sides
  5. 5 Build valuation Financial AnalystValuationModel.Build
    • Valuation requires closed register
    • Analysts own the model
  6. 6 Committee approval Managing PartnerTarget.Approve
    • Committee approves targets
  7. 7 Draft integration plan Integration LeadIntegrationPlan.Draft

Resources

  • Target
  • Diligence Request
  • Valuation Model
  • Synergy Case
  • Integration Plan

Three questions this genome answers

Each answer comes from the compiled genome alone. Pick another subject and the answer changes in place.

Financial Analyst, Integration Lead may perform SynergyCase.Validate. The rule: Synergies validated by both sides.

These steps wait for Diligence Lead:

  • Open diligence Deal Execution
  • Resolve requests Deal Execution

Diligence Lead act on Diligence Request, by a process step or under an access rule.

Every artifact from one genome

The same derivations and renderers the Playground runs, here for Meridian Partners at build time. Open it in the Playground to pick your own set.

Operations

How the work actually runs — who owns what, in what order, under which rules.

Process flow

The end-to-end sequence, each step with its owner.

Screening through close — the operating model that produces a defensible valuation.

  1. 1
    Screen target
    Test the target against the thesis before any diligence hours are committed.
    Deal LeadTarget.Screen
  2. 2
    Open diligence
    Stand up the request register across financial, legal, commercial, technical, and people.
    Diligence LeadDiligenceRequest.List
  3. 3
    Resolve requests
    Work the register to closed, flagging anything that changes the thesis.
    Diligence LeadDiligenceRequest.Resolve
  4. 4
    Validate synergies
    Test each claimed synergy against diligence evidence and mark its confidence.
    Financial AnalystSynergyCase.Validate
  5. 5
    Build valuation
    Assemble base, upside, and downside cases from the resolved register.
    Financial AnalystValuationModel.Build
  6. 6
    Committee approval
    Investment committee decides go, no-go, or revised terms.
    Managing PartnerTarget.Approve
  7. 7
    Draft integration plan
    Turn the approved operating model into the first hundred days.
    Integration LeadIntegrationPlan.Draft

Owned end to end by Managing Partner.

SOP / runbook

The same process as a numbered operating procedure.

PurposeScreening through close — the operating model that produces a defensible valuation.
OwnerManaging Partner
TriggerA target enters the pipeline.
  1. 1. Screen target
    Test the target against the thesis before any diligence hours are committed.
    Performed by Deal Lead
  2. 2. Open diligence
    Stand up the request register across financial, legal, commercial, technical, and people.
    Performed by Diligence Lead
  3. 3. Resolve requests
    Work the register to closed, flagging anything that changes the thesis.
    Performed by Diligence Lead
  4. 4. Validate synergies
    Test each claimed synergy against diligence evidence and mark its confidence.
    Performed by Financial Analyst
  5. 5. Build valuation
    Assemble base, upside, and downside cases from the resolved register.
    Performed by Financial Analyst
  6. 6. Committee approval
    Investment committee decides go, no-go, or revised terms.
    Performed by Managing Partner
  7. 7. Draft integration plan
    Turn the approved operating model into the first hundred days.
    Performed by Integration Lead

Key positions

The roles this operation needs and who reports to whom.

Investment Committee

  • Managing Partner
    Chairs the investment committee and owns the final go/no-go.
    Committee approval
    • Deal Lead
      Runs one deal end to end and owns the recommendation.
      Screen target
      • Diligence Lead
        Coordinates the workstreams and owns the request register.
        Open diligenceResolve requests
      • Financial Analyst
        Builds the valuation model and tests the synergy cases.
        Validate synergiesBuild valuation
    • Integration Lead
      Owns the first hundred days and inherits the operating model at close.
      Draft integration plan

Each chip is a step of the process that role owns.

RACI matrix

Every step against every role — responsible, accountable, consulted.

StepManaging PartnerDeal LeadDiligence LeadFinancial AnalystIntegration Lead
Screen targetAR
Open diligenceACR
Resolve requestsARC
Validate synergiesARC
Build valuationACR
Committee approvalRCC
Draft integration planAR

R responsible · A accountable · C consulted — derived from step owners, the process operator, and access rules.

Policies & rules

The constraints that govern each operation, stated as rules.

  • Valuation requires closed register condition

    No valuation is built while financial or legal requests are still open.

    ValuationModel.Build
  • Committee approves targets access

    Approval to proceed is the committee’s alone — a deal lead cannot approve their own deal.

    Target.Approve Managing Partner
  • Analysts own the model access

    The model is built by the analyst who can defend it, not by the person selling the deal.

    ValuationModel.Build Financial AnalystManaging Partner
  • Synergies validated by both sides access

    A synergy counts once the analyst and the person who has to deliver it both sign it.

    SynergyCase.Validate Financial AnalystIntegration Lead

Product

What gets built on top of it — the data, the screens, the API.

Data model

The entities, their fields, and how they relate.

Target ScreenApprove

A company under evaluation, from first screen through close or pass.

  • legalName string required
  • sector string required
  • revenue number
  • stage enum required screening · diligence · negotiation · closed · passed
Diligence Request Resolve

One information request against a target, with its owner and status.

  • workstream enum required financial · legal · commercial · technical · people
  • question text required
  • status enum required open · answered · flagged
Valuation Model Build

The financial model behind an offer — base, upside, and downside cases.

  • method enum required dcf · comparables · precedent · lbo
  • enterpriseValue number required
  • impliedMultiple number
  • adjustedEbitda number
  • workingCapitalPeg number
  • netDebt number
  • preparedOn date
Synergy Case Validate

A named cost or revenue synergy with an owner and a confidence level.

  • category enum required cost · revenue · capital
  • annualValue number required
  • confidence enum required high · medium · low
Integration Plan Draft

The first-hundred-days plan for a target that clears committee.

  • owner string required
  • startDate date
  • workstreamCount number

Screen map

Every route and the page it resolves to.

Shell: DealRoom

/pipeline
Pipeline 🔒
Deal pipeline.
Target tablesummary
/targets/:id
Target Detail 🔒
Single target.
Target formactions
/diligence
Diligence Register 🔒
Request register.
Diligence Request table
/valuation/:id
Valuation Workbench 🔒
Valuation cases.
Valuation Model actions

Example UI

A working admin table and detail form, built from the fields.

Pipeline ScreenApprove
TargetSectorStageRevenue ($M)Deal lead
Halcyon FabricationIndustrialsdiligence84.2R. Ibarra
Northwind LogisticsTransportnegotiation143S. Adeyemi
Copperline FoodsConsumerscreening31.5R. Ibarra
Vantage DentalHealthcarepassed22.8T. Brennan
Target detail

API surface

The endpoints, grouped by namespace, with their operations.

Deals/api/deals

Pipeline, diligence, and valuation operations.

  • GET /api/deals/targets Target.List Pipeline by stage.
  • GET /api/deals/targets/{id} Target.Read One target in full.
  • POST /api/deals/targets/{id}/approve Target.Approve Record a committee decision.
  • GET /api/deals/requests DiligenceRequest.List The register, by workstream.
  • POST /api/deals/requests/{id}/resolve DiligenceRequest.Resolve Close a request.
  • GET /api/deals/valuations/{id} ValuationModel.Read A model and its cases.
  • POST /api/deals/valuations ValuationModel.Build Build a model.

Technology

Where it runs and who can reach it.

Architecture diagram

The cells this runs on and what talks to what.

DealRoomWeb
nextjs 15
The partner-facing deal room.
MeridianPartners.Product.Web
PipelineService
nestjs 10
Targets, stages, and committee decisions.
MeridianPartners.Product.Api
DiligenceService
nestjs 10
The request register and its workstreams.
MeridianPartners.Product.Api
ValuationEngine
express 4
Runs the model cases off resolved diligence.
MeridianPartners.Operational
DealDb
postgres 16
Targets, requests, models, synergies.
MeridianPartners.Product.Core
  • DealRoomWeb → PipelineService pipeline
  • DealRoomWeb → DiligenceService register
  • ValuationEngine → DiligenceService resolved requests
  • PipelineService → ValuationEngine target.approved
  • PipelineService → DealDb depends-on
  • DiligenceService → DealDb depends-on

Environment topology

Dev, staging, and production, with the providers behind each.

dev
Analyst sandboxes with synthetic targets.
Providers
AzurecloudSnowflakedatabase
Cells
none
staging
Committee rehearsal environment.
Providers
AzurecloudSnowflakedatabaseEntraIdauth
Cells
none
prod
Live deals.
Providers
AzurecloudSnowflakedatabaseEntraIdauthDatasitestorage
Cells
DealRoomWebPipelineServiceDiligenceServiceValuationEngineDealDb

Access-control matrix

Which role may perform which operation, derived not declared.

OperationManaging PartnerDeal LeadDiligence LeadFinancial AnalystIntegration Lead
Target.ApproveCommittee approves targets✓
ValuationModel.BuildAnalysts own the model✓✓
SynergyCase.ValidateSynergies validated by both sides✓✓
No access rule governs
Target.ScreenTarget.ListTarget.ReadDiligenceRequest.ResolveDiligenceRequest.ListValuationModel.ReadIntegrationPlan.Draft

Derived, not declared — this is the list an audit asks about.

Make yours

Start from Meridian Partners and change what differs, or pick another company as your template. Three ways in:

  1. 1. Download the template

    The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.

    Download Meridian Partners as JSON
  2. 2. Start an agent from it

    Paste this into an agent that has the DNA MCP server connected. It drafts your model in the conversation and saves only when you ask.

    Use the DNA MCP server (https://agents.dna.codes) to help me model how my company works.
    Start from the Meridian Partners genome at https://dna.codes/genome/ma.json. It is an example company, not mine.
    Read its roles, process steps, rules and resources, then ask me how my company differs.
    Draft my company's operating model in this conversation, as structure/v1 and behaviour/v1 documents, and use `validate` on each draft.
    Do not save anything: call `apply` only when I ask you to save.
  3. 3. Join the waitlist

    The hosted product runs your model for your team and your agents.

Which of these sounds like you? Pick as many as apply.

The most useful box on this page. Rough is fine, and “nowhere, honestly” is a real answer and a common one.

We reply by hand, usually within a day. No sequence, no drip, no spam.