The schedule keeps slipping in small increments
A schedule that slips by a week every month rarely recovers. By month six you are months behind, but the slippage was never large enough to trigger an escalation.
If your implementation has slipped twice in a row, treat it as a leading indicator and ask for a re-baselined plan with explicit dependencies — not a generic catch-up.
Configuration decisions are deferred 'until later'
Decisions about chart of accounts, costing methods, intercompany flows, and integration patterns belong in the first 90 days. When they slide to month four or five, the rework cost grows exponentially.
Track every open design decision with an owner and a deadline. Anything sitting open longer than 30 days is a risk.
User involvement is shrinking
Implementations succeed when business users own the future-state design. If your finance, operations, and warehouse leaders are no longer attending working sessions, the design is being made for them — not by them.
Adoption problems at go-live trace back to this almost without exception.
The consulting team rotates
Junior consultants rotating in and out of your project is a sign that the partner is staffing for utilization, not outcome. Ask who is actually accountable for the design and stay with them.
What to do
Most of these signs are fixable in the implementation phase. They are very expensive to fix after go-live. A short, independent assessment from a senior Sage X3 consultant is the cheapest insurance available at that point in a project.