The Legacy System Conversation Nobody Wants to Have
Most apparel teams know the planning system is holding them back. They keep working around it because the alternative — replacement — feels worse than the workarounds. It is not, and the cost of waiting compounds every season.
Every mid-market apparel brand we talk to has a version of the same conversation, scheduled at the same point in every quarter, that nobody wants to have. It is the conversation about the planning system.
The shape is consistent. The team knows the current setup is holding them back. There are workarounds for everything — a spreadsheet that imports from the ERP because the ERP report is unusable, a separate hindsight file because the planning tool's reporting is two seasons stale, a buying file that gets manually reconciled against the OTB twice a week. Each workaround has an owner. Each owner is the only person who knows how it really works.
The conversation gets postponed because the cost of replacement feels concrete and immediate, while the cost of staying feels diffuse and distant. A new system is a budget line, an implementation calendar, a change-management exercise. The current system is just... what we do.
The cost of staying is not diffuse — it is structural
A 12-month delay on replacement means another four buying events on the existing setup, with the same 1–3 points of IMU at risk per event. It means another season's worth of carry-over decisions made from memory. It means continuing to lose senior planners to other brands because the work is reconciliation, not analysis.
The math is straightforward, but it never gets done because the cost of staying is not on anyone's quarterly review. Workarounds do not show up on a P&L line. The senior planner who left because the role was 60% file maintenance is replaced with someone junior, and the institutional knowledge that walked out the door does not appear in any system.
What actually unlocks the conversation
The unlock, in our experience, is not a better ROI deck. It is a smaller commitment. The reason mid-market brands postpone the conversation is that the market has trained them to expect a 12-month, seven-figure implementation — because for two decades, that is what enterprise platforms required.
Once it becomes plausible that the replacement is a 4–8 week onboarding without an SI partner — once "live in weeks, not quarters" is something the team can verify, not just hear — the conversation gets unstuck. The decision stops being "do we trade certain near-term pain for uncertain long-term gain" and starts being "do we want to fix this before next season opens."
What we tell teams who are stuck on the conversation
Two things.
First: list the workarounds. Every brand has them; few brands have them written down. Once the list exists, the cost of the existing system is no longer abstract. The reconciliation spreadsheet that takes 6 hours every Monday is a $40K/year line item by itself.
Second: pilot, do not transform. The teams that succeed do not migrate everything at once. They run one season — typically a smaller season or a single department — in parallel. The spreadsheets stay. The new system runs alongside. By the end of the parallel season, the team has confidence in the data feed and a working configuration, and the spreadsheet retirement happens on schedule.
The conversation nobody wants to have ends when the alternative stops being a year-long bet and starts being something the team can validate before they commit to retiring the file stack.
If your team is stuck on this conversation, we are happy to walk through what a parallel-season pilot looks like.