HRIS built for M&A transaction readiness

BVXpress was the SaaS business unit within ICI (M&A advisory). From 2012–2021 I owned the complete HRIS end-to-end. The HRIS shipped as a BVXpress product for ICI clients and acquired companies—not internal-only tooling. Scope: HRIS ingestion, normalization, people analytics, diligence reporting, and transaction compliance, shaped by post-merger integration teams on live deals.

Product Manager · BVXpress / ICI M&A · HR Tech · People Analytics 2012–2021
API-first
Connect any source HRIS; analytics layer, not rip-and-replace
Adapters
System-agnostic integration: Workday, SAP, ADP, local payroll
Normalized
Job families, comp views, hierarchy mapping, employment types
People analytics
Payroll and contract risk surfaced on diligence dashboards

Who it was for

ICI clients and acquired companies on the BVXpress product suite: M&A workforce due diligence and integration teams, plus post-merger entities themselves.

Day-one users were integration and diligence teams; the product goal was a sticky system that would expand to management and HR business partners in the new company once workforce truth was trustworthy.

Why we needed this

Legacy HR doesn’t handle mergers well. Every acquisition meant months of migration, incompatible systems, duplicate records, and HR teams drowning in manual reconciliation, with no combined workforce metrics during due diligence.

We built for transaction readiness from day one, not bolt-on reporting after the fact.

The M&A problem we solved

Traditional approach

Acquired Co A → Their HRIS → Migrate to ours → 6 to 18 mo
Acquired Co B → Different HRIS → Another migration → +6 mo
  • Each integration is a one-off project
  • Data quality varies wildly
  • No standard data model
  • HR can’t answer basic diligence questions

Our approach

Acquired Co → API connect → Instant visibility
→ Standardized model → Dashboards → Transaction reporting
  • Reusable integration pattern
  • Validation and confidence at ingestion
  • Normalized schema across targets
  • Real-time answers for deal teams

What we built

Beyond a typical employee roster, reporting structure, pay data, and employment types, the platform connected upstream HR tooling and delivered diligence-ready analytics and reporting for transaction teams.

1. HRIS ingestion & adapters

Pull workforce data from acquired entities’ HRIS and payroll tooling. System-agnostic integration layer; Frappe HRMS as reference implementation; extend to Workday, SuccessFactors, ADP, and regional payroll.

2. Normalized workforce model

Job titles to families, compensation to currency-neutral views, org hierarchy mapping, and employment types in one schema so combined-entity metrics are comparable.

3. People analytics & diligence dashboards

Transaction-ready views: headcount by geography, total comp burden, retention and key-performer risk. Teams could quickly flag payroll anomalies and employee-contract concerns without ad-hoc report projects.

4. Diligence reporting

API-first outputs for deal rooms and data rooms: combined workforce answers PMI and diligence stakeholders needed in real time, not after migration.

5. Compliance & audit (transactions)

Requirements driven by post-merger integration teams across acquisitions: historical preservation, audit trails, GDPR-aware handling, and document retention from the start.

6. Separation of concerns

Source HRIS and payroll stay system of record. We pull, normalize, and analyze on top; Frappe handles payroll depth so we focus on M&A-specific analytics and integration.

What discovery showed

M&A is a different job-to-be-done

Focus groups with HR ops and deal-team stakeholders during live transactions surfaced a split from day-to-day HR: users needed rapid multi-source ingestion, flexible schema mapping, and diligence-ready rollups, not another ESS portal. Opportunity maps ranked transaction visibility above employee self-service for the first release.

Integration beat replacement

Workflow interviews and a build-vs-buy matrix killed the “replace every payroll system” hypothesis. Stakeholders wanted source systems to stay authoritative; the product should connect, normalize, and report. That research drove the adapter pattern and Frappe for payroll depth instead of rebuilding compliance engines.

Data trust was the workflow blocker

Shadowing reconciliation during diligence showed duplicate records and inconsistent fields were why teams reverted to spreadsheets. Tree tests on dashboard tasks (headcount by country, comp burden, retention risk) failed when numbers disagreed across sources. We prioritized validation at ingestion, duplicate handling, and confidence scores before adding net-new analytics.

Adoption had to survive deal crunch

HR leads in post-close integration said they would not learn a new tool mid-transaction unless paths were obvious under pressure. Prototype walkthroughs and tree tests on core diligence flows informed a minimal dashboard set and plain-language labels. Winning integration teams first was the path to management and HR business partners in the combined entity.

Technical decisions

Stack
.NET / Azure
Payroll
Frappe HRMS: compliance-heavy domain; we don’t rebuild payroll engines
Sync
Bidirectional: source systems remain system of record; HRIS is analytics layer
Events
Event-driven: real-time updates aligned to deal pace
API
API-first: deal rooms, data rooms, and diligence tooling

What’s next

Workday adapter SAP SuccessFactors ADP Virtual data room push Attrition & retention scoring Mobile exec metrics Employment diligence docs

PM takeaways

“The best HR system for M&A is one that makes the deal team say ‘finally, something that just works.’”