Notes from a Mid-Market Implementation: What the First 30 Days Actually Look Like

The phrase "live in weeks, not quarters" has been used so often that it sounds like a marketing claim. For mid-market apparel brands evaluating a planning platform, the question is fair: what actually happens in those weeks? Here is the unromantic version, drawn from typical RetailNorthstar onboardings for brands in the $20M–$200M revenue range.

Week 1 — Configuration

The first week is not about learning the platform. It is about translating the team's existing planning structure into the platform's data model. Department hierarchy. Period calendar. Channel structure. Size curve definitions. Vendor list with current MOQs and lead times.

Most of this exists in the team's spreadsheets. Pulling it out and reformatting it is the bulk of week 1's work. It is not exciting, and it is the difference between a 4-week onboarding and a 4-month one. The teams that move fastest are the ones that have a single planner own this translation work — not a committee, not a project manager, but a senior planner who can answer questions about season boundaries and carry-over rules without needing to consult anyone.

Week 2 — Historical data

Week 2 is hindsight. Sales, inventory, and margin data from the prior 2–3 seasons gets imported. Sell-through by style, color, and size. Markdown depth. Size performance against the curve. This is what powers carry-over decisions in the new system, and it is what makes the platform useful from day one instead of from season three.

The data quality issues that surface in this week are revealing. They are almost always pre-existing — bad style codes that nobody noticed, channel splits that drift over time, store closures that were never reflected in the warehouse data. The platform does not create these issues; it is the first system that surfaces them in one place. Week 2 is often the week the team realizes how much of their reporting was built on quietly broken assumptions.

Week 3 — Team training and parallel work

The training is short — typically 4–6 hours total, split across roles. The interface is meant to be obvious. The longer part of week 3 is starting parallel work: the first piece of the planning calendar runs in both spreadsheets and the new platform, side by side.

The choice of what to run in parallel matters. Brands that try to parallel everything stall. Brands that pick a single department or a single buying event and run it cleanly in both environments build confidence quickly. The decision rule we suggest: pick the smallest piece where the team will notice if the answer is wrong. That is where you want to verify the platform first, because it is where the team's judgment is most calibrated.

Week 4 — First real decision

By week 4, the team is making at least one real planning decision in the platform. Not a parallel decision, not a pilot — a decision that goes into the actual season. For most teams, this is a depth call on a small set of styles, or a carry-over decision on a single category, or a re-allocation triggered by an in-season signal that the platform surfaced before the spreadsheet would have.

This is the moment that determines onboarding success. The team has either internalized that the new system is faster and more reliable than the spreadsheet stack, or they have not. In our experience, the teams that pass this milestone in week 4 are at full adoption by week 8. The teams that drag it into week 6 or 7 typically have a different problem — usually a senior planner who is not bought in — and that is a leadership conversation, not a software one.

What "live in weeks" really means

Live in weeks does not mean "everything is done." It means the team is making real decisions in the platform within four weeks, with a clear path to retiring the spreadsheet stack over the following 4–8 weeks. It means the implementation is operational, not aspirational.

For executive teams trying to assess whether the timeline is real, the question to ask is not "how long until live" but "what does the team need to commit to internally for the timeline to hold." The answer is: one senior champion, the historical data export, and the discipline to not parallel-run everything at once. That is the implementation in three sentences.

The full demo walks through the platform you would be working in by week 4.