Office technology dealer M&A due diligence: a service operations checklist

David Mensah, Developer Advocate at Auralis AI

David Mensah

October 14, 2026 · 5 min read

Two people shaking hands
On this page
  1. Where the coverage gap shows up
  2. Where the headcount gap shows up
  3. The checklist
  4. Sources

In its August 3-7 roundup, The Cannata Report covered DEX Imaging’s acquisition of Imagine Technology Group, an Arizona dealer, and GFI Digital’s acquisition of TDS IT, a longtime Xerox partner, in North Little Rock, Arkansas. The roundup reports the transactions. For operational due diligence, we’d also want to know what happens to the acquired company’s call volume once the deal closes.

DFIN’s checklist for M&A due diligence treats contract review as central, calling it “one of the most important workstreams,” because what turns up there can affect closing terms and how the two companies come together. The same checklist asks for the target’s list of tech vendors and vendor agreements, along with its customer and service contracts. Axiom Law’s due diligence guide goes further on the tech side: build an inventory of the target’s IT systems, software, databases, networks, servers and hardware, check ownership and licensing terms on each one, and gauge whether the setup will actually work with the acquirer’s before you count on a clean fit.

Neither checklist specifically discusses office technology dealer operations, but a dealer’s e-automate environment, service dispatch setup and meter data are the kind of IT infrastructure and vendor-tied contracts they’re describing. It’s easy for a dealer’s own pre-close review to stay financial and legal and leave service operations until after the deal, which is the order we’d reverse.

Where the coverage gap shows up

According to ENX, Advanced Office of Irvine, California ran into this after acquiring an MPS company. An extensive population of A4 devices from the deal sat outside their service area, without dealer-supported contracts for supplies or service. That meant fielding those service calls through local dispatch first, then coordinating a time-and-materials call with dealerships in that part of the country. The back and forth stretched out downtime for customers and pushed costs up in their service department.

A contract review alone may not surface a gap like that. Map device locations against your own service radius, and against the vendor inventory above, before closing.

Where the headcount gap shows up

One dealer we work with folded two acquisitions into the same team and was looking at a 30 to 40% jump in volume the following quarter. Extra seats to cover that, in our experience, usually get turned down. When the ask is denied, the existing team ends up absorbing the acquired workload. Your own contact mix before the deal, meter reads, toner orders, service calls and contract or billing questions, gives you a real baseline for sizing what the acquisition adds to it.

The checklist

Run these checks before signing.

  1. Start with the target’s technology and vendor inventory: IT systems, software licenses, and vendor and service agreements. Review ownership, compliance and licensing terms on each one before you count on continuity.
  2. Then get the device list and match every machine against your actual service radius. Flag out-of-area devices and price the coverage gap into the deal.
  3. Ask what share of the fleet sits on a data collection agent. e-automate’s FMAudit integration syncs meters from connected devices straight into billing. For devices not on FMAudit, check whether the acquired operation is using e-automate’s automatic email or fax meter requests, a phone list for staff to work, or something else entirely.
  4. Pull a sample call type report from the target’s e-automate before you close, and check the categorization has actually been consistent, not just available. If you lean on the Service Statistics report specifically, know that it counts activity for calls with at least one labor record logged against them, so a call closed without one won’t show up there.
  5. Model the volume increase against your current headcount, not the org chart you’re planning after the deal.
  6. Decide, before close, what gets automated and what stays with a person. We’d recommend automating meter reads, toner orders and routine service call intake where it makes sense, handled around the clock and written straight into e-automate (that’s what we built Auralis to do), and keeping people on the calls that actually need one, like a customer whose machine has been down all week, or a new account that isn’t sure about you yet.

For step 6, Build vs buy: how to add AI agents to your team compares building an AI agent in-house with buying one on time to go live, cost, upkeep and who owns it afterwards.

Sources

Share this

For e-automate dealers

See Auralis on your own service desk

A 30-minute walkthrough on your workflow — meter reads, dispatch, supplies and escalation.

Book a demo
David Mensah, Developer Advocate at Auralis AI

David Mensah

Developer Advocate

David is Auralis's developer advocate, bridging engineering and the outside world with the tutorials, integration guides, and technical content that help teams build with Auralis. If you've ever connected Auralis to your stack in under an hour, you've read his work. His documentation philosophy is that the fastest support ticket is the one that never gets filed: clear guides, honest examples, and answers where developers actually look. He works directly with customer engineering teams to turn their feedback into better docs and a better product.

We use cookies to run this site and, with your consent, to analyze usage and improve our marketing. You can accept all, reject non-essential, or choose. See our Cookie Policy.