From Pre-Sales to Support: What Three Decades of ERP Engagements Taught Me

An ERP project is a lifecycle, not a launch

A lot of people treat go-live as the finish line. In ERP it's barely the halfway point. I've worked the full arc, pre-sales, scoping, implementation, rollout, customization, upgrades, and on-going support, and the engagements that succeeded were the ones where someone held the whole lifecycle in their head from day one.

When you've sat with a customer during pre-sales and you know you'll still be supporting them three years later, you make different decisions. You don't over-promise to win the deal. You design for the upgrade you know is coming. You build the customization in a way that won't break the next version. The long view changes everything.

Structured methodology beats heroics

Early in my career I learned to deliver pragmatic, cost-effective solutions to complex business problems using structured methodologies and techniques. That phrasing sounds dry until you've watched an unstructured project go sideways.

ISO, CMMI Level 5, ITIL, I've worked inside all of them, and the value isn't the audit. It's that a structured approach means the same problem gets solved the same reliable way whether the team is two people or fifteen. I once ramped a team from 2 to 15 for a global application maintenance engagement; the only reason that scaled without chaos was that the process was already written down.

The unglamorous work earns the trust

Some of the work I'm proudest of was the least glamorous. Fit-Gap analysis against a country's tax laws. A roll-out for a Switzerland-based customer where the win was simply that nothing broke. Two consecutive years of customer satisfaction ratings of 5 out of 5, earned not by a single brilliant feature but by showing up, every cycle, with predictable delivery.

In enterprise software, trust compounds. A customer who has seen you deliver clean for two years will give you the benefit of the doubt on the third. That trust is the real asset.

What I carry forward

The skills transfer further than the acronyms suggest. Understanding how a manufacturing business actually runs, translating that into requirements, and shipping something that holds up under real load, that's the same muscle whether the system is SAP, Baan, or an AI product I'm building today. The technology keeps changing. The discipline of taking a complex business problem and turning it into a working solution does not.