Notes from the field on ERP, AI, and operations.

Every proposal names senior people on the cover page. Here are the four questions that tell you whether they're the ones who will actually do the work — and why most buyers never ask until it's too late.

Every troubled ERP project looks different on the surface. Strip away the specifics and the same handful of early, quiet decisions show up again and again — here is the pattern, and what building for it from day one looks like.

Point-to-point connections accumulate one reasonable decision at a time until the system they add up to is the problem. Here is where integration architecture actually gets decided — and where it usually doesn't.

Migration plans treat data as a task on a timeline. The projects that hold up treat it as the central decision it actually is — here is where that judgment call gets made, and where it goes wrong.

Most AI pitches start with the model and work backward to a business problem. Here is why the ones that actually deliver start with data quality and process discipline instead.

Implementation leadership is not project management. Here is what the judgment calls actually look like across 50+ NetSuite rollouts — and how to tell who is really leading yours.

Most ERP and cloud firms sell senior expertise and deliver with junior staff. Here is what actually changes when the person who scoped the project stays on it through cutover.

Troubled ERP projects rarely fail for the reasons stated in the status report. Here is what recovery actually involves — and why the first move is almost never technical.