ERP & critical systems

Selection, migration, and implementation of the systems your business can't run without — decisions most companies make once a decade, guided by people who've made them dozens of times.

An ERP selection is a strange kind of decision. It's among the most expensive and least reversible choices a mid-market company makes — and most leadership teams will make it exactly once. The vendors across the table, meanwhile, have run this exact sales process hundreds of times.

That asymmetry is the problem we're hired to fix.

The triggers repeat: a system at the end of its road — out of support, out of capacity, or out of alignment with how the business actually runs now. An acquisition (or several) that left the company running two of everything. A new owner who needs the numbers to consolidate cleanly and the operations to scale. Or a selection already underway that's starting to feel like it's being run by the vendors instead of the buyer.

Sometimes we're called after the contract is signed, when an implementation is drifting — over budget, past deadline, and nobody inside the building is quite sure whether the integrator's story holds up. That call works better earlier, but it's never too late for a straight answer.

An executive who has selected, implemented, and lived with these systems — as the operator, not the salesperson — leads the work. For a selection: requirements grounded in how your business actually operates (not a 400-line RFP template), a shortlist that reflects your size and complexity, structured demos the vendors can't script their way through, and contract negotiation that reflects having seen these agreements from both sides.

For a migration or implementation: sequencing, data-quality reality checks, integrator management, and the discipline to protect scope — because most ERP failures aren't software failures; they're governance failures with a software invoice attached.

We're fiercely tech-agnostic — no reseller margin, no implementation arm to feed, no favorite vendor — so the recommendation starts and ends with your business.

And we mean the whole business. One of the quiet killers of these programs is the eleventh-hour stakeholder: the leader who surfaces mid-implementation with "no one talked to me, and this won't work for our part of the business." By then it's rework, delay, and budget. We get every business unit to the table during selection — requirements gathered from the people who'll live with the system, objections surfaced while they're still cheap, and a decision the whole leadership team has actually signed up for, not just received.

A decision your team can defend — to the board, the owners, and themselves in three years: a selection with documented reasoning, a realistic budget and timeline (including the parts vendors quote quietly), and an implementation governed like the business-critical program it is, with a named owner and honest status reporting throughout.

Not a reselling arrangement, not a bench of billable implementers looking for a long engagement, and not a 400-page requirements study. If the honest answer is "your current system is fine — fix the process around it," that's the recommendation.

A fast-growing risk-and-insurance firm had outgrown a single monolithic application and needed a pragmatic path forward — read the case study. For the acquisition angle, our field note on buy-and-build integration covers why the ERP decision is the one most often rushed, and shouldn't be.

If a platform decision is on your calendar this year, the cheapest insurance is a conversation before the vendor meetings start. Start the conversation.