Forum  Working Session
Cadence next-season build commit — capacity commit (full vs staged) · 3 round(s)
Sales · Operations · facilitated by Forum
Coordinator · opens
Opening the floor. **The conflict:** Sales is forecasting ~20% QoQ growth and wants to commit full max capacity now to capture upside ("sell everything we make"). Operations is seeing finished-goods inventory build and a port backlog, and is flagging that a full commit locks in largely irreversible exposure after the July-1 cutoff. **The decision on the table for Cadence next-season build:** commit full max capacity now, or move to a staged commit with defined trigger gates. Floor goes to @Sales first — make the case for full commit. @Operations, hold your response until Sales has laid out its position; you'll have equal time to rebut. Both of you: bring specific numbers, dates, and tradeoffs — not generalities.
Sales · weighs in
Sales position: we're forecasting ~20% QoQ growth and we're selling everything we make. A peak-season stockout puts roughly $30M of bookings at risk and the waitlist churns fast — those buyers don't wait, they go to a competitor. The cost of being short is bigger than the cost of being long, so I'm asking for full max capacity committed now, before July 1. I do want to flag honestly: RevOps's cohort work says a large share of the last two quarters' unit growth is first-time buyers riding the stay-home surge, and durability past the next two quarters isn't proven. That's a reason to watch the back half of the season closely, not a reason to under-build peak. @Operations, your turn.
grounded on: demand_durability growth_forecast ops_inventory_signal sales_demand_claim understock_cost understock_position
Operations · weighs in
@Sales — fair, and the $30M stockout risk is real, but the inventory signal cuts the other way. FG weeks-of-supply have drifted from ~4 to ~9 over the last quarter, trending up a few tenths every week, and we currently have 3 inbound containers sitting at Long Beach because the regional DC has no rack space. That's not "selling everything we make" — that's supply arriving faster than it leaves. The RevOps cohort caveat you flagged yourself reinforces it: if the back half of the season softens, the last-quarter units are the ones we can't redeploy. On irreversibility: after July 1 the CM tools and reserves the cells, and that capacity is ours whether we use it or not — no reassignment to another program. A full max-capacity commit means ~25-30% of output sits unsold for ~two quarters, which is roughly $40M in working capital tied up plus resale-price erosion on a $2,000+ premium product. That number isn't Finance-validated, flagging that openly. The staged alternative: commit Q+1 firm now, hold Q+2 as a confirmable option. CM has signaled willingness, premium is ~2-4% of the deferred block (~$1-2M on a ~$50M block), and we confirm ~8 weeks before Q+2 production starts. We get the upside cover for the peak with a real exit if the demand signal you described starts matching what WMS is showing. @Coordinator — that's Operations' position.
grounded on: inventory_now lead_time ops_inventory_signal overcommit_cost port_backlog reversible_date sales_demand_claim staged_option_feasibility staged_option_terms
Coordinator · focuses the group
Good — both positions are now on the record with numbers. Before I call this converged, I need one direct exchange: @Sales — Operations has put a specific staged structure on the table: Q+1 firm now, Q+2 held as a confirmable option with an 8-week pre-production gate, premium ~$1-2M. Do you accept that, reject it, or counter with a modified trigger (e.g., different gate timing, a specific WOS/booking threshold for the Q+2 confirmation, or a partial commit like 70/30)? @Operations — if Sales accepts a staged commit, what are the concrete trigger metrics and the exact confirmation date you need for the Q+2 block? Name the number, not the category. One round, then I synthesize.
Sales · weighs in
Counter, not accept. The WMS doubling to ~9 weeks of supply and the waitlist conversion slipping from ~70% to ~55% are real signals, so I won't fight for full max. But Q+1 firm alone doesn't cover peak — the $30M stockout exposure is concentrated in the front of the season, and a 70/30 split gets us most of the cover with a real exit. @Coordinator — Sales counters with **70/30 staged**: commit 70% of max capacity firm now, hold 30% as a confirmable Q+2 option with the 8-week pre-production gate and ~$1-2M premium. @Operations — name the two triggers I need: (1) the WOS threshold above which you pull the Q+2 option *down* (not up), and (2) the booking-pace or conversion threshold that lets me push it back *up*. Specific numbers, not categories, and the exact confirmation date. One round, then I want a decision.
grounded on: growth_forecast ops_inventory_signal pull_forward sales_demand_claim understock_cost understock_position waitlist_conversion
Operations · weighs in
Records checked — my prior message stands. The trigger numbers (WOS ≥11 pull-down, sell-through <85% pull-down, conversion >65% for 3 weeks plus WOS ≤7 push-up) are my operational call, not drawn from the records, and I want to be clear on that. The records I do have: - Current FG WOS ~9, drifting up from ~4 — that's the baseline both triggers reference. - 8-week pre-production gate with ~$1-2M premium on a ~$50M deferred block — that's the mechanism the triggers sit inside. - July 1 cutoff, cells non-reassignable after — confirms why the trigger design matters. What the records do **not** give me, and I want on the record as explicit unknowns: the exact Q+2 confirmation calendar date (mid-Q+1 is directional, not a stamped date), the conversion/sell-through thresholds I'm proposing (those are my proposal, not validated), and any Finance sign-off on the $40M working-capital exposure. @Coordinator — if those trigger numbers need to be defensible to Finance or the CM clause, I want a second pass before sign-off. Sales and I are aligned on structure; the numbers need a 48-hour validation window.
grounded on: inventory_now lead_time ops_inventory_signal overcommit_cost reversible_date sales_demand_claim staged_option_feasibility staged_option_terms
Coordinator · focuses the group
Structure is locked: **70/30 staged commit, 8-week pre-production gate, ~$1-2M premium**. Three open items before this is signable: @Operations — name the single **calendar date** for the Q+2 confirmation gate (not 'mid-Q+1'). And confirm the two trigger pairs in one line each: **(a) WOS ≥ ___ OR sell-through < ___% → pull Q+2 down to zero**, **(b) WOS ≤ ___ AND conversion > ___% for ≥3 weeks → push Q+2 up to full 30%**. State whether the pull-down is binary (full release) or stepped (e.g., release 15% first). @Sales — once Operations gives the date, do you accept it? Yes/no, and if you want a different number inside either trigger, say it now. @Finance — flagging now: we need same-day confirmation that the ~$40M working-capital exposure on a full-max scenario is rejected in favor of the staged path, and that the $1-2M premium is an authorized spend line. Silent assent counts as yes; explicit objection goes on the record. One round, then I close it.
Sales · weighs in
Calendar date: not in my records. Operations owns the CM production calendar — I'll accept the date @Operations names once they put a stamped date on it, not a directional "mid-Q+1." If they don't have one, CM is the source. Structure acceptable subject to that date and Finance sign-off on the $1-2M premium line. @Finance — explicit ask, not silent assent: confirm the premium is authorized and the staged path replaces the ~$40M full-max exposure. @Coordinator — ready to close once the date lands and Finance responds.
grounded on: growth_forecast pull_forward sales_demand_claim understock_cost
Operations · weighs in
@Sales — fair. The records give me the gate as **~8 weeks before Q+2 production start, directionally mid-Q+1**, but no stamped calendar date — that's with the CM and isn't in my files. I'll get a stamped date from the CM production calendar before sign-off; until then, I'm not putting a number on paper I can't defend. On the trigger pairs, I have to be straight: **the WOS ≥11 / sell-through <85% pull-down and WOS ≤7 / conversion >65% for ≥3 weeks push-up numbers are my proposal, not records** — I flagged that in the prior round and I'm holding it. Pull-down I'd structure as a **stepped release (15% first, then the remaining 15% two weeks later)**, not binary, so we don't slam a door on a recovering signal. @Coordinator — signable package from Ops side, contingent on three things: (1) CM-stamped confirmation date replacing "mid-Q+1", (2) 48-hour validation window on the trigger thresholds with Sales and Finance in the room, (3) Finance sign-off on the staged path replacing the ~$40M full-max exposure and authorizing the $1-2M premium. Sales has the structure; the date and the validation are the gate.
grounded on: overcommit_cost reversible_date staged_option_feasibility staged_option_terms
Coordinator · brings to the meeting
Escalating to humans. Structure is locked: **70/30 staged commit, 8-week pre-production gate, stepped pull-down (15% then 15% two weeks later), proposed triggers WOS ≥11 or sell-through <85% → pull, WOS ≤7 AND conversion >65% for ≥3 weeks → push**. Humans must decide three things: 1. **Stamped Q+2 confirmation date** — @Operations to get from CM production calendar. Until that date is on paper, the gate isn't enforceable. 2. **Finance authorization** — explicit yes/no on the $1-2M premium line replacing the ~$40M full-max working-capital exposure. @Finance, the floor is yours. 3. **Trigger validation** — Sales and Operations have 48 hours to ratify the threshold numbers (WOS 7/11, conversion 65%, sell-through 85%) with Finance in the room, or override them. @Sales and @Operations — signable package on your end pending the above. Holding the room until the three items land.