← M&A Integration Suite Contracting Model · Artifact 8 · how to read this suite

Consulting SOW & Engagement Model

Download Word

This document establishes the contracting model for the entire integration program. It contains the engagement statement of work under which Arrington Advisory Group provides program management to ACME Health, and it defines the three tiers of contracting paper through which every non-employee resource on the program is engaged — consulting, technology vendors, and staff augmentation. It also sets the rules for a problem specific to transactions: paper signed before closing binds an entity that will not exist in the same form afterward. Executed February 20, 2023.

Note the date. This document precedes the Integration Charter by one week. That sequence is deliberate and is how consulting engagements actually begin: the acquirer engages a program manager, and the program manager's first substantive deliverable is the Charter that the Steering Committee then approves on February 27. A Charter cannot appoint the person who wrote it. The engagement SOW is what authorizes him to write it.

Table of Contents

Part I — The Engagement
  1. Parties, Term and Instrument
  2. Scope of Services and Deliverables
  3. Acceptance, Fees and Invoicing
  4. Independence, Conflicts and the Clean Team Boundary
Part II — The Program Contracting Model
  1. Three Tiers of Contracting Paper
  2. Deliverable SOW versus Staff Augmentation
  3. Rate Card and Vehicle Selection
  4. Co-Employment Guardrails
Part III — The Transaction Problem
  1. Contracting Across the Close
  2. Register of Program Contracting Instruments
  3. Execution
Part I — The Engagement

1. Parties, Term and Instrument

AttributeProvision
ClientACME Health
SupplierArrington Advisory Group
InstrumentStatement of Work No. ARR-2023-01, issued under the Master Services Agreement between the parties dated April 2021
VehicleDeliverable statement of work — fees tied to accepted deliverables, not to hours worked
Engagement leadC. Tyrrell, Program Manager, Integration
Client relationship ownerD. Ashmore, EVP & CFO, ACME Health
EffectiveFebruary 20, 2023
TermThrough exit of the final Transition Services Agreement and formal program close. Extension by written amendment only.
Not-to-exceedSet per phase; the pre-close phase authorization does not carry into the post-close phase without amendment
Phased authorization rather than a single not-to-exceed for the whole engagement. At signing, nobody could state with confidence what the post-close program required, because the Clean Team Protocol barred the analysis that would answer the question. Committing a single figure across a four-phase engagement would have meant either over-committing the client or under-scoping the supplier. Phase authorization puts the re-estimate on the calendar instead of leaving it to a difficult conversation later.

2. Scope of Services and Deliverables

Arrington provides program management, and specialist capability in the three areas where ACME's internal bench is thinnest — identity resolution, integration architecture, and cloud platform engineering. Seventeen Arrington personnel are engaged across the program: thirteen onshore and four offshore.

Service areaArrington rolePrincipal deliverables
Program managementProgram Manager; PMO AnalystIntegration Charter, Integration Management Plan, WBS and schedule, RAIDD log, status and steering reporting, change control administration, closeout
Change and communicationsChange & Communications LeadCommunications Plan, Change & Culture Plan, Day 1 and Day 100 communications
Identity resolutionPrincipal Consultant; Senior Data Engineer; Data Quality AnalystData Migration & EMPI Strategy, match rules and survivorship specification, data profiling, steward SOPs
Integration architectureIntegration Architect; Senior EngineerIntegration Architecture & Interface Plan, canonical model, interface build and cutover
Cloud platformCloud Architect; Senior Cloud Engineer; FinOps AnalystCloud Migration Strategy, landing zone design, wave plan, FinOps foundation
Core administration migrationPrincipal ConsultantPlatform consolidation approach, migration and decommissioning plan
ContractsContracts ConsultantChange-of-control sweep, Vendor & Contract Disposition Matrix, consent and novation packages
Test execution (offshore)Offshore Delivery Manager; Test Lead; two QA EngineersInterface regression suite, execution and defect reporting

2.1 Explicitly excluded from this engagement

3. Acceptance, Fees and Invoicing

3.1 The acceptance mechanism

Each deliverable in Section 2 carries a named ACME acceptor, a defined acceptance period, and written acceptance criteria agreed before work begins. Deliverables are invoiced on acceptance. Where a deliverable is rejected, the rejection must state which criterion is unmet; Arrington remediates at its own cost and resubmits.

Acceptance criteria written before the work starts is the whole mechanism. A deliverable SOW without them collapses into time and materials with extra paperwork, because the parties end up negotiating what "complete" means while looking at the invoice. The named-acceptor requirement matters equally: a deliverable everyone reviews is a deliverable nobody accepts.

3.2 Fee structure

ComponentBasis
Deliverable feesFixed fee per accepted deliverable, priced from the rate card in Section 7 against an agreed effort estimate. Overrun against the estimate is Arrington's risk.
Ongoing program managementMonthly fixed fee for the duration of each authorized phase, covering the standing program management function that is not deliverable-shaped
ExpensesReimbursed at cost against ACME's travel policy. No markup. Pre-approval required above a per-trip threshold.
Rate escalationFixed for the first twelve months; thereafter by written amendment only
InvoicingMonthly in arrears. Deliverable fees invoiced in the month of written acceptance.

3.3 Termination

4. Independence, Conflicts and the Clean Team Boundary

4.1 Conflict representation

Arrington represents that it holds no engagement with Cumberland Valley Health Plan, no engagement with a competing bidder, and no financial interest in the transaction outcome. Arrington's fees are not contingent on closing, on synergy attainment, or on any transaction metric.

Contingent fees were considered and rejected, and the reasoning is worth stating. Tying the program manager's compensation to synergy capture appears to align incentives. In practice it corrupts exactly the judgments the role exists to make: whether to recommend a TSA extension, whether to report a synergy shortfall early, whether to tell the Sponsor that a target is no longer achievable. A program manager paid on the number is the wrong person to ask whether the number is real.

4.2 Why Arrington is not the Clean Team

Arrington personnel are integration advisors with broad access to ACME's planning. That access is incompatible with the information barrier. The Clean Team is therefore engaged separately from Harpeth Clean Team Services, which has no other role in the transaction, and no Arrington personnel hold Clean Team credentials or receive restricted-category information in any form other than issued Release Memoranda.

Part II — The Program Contracting Model

5. Three Tiers of Contracting Paper

Twenty-eight of the seventy-three people on this program are not employees of either party. They reach the program through three distinct kinds of paper, and the distinction is not administrative — it determines who owns the outcome when the work goes wrong.

TierInstrumentPeopleWho owns the outcome
Tier 1Consulting engagement SOW — Arrington Advisory Group17Supplier for named deliverables; ACME for all decisions
Tier 2Technology and specialist vendor SOWs — fixed price7Vendor, against a defined result
Tier 3Staffing firm SOWs under MSA — time and materials4ACME — the firm supplies capacity, not outcomes

5.1 Tier 2 — technology and specialist vendors

VendorInstrumentScope and why fixed price
Harpeth Clean Team ServicesFixed-price SOW, pre-closeA defined analytical service with a defined end date. Fixed price is right because the scope is bounded by law and the engagement dissolves at closing.
Gallatin EDI AssuranceFixed-price SOW, post-closeX12 transaction assurance across 834 enrollment, 837 claims, 835 remittance, 270/271 eligibility and 820 premium. A specialist result ACME cannot produce internally.
Microsoft AzureEnterprise agreement plus BAAConsumption-based platform, not a services engagement. Contracted by IT under the program's cloud strategy; requires an executed Business Associate Agreement before any protected health information reaches the platform.
Rutherford Cloud OperationsManaged service agreement, co-managed model⭐ Operations of the Azure estate during and after migration, on a contracted step-down from vendor-operated to ACME-operated. Requires a BAA, a three-party responsibility matrix as an exhibit, and transition-out terms — the exit is designed at signature, not discovered at renewal.
EDI assurance is contracted to a specialist rather than absorbed into general QA, and that is a defensible spend. X12 transaction testing is not generic quality assurance. A firm that tests 834 enrollment files for a living knows the failure modes — segment-level rejections, trading partner variation, the difference between a file that passes validation and a file the receiving system will actually load. Buying that as a fixed-price result costs less than building it and carries the risk on the vendor's side of the line.

5.2 Tier 3 — staff augmentation

Two Rivers Talent Partners supplies four data stewards under time-and-materials SOWs issued against a master services agreement. This is the one population on the program where ACME rents hours rather than buying a result, and Section 6 explains why that is the correct choice here and Section 8 explains what it obliges ACME to do.

6. Deliverable SOW versus Staff Augmentation

This is the distinction the whole contracting model turns on. Under a deliverable or fixed-price SOW, the supplier owns the outcome: ACME defines what "done" looks like, the supplier decides how to get there, and overrun is the supplier's problem. Under staff augmentation, ACME owns the outcome: it rents qualified hours, directs the work itself, and overrun is ACME's problem. Neither is better. Choosing the wrong one for the work is what causes trouble.
DimensionDeliverable / fixed-price SOWStaff augmentation (T&M)
What is boughtA defined resultQualified capacity
Who directs the workSupplierACME
Who carries overrunSupplierACME
Payment triggerWritten acceptance of a deliverableHours worked, approved on a timesheet
Right fit whenScope is definable in advance and the result is separable from ACME's own workScope is continuous, volume-driven or unpredictable, and the work is inseparable from internal operations
Failure modeEndless change orders when acceptance criteria were vagueCost drifts with no deliverable to point at; co-employment exposure

6.1 Why the data stewards are staff augmentation and not a fixed-price service

Clerical review of identity matches is continuous, volume-driven queue work whose size cannot be known until profiling is complete. It also requires the reviewers to work inside ACME's systems, against ACME's data governance rules, under an ACME supervisor's quality standards. Fixed-pricing that means pricing an unknown volume of an activity ACME must control — which produces either a padded price or a vendor incentivized to close the queue rather than to close it correctly.

And here the healthcare asymmetry decides it. A steward who wrongly rejects a match leaves a duplicate record — annoying, and fixable later. A steward who wrongly confirms a match merges two people: one member's protected health information becomes visible under another's record, claims pay against the wrong history, and a clinician may read the wrong chart. Those two errors are not symmetrical, so throughput must never be the thing the contract rewards. Staff augmentation lets ACME set the quality standard and own the consequence. A fixed-price queue-clearing contract would pay a vendor to be fast.

7. Rate Card and Vehicle Selection

7.1 Rate card

Rates below are the blended basis on which deliverable fees are priced and against which time-and-materials hours are billed. They are inclusive of benefits, overhead and supplier margin.

CategoryRate / hourApplies to
Engagement lead / Program Manager$265Tier 1
Principal consultant$245Tier 1 — identity resolution, core admin migration
Architect — integration, cloud$230Tier 1
Senior engineer / senior analyst$195Tier 1
Analyst — PMO, data quality, FinOps$155Tier 1
Offshore delivery manager$95Tier 1 offshore
Offshore test lead$80Tier 1 offshore
Offshore QA engineer$65Tier 1 offshore
Specialist EDI analystFixed priceTier 2 — priced as a result, not an hour
Data steward$68Tier 3
Data steward supervisor$92Tier 3

7.2 The offshore boundary

Offshore personnel work interface regression testing against de-identified and synthetic datasets. No member-level data leaves the United States, per Tennessee Department of Commerce and Insurance conditions and ACME privacy policy. This constraint is inherited, not negotiated, and it is the reason the offshore population is concentrated in interface testing rather than distributed across the program: interface testing is the substantial body of work that can be performed correctly without ever touching a real member record.

7.3 Vehicle selection rule

If the work is…Then contract it as…
A definable result, separable from ACME operations, with agreeable acceptance criteriaDeliverable or fixed-price SOW
A specialist capability ACME does not have and does not intend to buildFixed-price SOW — buy the result
Continuous, volume-driven, or inseparable from internal operations and governanceStaff augmentation — and accept that ACME owns the outcome
Permanent capability the combined entity will need after the program endsNeither — hire

8. Co-Employment Guardrails

Staff augmentation personnel are employees of the staffing firm. Treating them as ACME employees creates worker-classification and co-employment exposure — a risk that lands on HR and Legal, and one a program manager should raise before Procurement discovers it.

ProhibitedRequired instead
Placing contractors on the ACME organization chartShown on the Resource Plan with contract vehicle and supplier named
Assigning ACME job titles or business cardsSupplier titles retained; access badges identify contractor status
Including contractors in employee performance review cyclesPerformance feedback routed through the supplier's engagement manager
Direct participation in employee benefits, bonus or equity programsCompensation is entirely the supplier's concern
Open-ended engagement with no defined endEach SOW carries a term and an end date; extension is a decision, not a default
ACME managers approving contractor time off or setting personal work schedulesSupplier manages its own personnel; ACME specifies coverage requirements
The tension is real and worth naming rather than glossing. Staff augmentation exists precisely because ACME needs to direct the work — that is the whole point of choosing the vehicle. The line is between directing the work and managing the person. The Program Manager may tell a data steward which queue to work and what quality standard applies. He may not conduct their performance review, approve their vacation, or put them in the ACME org chart. The Resource Plan records the vehicle for every named individual so that the line is visible rather than remembered.
Part III — The Transaction Problem

9. Contracting Across the Close

Every instrument in this program is signed either side of a moment when one of the parties ceases to exist. Cumberland Valley Health Plan merges into ACME Health at closing. Paper signed before that date binds an entity whose legal form is about to change, and paper that names the wrong party may require consent, assignment or novation before it works on Day 1. This is not a technicality — a critical service under a contract nobody transferred is a Day 1 outage.

9.1 Who is the contracting party

InstrumentContracting partyRationale
Arrington engagement SOW (this document)ACME HealthACME is the surviving entity and the buyer of the service. No transfer required at closing.
Harpeth Clean Team SOWACME Health, with Cumberland Valley counsel as a named beneficiaryThe service protects both parties; the engagement ends at closing so no transfer arises.
Gallatin EDI Assurance SOWACME HealthSigned post-close. No transaction complication.
Two Rivers staffing SOWsACME HealthSigned post-close, because the work cannot lawfully begin before it.
Azure enterprise agreement and BAAACME HealthPre-existing ACME relationship, expanded. The BAA must be confirmed to cover the enlarged member population.
Cumberland Valley's inherited contractsDetermined case by caseThe material problem. Addressed in the Vendor & Contract Disposition Matrix, not here.

9.2 The rule this program applied

Where a program instrument could be signed by ACME alone, it was — because ACME survives the transaction and a contract with the surviving entity needs no action at closing. Where the work could not lawfully begin until after closing, the paper was dated after closing rather than signed early in anticipation. Both choices trade a little speed for the elimination of a novation requirement.

The distinction between assignment and novation is the one to have straight. Assignment transfers the benefit of a contract; the original party remains liable for the obligations. Novation replaces one party with another entirely, extinguishing the original party's obligations — and because it changes who the counterparty must look to for performance, it requires the counterparty's consent. That consent is a negotiating opportunity for a vendor who knows an acquisition is underway, which is why the change-of-control sweep starts months before it is needed.

9.3 What this program deliberately did not do

10. Register of Program Contracting Instruments

RefInstrumentTierVehiclePeopleStatus at Day 1
ARR-2023-01Arrington Advisory Group — integration program management1Deliverable SOW17Active
HAR-2023-01Harpeth Clean Team Services — pre-close clean team2Fixed price4Dissolved at close
GAL-2023-01Gallatin EDI Assurance — X12 transaction assurance2Fixed price3Active
TWO-2023-01Two Rivers Talent Partners — data stewardship capacity3Staff aug (T&M)4Active
MSFT-EAMicrosoft Azure enterprise agreement and BAA2ConsumptionBAA scope confirmation required
The Azure row is amber for a reason that generalizes. ACME held an existing enterprise agreement and an executed Business Associate Agreement, so the platform relationship looked settled. But a BAA is scoped to the protected health information it covers, and the combined entity's member population is materially larger than the one contemplated when the original was executed. Confirming that scope is a Day 1 gate condition. An inherited agreement that exists is not the same as an inherited agreement that covers what you are about to do with it.

11. Execution

This statement of work is not effective until executed by an authorized signatory of both parties and endorsed by ACME Legal. ⚠ Work performed before execution is performed at Supplier's risk and is not payable.

For ACME Health
D. Ashmore
EVP & Chief Financial Officer · Executive Sponsor, accountable for the engagement
Date: _______________
For Arrington Advisory Group
G. Hollowell
Managing Principal · authorized signatory
Date: _______________
Procurement approval
H. Castellow
VP Procurement, ACME Health
Date: _______________
The Program Manager's name does not appear on this page, and on this instrument in particular that is worth stating plainly. C. Tyrrell is the engagement lead named in §1 and the person accountable for delivering everything in §2 — and he can sign neither side of it. He cannot bind Arrington, because that authority sits with the firm's Managing Principal; and he obviously cannot sign for ACME, because he is the supplier. Signature authority follows accountability for the commitment, not accountability for the work — and an engagement where the person doing the work also signs for the buyer has no independent check on scope or price at all.
Four signatures, each a different check, and the legal one is the check the others cannot perform. The Sponsor confirms the work is wanted and funded. The supplier's officer binds the firm. Procurement confirms the commercial terms match the framework agreement. Legal confirms that the clauses which only matter later — liability, data handling, termination, transition assistance and the warranty obligations — are actually present rather than assumed. ⚠ It is the signature most often skipped under schedule pressure, and the only one that reads the parts of a document nobody expects to need.

Related artifacts: 1 — Integration Charter (§8.2, delegated authority) · 5 — Clean Team Protocol · 14 — Resource Plan · 21 — Vendor & Contract Disposition Matrix · 33 — Data Steward SOPs & SLA