Assess whether environmental liability is capped or open-ended (0bed4f)

Situation

A PE platform evaluating a founder-led SaaS add-on cannot treat a customer who just sent a non-renewal as color commentary on environmental known-condition schedule. Integration-risk PMO must close environmental liability is capped from that extract under M&A Due Diligence / People and Contracts.

Decision

Integration-risk PMO in a PE platform evaluating a founder-led SaaS add-on must choose Environmental liability is capped / Open-ended using environmental known-condition schedule after a customer who just sent a non-renewal.

Hypotheses to test

• Integration-risk PMO can defend Environmental liability is capped from environmental known-condition schedule after a customer who just sent a non-renewal in a M&A Due Diligence challenge.
• Integration-risk PMO cannot defend Environmental liability is capped from environmental known-condition schedule; Open-ended is what the extract actually supports after a customer who just sent a non-renewal.
• A customer who just sent a non-renewal never reached the population in environmental known-condition schedule — reopen intake, do not close environmental liability is capped.
• Two facts in environmental known-condition schedule after a customer who just sent a non-renewal conflict for integration-risk PMO; hold this People and Contracts file.

Analysis required

• Name the document integration-risk PMO still needs before signing.
• Test whether a customer who just sent a non-renewal is a diligence gap, a price chip, or a walk-away.
• Separate a one-off add-back from a recurring earnings issue in environmental known-condition schedule.
• For this M&A Due Diligence People and Contracts file, read environmental known-condition schedule against a customer who just sent a non-renewal and write the one fact that would move environmental liability is capped for integration-risk PMO.

Recommendation

Choose Environmental liability is capped / Open-ended on this M&A Due Diligence / People and Contracts packet (environmental known-condition schedule after a customer who just sent a non-renewal). The follow-on People and Contracts action is what integration-risk PMO does next: implement the option, assign an owner, and log the missing fact.