What Should a CFO Review in the First 100 Days After an Acquisition?

What should a CFO review immediately after an acquisition?

The first financial job after an acquisition is not to start cutting anything that looks duplicated. It is to establish what the combined business is paying for, who owns each recurring cost, what contractual deadlines are approaching, and what operational dependency must be resolved before a supplier, application, or service can actually be removed.

A useful post-acquisition cost review should answer five questions:

• •What are the two businesses paying for now?
• •Who owns each material recurring expense?
• •Which vendors, applications, and services overlap?
• •Which contracts create near-term decisions?
• •What must happen operationally before a cost can be eliminated or consolidated?

That distinction matters because an apparently duplicate cost can still support a required workflow, data set, customer commitment, security function, migration, or reporting process. The review should identify avoidable duplication without confusing temporary integration cost with waste.

First 100 days after an acquisition: the cost-review sequence

Timing	Review	Required output
Days 1–30	Vendor master, trailing AP spend, contracts, applications, identity environments, cloud/telecom commitments, owners, renewal and notice dates	Unified recurring-cost, contract, ownership, and decision-date inventory
Days 31–60	Duplicate suppliers, duplicate software, overlapping infrastructure, pricing differences, unused licenses, unclear ownership	Prioritized overlap and contract-decision queue
Days 61–90	Business dependencies, data migration, integrations, transition cost, termination rights, customer or reporting requirements	Implementation-ready decisions with economics and risk
Days 91–100+	Renegotiation, consolidation, license reduction, migration, cancellation, implementation, measurement	Approved actions with accountable owners and realized-result tracking

What evidence should finance collect before deciding what to consolidate?

Start with evidence rather than a list of proposed savings.

Evidence	Fields to capture	What it answers
Vendor master	Vendor, entity, category, business owner	Who are both companies buying from?
Trailing 12-month AP spend	Vendor, invoice amount, frequency, cost center	What is the actual recurring spend pattern?
Active contracts and amendments	Scope, quantity, term, minimum commitment, renewal date, notice requirement	What can be changed, and when?
SaaS and application inventory	Product, users, owner, purpose, integrations	Which applications overlap or may no longer be required?
Identity and access inventory	Identity provider, active accounts, guest accounts, dependent applications	Which legacy access remains because systems have not been migrated?
Cloud and telecom inventory	Provider, service, environment, commitment, owner	Which infrastructure or connectivity costs overlap?
Purchase orders	Supplier, scope, committed amount, owner	What future spend has already been authorized?
Business ownership	Executive sponsor, operating owner, technical owner	Who can validate whether the service is still needed?
Migration dependencies	Data, integrations, workflows, customer dependencies	What has to happen before cancellation or consolidation?

The goal is one authoritative cost-and-ownership inventory. A vendor appearing in both companies is a review trigger, not proof that one relationship should be terminated.

Which duplicate costs should be reviewed first?

Prioritize decision urgency and materiality.

Start with:

• •material recurring spend;
• •contracts approaching a renewal or notice deadline;
• •vendors used by both businesses for substantially similar services;
• •duplicate SaaS applications;
• •overlapping cloud, telecom, or infrastructure commitments;
• •costs with no clearly accountable owner;
• •materially different pricing for comparable scope;
• •licenses associated with departed, transferred, or migrated employees;
• •services attached to systems already scheduled for retirement.

A contract's decision date may occur before its expiration date. Finance should extract the actual renewal and notice provisions from the agreement instead of assuming that the nominal renewal date is the last day the company can change quantity or terms.

Why should duplicate vendors not be consolidated automatically?

"Duplicate" and "redundant" are not the same thing.

Two suppliers that appear to provide the same service can support different:

• •business units;
• •geographies;
• •customer commitments;
• •service levels;
• •integrations;
• •data environments;
• •security requirements;
• •reporting requirements;
• •operational workflows.

Two software platforms can also coexist temporarily because the acquired company has not finished migrating users, data, automations, integrations, or historical records.

Before recommending consolidation, leadership should determine:

• •Can the remaining supplier or platform support the complete required scope?
• •What must migrate?
• •Who owns that migration?
• •What will transition cost?
• •What can break?
• •What contract obligations remain?
• •When can the incumbent cost actually be removed?

The economic decision is not simply "which vendor costs more?" It is the net financial and operating effect after implementation requirements are included.

How should a CFO evaluate the economics of a post-acquisition cost opportunity?

Separate four numbers:

• •Current recurring cost — what the business pays today.
• •Validated future run-rate — what the business expects to pay after the approved change.
• •One-time implementation cost — migration, integration, transition, professional services, or internal effort required to make the change.
• •Timing to realization — when the invoice, contract, payroll, or cash outflow will actually change.

Do not count an identified opportunity as realized savings merely because it appears in a presentation. A recommendation becomes financial impact only after the required operating and contractual actions occur.

What causes post-acquisition cost synergies to disappear?

Waiting until renewal to inspect the contract

The business can discover that it needs fewer licenses or a different supplier only after the contractual decision window has already passed.

Treating every duplicate system as immediately removable

A legacy application can still authenticate users, own automations, hold historical data, or support an acquired workflow.

Negotiating before determining the required footprint

A lower price on unnecessary quantity can preserve unnecessary spend.

Failing to assign an accountable owner

Temporary duplication can become permanent when nobody owns the migration, contract, or retirement decision.

Confusing identified savings with realized savings

Leadership should measure actual contract, invoice, or operating-cost change after implementation.

Questions a CFO should ask during the first 100 days

• •Which material contracts have decision dates in the next 180 days?
• •Which vendors are used by both businesses?
• •Which applications perform overlapping functions?
• •Which recurring costs have no clearly accountable owner?
• •Which systems remain active only because migration is incomplete?
• •Are departed or migrated employees still carrying paid licenses?
• •What contract quantity does the combined business actually require?
• •Which consolidations require data, identity, or workflow migration?
• •What one-time implementation cost is required to create recurring benefit?
• •Which identified opportunities have actually reached a contract, invoice, or cash-flow result?

When should a cost opportunity not be prioritized yet?

An apparent saving may need to wait if removing the expense could:

• •disrupt customer delivery;
• •interrupt financial reporting;
• •create an access or security problem;
• •eliminate required data access;
• •interfere with an active migration;
• •create a larger implementation cost than the expected benefit;
• •violate a contract or customer requirement.

The objective is to distinguish avoidable duplication from transitional cost that is temporarily required to complete integration safely.

Frequently asked questions

The Blackspire post-acquisition decision file

For each material opportunity, create one decision row:

Opportunity	Current cost	Evidence	Contract decision date	Operating dependency	Implementation cost	Owner	Approved action	Realization status
—	—	—	—	—	—	—	—	—

This converts a theoretical synergy list into an implementation queue leadership can manage.

Related Blackspire resources

For a broader review of recurring suppliers, contracts, pricing, and operating ownership, see Blackspire's vendor spend review.