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 Screen target
- 2 Open diligence
- 3 Resolve requests
- 4 Validate synergies
- Synergies validated by both sides
- 5 Build valuation
- Valuation requires closed register
- Analysts own the model
- 6 Committee approval
- Committee approves targets
- 7 Draft integration plan
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.
- 1Screen targetTest the target against the thesis before any diligence hours are committed.
- 2Open diligenceStand up the request register across financial, legal, commercial, technical, and people.
- 3Resolve requestsWork the register to closed, flagging anything that changes the thesis.
- 4Validate synergiesTest each claimed synergy against diligence evidence and mark its confidence.
- 5Build valuationAssemble base, upside, and downside cases from the resolved register.
- 6Committee approvalInvestment committee decides go, no-go, or revised terms.
- 7Draft integration planTurn the approved operating model into the first hundred days.
Owned end to end by Managing Partner.
SOP / runbook
The same process as a numbered operating procedure.
- 1. Screen targetTest the target against the thesis before any diligence hours are committed.Performed by Deal Lead
- 2. Open diligenceStand up the request register across financial, legal, commercial, technical, and people.Performed by Diligence Lead
- 3. Resolve requestsWork the register to closed, flagging anything that changes the thesis.Performed by Diligence Lead
- 4. Validate synergiesTest each claimed synergy against diligence evidence and mark its confidence.Performed by Financial Analyst
- 5. Build valuationAssemble base, upside, and downside cases from the resolved register.Performed by Financial Analyst
- 6. Committee approvalInvestment committee decides go, no-go, or revised terms.Performed by Managing Partner
- 7. Draft integration planTurn 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 PartnerChairs the investment committee and owns the final go/no-go.Committee approval
- Deal LeadRuns one deal end to end and owns the recommendation.Screen target
- Diligence LeadCoordinates the workstreams and owns the request register.Open diligenceResolve requests
- Financial AnalystBuilds the valuation model and tests the synergy cases.Validate synergiesBuild valuation
- Integration LeadOwns 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.
| Step | Managing Partner | Deal Lead | Diligence Lead | Financial Analyst | Integration Lead |
|---|---|---|---|---|---|
| Screen target | A | R | |||
| Open diligence | A | C | R | ||
| Resolve requests | A | R | C | ||
| Validate synergies | A | R | C | ||
| Build valuation | A | C | R | ||
| Committee approval | R | C | C | ||
| Draft integration plan | A | R |
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.
- Committee approves targets access
Approval to proceed is the committee’s alone — a deal lead cannot approve their own deal.
- Analysts own the model access
The model is built by the analyst who can defend it, not by the person selling the deal.
- Synergies validated by both sides access
A synergy counts once the analyst and the person who has to deliver it both sign it.
Product
What gets built on top of it — the data, the screens, the API.
Data model
The entities, their fields, and how they relate.
ScreenApproveA 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
ResolveOne 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
BuildThe 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
ValidateA 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
DraftThe 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/targets/:id/diligence/valuation/:idExample UI
A working admin table and detail form, built from the fields.
| Target | Sector | Stage | Revenue ($M) | Deal lead |
|---|---|---|---|---|
| Halcyon Fabrication | Industrials | diligence | 84.2 | R. Ibarra |
| Northwind Logistics | Transport | negotiation | 143 | S. Adeyemi |
| Copperline Foods | Consumer | screening | 31.5 | R. Ibarra |
| Vantage Dental | Healthcare | passed | 22.8 | T. Brennan |
API surface
The endpoints, grouped by namespace, with their operations.
/api/dealsPipeline, diligence, and valuation operations.
- GET
/api/deals/targetsTarget.List Pipeline by stage. - GET
/api/deals/targets/{id}Target.Read One target in full. - POST
/api/deals/targets/{id}/approveTarget.Approve Record a committee decision. - GET
/api/deals/requestsDiligenceRequest.List The register, by workstream. - POST
/api/deals/requests/{id}/resolveDiligenceRequest.Resolve Close a request. - GET
/api/deals/valuations/{id}ValuationModel.Read A model and its cases. - POST
/api/deals/valuationsValuationModel.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.
MeridianPartners.Product.WebMeridianPartners.Product.ApiMeridianPartners.Product.ApiMeridianPartners.OperationalMeridianPartners.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.
Access-control matrix
Which role may perform which operation, derived not declared.
| Operation | Managing Partner | Deal Lead | Diligence Lead | Financial Analyst | Integration Lead |
|---|---|---|---|---|---|
Target.ApproveCommittee approves targets | ✓ | ||||
ValuationModel.BuildAnalysts own the model | ✓ | ✓ | |||
SynergyCase.ValidateSynergies validated by both sides | ✓ | ✓ |
Target.ScreenTarget.ListTarget.ReadDiligenceRequest.ResolveDiligenceRequest.ListValuationModel.ReadIntegrationPlan.DraftDerived, 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. Download the template
The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.
Download Meridian Partners as JSON2. 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. Join the waitlist
The hosted product runs your model for your team and your agents.