Rippling vs Firstbase for PE Portfolio Companies After Close

A platform company that's been running for years usually has some version of an asset process already, even if it's informal. An add-on being folded in typically arrives with its own vendor relationships, its own naming conventions, and often no clean asset register at all. Treat the two as separate integration problems rather than assuming the add-on will simply adopt the platform's existing process on its own.

Audit the add-on's hardware before migrating anyone into shared systems. A device that shows up in your platform without a matching physical unit, or a laptop still running the add-on's old software stack, is a problem you'll spend more time tracing later than you'd spend catching it now.

This audit is worth the time even for a small add-on. A team of a dozen people can still hold enough undocumented hardware to create a real gap in your combined asset register if nobody checks before the systems merge.

Deal teams focus heavily on financial and operational integration in the early days after close, and hardware tends to fall to whoever has spare time, which often means it doesn't get done at all. That's exactly when a departing employee from the acquired company, uncertain about their status, is most likely to walk off with a laptop nobody's tracking yet.

Put device inventory and access control on the integration checklist itself, not as a side task. If your integration plan already has a hundred-day structure, this belongs in the first two weeks, not somewhere in month three.

A post-close device checklist should include these items:

• Start device inventory in the first weeks after close, before hardware falls to whoever has spare time and never gets done.
• Record which legal entity bought each device and which entity employs the person using it, since rollups blur that line.
• Capture an add-on's vendor relationships and naming conventions instead of assuming a clean asset register exists.
• Keep a fixed asset register current, because buy-side diligence on a future sale typically asks for one.

A portfolio company operating through several legal entities, common after a rollup of add-ons, means a device purchased under one entity's name might be used by an employee technically on another entity's payroll. This matters for accounting and for a future diligence process, even if it never causes a day-to-day operational problem. Rippling and Firstbase both let you track ownership at the device level, but neither one resolves the underlying legal entity question for you, that's a decision your finance team and counsel need to make explicit.

Get this resolved on paper even if it never shows up in daily operations. A future buyer's diligence team will ask, and a clean answer at that point is worth far more than the small effort it takes to document it now.

Buy-side diligence on a future sale will typically ask for a fixed asset register, and a device fleet with clean, current records is a small but real point in your favor during that process, while a fleet nobody's tracked is a scramble a few months before close. Building this record now, while it's routine maintenance, is considerably cheaper than reconstructing it under deal pressure later.

This is a case where the operational discipline pays for itself twice: once in day-to-day security, and again in the far more visible moment of a diligence data room.

A holding company deciding whether every portfolio company should run the same device platform is really deciding how centralized it wants operations to be, which is a governance question that predates any specific vendor choice. Forcing a platform onto a portfolio company that already has a working process just to standardize for its own sake tends to create more friction than value, unless there's a genuine operational or diligence reason driving it.

Even without forcing every portfolio company onto the same platform, a holding company benefits from knowing at a glance which portfolio companies have a functioning device management process and which don't. Process Street can serve as a lightweight cross-portfolio checklist for that visibility without mandating a single tool. Save the harder push toward one standardized platform for portfolio companies where an add-on integration or an upcoming exit actually makes it worth the disruption.

A quarterly check-in on this, alongside whatever other operating metrics you already review across the portfolio, is usually enough to catch a company that's fallen behind before it becomes a diligence surprise later.